On 10/16/2012 10:30 AM, [email protected] wrote: > Thanks, but I have tried that, adding -c and monitoring constantly. > netstat is blind to these, as it showed nothing even as Shorewall > blocked more. I suspect netstat monitors -source- port (which is > random), so I set Wireshark to listen for the particular IP, and it was > blind as well, when flurries of hits were blocked by Shorewall. > > > I can't believe this network traffic and sockets are invisible!
They won't be visible so long as you are blocking the traffic with the firewall. You have to temporarily unblock it to be able to track it. Do you run Squid on your firewall? -Tom -- Tom Eastep \ When I die, I want to go like my Grandfather who Shoreline, \ died peacefully in his sleep. Not screaming like Washington, USA \ all of the passengers in his car http://shorewall.net \________________________________________________ ------------------------------------------------------------------------------ Don't let slow site performance ruin your business. Deploy New Relic APM Deploy New Relic app performance management and know exactly what is happening inside your Ruby, Python, PHP, Java, and .NET app Try New Relic at no cost today and get our sweet Data Nerd shirt too! http://p.sf.net/sfu/newrelic-dev2dev _______________________________________________ Shorewall-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/shorewall-users
