> On Aug 22, 2025, at 3:09 AM, Patrick M. Hausen <hau...@punkt.de> wrote:
>
> Hi all,
>
>> Am 08.08.2025 um 16:07 schrieb Patrick M. Hausen <hau...@punkt.de>:
>> someone hinted in the original pr that this might be due to the fact
>> that I am using USB ethernet which is brought up later than regular
>> NICs.
>>
>> I don't have much choice on an RPI CM3+, but I'll investigate in
>> that direction. If vxlan works in a VM with an em(4) NIC we can consider
>> this solved.
>
> With em0 instead of ue0 the vxlan interfaces come up as expected.
>
> Now one remaining question:
>
> Why not start USB network interfaces that are connected at boot time
> together with all regular interfaces? They don't come and go in my context,
> they are just connected via USB.
Well the rc.d scripts actually run late.
From rc.d/netif,
```
# Create IEEE802.11 interface
wlan_up $cmdifn
# Create cloned interfaces
clone_up $cmdifn
# Rename interfaces.
ifnet_rename $cmdifn
# Configure the interface(s).
netif_common ifn_start $cmdifn
```
The cloned interfaces are created first, then they, including the physical
interfaces, say em0 and ue0, are configured.
So I guess your config of em0 is before vxlan0, and ue0 is after vxlan0. You
may move ue0 before vxlan0 in rc.conf and give it another try.
Best regards,
Zhenlei
>
> Kind regards,
> Patrick
> --
> punkt.de GmbH
> Patrick M. Hausen
> .infrastructure
>
> Sophienstr. 187
> 76185 Karlsruhe
>
> Tel. +49 721 9109500
>
> https://infrastructure.punkt.de
> i...@punkt.de
>
> AG Mannheim 108285
> Geschäftsführer: Daniel Lienert, Fabian Stein
>
