FreeBSD Bridging doesn't work on FreeBSD 11

Adam Vande More amvandemore at
Thu Sep 21 17:01:44 UTC 2017

On Thu, Sep 21, 2017 at 9:09 AM, Alexey Dokuchaev <danfe at> wrote:

> I don't have a precise answer to your question, but certain network
> features had been broken in FreeBSD 11+, including bridging [1] and
> LAGG [2].  You might want to try 10.4 for the time being as there's
> currently low interest in fixing those regressions, unfortunately.
> ./danfe

It is disingenuous to imply things are broken when they are not.  The first
link you sent isn't close to conclusive, and may have absolutely nothing to
do with a bridge per se.  You can also find the OP's more in-depth
description in the mailing list archives along with other relevant
information to your "broken" claim.  Many of us are using bridges without
issue.  For example:

bridge0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu
        description: vm-public
        ether 02:68:50:0c:f1:00
        inet netmask 0xffffff00 broadcast
        nd6 options=1<PERFORMNUD>
        groups: bridge
        id 00:00:00:00:00:00 priority 0 hellotime 2 fwddelay 15
        maxage 20 holdcnt 6 proto rstp maxaddr 2000 timeout 1200
        root id 00:00:00:00:00:00 priority 0 ifcost 0 port 0
        member: tap0 flags=143<LEARNING,DISCOVER,AUTOEDGE,AUTOPTP>
                ifmaxaddr 0 port 5 priority 128 path cost 2000000
        member: wlan0 flags=143<LEARNING,DISCOVER,AUTOEDGE,AUTOPTP>
                ifmaxaddr 0 port 3 priority 128 path cost 33333
# freebsd-version -ku

If things like bridge or lagg were actually broken in  some non-edge case,
hard to replicate way then it would receive its due attention.  If you've
got an edge case no one else can replicate, it's probably going to sit out
there awhile.


More information about the freebsd-questions mailing list