On Fri, 2008-10-10 at 21:59 +0200, Henrik Nordstrom wrote:
> If you have ip forwarding enabled then you can use iptables rules to
> select what traffic should really be sent to the proxy and what should
> be forwarded as-is, as a complement to the acls possible in the router.
Yep, I'm doing this o
On fre, 2008-10-10 at 14:55 +0200, Dalibor Dukic wrote:
> I didn't get this bypass interception? I have another SQUID box in this
> setup in same wccp web-cache group but with disabled ip forwarding. What
> exactly I'm loosing?
If you have ip forwarding enabled then you can use iptables rules to
Hi,
On Fri, 2008-10-10 at 02:41 +0200, Henrik Nordstrom wrote:
> It's not from Squid, these packets are from the client, and because the
> proxy server no longer knows about the connection the packet gets
> forwarded.
Thank You Henrik, it's so obvious right now.
> You can avoid this if you di
On fre, 2008-10-10 at 00:19 +0200, Dalibor Dukic wrote:
> I have transparent SQUID proxy with L2/L3 switch redirecting HTTP
> traffic to proxy through GRE tunnel. Yesterday, I've noticed that SQUID
> box is sending strange packets (TCP RST) to destination web server in
> order to terminate connect
> Hi,
>
> I have transparent SQUID proxy with L2/L3 switch redirecting HTTP
> traffic to proxy through GRE tunnel. Yesterday, I've noticed that SQUID
> box is sending strange packets (TCP RST) to destination web server in
> order to terminate connection. The problem is because these packets have
>
Hi,
I have transparent SQUID proxy with L2/L3 switch redirecting HTTP
traffic to proxy through GRE tunnel. Yesterday, I've noticed that SQUID
box is sending strange packets (TCP RST) to destination web server in
order to terminate connection. The problem is because these packets have
source addres
