On Wed, Jan 13, 2016 at 9:45 AM, Alexander V. Chernikov <melif...@ipfw.ru>

> I suspect the reason here is link state bridge handling.
> ix0 does not seem to have IFCAP_LINKSTATE option but re(4) does. Probably
> wlan0 doesn't have LINKSTATE option.
> Code in bridge_linkcheck() doesn't handle the case with both "has link
> state" and "no link state" interfaces well:
> if reX is the only interface w/ IFCAP_LINKSTATE and it goes down, bridge
> will also change its link state to down.
> (However, bridge does not seem to have link state option itself, so
> RT_LINK_IS_UP() macro should return true...)
​For validating your "IFCAP_LINKSTATE" hypothesis, I've plug an USB
ethernet adapter ue(4) that didn't support IFCAP_LINKSTATE.
And I've setup the bridge0 with wlan0 and ue0 (in place of re1): same bug
triggered. I need to ​plug a cable for correct routing.

​root@fbsd-router:~ # ifconfig bridge0
bridge0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu
        ether 02:6b:c0:de:b8:00
        inet netmask 0xffffff00 broadcast
        nd6 options=9<PERFORMNUD,IFDISABLED>
        groups: bridge
        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: ue0 flags=143<LEARNING,DISCOVER,AUTOEDGE,AUTOPTP>
                ifmaxaddr 0 port 7 priority 128 path cost 55
        member: wlan0 flags=143<LEARNING,DISCOVER,AUTOEDGE,AUTOPTP>
                ifmaxaddr 0 port 5 priority 128 path cost 33333
root@fbsd-router:~ # ifconfig ue0
mtu 1500
        ether 00:19:fd:4e:77:4d
        media: Ethernet autoselect (none)
        status: no carrier
freebsd-current@freebsd.org mailing list
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Reply via email to