NetBSD Problem Report #37429

From martin@duskware.de  Sun Nov 25 10:07:09 2007
Return-Path: <martin@duskware.de>
Received: from mail.netbsd.org (mail.netbsd.org [204.152.190.11])
	by narn.NetBSD.org (Postfix) with ESMTP id 6803B63B88C
	for <gnats-bugs@gnats.netbsd.org>; Sun, 25 Nov 2007 10:07:09 +0000 (UTC)
Message-Id: <20071125062831.C171B63B88C@narn.NetBSD.org>
Date: Sun, 25 Nov 2007 06:28:31 +0000 (UTC)
From: mcs@darkregion.net
Reply-To: mcs@darkregion.net
To: netbsd-bugs-owner@NetBSD.org
Subject: More than one network restart with ifconfig.if and INET6 doesn't act right.
X-Send-Pr-Version: www-1.0

>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
>Last-Modified:  Wed Nov 19 21:55:01 +0000 2008
>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.

>Audit-Trail:
From: David Young <dyoung@pobox.com>
To: mcs@darkregion.net, gnats-bugs@NetBSD.org
Cc: gnats-admin@NetBSD.org, netbsd-bugs@NetBSD.org
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 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      Urbana, IL * (217) 278-3933 ext 24

Home	PR Database Search