<br><br><div class="gmail_quote">On Wed, Apr 14, 2010 at 14:42, Isidor Zeuner <span dir="ltr"><<a href="mailto:chilli@quidecco.de">chilli@quidecco.de</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
Hi Jason,<br>
<div class="im"><br>
><br>
> Can anyone share configuration settings (or point me towards and article or<br>
> how-to), with regard to iptable rules, to ensure that port 80 traffic is<br>
> transparently routed through to squid? I'd need to ensure that port 80<br>
> traffic to the server itself is still available as the server runs apache<br>
> for teh charging portal.<br>
><br>
<br>
</div>The HS_POSTAUTH_PROXY and HS_POSTAUTH_PROXYPORT configuration settings<br>
are there to configure a transparent proxy to handle requests after<br>
the user is authenticated. This is handled through chilli, not<br>
iptables, and does not prevent you from still running a web server.<br>
<br>
Best regards,<br>
<br>
Isidor<br></blockquote></div><br>For the information of other (potential) users, I have not been able to get this successfully work with the Squid proxy on the same server as chilli (ie. HS_POSTAUTH_PROXY = 127.0.0.1). I have confirmed, via lynx, that squid works fine for localhost/<a href="http://127.0.0.1">127.0.0.1</a> connections, but it does not work through chilli for chilli authenticated clients.<br>
<br>Debug logs showed redirection to squid, but according to squid logs it (squid) was not receiving the request.<br><br>Unfortunately, I'm not development minded enough to know what the problem is or might be. If anyone has it working in this scenario, I would like to hear from you if your willing to provide some advice on your configuration.<br>
<br clear="all"><br>Thanks.<br><br>-- <br>Cheers,<br>Jason<br>