Bridge member that is not an assigned interface
|Affected version:||Affected Architecture:|
As suggested on #2385, a solution for bridge members showing up in unwanted places in the web GUI and the rule set would be to allow adding members that are not assigned interfaces. For this to work, something needs to be worked out for members that need some type of extra configuration (like wireless devices).
#1 Updated by Ryan J about 1 year ago
- File interface-assignments.png added
- File bridges.png added
- File rules.png added
- File system-tunables.png added
I'm adding screenshots of a configuration I use that would benefit from this. For firewall rules, the only interfaces I'm interested in are LAN0 and LAN1. I never add any rules to LINK0, LINK1, WIFI0, or WIFI1. Right now the only reasons to assign those interfaces are so they can participate as bridge members and so the wireless interfaces can be configured.