Mike Lander wrote: > Yes this accurately reflects the network topology? > However I been testing squid through this now and > the brower pauses an balks at times. So I tried > 10.194.79.181 in tcp outgoing in squid.conf > and browsing was fine. When I changed tcp > outgoing to 66.224.62.120, the trouble started > again. You would of thought I would have been > the lan gateway causing trouble. any ideas?
Wireshark is your friend.
Tom ,
Here is a tcpdump from eth1, I tryed
one from eth0. Because I have tcpoutgoing
in squid to 66.224.62.120. Squid should be
trying to go out eth0. But I could see no
evidence of traffice from 66.224.62.120
sniffing eth0. So this is a binary dump
of eth1 lan with host 10.194.79.199
trying to browse web pages through
squid.
PS the dump is binary
Mike
bindump.gz
Description: GNU Zip compressed data
------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________ Shorewall-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/shorewall-users
