Bug #64


VLAN interface choices in 2.0 (creating, assigning)

Added by Jim Pingle over 12 years ago. Updated almost 12 years ago.

Web Interface
Target version:
Start date:
Due date:
% Done:


Estimated time:
Plus Target Version:
Release Notes:
Affected Version:
Affected Architecture:


While fixing some other issues I noticed that when you attempt to create additional VLANs, the VLAN interfaces are also offered as potential parents. Furthermore, when assigning interfaces the VLAN interfaces show up twice, once as usual ("VLAN 10 on em0") and then again as "em0_vlan10 (xx:...:xx)"

This seems to be a side effect of the VLAN interface naming changes, and they are being included since the interface name starts with a supported driver: "em0_vlan10" does start with "em".

It probably needs some extra checks to exclude interfaces from those places that have "vlan" in the actual interface name.


vlan-config-problem.png (6.09 KB) vlan-config-problem.png Jim Pingle, 09/09/2009 07:55 PM
vlan-assign-problem.png (4.22 KB) vlan-assign-problem.png Jim Pingle, 09/09/2009 07:55 PM
Actions #1

Updated by Ermal Luçi about 12 years ago

  • Status changed from New to Feedback

It should be fixed as of now.

Forgotten reference to the issue during commit.

Actions #2

Updated by Jim Pingle about 12 years ago

I did a sync on a 2.0 test box just now and I still see a VLAN interfaces in both of the places I mentioned, as new VLAN parent choices, and as interfaces to assign.

Now I only see one of the incorrect VLAN interface choices listed, but I have two defined. I think before they had both shown up but I'd have to revert and try it again to be sure. So it's a little better than it was before at least.

Actions #3

Updated by Ermal Luçi about 12 years ago

  • Status changed from New to Feedback
  • % Done changed from 0 to 100
This fixes it.
Seems netstat has problems with such long interface names.

Actions #4

Updated by Chris Buechler almost 12 years ago

  • Status changed from Feedback to Resolved

part of this is fixed, the remaining issue is covered in a ticket I opened today.


Also available in: Atom PDF