>Number:         9518
>Category:       bin
>Synopsis:       ipnat fails under NetBSD 1.4T
>Confidential:   no
>Severity:       critical
>Priority:       high
>Responsible:    bin-bug-people (Utility Bug People)
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Wed Mar  1 12:24:01 2000
>Last-Modified:
>Originator:     Mason Loring Bliss
>Organization:
   Mason Loring Bliss   mason@acheron.middleboro.ma.us              E w i g e
awake ? sleep : dream;  http://acheron.ne.mediaone.net  B l u m e n k r a f t
>Release:        2000.02.29
>Environment:
	
System: NetBSD acheron.middleboro.ma.us 1.4T NetBSD 1.4T (MLB) #4: Wed Mar 1 00:11:10 EST 2000 root@acheron.middleboro.ma.us:/usr/src/sys/arch/i386/compile/MLB i386


>Description:

Between February 16th and February 29th, something changed which causes ipnat
to fail. It may be related to whatever it is that causes ifconfig to display
incorrect settings on (at least) some cards.

For instance:

ne0: flags=8863<UP,BROADCAST,NOTRAILERS,RUNNING,SIMPLEX,MULTICAST> mtu 1500
        address: 00:40:05:6a:5e:fe
        media: Ethernet autoselect (10baseT)
        inet 0.0.0.0 netmask 0xff000000 broadcast 255.255.255.255

This interface is, in fact, configured differently. Each item on the third
line is shown incorrectly. This is how the interface is set after being
configured by a dhcp server.

>How-To-Repeat:

Build -current, try to use ipnat.

>Fix:

Unknown as yet.

>Audit-Trail:
>Unformatted: