Jason Haar-2 wrote > On 15/04/15 22:58, Amos Jeffries wrote: >> Squid has zero control over what TCP connections the *client* opens. >> You need to use tcpdump on the Squid machine, or machine(s) at the >> other end of the WAN1/2 connections to see what the Squid->origin >> traffic uses. > > Amos is so right. Stop fiddling around with tools like traceroute whose > behaviour *might* mimic that which squid is doing and instead use > tcpdump to actually *see* what squid is doing. Anyone running network > services has got to become proficient in the use of network sniffers - > they are invaluable > > > Very True.. I need to learn using tcpdump now. > > -- > Cheers > > Jason Haar > Corporate Information Security Manager, Trimble Navigation Ltd. > Phone: +1 408 481 8171 > PGP Fingerprint: 7A2E 0407 C9A6 CAF6 2B9F 8422 C063 5EBB FE1D 66D1 > > _______________________________________________ > squid-users mailing list > squid-users@.squid-cache > http://lists.squid-cache.org/listinfo/squid-users -- View this message in context: http://squid-web-proxy-cache.1019090.n4.nabble.com/squid-tcp-outgoing-address-feature-not-working-tp4670741p4670771.html Sent from the Squid - Users mailing list archive at Nabble.com. _______________________________________________ squid-users mailing list squid-users@xxxxxxxxxxxxxxxxxxxxx http://lists.squid-cache.org/listinfo/squid-users
