Bug #1153
Re-assignment of bridge interfaces should be restricted
| Status: | Resolved | Start date: | 01/02/2011 | |
|---|---|---|---|---|
| Priority: | Low | Due date: | ||
| Assignee: |  Renato Botelho |
% Done: | 100% |
|
| Category: | Interfaces | |||
| Target version: | 2.1 | |||
| Affected version: | 2.0 | Affected Architecture: |
Description
It is possible to create an invalid config by reassigning an interface that is bridged. For example you can have LAN and WAN, and create bridge0 containing LAN and WAN, then go re-assign either WAN or LAN as bridge0, which then makes bridge0 one of the bridge member interfaces. Upon inadvertently doing this, the system froze up for me, not entirely unexpectedly. It did reboot fine after a power cycle, and if_bridge apparently ignored the request to add it to itself, as it only showed the one remaining physical interface as a member.
Need some additional input validation to prevent this type of obvious mistake, maybe just not allowing a bridge interface to be assigned to an interface which is bridged.
Associated revisions
Do not allow bridge members to be assigned to itself. Fixes #1153
History
#1
Updated by Chris Buechler over 2 years ago
- Subject changed from Re-assignment of bridged interfaces should be restricted to Re-assignment of bridge interfaces should be restricted
#2
Updated by Renato Botelho 4 months ago
- Assignee set to Renato Botelho
- Target version set to 2.1
#3
Updated by Renato Botelho 4 months ago
- Status changed from New to Feedback
- % Done changed from 0 to 100
Applied in changeset 95540233e3b9d8c4be5616065edcc6e1f2e2f972.
#4
Updated by Chris Buechler 4 months ago
- Status changed from Feedback to Resolved