[Bug 250749] /etc/network.subr: Mitigate absence of LINK_UP notification when VIRTIO_NET_F_STATUS is not negotiated

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

Johan Ström <johan@stromnet.se> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |johan@stromnet.se

--- Comment #2 from Johan Ström <johan@stromnet.se> ---
I think I might have the same issue with vlan interfaces on vtnet interface
(proxmox host with virtio interface), dhclient never starts at boot or later.

Relevant rc.conf:

vlans_vtnet0="vlan2 vlan10 vlan11 vlan12 vlan13 vlan14 vlan15 vlan16 vlan17
vlan18 vlan19 vlan40"
ifconfig_vtnet0="inet ......"

create_args_vlan12="vlan 12"
ifconfig_vlan12="up DHCP"


vlan12 is brought UP but dhclient is never launched at boot (or when trying
restarting netif).
Manually creating the device with "ifconfig vlan12 create vlan 12 vlandev
vtnet0" gives the following event in devd:

Pushing table                                                                  
setting *=!system=ETHERNET subsystem=vlan12 type=IFATTACH
setting _=system=ETHERNET subsystem=vlan12 type=IFATTACH
setting timestamp=1695243315.525712                                            
setting system=ETHERNET                                                        
setting subsystem=vlan12                                                       
setting type=IFATTACH                                                          
Processing notify event                                                        



The devd.conf has rule:
#
notify 0 {
   match "system"    "IFNET";
   match "type"      "LINK_UP";
   media-type     "ethernet";
   action "service dhclient quietstart $subsystem";
};


So, I added /etc/devd/vtnet-dhcp.conf:


notify 20 {
   match "system"    "ETHERNET";
   match "type"      "IFATTACH";
   match "subsystem"    "vlan.*";
   media-type     "ethernet";
   action "service dhclient quietstart $subsystem";
};


With this added, vtnet-based vlan with DHCP works as expected (on boot, on
netif restart)

-- 
You are receiving this mail because:
You are the assignee for the bug.