Page MenuHomeFreeBSD

15.0R/relnotes: Bridge, take three
Needs ReviewPublic

Authored by ziaee on Sep 5 2025, 4:17 PM.
Tags
None
Referenced Files
Unknown Object (File)
Wed, Oct 1, 5:01 PM
Unknown Object (File)
Sat, Sep 27, 7:55 PM
Unknown Object (File)
Wed, Sep 24, 2:50 AM
Unknown Object (File)
Wed, Sep 24, 1:07 AM
Unknown Object (File)
Mon, Sep 15, 11:17 AM
Unknown Object (File)
Sep 8 2025, 8:47 PM
Unknown Object (File)
Sep 6 2025, 10:01 PM
Unknown Object (File)
Sep 5 2025, 11:06 PM
Subscribers
None

Details

Reviewers
markj
ivy
kp
bofh
Group Reviewers
bridge
Summary

I'm not sure I really understand this. Ok, what about this?

Reported by: markj

Diff Detail

Repository
R9 FreeBSD doc repository
Lint
Lint Skipped
Unit
Tests Skipped
Build Status
Buildable 66844
Build 63727: arc lint + arc unit

Event Timeline

ziaee requested review of this revision.Sep 5 2025, 4:17 PM
ziaee created this revision.
website/content/en/releases/15.0R/relnotes.adoc
876

These sentences should probably be in the opposite order. I would further explain why it's a bad idea to have member interfaces with IP addresses assigned, but I don't know enough to write such an explanation myself. I would avoid announcing a timeline for removal of this support.

website/content/en/releases/15.0R/relnotes.adoc
876

the sysctl belongs to bridge(4), not ifconfig(8), i.e. this is checked in the kernel, ifconfig just reports the error.

regarding deprecation, bridge.4 currently says "This sysctl variable will be removed in FreeBSD 16.0" but at this point i expect this may be pushed to 17.0. i agree with not mentioning a specific release, just say it's deprecated and will be removed.

regarding wording of the reason why we don't like this: in general it's semantically incorrect to assign a layer 3 (IP) address to a layer 2 interface (bridge member). more specific, this doesn't work properly in FreeBSD and causes problems for users, e.g. https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=289295. if this isn't enough detail to write a release note, i can think about it more and try to come up with something, but the tl;dr is it doesn't work and we don't want to permit users to configure networking in a way that doesn't work.

is this still in flight? we need something for 15.0 since the current relnotes are wrong (they say this is disabled by default, which it's not since we backed off on that for now).

Oops, yeah I'll work on this today, we need this.