Date: Tue, 11 Nov 2003 15:14:23 +0300 (MSK) From: sp@alkor.ru To: FreeBSD-gnats-submit@FreeBSD.org Subject: kern/59172: Zebra interface route causes kernel panic for cloned interface Message-ID: <200311111214.hABCENGc017632@rvrng.alkor.ru> Resent-Message-ID: <200311111220.hABCKF2R019993@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
>Number: 59172 >Category: kern >Synopsis: Zebra interface route causes kernel panic for cloned interface >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 Nov 11 04:20:13 PST 2003 >Closed-Date: >Last-Modified: >Originator: >Release: FreeBSD 4.9-STABLE i386 >Organization: >Environment: System: FreeBSD rvrng.alkor.ru 4.9-STABLE FreeBSD 4.9-STABLE #4: Tue Nov 11 13:25:14 MSK 2003 sp@rvrng.alkor.ru:/usr/obj/usr/src/sys/GENERIC i386 >Description: If you are using zebra with interface route with cloned interface you can get kernel panic. Of course this is rare situation, but it indicates something wrong in kernel. >How-To-Repeat: /usr/local/etc/zebra/zebra.conf -------------------------------- ip route 0.0.0.0/0 your-gw ip route 192.0.2.1/25 vlan10 8 -------------------------------- # zebra is running, # interface vlan10 does not exists ifconfig vlan10 create ifconfig vlan10 192.0.2.129/30 vlan 123 vlandev your_ether_if The last command causes kernel panic current process is indicated as zebra. >Fix: Don't use interface route. >Release-Note: >Audit-Trail: >Unformatted:
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200311111214.hABCENGc017632>