Subject: port-i386/1426: ep driver sometimes sends packets out wrong media
To: None <gnats-bugs@gnats.netbsd.org>
From: John Hawkinson <jhawk@MIT.EDU>
List: netbsd-bugs
Date: 08/31/1995 03:36:06
>Number: 1426
>Category: port-i386
>Synopsis: ep driver sometimes sends packets out wrong media
>Confidential: no
>Severity: non-critical
>Priority: low
>Responsible: gnats-admin (GNATS administrator)
>State: open
>Class: sw-bug
>Submitter-Id: net
>Arrival-Date: Thu Aug 31 03:50:03 1995
>Last-Modified:
>Originator: John Hawkinson
>Organization:
MIT SIPB
>Release: $NetBSD: if_ep.c,v 1.81 1995/07/27 05:01:08 mycroft Exp $
>Environment:
System: NetBSD lola-granola 1.0A NetBSD 1.0A (LOLA) #99: Mon Aug 28 20:37:08 EDT 1995 ghudson@lola-granola:/afs/sipb.mit.edu/project/netbsd/dev/current-source/build/i386_nbsd1/sys/arch/i386/compile/LOLA i386
>Description:
On a 3c509 (ep) configured for UTP via it's install disk, with
flags set to -link0 -link1 -link2 (incorrect), at least one packet
will be sent and one packet received out the UTP interface, and then
no packets will be received or sent. Deleting the arp entry
with (route delete) and pinging again causes the problem to recurr.
This is particularly annoying in the case of an install script that
tries to ping a default router with all possible link[012] combinations,
since it produces false positives on the first try.
>How-To-Repeat:
>Fix:
Kludge around it by pinging twice, trying -link0 -link1 -link2
last, or some other boring incorrect method. Is this a hardware
bug?
>Audit-Trail:
>Unformatted:
>how-To-Repeat:
ifconfig ep0 inet 18.70.0.227
ping 18.70.0.1
(one packet received...)
ping 18.70.0.1
(no answer)
route delete 18.70.0.1
ping 18.70.0.1
(one packet received...)
ping 18.70.0.1
(no answer)
etc. etc.