Did you notice this strange output with bridge and span on 15.0-RELEASE?

Emrion

Emrion

Hi,

I noticed that when you add a span interface to a bridge, ifconfig doesn't display the bridge members anymore.

Under 14.3-RELEASE:
Code: 
# ifconfig bridge0 create
# ifconfig bridge0 addm re0 span vr0
# ifconfig bridge0
bridge0: flags=1008843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST,LOWER_UP> metric 0 mtu 1500
    options=0
    ether 58:9c:fc:10:d2:2f
    id 00:00:00:00:00:00 priority 32768 hellotime 2 fwddelay 15
    maxage 20 holdcnt 6 proto rstp maxaddr 2000 timeout 1200
    root id 00:00:00:00:00:00 priority 32768 ifcost 0 port 0
    member: re0 flags=143<LEARNING,DISCOVER,AUTOEDGE,AUTOPTP>
            ifmaxaddr 0 port 1 priority 128 path cost 55
    member: vr0 flags=8<SPAN>
            ifmaxaddr 0 port 2 priority 128 path cost 55
    groups: bridge
    nd6 options=9<PERFORMNUD,IFDISABLED>
#

Under 15.0-RELEASE:
Code: 
# ifconfig bridge0 create
# ifconfig bridge0 addm re0
# ifconfig bridge0
bridge0: flags=1008843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST,LOWER_UP> metric 0 mtu 1500
    options=10<VLAN_HWTAGGING>
    ether 44:8a:5b:59:8b:35
    id 00:00:00:00:00:00 priority 32768 hellotime 2 fwddelay 15
    maxage 20 holdcnt 6 proto rstp maxaddr 2000 timeout 1200
    root id 00:00:00:00:00:00 priority 32768 ifcost 0 port 0
    bridge flags=0<>
    member: re0 flags=143<LEARNING,DISCOVER,AUTOEDGE,AUTOPTP>
            port 1 priority 128 path cost 55 vlan protocol 802.1q
    groups: bridge
    nd6 options=9<PERFORMNUD,IFDISABLED>
# ifconfig bridge0 span vr0
# ifconfig bridge0
bridge0: flags=1008843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST,LOWER_UP> metric 0 mtu 1500
    options=10<VLAN_HWTAGGING>
    ether 44:8a:5b:59:8b:35
    groups: bridge
    nd6 options=9<PERFORMNUD,IFDISABLED>
#

You can also see the strange bridge flags=0<> when there is just a normal member in the bridge.

Can anyone confirm this weird behaviour (as for me, it's a bug)?

Note: you can create some tap and use them if you don't want to touch the physical interfaces.
 
I'm disappointed that no one took the time to verify this problem. I guess that few people use span interfaces.

Anyway, I made a PR 292634 and wrote a patch for solving this issue. It's probably a very ancient (and more serious than I was thinking) bug. I see it just now because of the VLAN update on the FreeBSD network stack.
 
You must log in or register to reply here.
Back
Top