Subject: kern/31964: frozen networking with tlp and trafshow
To: None <,,>
From: None <>
List: netbsd-bugs
Date: 11/01/2005 03:42:00
>Number:         31964
>Category:       kern
>Synopsis:       frozen networking with tlp and trafshow
>Confidential:   no
>Severity:       critical
>Priority:       high
>Responsible:    kern-bug-people
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Tue Nov 01 03:42:00 +0000 2005
>Release:        NetBSD 2.0.2
System: NetBSD 2.0.2 NetBSD 2.0.2 (GENERIC) #0: Wed Mar 23 08:53:42 UTC 2005 i386
Architecture: i386
Machine: i386
Started trafshow using libpcap-0.9.3nb3. When I exited my networking was
dead. When I restart trafshow my networking works again.

Or when I start tcpdump, my networking works again.

If I use "sudo trafshow -p" my networking does not come back up.

My network card:

tlp0 at pci0 dev 9 function 0: Lite-On 82C169 Ethernet, pass 2.0
tlp0: interrupting at irq 5
tlp0: Ethernet address 00:a0:cc:24:2d:40
ukphy0 at tlp0 phy 1: Generic IEEE 802.3u media interface
ukphy0: MTD972 10/100 media interface (OUI 0x00032d, model 0x0000), rev. 8
ukphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto

Taking interface down, delete and back "up" and also assign an IP
does not work to make my networking come alive again.

A "reboot" works to make the card work again.

When trafshow or tcpdump is running (and my networking is working):

 mtu 1500

and my networking works.

When trafshow (or tcpdump) is stopped (and my networking is down):


tcpdump says I have traffic out but nothing in.  tcpdump on another
machine shows traffic going both ways even when network appears to
be down.

netstat -ain output shows no change whether I am running tcpdump
or not:

Name  Mtu   Network       Address              Ipkts Ierrs    Opkts Oerrs 
tlp0  1500  <Link>        00:a0:cc:24:2d:40  1750619     0   638304     1  5512
tlp0  1500  fe80::/64     fe80::2a0:ccff:fe
                           ff02::1:ff24:2d40  1750619     0   638304     1 
tlp0  1500  192.168/24        1750619     0   638304     1  5512

(Greg Troxel gave me some more ideas for troubleshooting, but I
didn't try all yet.)

I recall I had same problem with same nic on another hardware
a few months ago.
Start and exit tcpdump or trafshow.