On 2008/03/05 12:02, Mike Tancsa wrote:
On FreeBSD, I created this simple userland script that resets the nic by
watching for its up/down events in syslog's kern.* facility. The proper
fix on FreeBSD is at
Ah, good idea. The OpenBSD kernel doesn't log interface events, but this
can be done
At 06:05 PM 2/26/2008, Jared D. McNeill wrote:
Stuart Henderson wrote:
I've seen some problems with the onboard NICs on net5501, where
if the device connected is unplugged and replugged, the interface
has link, is able to transmit packets, but is unable to receive
packets (nothing shown in
On Feb 26, 2008, at 18:05 , Jared D. McNeill wrote:
Stuart Henderson wrote:
I've seen some problems with the onboard NICs on net5501, where
if the device connected is unplugged and replugged, the interface
has link, is able to transmit packets, but is unable to receive
packets (nothing
I've seen some problems with the onboard NICs on net5501, where
if the device connected is unplugged and replugged, the interface
has link, is able to transmit packets, but is unable to receive
packets (nothing shown in tcpdump on the interface). Bringing
the interface down and back up fixes it.
At 12:52 PM 2/26/2008, Stuart Henderson wrote:
I've seen some problems with the onboard NICs on net5501, where
if the device connected is unplugged and replugged, the interface
has link, is able to transmit packets, but is unable to receive
packets (nothing shown in tcpdump on the interface).
Stuart Henderson wrote:
I've seen some problems with the onboard NICs on net5501, where
if the device connected is unplugged and replugged, the interface
has link, is able to transmit packets, but is unable to receive
packets (nothing shown in tcpdump on the interface). Bringing
the interface
