[Chilli] Squid transparent proxy on same server

[Jason Allen]

Thanks Isidor, this looks great.

How does it work? ( I could not find any further details on coova's website
or wiki). Does chilli auto redirect the post-auth user received packets to
the defined proxy server? Is it only port 80 destination traffic? Thus if
squid is installed on the same box as coova (and apache), then 127.0.0.1 and
3128 would be valid and correct entries?

I'm using Coova v1.2.1 and have set the config file proxy settings to
127.0.0.1 3128 but am not seeing any client activity in squid's access.log.
I know squid is working properly, because if I define the proxy in a client
browser then squid's access.log is recording the relevant entries.


Thanks.

On Wed, Apr 14, 2010 at 14:42, Isidor Zeuner <chilli at quidecco.de> wrote:

> Hi Jason,
>
> >
> > Can anyone share configuration settings (or point me towards and article
> or
> > how-to), with regard to iptable rules, to ensure that port 80 traffic is
> > transparently routed through to squid? I'd need to ensure that port 80
> > traffic to the server itself is still available as the server runs apache
> > for teh charging portal.
> >
>
> The HS_POSTAUTH_PROXY and HS_POSTAUTH_PROXYPORT configuration settings
> are there to configure a transparent proxy to handle requests after
> the user is authenticated. This is handled through chilli, not
> iptables, and does not prevent you from still running a web server.
>
> Best regards,
>
> Isidor
> _______________________________________________
> Chilli mailing list
> Chilli at coova.org
> http://lists.coova.org/cgi-bin/mailman/listinfo/chilli
>



-- 
Cheers,
Jason
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.coova.org/pipermail/chilli/attachments/20100415/70d446db/attachment.htm>