Date: Fri, 8 Aug 2025 22:29:54 +0800 From: Zhenlei Huang <zlei@FreeBSD.org> To: "Patrick M. Hausen" <hausen@punkt.de> Cc: "freebsd-net@freebsd.org" <freebsd-net@freebsd.org> Subject: Re: Static vxlan configuration fails - probably because of wrong order in rc Message-ID: <2D661596-51F1-4573-8C3F-59467245AC0F@FreeBSD.org> In-Reply-To: <5F0F9208-9F4B-401B-B7B8-BCF64737A97F@punkt.de> References: <D0196A32-4382-4EFB-A746-FA841787FA9A@punkt.de> <5F0F9208-9F4B-401B-B7B8-BCF64737A97F@punkt.de>
next in thread | previous in thread | raw e-mail | index | archive | help
> On Aug 8, 2025, at 10:07 PM, Patrick M. Hausen <hausen@punkt.de> wrote: > > Hi all, > >> Am 06.08.2025 um 23:22 schrieb Patrick M. Hausen <hausen@punkt.de>: >> >> Setups I tried which do not work: >> >> ------- >> cloned_interfaces="vxlan0" >> create_args_vxlan0="vxlanid 42 vxlanlocal 192.168.5.102 vxlangroup 224.0.2.6 vxlandev ue0" >> ifconfig_vxlan0_ipv6="inet6 fd37:dedf:2418::2/64 auto_linklocal" >> ------- >> [...] > > 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. > > Sorry about the noise. Thanks for your report. The bug should definitely be fixed. There're still some pending work on vxlan(4). To be optimism, the fix should be in 15.0-RELEASE ! Best regards, Zhenlei > > Kind regards, > Patrick
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?2D661596-51F1-4573-8C3F-59467245AC0F>