Re: Static vxlan configuration fails - probably because of wrong order in rc

From: John Baldwin <jhb_at_FreeBSD.org>
Date: Fri, 22 Aug 2025 19:02:13 UTC
On 8/22/25 14:35, Patrick M. Hausen wrote:
> Hi,
> 
>> Am 22.08.2025 um 19:52 schrieb Zhenlei Huang <zlei@freebsd.org>:
>>> root@pi7:~ # uname -a
>>> FreeBSD pi7.ettlingen.hausen.com 14.3-RELEASE FreeBSD 14.3-RELEASE releng/14.3-n271432-8c9ce319fef7 GENERIC arm64
>>
>> If that is not custom kernel, the arm64 GENERIC config includes std.broadcom which have smsc support [1].
>>
>> You can also verify that by
>>
>> ```
>> # kldstat -m smsc
>> ```
>> or
>> ```
>> # kldstat -v | grep smsc
>> ```
> 
> root@pi7:~ #  kldstat -m smsc
> kldstat: can't find module smsc: No such file or directory
> root@pi7:~ # kldstat -v | grep smsc
> 194 smsc/miibus
> 193 uhub/smsc
> 119 miibus/smscphy
> 
> Standard GENERIC kernel. So it's compiled in? Then why does loading it
> in /boot/loader.conf - which should not do anything but throw an error -
> change the order in which the interfaces are set up?

A verbose dmesg of the two cases would probably be helpful.

-- 
John Baldwin