> On Apr 20, 2025, at 8:20 AM, pa...@paige.bio wrote: > > Hey I was kind of wondering for my own info, where would be a good place to > open a bug for this particular problem if not here? > I noticed something earlier which was upon specifying the tunneling parameter > for a vxlan interface, I didn’t see tunnelfib in the summary for the > interface after but it accepted the parameter. Maybe it’s not supposed to > show it in summary I seem to remember on openbsd that it would though (seems > like it should)
Just try to make it clear. The support for ioctl SIOCSTUNFIB ( ifconfig vxlan[N] tunnelfib x ) was added via commit https://cgit.freebsd.org/src/commit/?id=7f7a804ae077 <https://cgit.freebsd.org/src/commit/?id=7f7a804ae077> . The man page of ifconfig(8) was updated to reflect the change, but vxlan(4) was not. Well by default the tunnelfib of a vxlan(4) interface is 0 ( the system's default fib ) and is not displayed. If you set it to a fib number other than 0, ifconfig(8) will show that. ``` # ifconfig vxlan0 vxlan0: flags=1008802<BROADCAST,SIMPLEX,MULTICAST,LOWER_UP> metric 0 mtu 1470 options=80020<JUMBO_MTU,LINKSTATE> ether 58:9c:fc:00:7c:2c groups: vxlan media: Ethernet autoselect (autoselect <full-duplex>) status: active nd6 options=29<PERFORMNUD,IFDISABLED,AUTO_LINKLOCAL> # sysctl net.fibs=2 net.fibs: 1 -> 2 # ifconfig vxlan0 tunnelfib 1 # ifconfig vxlan0 vxlan0: flags=1008802<BROADCAST,SIMPLEX,MULTICAST,LOWER_UP> metric 0 mtu 1470 options=80020<JUMBO_MTU,LINKSTATE> ether 58:9c:fc:00:7c:2c groups: vxlan tunnelfib: 1 media: Ethernet autoselect (autoselect <full-duplex>) status: active nd6 options=29<PERFORMNUD,IFDISABLED,AUTO_LINKLOCAL> ``` > where would be a good place to open an inquiry about that? > > Thanks > > Sent from my iPhone > >> On Jan 24, 2025, at 8:11 AM, bugzilla-nore...@freebsd.org wrote: >> >> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=278028 >> >> Zhenlei Huang <z...@freebsd.org> changed: >> >> What |Removed |Added >> ---------------------------------------------------------------------------- >> Status|New |Closed >> Resolution|--- |Works As Intended >> >> --- Comment #14 from Zhenlei Huang <z...@freebsd.org> --- >> Given this is not the fault of if_vxlan(4) but is a configuration problem ( >> duplicated MAC address ), I'm closing this issue now. >> >> -- >> You are receiving this mail because: >> You are the assignee for the bug. Best regards, Zhenlei
