DragonFlyBSD

Hi, recently tried configuring a bridge/stp alongside freebsd host with bridge. Looks like DragonFly version has some bugs in it... Dunno whether they are serious one or not. From time to time it loses connectivity and falls back to "blocking". Much more frequently following situation occurs:

FreeBSD (net.link.bridge.log_stp=1):

Jan 9 22:08:45 limbo kernel: arp: 172.29.1.195 moved from b6:02:35:28:d0:b1 to d4:3d:7e:48:ab:9d on bridge0
Jan 9 22:28:41 limbo kernel: arp: 172.29.1.195 moved from b6:02:35:28:d0:b1 to d4:3d:7e:48:ab:9d on bridge0

DragonFly (net.link.bridge.debug=1):

Jan 9 22:07:36 probe kernel: ff:ff:ff:ff:ff:ff 02:3b:77:1f:48:00 type 0608 lla b6:02:35:28:d0:b1
Jan 9 22:07:36 probe kernel: 02:3b:77:1f:48:00 52:54:00:12:34:56 type 0608 lla b6:02:35:28:d0:b1
Jan 9 22:08:45 probe kernel: ff:ff:ff:ff:ff:ff 02:3b:77:1f:48:00 type 0608 lla b6:02:35:28:d0:b1
Jan 9 22:10:40 probe kernel: ff:ff:ff:ff:ff:ff 02:3b:77:1f:48:00 type 0608 lla b6:02:35:28:d0:b1
Jan 9 22:12:13 probe kernel: ff:ff:ff:ff:ff:ff 94:eb:cd:2d:05:5f type 0608 lla b6:02:35:28:d0:b1
Jan 9 22:12:13 probe kernel: ff:ff:ff:ff:ff:ff 94:eb:cd:2d:05:5f type 0608 lla b6:02:35:28:d0:b1
Jan 9 22:25:43 probe kernel: ff:ff:ff:ff:ff:ff 84:8e:df:11:d2:e2 type 0608 lla b6:02:35:28:d0:b1
Jan 9 22:25:44 probe kernel: ff:ff:ff:ff:ff:ff 84:8e:df:11:d2:e2 type 0608 lla b6:02:35:28:d0:b1
Jan 9 22:27:11 probe kernel: ff:ff:ff:ff:ff:ff 94:eb:cd:2d:05:5f type 0608 lla b6:02:35:28:d0:b1
Jan 9 22:27:11 probe kernel: ff:ff:ff:ff:ff:ff 94:eb:cd:2d:05:5f type 0608 lla b6:02:35:28:d0:b1
Jan 9 22:27:32 probe kernel: ff:ff:ff:ff:ff:ff 02:3b:77:1f:48:00 type 0608 lla b6:02:35:28:d0:b1
Jan 9 22:27:32 probe kernel: 02:3b:77:1f:48:00 52:54:00:12:34:56 type 0608 lla b6:02:35:28:d0:b1
Jan 9 22:28:41 probe kernel: ff:ff:ff:ff:ff:ff 02:3b:77:1f:48:00 type 0608 lla b6:02:35:28:d0:b1

re0: flags=8943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST> mtu 1500
options=19<RXCSUM,VLAN_MTU,VLAN_HWTAGGING>
inet6 fe80::d63d:7eff:fe48:ab9d%re0 prefixlen 64 scopeid 0x1
ether d4:3d:7e:48:ab:9d
media: Ethernet autoselect (1000baseT <full-duplex>)
status: active

bridge0: flags=8043<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet6 fe80::b402:35ff:fe28:d0b1%bridge0 prefixlen 64 scopeid 0x3
inet 172.29.1.195 netmask 0xffffff00 broadcast 172.29.1.255
ether b6:02:35:28:d0:b1
priority 32768 hellotime 2 fwddelay 15 maxage 20
member: tap0 flags=3<LEARNING,DISCOVER>
member: re0 flags=37<LEARNING,DISCOVER,STP,DESIGNATED,ROOT>
port 1 priority 128 pathcost 55 forwarding
bondweight 1
designated root: 8000b6023528d0b1
designated bridge: 8000b6023528d0b1
designated cost: 54
designated port: 0

There's no hints on how bridge should be set up also. The recipe that works for me flawlessly is:

1. Clone one bridge interface:
cloned_interfaces=bridge0

1. Bring child interfaces up:
ifconfig_re0=up

2. Set up inet on the bridge in first configuration directive:
ifconfig_bridge0=DHCP
or:
ifconfig_bridge0='inet 172.29.1.100/24'

3. Add other interfaces:
ifconfig_bridge0_alias0='addm re0 stp re0'

Just to pinpoint - FreeBSD guide page is fine about bridges except that DHCP will not work in aliases.