Subject: Re: kern/34517 (re(4) drops all traffic in promiscuous mode)
To: None <kern-bug-people@netbsd.org, gnats-admin@netbsd.org,>
From: Andreas Gustafsson <gson@gson.org>
List: netbsd-bugs
Date: 11/26/2006 20:25:02
The following reply was made to PR kern/34517; it has been noted by GNATS.
From: gson@gson.org (Andreas Gustafsson)
To: gnats-bugs@NetBSD.org
Cc:
Subject: Re: kern/34517 (re(4) drops all traffic in promiscuous mode)
Date: Sun, 26 Nov 2006 22:20:48 +0200
tsutsui@NetBSD.org wrote:
> State-Changed-From-To: open->feedback
> State-Changed-Why:
> Is there still this problem on -current? It works for me:
I tried a kernel built from yesterday's -current sources. It now
works better but still not well: packets are still dropped, but now
only for the first few seconds after tcpdump is started. After that,
traffic starts flowing again.
In my latest test, I started a tcpdump about two seconds after
starting a ping; note how packets 2 through 4 are missing from the
the ping output:
$ ping -n 10.0.1.254
PING 10.0.1.254 (10.0.1.254): 56 data bytes
64 bytes from 10.0.1.254: icmp_seq=0 ttl=255 time=3.215 ms
64 bytes from 10.0.1.254: icmp_seq=1 ttl=255 time=3.250 ms
64 bytes from 10.0.1.254: icmp_seq=5 ttl=255 time=3.245 ms
64 bytes from 10.0.1.254: icmp_seq=6 ttl=255 time=3.251 ms
64 bytes from 10.0.1.254: icmp_seq=7 ttl=255 time=3.272 ms
In the output from tcpdump itself, you see the requests but not
the responses:
$ sudo tcpdump -n -i re0
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on re0, link-type EN10MB (Ethernet), capture size 96 bytes
22:03:03.805794 IP 10.0.1.1 > 10.0.1.254: icmp 64: echo request seq 2
22:03:04.805817 IP 10.0.1.1 > 10.0.1.254: icmp 64: echo request seq 3
22:03:05.805805 IP 10.0.1.1 > 10.0.1.254: icmp 64: echo request seq 4
22:03:06.805818 IP 10.0.1.1 > 10.0.1.254: icmp 64: echo request seq 5
22:03:06.808886 IP 10.0.1.254 > 10.0.1.1: icmp 64: echo reply seq 5
22:03:07.805841 IP 10.0.1.1 > 10.0.1.254: icmp 64: echo request seq 6
22:03:07.808915 IP 10.0.1.254 > 10.0.1.1: icmp 64: echo reply seq 6
22:03:08.805851 IP 10.0.1.1 > 10.0.1.254: icmp 64: echo request seq 7
22:03:08.808945 IP 10.0.1.254 > 10.0.1.1: icmp 64: echo reply seq 7
Here's the output from "ifconfig re0":
$ ifconfig re0
re0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
capabilities=3f80<TSO4,IP4CSUM_Rx,IP4CSUM_Tx,TCP4CSUM_Rx,TCP4CSUM_Tx,UDP4CSUM_Rx,UDP4CSUM_Tx>
enabled=0
address: 00:50:fc:fe:81:9a
media: Ethernet autoselect (100baseTX full-duplex)
status: active
inet 10.0.1.1 netmask 0xffffff00 broadcast 10.0.1.255
inet6 fe80::250:fcff:fefe:819a%re0 prefixlen 64 scopeid 0x2
--
Andreas Gustafsson, gson@gson.org