W dniu 18.05.2025 o 18:06, A FreeBSD User pisze:
Hello,
running recent CURRENT (FreeBSD 15.0-CURRENT #68 main-n277334-d9900b9ea2b2: Sun
May 18
16:51:02 CEST 2025), I ran into the following problem:
Can not add interfaces anymore to a bridge device.
Neither existing physical devices, nor epair devices created during setup of
jails - with the
result of no jails availabel and/or no bridge working.
A more amusing part of this story is: I ran almost two identical boxes, based
upon elderly
IvyBridge CPUs, both on outdated ASrock Z77 Pro mainboards. One machine, the
now-failing-one, has moved to AMD Ryzen 9700X based box based on ASrock B850
mainboard - just
for the record, if this is of importance or interest.
On both systems I use custom kernels, mostly disabling unused devices. Having
an ABI issue in
mind, I recompiled the whole world/kernel on the system with AMD CPU, but the
issue is the
still persistent.
A real hardware problem or just a coincidence with faulty code?
Thanks for helping,
O. Hartmann
Hello Oliver,
please follow this commit:
https://github.com/freebsd/freebsd-src/commit/b61850c4e6f6b0f21b36da7238db969d9090309e
and this thread:
https://lists.freebsd.org/archives/freebsd-current/2025-May/007602.html
TL;DR: set net.link.bridge.member_ifaddrs=1 (the earlier, the better,
loader.conf prefered) and before FreeBSD 16.0-RELEASE (still plenty of
time), either remove addresses the bridge members, or consider migration
to different bridge (Netmap ?!) or consider migration to different OS.
Cheers
Marek
