Subject: Re: bin/29126: tcpdump leads to packet loss
To: None <email@example.com, firstname.lastname@example.org,>
From: Christos Zoulas <email@example.com>
Date: 01/26/2005 15:29:17
On Jan 26, 6:17pm, firstname.lastname@example.org (Manuel Bouyer) wrote:
-- Subject: Re: bin/29126: tcpdump leads to packet loss
| The following reply was made to PR kern/29126; it has been noted by GNATS.
| From: Manuel Bouyer <email@example.com>
| To: gnats-bugs@NetBSD.org
| Cc: gnats-admin@NetBSD.org, netbsd-bugs@NetBSD.org
| Subject: Re: bin/29126: tcpdump leads to packet loss
| Date: Wed, 26 Jan 2005 19:17:34 +0100
| On Wed, Jan 26, 2005 at 02:03:00PM +0000, firstname.lastname@example.org wrote:
| > Starting tcpdump with or without arguments leads to heavy packet loss, (like freezing all connections, up to 15 seconds) until the first packets are seen on the screen from the dump. During dump flow, no packet loss is detected, but same scenario happens if you stop tcpdump with CTRL-C. Again heavy packet loss. This can lead to break established connections (ssh for example). Maybe this is NIC related. I'm using an ex0 (3com 3c905 txm) Network Card. Verified on 2.99.10 and 2.99.15.
| This is because the driver reset the adapter when changing promiscous mode,
| which also has the effect of taking the link down (so media settings have to
| be renegotiated with the remote end. If you have spanning tree enabled,
| you're also hit by a spanning-tree cold restart). I don't know if, for
| this particular nic it's possible to enable/disable promiscous mode without
| resetting the adapter. Some drivers could possibly be smarter here, but
| it's definitively nic-dependant.
And you can set the spanning tree port to be 'smart', i.e. not to restart