> Run tcpdump on local interface. ...on operating systems where the loopback interface supports packet capture.
It does so on Linux, where the loopback interface is named just "lo": > tcpdump -i lo and it does so on the BSDs, where it's named "lo0", and it does so on Digital UNIX (if you've configured the interface to allow packet capture), where it's named "lo0", but it does not do so on, for example, Solaris (where it's named "lo0", but you can't open it with tcpdump). On machines where you can't capture on the loopback interface, you might not be able to capture traffic between applications running on the same machine. (On a Solaris 2.6 machine here, for example, if I try to ping the machine from itself, while sniffing on the interface with the IP address that I'm pinging, I don't see the pings.) - This is the TCPDUMP workers list. It is archived at http://www.tcpdump.org/lists/workers/index.html To unsubscribe use mailto:[EMAIL PROTECTED]?body=unsubscribe
