> PS: Is there a posibility to sniff packets which use the loopback
> interface only,
Assuming that "libpcap" on your particular version of your particular OS
allows snooping on the loopback interface (which worked on the Debian
Slink partition on my machine at home, as well as on the FreeBSD
partition, but, alas, doesn't work on Solaris 2.x at work or on the
Solaris 7 partition at home), it should Just Work - select the loopback
interface in the "Capture/Start" dialog box (which should show up in the
combo box for the interface iff
SIOCGIFCONF on your OS returns information about the loopback
interface;
it doesn't have a name that starts with "dummy" or includes a
":";
it's up;
"libpcap" lets you open it)
or, if it's not in the box, try typing its name in directly.
> because client and server are running on the same machine?
Note that this means "'real' network traffic going over the loopback
interface", not "UNIX-domain socket traffic", which is another type of
socket traffic going between processes on the same machine (e.g., X
traffic to ":0.0" normally uses a UNIX-domain socket).
