Re: net.link.bridge.member_ifaddrs has landed in stable/14

I have compiled the latest 14-STABLE too and looked at my bridge configuration before changing this net.link.bridge.member_ifaddrs to 0.

After reboot my system did not respond on the IP4 bridge address and it turned out I had forgot "inet6 -auto_linklocal" on the member interface, which only had “up” before.

But now it is working fine.

Peter

> On 23 May 2025, at 15:43, Ronald Klop <[email protected]> wrote:
> 
> 
> Van: void <[email protected]>
> Datum:vrijdag, 23 mei 2025 15:20
> Aan:[email protected]
> CC:[email protected]
> Onderwerp:Re: net.link.bridge.member_ifaddrs has landed in stable/14
> 
> On Wed, May 21, 2025 at 05:04:50AM +0100, Lexi Winter wrote:
> >hello,
> >
> >i have just MFC'd the sysctl net.link.bridge.member_addrs to stable/14.
> >for detail see: https://cgit.freebsd.org/src/commit/?h=stable/14&id=ff1980d569c8167d38cda5f2713664866d9802bc
> >
> >in short, if you have a bridge with a lot of members (20+) and you do
> >not have any IP addresses assigned to those bridge members, you should
> >see a significant performance improvement from enabling this sysctl.
> >
> >please feel free to test this and report any problems.
> 
> Hi,
> 
> I'm not seeing that sysctl available yet, on a stable/14 system
> built a few hrs ago from sources updated today.
> 
> % uname -aKU
> FreeBSD desktop.home.arpa 14.3-STABLE FreeBSD 14.3-STABLE stable/14-n271551-4e0a5fd7b608 DESKTOP amd64 1403501 1403501
> 
> % sysctl net.link.bridge.member_addrs
> sysctl: unknown oid 'net.link.bridge.member_addrs'
> %
> -- 
>  
> 
> 
> I think there is a typo in the message. Try the sysctl name from the subject of the message.
> 
> Regards,
> Ronald.
>