Re: BPF does not pick up loopback activity

> Note that the packets sent to the local IP address are not picked up by > tcpdump. This can be tried with any traffic type, I have just used ping > as an example. > > Is this the correct/desired behaviour? If it is, is there any other way > to capture these packets? This is the expected beha

Re: BPF does not pick up loopback activity

*doh* of course... the loopback device! thanks Henry On Mon, 6 Aug 2001, [EMAIL PROTECTED] wrote: Hi, to see the packets to 192.168.2.1 you have to specify the interface lo0, because it's your own address. Packets to this address aren't send to fxp0. So use: tcpdump -ni

Re: BPF does not pick up loopback activity

Hi, to see the packets to 192.168.2.1 you have to specify the interface lo0, because it's your own address. Packets to this address aren't send to fxp0. So use: tcpdump -ni lo0 Martin > Take the following example: > # ifconfig fxp0 > fxp0: flags=8843 mtu 1500 > inet 192.168.2.1 netmas

BPF does not pick up loopback activity

Take the following example: # ifconfig fxp0 fxp0: flags=8843 mtu 1500 inet 192.168.2.1 netmask 0xff00 broadcast 192.168.2.255 ether 00:90:27:94:84:34 media: Ethernet autoselect (100baseTX ) status: active # tcpdump -ni fxp0 & # ping 192.168.2.1 PING 192.168.2.1