Feature #2386

Bridge member that is not an assigned interface

Added by Erik Fonnesbeck about 1 year ago. Updated about 1 year ago.

Status:New Start date:04/19/2012
Priority:Normal Due date:
Assignee:- % Done:

0%
Category:Interfaces
Target version:Future
Affected version: Affected Architecture:

Description

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).

interface-assignments.png - Screenshot of interface assignments. (91 kB) Ryan J, 04/25/2012 06:55 pm

bridges.png - Screenshot of bridge configurations. (84.1 kB) Ryan J, 04/25/2012 06:55 pm

rules.png - Screenshot of firewall rules. (92.2 kB) Ryan J, 04/25/2012 06:55 pm

system-tunables.png - Screenshot of system tunables. (208.3 kB) Ryan J, 04/25/2012 06:55 pm

History

#1 Updated by Ryan J about 1 year ago

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.

Also available in: Atom PDF