Date: Tue, 26 Aug 2025 14:02:05 -0400 From: John Baldwin <jhb@FreeBSD.org> To: "Patrick M. Hausen" <hausen@punkt.de> Cc: Zhenlei Huang <zlei@freebsd.org>, =?UTF-8?Q?Dag-Erling_Sm=C3=B8rgrav?= <des@FreeBSD.org>, "freebsd-net@freebsd.org" <freebsd-net@freebsd.org> Subject: Re: Static vxlan configuration fails - probably because of wrong order in rc Message-ID: <c51b55c3-c634-4d29-9350-2748584d5418@FreeBSD.org> In-Reply-To: <991B637F-2C2B-4387-BE5B-909120E158B1@punkt.de> References: <D0196A32-4382-4EFB-A746-FA841787FA9A@punkt.de> <5F0F9208-9F4B-401B-B7B8-BCF64737A97F@punkt.de> <A4CFF5AE-36E5-43E9-88D1-E0B02F2FF475@punkt.de> <7000BD16-48A8-4D4A-A5F9-843F9F15F1FB@FreeBSD.org> <F918B38C-84D4-46DC-A39C-031CFF3EC044@punkt.de> <86y0rbiyln.fsf@ltc.des.dev> <738B8306-03E4-464A-B55A-66F635A2B5D3@FreeBSD.org> <44753230-F684-439D-B633-3CFFB99905C1@punkt.de> <864itzxrmr.fsf@ltc.des.dev> <AE63A2C4-C543-4B1B-8421-40D093FA9747@punkt.de> <A007B8A0-0F14-440F-9B90-E6FF02576DA7@FreeBSD.org> <75885C39-68D7-437E-9ECB-581E59AADC61@punkt.de> <701d0ee9-b532-4bd4-9ff5-7e485eef9447@FreeBSD.org> <991B637F-2C2B-4387-BE5B-909120E158B1@punkt.de>
next in thread | previous in thread | raw e-mail | index | archive | help
On 8/22/25 17:30, Patrick M. Hausen wrote: > Hi, > >> Am 22.08.2025 um 21:02 schrieb John Baldwin <jhb@FreeBSD.org>: >> >> A verbose dmesg of the two cases would probably be helpful. > > I set verbose_loading="YES", then booted two times, once without, once > with if_smsc_load="YES". > > -------- > $ diff dmesg-not-loaded.txt dmesg-loaded.txt > 10a11 >> module smsc already present! > 12c13 > < avail memory = 945016832 (901 MB) > --- >> avail memory = 944844800 (901 MB) > 178a180 >> vxlan0: Ethernet address: 58:9c:fc:00:82:82 > 182d183 > < vxlan0: Ethernet address: 58:9c:fc:00:82:82 > -------- That's not the full dmesg, just a diff. That said, USB devices are probed asynchronously in parallel with the early userland startup. If the USB ethernet device isn't attached by the time /etc/rc.d/netif runs, the the vxlan device is probably just not configured. (You haven't included `ifconfig` output in any of your e-mails, so I have to guess at what the status of vlxan0 might be in the non-working case.) The way wlanX and vlan devices are handled is that they are not "regular" clone devices, but instead are tied to a parent interface (e.g. wlans_foo0="wlanX" or vlans_foo0="foo0.123"). This means that `/etc/rc.d/netif/start foo0` (invoked by devd when a hot plug NIC such as USB is attached) is able to create those pseudo interfaces anytime a foo0 device arrives. This is what the last comment in your bug is referring to (in essence). You could create a custom config file for devd that brings the vlxan interface up when ue0 arrives as a local fix. A more general fix would be to add support for a 'vxlans_<IF>' variable similar to `vlans_<IF>' which would be a list of child vxlan interfaces. You would then just need `vxlans_ue0="vxlan0"` instead of cloned_interfaces="vxlan0" in rc.conf. -- John Baldwin
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?c51b55c3-c634-4d29-9350-2748584d5418>