Re: bin/37429: More than one network restart with ifconfig.if and INET6 doesn't act right.

[David Young <dyoung%pobox.com@localhost>]

The following reply was made to PR bin/37429; it has been noted by GNATS.

From: David Young <dyoung%pobox.com@localhost>
To: mcs%darkregion.net@localhost, gnats-bugs%NetBSD.org@localhost
Cc: gnats-admin%NetBSD.org@localhost, netbsd-bugs%NetBSD.org@localhost
Subject: Re: bin/37429: More than one network restart with ifconfig.if and 
INET6 doesn't act right.
Date: Wed, 19 Nov 2008 15:53:26 -0600

 On Sun, Nov 25, 2007 at 10:10:00AM +0000, mcs%darkregion.net@localhost wrote:
 > >Number:         37429
 > >Category:       bin
 > >Synopsis:       More than one network restart with ifconfig.if and INET6 
 > >doesn't act right.
 > >Confidential:   no
 > >Severity:       non-critical
 > >Priority:       medium
 > >Responsible:    bin-bug-people
 > >State:          open
 > >Class:          sw-bug
 > >Submitter-Id:   net
 > >Arrival-Date:   Sun Nov 25 10:10:00 +0000 2007
 > >Originator:     Matthew C. Smith
 > >Release:        4.0_RC4
 > >Organization:
 > >Environment:
 > NetBSD lanv6.darkregion.net 4.0_RC4 NetBSD 4.0_RC4 (GENERIC) #0: Thu Nov  8 
 > 02:07:30 PST 2007  
 > builds@wb34:/home/builds/ab/netbsd-4-0-RC4/i386/200711080452Z-obj/home/builds/ab/netbsd-4-0-RC4/src/sys/arch/i386/compile/GENERIC
 >  i386
 > >Description:
 > If you have an inet6 address in an ifconfig.if(5) file and you run
 > 
 > /etc/rc.d/network restart
 > 
 > after the inet6 address has already been assigned to the interface (either 
 > manually via ifconfig or for the first time through ifconfig.if(5) and a 
 > network restart), the inet6 address fails to work as it did (for instance, 
 > you can't ping6 the inet6 address).
 > 
 > Also, I'm running this instance of NetBSD under a Ubuntu/VMWare host.
 > >How-To-Repeat:
 > Step 1:
 > echo inet6 fdc7:XXXX:XXXX:3::1/64 up > /etc/ifconfig.pcn0
 > /etc/rc.d/network restart
 > ping6 fdc7:XXXX:XXXX:3::1
 >   (works)
 > 
 > Step 2:
 > /etc/rc.d/network restart
 > ping6 fdc7:XXXX:XXXX:3::1
 >   (times out)
 > 
 > 
 > 
 > Note, step 1 can be replaced by removing the inet6 address (if assigned), 
 > and ifconfig'ing manually; the end result is the same: if you do a network 
 > restart with the address already assigned, the address will fail afterwards.
 > 
 > Note also, that ifconfig'ing manually two times in a row does *not* achieve 
 > the same effect as a network restart; the address continues to work.
 > >Fix:
 > As a work-around, you can remove the inet6 address and add it back (either 
 > manually or via a single network restart).  Just don't ab[use] network 
 > restart.
 
 This bug should be fixed in 5.0.  Will you try a 5.0 beta kernel and
 let us know?  Thanks!
 
 Dave
 
 -- 
 David Young             OJC Technologies
 dyoung%ojctech.com@localhost      Urbana, IL * (217) 278-3933 ext 24