amd64/188245: Critical vlan problem with OpenBGP
Marcelo Gondim
gondim at bsdinfo.com.br
Thu Apr 3 23:40:01 UTC 2014
>Number: 188245
>Category: amd64
>Synopsis: Critical vlan problem with OpenBGP
>Confidential: no
>Severity: non-critical
>Priority: low
>Responsible: freebsd-amd64
>State: open
>Quarter:
>Keywords:
>Date-Required:
>Class: sw-bug
>Submitter-Id: current-users
>Arrival-Date: Thu Apr 03 23:40:00 UTC 2014
>Closed-Date:
>Last-Modified:
>Originator: Marcelo Gondim
>Release: 10-STABLE
>Organization:
>Environment:
FreeBSD rt01.xxxxx.xxx.xx 10.0-STABLE FreeBSD 10.0-STABLE #5 r264032: Wed Apr 2 23:32:55 BRT 2014 root at rt01.xxxxx.xxx.xx:/usr/obj/usr/src/sys/INTNET10 amd64
>Description:
We have a router that connects 4 cities to the Internet using iBGP and eBGP. We are using OpenBGP for this function.
Each city reaches the router via VLANs created on the lagg interface:
# ifconfig lagg1
lagg1: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
options=4019b<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM,TSO4,VLAN_HWTSO>
ether 00:15:17:8c:81:d6
inet6 fe80::215:17ff:fe8c:81d6%lagg1 prefixlen 64 scopeid 0xd
nd6 options=21<PERFORMNUD,AUTO_LINKLOCAL>
media: Ethernet autoselect
status: active
laggproto lacp lagghash l2,l3,l4
laggport: em5 flags=1c<ACTIVE,COLLECTING,DISTRIBUTING>
laggport: em2 flags=1c<ACTIVE,COLLECTING,DISTRIBUTING>
# ifconfig vlan0
vlan0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
options=103<RXCSUM,TXCSUM,TSO4>
ether 00:15:17:8c:81:d6
inet 186.xxx.xx.1 netmask 0xffffffe0 broadcast 186.xxx.xx.31
inet6 fe80::215:17ff:fe8c:81d6%vlan0 prefixlen 64 scopeid 0xe
inet6 2804:xxxx:dead::1 prefixlen 64
nd6 options=21<PERFORMNUD,AUTO_LINKLOCAL>
media: Ethernet autoselect
status: active
vlan: 3081 parent interface: lagg1
# ifconfig vlan1
vlan1: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
options=103<RXCSUM,TXCSUM,TSO4>
ether 00:15:17:8c:81:d6
inet 177.xx.xxx.254 netmask 0xffffffe0 broadcast 177.xx.xxx.255
inet6 fe80::215:17ff:fe8c:81d6%vlan1 prefixlen 64 scopeid 0xf
inet6 2804:xxxx:cafe::1 prefixlen 64
nd6 options=21<PERFORMNUD,AUTO_LINKLOCAL>
media: Ethernet autoselect
status: active
vlan: 3082 parent interface: lagg1
# ifconfig vlan2
vlan2: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
options=103<RXCSUM,TXCSUM,TSO4>
ether 00:15:17:8c:81:d6
inet 186.xxx.xx.1 netmask 0xffffffe0 broadcast 186.xxx.xx.31
inet6 fe80::215:17ff:fe8c:81d6%vlan2 prefixlen 64 scopeid 0x10
inet6 2804:xxxx:cade::1 prefixlen 64
nd6 options=21<PERFORMNUD,AUTO_LINKLOCAL>
media: Ethernet autoselect
status: active
vlan: 2126 parent interface: lagg1
# ifconfig vlan3
vlan3: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
options=103<RXCSUM,TXCSUM,TSO4>
ether 00:15:17:8c:81:d6
inet 186.xxx.xx.1 netmask 0xffffffe0 broadcast 186.xxx.xx.31
inet6 fe80::215:17ff:fe8c:81d6%vlan3 prefixlen 64 scopeid 0x11
inet6 2804:xxxx:bad::1 prefixlen 64
nd6 options=21<PERFORMNUD,AUTO_LINKLOCAL>
media: Ethernet autoselect
status: active
vlan: 3088 parent interface: lagg1
So far everything works perfectly. But when I did:
# ifconfig vlan4 create
All my routing stopped, nor the killing bgpd process and restarting it did back operation. This did not happen in FreeBSD 9.2
The system only returned to work after the router rebooted.
This problem does not happen if I start the router with the settings of the new vlan on /etc/rc.conf
I see this as a serious problem for a router.
>How-To-Repeat:
With OpenBGP running, run the following command:
# ifconfig vlanX create
>Fix:
>Release-Note:
>Audit-Trail:
>Unformatted:
More information about the freebsd-amd64
mailing list