Re: [squid-users] Internet page accelerator and squid

On 1/31/06, Chris Robertson <crobertson@gci.com> wrote:
> > -----Original Message-----
> > From: Juan Chipoco [mailto:jchipoco@gmail.com]
> > Sent: Monday, January 30, 2006 2:16 PM
> > To: squid-users@squid-cache.org
> > Subject: [squid-users] Internet page accelerator and squid
> >
> >
> > Hi
> >
> > I'm trying to setup squid to be used as a Proxy Cache Server
> > for a group of
> > computers connected to Internet via a Satellite link.
> >
> > My provider is using Internet Page Accelerator(IPA) software, who runs
> > in all my peers. The first one is the RPA (Remote Page Accelerator),
> > this software runs on the remote side (port 9877) and works as a proxy
> > server to the client PCs, its main function is to ask the HPA (Hub
> > Page Accelerator, a software running at the HUB (port 9876)or ISP
> > provider) to download an specific Web Page and assemble all the pieces
> > , and send them all together in a few data streams in order to
> > optimize space bandwith use (minimizing the quantity of TCP
> > connections that must be opened for each HTTP object).
>
> Just to clarify, from your perspective the IPA is "near" (installed on all client machines), the RPA, HPA and internet are on the "far" side.
>

Hi Chris
Thats right.

> >
> > The RPA then receives this few streams and pass them to the client PC.
> > I had been trying to configure squid with following directives but it
> > seems that the requests from all my clients doesnt pass trought it.
> > In my clients browsers I activated the proxy with IP
> > 192.168.30.150 port 9877.
>
> So you have set the browsers to use the RPA as a proxy? That would go a long way to explain why Squid isn't seeing any traffic.
>

Of course , squid wont see any traffic because my browsers are
pointing to 9877 port. So I introduce cache_peer in my squid.conf in
order of considering the remote host as my cache parent.

> > In my squid I have:
> >
> > cache_peer 192.168.30.150 parent 9877 0 no-query default
> > acl src all 0.0.0.0/0.0.0.0
> > always_direct deny all
> > never_direct allow all
> >
> > Can you help me please?
>
> Unless the IPA and RPA talk HTTP between them, I fear you are going to be out of luck. You could try setting a browser up to use 192.168.1.1 port 3128 (assuming Squid is running on the default port) as proxy, and see what happens, but I wouldn't hold my breath.
>

I think that you are right :( all will depend if IPA and RPA can talk
HTTP protocol, but I posted this email because someone in this list
told that he got this configuration working fine...but didnt put a
complete explanation that how he got it :(
Your suggest works (setting my browser up to use 192.168.1.1:3128) but
I would like to take adventage of IPA.

> > Maybe i need an iptables rule in order tu redirect port 9877 to 3128?
>
> Even if you get this traffic to Squid, it might not understand the requests. Since you seem to have set proxy manually, don't start rerouting traffic with iptables now. It's all dependant on how the IPA and RPA communicate.
>

Thanks anyway ....I will read more about IPA in order to understand
how it communicate with RPA.

Thanks por your interest and time Chris

Juan Chipoco

> >
> > My network:
> >
> >
> > satellital
> > modem-------firewall/proxy-192.168.1.1-------hub-------network
> > 192.168.1.x
> >
> >
> > Thanks in advance.
> > Juan
> > --
> >
>
> Chris
>

--
Juan Chipoco Vidal
GNU/Linux Security Administrator
Cel: +(511) 9871-8095
Phone:+(511) 330-0786