Re: Static vxlan configuration fails - probably because of wrong order in rc
"Patrick M. Hausen" <[email protected]>
| Newsgroups | gmane.os.freebsd.devel.net |
|---|---|
| Message-ID | <[email protected]> |
Ho all, > Am 22.08.2025 um 05:54 schrieb Zhenlei Huang <[email protected]>: > 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. The order of variable assignments in rc.conf does not influence in which order things are run at startup ;-) I also browsed rc.d/netif and rc.subr but could not find if and why ue0 is actually configured later than, say, em0. I suspect the device node for ue0 simply does not exist before it is actually configured while the ones for "real" interfaces are always present. That would at least explain what we observe. Kind regards, Patrick -- punkt.de GmbH Patrick M. Hausen .infrastructure Sophienstr. 187 76185 Karlsruhe Tel. +49 721 9109500 https://infrastructure.punkt.de [email protected] AG Mannheim 108285 Geschäftsführer: Daniel Lienert, Fabian Stein