Skip site navigation (1)Skip section navigation (2) 
Date:      Wed, 20 Sep 2023 21:06:25 +0000
From:      bugzilla-noreply@freebsd.org
To:        bugs@FreeBSD.org
Subject:   [Bug 250749] /etc/network.subr: Mitigate absence of LINK_UP notification when VIRTIO_NET_F_STATUS is not negotiated
Message-ID:  <bug-250749-227-lzbWrk4VLG@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-250749-227@https.bugs.freebsd.org/bugzilla/>
References:  <bug-250749-227@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help 
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D250749

Johan Str=C3=B6m <johan@stromnet.se> changed:

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

--- Comment #2 from Johan Str=C3=B6m <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 late=
r.

Relevant rc.conf:

vlans_vtnet0=3D"vlan2 vlan10 vlan11 vlan12 vlan13 vlan14 vlan15 vlan16 vlan=
17
vlan18 vlan19 vlan40"
ifconfig_vtnet0=3D"inet ......"

create_args_vlan12=3D"vlan 12"
ifconfig_vlan12=3D"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=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=
=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=
=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20
setting *=3D!system=3DETHERNET subsystem=3Dvlan12 type=3DIFATTACH
setting _=3Dsystem=3DETHERNET subsystem=3Dvlan12 type=3DIFATTACH
setting timestamp=3D1695243315.525712=20=20=20=20=20=20=20=20=20=20=20=20=
=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=
=20=20=20=20=20=20=20
setting system=3DETHERNET=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=
=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=
=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20
setting subsystem=3Dvlan12=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=
=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=
=20=20=20=20=20=20=20=20=20=20=20=20=20=20
setting type=3DIFATTACH=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=
=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=
=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20
Processing notify event=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=
=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=
=20=20=20=20=20=20=20=20=20=20=20=20=20=20



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)

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

Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-250749-227-lzbWrk4VLG>