Opened 6 years ago

Last modified 6 years ago

#10884 new defect

LuCI VLAN handling encourages bricking config

Reported by: jb-debbugs@… Owned by: developers
Priority: lowest Milestone: Netifd Implementation
Component: base system Version: Trunk
Keywords: Cc:


As mentioned in , adding the base interface of an interface also used with VLANs to a bridge causes traffic to those VLANs to be swallowed by the bridge. As VLANs are mostly used on the LAN side, this will often result in a semi-bricked router.

Unfortunately, the current LuCI UI for adding interfaces to a bridge tends to encourage this by presenting the possible interfaces as a list of checkboxes with both the base interface (such as "eth0") and its VLAN tagged subinterfaces (such as "eth0.1") next to each other and no warning or error if both are checked.

As a short term solution, I suggest changing this so having an untagged interface as part of a bridge is not allowed if any of the logical networks (zones?) include tagged variants of the same interface.

Longer term the best solution would be for the kernel to confine the bridging of an untagged interface to untagged frames from/to that interface (if any other kernel config refers to VLANs on that interface), effectively treating "untagged frame" as another VLAN (e.g. VLAN 0 or VLAN -1).

But kernel bugs are not an OpenWRT issue, so the LuCI change would be way to go at this time.

Attachments (0)

Change History (1)

comment:1 Changed 6 years ago by jow

  • Component changed from luci to base system
  • Milestone changed from Backfire 10.03.2 to Netifd Implementation
  • Owner set to developers
  • Priority changed from normal to lowest

Add Comment

Modify Ticket

as new .

E-mail address and user name can be saved in the Preferences.

Note: See TracTickets for help on using tickets.