>Number:         4018
>Category:       port-i386
>Synopsis:       install-time network-config bug
>Confidential:   no
>Severity:       non-critical
>Priority:       medium
>Responsible:    gnats-admin (GNATS administrator)
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Tue Aug 19 21:50:02 1997
>Last-Modified:
>Originator:     Eric Mumpower
>Organization:
MIT
	
>Release:        1.2.1
>Environment:
	
System: NetBSD starry-night.cygnus.com 1.2.1 NetBSD 1.2.1 (INSTOTHER) #0: Sat Mar 22 21:07:16 PST 1997 perry@jekyll.piermont.com:/usr/src/sys/arch/i386/compile/INSTOTHER i386


>Description:
An install of NetBSD/i386 1.2.1 with a 3c509 using its UTP interface
will wrongly configure hostname.ep0 such that that interface is not
properly initialized at boot time, and necessitates hand-adjusting
hostname.ep0 to allow proper boottime configuration.
	
>How-To-Repeat:
Install NetBSD/i386 1.2.1; have an ethercard such as the 3c509 with UTP
interface, such that you will need to give both parameters "link0 link1"
when invoking ifconfig. During the install procedure (as per dot.instutils),
give the hostname and, IP address for the interface associated with this
ethernet card, and reply 'n'o, that the interface does not have a special
netmask. The ifconfig.ep0 which will be created will contain a line such as

inet starry-night.cygnus.com  link0 link1

which, upon the next proper system boot, will be misinterpreted by
/etc/netstart -- "link0" will be interpreted as the mask, and "link1" will
be interpreted as the bcaddr, resulting in the invocation of ifconfig as
  "ifconfig ep0 inet starry-night.cygnus.com netmask link0 broadcast link1"
... which is completely wrong.
	
>Fix:
 I'm not familiar enough with NetBSD to suggest any useful nonobvious
solution. I suspect the right thing is to fix the install script rather than
the netstart script, but I'm sure you knew that. :-)
	
>Audit-Trail:
>Unformatted: