Subject: kern/9468: ray0 interface fails to come up
To: None <gnats-bugs@gnats.netbsd.org>
From: Wolfgang Rupprecht <wolfgang@wsrcc.com>
List: netbsd-bugs
Date: 02/22/2000 16:27:42
>Number: 9468
>Category: kern
>Synopsis: ray0 interface fails to come up
>Confidential: no
>Severity: serious
>Priority: low
>Responsible: kern-bug-people (Kernel Bug People)
>State: open
>Class: sw-bug
>Submitter-Id: net
>Arrival-Date: Tue Feb 22 16:27:00 2000
>Last-Modified:
>Originator: Wolfgang Rupprecht
>Organization:
W S Rupprecht Computer Consulting, Fremont CA
>Release: -current 2/22/2000
>Environment:
System: NetBSD capsicum.wsrcc.com 1.4T NetBSD 1.4T (WSRCC) #1: Tue Feb 22 01:15:43 PST 2000 wolfgang@capsicum.wsrcc.com:/v/src/netbsd/NetBSD-current/usr/src/sys/arch/i386/compile/WSRCC i386
>Description:
ray0 interface fails to come up without repeated ifconfig up/down
toggles.
>How-To-Repeat:
put the following two lines in /etc/ifconfig.ray0
nwid my_network_name
inet 192.168.197.1 link0
After the ifconfig notice that the ray0 interface is still marked
as down.
It does eventually come up if one lays on the ^C key to
interrupt the boot process and one does an 'ifconfig ray0 up'
by hand. (At this point many of the network daemons have been
killed, so the system is mostly hosed.)
Observed on a sony-505tx
workaround: dhclient seems to cycle over the ifconfig enough
to shake things loose. It is only the static config that give
problems.
>Fix:
>Audit-Trail:
>Unformatted: