Re: packets redirected to loopback never appear in tcpdump

2009-02-25 Thread Gregory Edigarov
Stuart Henderson wrote: On 2009-02-24, Gregory Edigarov wrote: Is this a bug of feature? the test case: # ifconfig lo1 192.168.0.1 up # ping 192.168.0.1 64 bytes from 192.168.0.1: icmp_seq=0 ttl=255 time=0.200 ms 64 bytes from 192.168.0.1: icmp_seq=1 ttl=255 time=0.111 ms 64 bytes from 192

Re: packets redirected to loopback never appear in tcpdump

2009-02-24 Thread Stuart Henderson
On 2009-02-24, Gregory Edigarov wrote: > Is this a bug of feature? > the test case: > > # ifconfig lo1 192.168.0.1 up > > # ping 192.168.0.1 > 64 bytes from 192.168.0.1: icmp_seq=0 ttl=255 time=0.200 ms > 64 bytes from 192.168.0.1: icmp_seq=1 ttl=255 time=0.111 ms > 64 bytes from 192.168.0.1: icmp

Re: packets redirected to loopback never appear in tcpdump

2009-02-24 Thread Giovanni Bechis
Gregory Edigarov wrote: Hello, Is this a bug of feature? the test case: This works for me with 4.5-beta: $ sudo ifconfig lo1 192.168.3.1 Password: $ ping 192.168.3.1 PING 192.168.3.1 (192.168.3.1): 56 data bytes 64 bytes from 192.168.3.1: icmp_seq=0 ttl=255 time=0.036 ms 64 bytes from 192.168

packets redirected to loopback never appear in tcpdump

2009-02-24 Thread Gregory Edigarov
Hello, Is this a bug of feature? the test case: # ifconfig lo1 192.168.0.1 up # ping 192.168.0.1 64 bytes from 192.168.0.1: icmp_seq=0 ttl=255 time=0.200 ms 64 bytes from 192.168.0.1: icmp_seq=1 ttl=255 time=0.111 ms 64 bytes from 192.168.0.1: icmp_seq=2 ttl=255 time=0.110 ms 64 bytes from 192.1