Subject: kern/28974: IPv6 tunnel create/destroy panics kernel
To: None <kern-bug-people@netbsd.org, gnats-admin@netbsd.org,>
From: None <stealthnetworkviper@gmail.com>
List: netbsd-bugs
Date: 01/15/2005 13:30:00
>Number:         28974
>Category:       kern
>Synopsis:       IPv6 tunnel create/destroy panics kernel
>Confidential:   no
>Severity:       critical
>Priority:       high
>Responsible:    kern-bug-people
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Sat Jan 15 13:30:00 +0000 2005
>Originator:     Rene van Dijk
>Release:        NetBSD 2.0
>Organization:
>Environment:
NetBSD viper.stealth.lan 2.0 NetBSD 2.0 (VIPER) #0: Fri Jan 14 18:55:15 CET 2005  root@viper.stealth.lan:/usr/src/sys/arch/i386/compile/VIPER i386
>Description:
After adding IPv6 tunnels and then destroy then the kernel will panic write a coredump and reboot. The coredumps are too big to upload since it's from 50MB to 145MB. However the problem also occures on the GENERIC config and CVS updated kernel. The kernel will panic faster when it's done from a script. Creating sleep 1 in the script after each line will cause the kernel to evoid panic. However this isn't allways the case.
>How-To-Repeat:
#!/bin/sh
ifconfig gif0 create tunnel 192.168.4.1 192.168.7.2 up
ifconfig gif0 inet6 2001:c:: prefixlen 64
ifconfig gif1 create tunnel 192.168.4.1 192.168.7.4 up
ifconfig gif1 inet6 2001:c:a:: prefixlen 64
route add -inet6 default 2001:c::

#!/bin/sh
ifconfig gif0 destroy
ifconfig gif1 destroy
>Fix: