Project

General

Profile

Actions

Bug #1153

closed

Re-assignment of bridge interfaces should be restricted

Added by Chris Buechler almost 11 years ago. Updated over 8 years ago.

Status:
Resolved
Priority:
Low
Category:
Interfaces
Target version:
Start date:
01/02/2011
Due date:
% Done:

100%

Estimated time:
Plus Target Version:
Release Notes:
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.

Actions #1

Updated by Chris Buechler almost 11 years ago

  • Subject changed from Re-assignment of bridged interfaces should be restricted to Re-assignment of bridge interfaces should be restricted
Actions #2

Updated by Renato Botelho almost 9 years ago

  • Assignee set to Renato Botelho
  • Target version set to 2.1
Actions #3

Updated by Renato Botelho almost 9 years ago

  • Status changed from New to Feedback
  • % Done changed from 0 to 100
Actions #4

Updated by Chris Buechler over 8 years ago

  • Status changed from Feedback to Resolved
Actions

Also available in: Atom PDF