[Bug 289142] sysutils/vm-bhyve: public bridge fails on 15-CURRENT unless net.link.bridge.member_ifaddrs=1 is set

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=289142

--- Comment #4 from Henryk Paluch <hpaluch@seznam.cz> ---
(In reply to Henryk Paluch from comment #3)

Addendum: I was partially wrong: there is LINK_UP event (I was wrong) but not
"media-type" (I was right).

I verified following workaround:

My minimal bridge definition in /etc/rc.conf

ifconfig_vtnet2="up"
ifconfig_bridge2="DHCP addm vtnet2"
cloned_interfaces="bridge2"

My new devd configuration file /etc/devd/hpbridge.conf with contents:

# kludge to make DHCP works on bridge (it has no media-type)
#
notify 0 {
        match "system"          "IFNET";
        match "type"            "LINK_UP";
        match "subsystem"       "bridge2";
        action "service dhclient quietstart   $subsystem";
};


With this devd configuration DHCP client starts properly and bridge gets
assigned IP address:

$ ifconfig -u bridge2

bridge2: flags=1008843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST,LOWER_UP> metric
0 mtu 1500
        options=10<VLAN_HWTAGGING>
        ether 58:9c:fc:10:de:3b
        inet 192.168.123.218 netmask 0xffffff00 broadcast 192.168.123.255
        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: vtnet2 flags=143<LEARNING,DISCOVER,AUTOEDGE,AUTOPTP>
                port 3 priority 128 path cost 2000 vlan protocol 802.1q
        groups: bridge
        nd6 options=9<PERFORMNUD,IFDISABLED>

$ ps ax | grep 'dhclient: bridge' | fgrep -v grep

1838  -  Is    0:00.00 dhclient: bridge2 [priv] (dhclient)
1862  -  ICs   0:00.00 dhclient: bridge2 (dhclient)


So now the question is - how could we filter LINK_UP just for bridges - to have
dedicated rule for them?

-- 
You are receiving this mail because:
You are on the CC list for the bug.