misc/113842: enabling IPv6 post-boot didn't work: required reboot
George Michaelson
ggm at mirin.apnic.net
Tue Jun 19 03:40:02 UTC 2007
>Number: 113842
>Category: misc
>Synopsis: enabling IPv6 post-boot didn't work: required reboot
>Confidential: no
>Severity: serious
>Priority: medium
>Responsible: freebsd-bugs
>State: open
>Quarter:
>Keywords:
>Date-Required:
>Class: sw-bug
>Submitter-Id: current-users
>Arrival-Date: Tue Jun 19 03:40:01 GMT 2007
>Closed-Date:
>Last-Modified:
>Originator: George Michaelson
>Release: FreeBSD 7.0-CURRENT i386
>Organization:
>Environment:
System: FreeBSD mirin.apnic.net 7.0-CURRENT FreeBSD 7.0-CURRENT #5: Mon Jun 11 10:43:34 EST 2007 root at mirin.apnic.net:/usr/obj/usr/src/sys/ULURU i386
>Description:
I had to bring up a stateless autoconfig node, which previous
was V4 only. It had V6 in the kernel. I wanted to avoid reboot.
Although I added V6 enabler directives to /etc/rc.conf, running
the /etc/rc.d/ scripts did not seem to work. rtsol did not work,
yet across a reboot, I came back with V6. go figure.
so what IS the sequence which can re-initialize interfaces and
sysctl kernel state, to bring V6 live?
>How-To-Repeat:
boot V4 only machine. add V6 enablers to rc.conf. try and
bring it live runtime, without a static V6 assignment.
>Fix:
better documentation of a sequence of commands which DTRT with
the interfaces, without disrupting existing V4 state.
just because it works across reboot doesn't mean its not broken!
>Release-Note:
>Audit-Trail:
>Unformatted:
More information about the freebsd-bugs
mailing list