Actions
Feature #2386
open
Bridge member that is not an assigned interface
Status:
Pull Request Review
Priority:
Normal
Assignee:
Category:
Interfaces
Target version:
Start date:
04/19/2012
Due date:
% Done:
0%
Estimated time:
Plus Target Version:
Release Notes:
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).
Files
| interface-assignments.png (91 KB) interface-assignments.png | Screenshot of interface assignments. | ||
| bridges.png (84.1 KB) bridges.png | Screenshot of bridge configurations. | ||
| rules.png (92.2 KB) rules.png | Screenshot of firewall rules. | ||
| system-tunables.png (208 KB) system-tunables.png | Screenshot of system tunables. |
Updated by Ryan J almost 10 years ago
- File interface-assignments.png interface-assignments.png added
- File bridges.png bridges.png added
- File rules.png rules.png added
- File system-tunables.png 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.
Updated by Viktor Gurov about 1 year ago
Updated by Renato Botelho about 1 year ago
- Status changed from New to Pull Request Review
- Assignee set to Viktor Gurov
- Target version changed from Future to CE-Next
Actions