Michael Butler: > On 5/16/25 15:52, Lexi Winter wrote: > > i don't really want to add a kernel message here for something that only > > affects a small percentage of users, unlike net.add_addr_allfibs which > > affected everyone who uses multiple fibs.
> That "small percentage" includes most folk currently using jails and/or > bhyve (via sysutils/vm-bhyve). i am not sure about this. i admit i have not done a survey :-) however, i believe most people using jails or bhyve are not affected. the Handbook is clear about the correct way to configure this[0], so people who followed the handbook to configure their jails or bhyve VMs should not run into this problem. it is unfortunate that the same information was not in bridge(4) until recently. > If, as the bridge(4) man page suggests, the sysctl "goes away" in 16+, we'll > need some other mechanism to interconnect these. It cannot simply "go away" > without offering a solution. Any pointers? the solution is to configure the IP addresses on the bridge(4) interface rather than on the epair. [0]- for jails, <https://docs.freebsd.org/en/books/handbook/jails/#creating-vnet-jail>: > ifconfig_bridge0="inet 192.168.1.150/24 addm em0 up" for bhyve, <https://docs.freebsd.org/en/books/handbook/virtualization/#virtualization-host-bhyve>: > # sysrc ifconfig_bridge0="inet <ipaddr>/<netmask> addm igb0 addm tap0" for bridges in general, <https://docs.freebsd.org/en/books/handbook/advanced-networking/#network-bridging>: > If the bridge host needs an IP address, set it on the bridge > interface, not on the member interfaces.
signature.asc
Description: PGP signature
