Changing VLAN tag messes up interface assignments

  • Looks like a bug to me. Replicates every time with clean install with single NIC (not necessary but that's what I've done).

    1. Create 4 vlans

    2. Create 4 interfaces and hit save

    3. Go to VLANs tab and edit first entry VLAN tag to 110

    4. Go to Interface assignments and see the effect

    What I expected to happen - LAN interface get assigned to VLAN 11 and OPT3 remains  assigned to VLAN 14.
    What actually happens      - LAN interface gets assigned to em0      and OPT3 becomes assigned to VLAN 110.

    Similar issue happens when changing any other VLAN entry except for the last one. Changing last VLAN entry changes interface assignment correctly.

  • Rebel Alliance Developer Netgate

    Add new tag, switch assignments, remove old tag.

    What you're seeing is the expected behavior, since changing the tag changes the physical interface name.

    The input validation should probably reject a tag change if the interface is assigned, though.

  • I pushed a change for this in master.

  • Hi jimp,

    Thanks for the workaround. Fair play when it comes to LAN interface. But why OPT3 assignment has changed as well?

    Hi ermal,

    Thanks for that. Will the change be effective in a new snapshot?

  • For what it's worth I have seen this behavior too and reported on it. Too lazy to look for the post to link to it. What I do for a work around is verify the interfaces are assigned to the correct vlan before applying the change. I have also seen this behavior when adding  a new vlan to an existing interface. Glad to see some movement on this one.

Log in to reply