Please, see below...
> Some bit of clarification here. "WCCP" is a protocol consisting of two
> packets HERE_I_AM and I_SEE_YOU. The HTTP traffic always goes via GRE
> protocol interface or layer-2 packet routing via Ethernet interface. The
> WCCP protocol configuratino in Squid and Cisco determi
On 5/01/2013 3:01 a.m., Roman Gelfand wrote:
So, the fortigate was configured based on the whitepaper you pointed
me to. The unencrypted http traffic works, but what I find is that
even though a request from the client arrives on squid via wccp, going
back it is routed via standard tcp/ip path.
So, the fortigate was configured based on the whitepaper you pointed
me to. The unencrypted http traffic works, but what I find is that
even though a request from the client arrives on squid via wccp, going
back it is routed via standard tcp/ip path. Is that how wccp
communication supposed to wo
Hey,
I have found this:
http://kb.fortinet.com/kb/viewContent.do?externalId=FD30096
which pretty much covers what needed to be done.
WCCP suppose to be a layer 2 interception which TPROXY is the closest
thing for that.
TPROXY use the same src IP of the client for outgoing traffic based on a
Based on what you configured you cisco router? what did you configured
on your cisco router?
What cisco device are you using?
did you had the chance to look at:
http://wiki.squid-cache.org/ConfigExamples/UbuntuTproxy4Wccp2
please try to share more information on the infrastructure and the whole
I use wccp/gre tunnel. Port 80
requests work but 443 don't. I am not sure if this is right, but even
though data was received on wccp, no data was transmitted back over
wccp. In other words, squid server response was routed back, through
eth0 interface, rather than go through wccp0 interface.
