Please add 802.1Q/VLAN tagging support to NetworkManager

Bug #353835 reported by Steven McCoy on 2009-04-02
This bug affects 14 people
Affects Status Importance Assigned to Milestone
network-manager (Ubuntu)
vlan (Debian)
vlan (Ubuntu)

Bug Description

Binary package hint: network-manager

I have eth0 as a static unconfigured interface and eth0.615 as a VLAN tagged interface in order to allow me to create virtual machines on different VLANs. I currently have to manually configure this and would like to use NetworkManager instead considering it has 802.1x now.

Ryan Anderson (ryan-ghruaim) wrote :

I use VLANs too, and had to remove network manager to get Pidgin to automatically connect. Firefox is only coming up online because you can tell it to ignore NM in about:config.

"Planned" in NM 0.9.X, or at least on some future roadmap. As such, I'm marking this Wishlist/Triaged

Changed in network-manager (Ubuntu):
status: New → Triaged
importance: Undecided → Wishlist
summary: - NetworkManager 0.7 lacks 802.1Q/VLAN tagging support
+ NetworkManager lacks 802.1Q/VLAN tagging support

I found this activity upstream:

which seems to be the basis for the claim that VLAN support has been added to NM. But this is only support for VLANs in RedHat and ilk.

Thomas Hood (jdthood) on 2012-07-26
summary: - NetworkManager lacks 802.1Q/VLAN tagging support
+ Pleas add 802.1Q/VLAN tagging support to NetworkManager
Thomas Hood (jdthood) on 2012-07-26
summary: - Pleas add 802.1Q/VLAN tagging support to NetworkManager
+ Please add 802.1Q/VLAN tagging support to NetworkManager

No, it's supported in NM regardless of the distro used; it's just not easy to configure; depends on the proper use of the config files. Closing as Fix Released.

To configure it you'll need to create a new connection manually in /etc/NetworkManager/system-connections; something like a file "VLAN615", with the following contents (uuid needs to be generated, which can be done with 'uuidgen -r'):





The available parameters for the [vlan] block are defined in source:

However, the actual names to use (as key=) for the parameters are the NM_SETTING_VLAN_* constants; which are defined here:

Changed in network-manager (Ubuntu):
status: Triaged → Fix Released
Changed in vlan (Ubuntu):
status: New → Invalid
Thomas Hood (jdthood) wrote :

OK, but where is this documented other than here? Can we reopen this as a wish for additional documentation of some sort?

Michael (auslands-kv) wrote :

Thanks to everybody. That helped a lot.

Now, is there any chance to get the VLAN connection up as soon as a cable is connected? This works fine for 802-3-ethernet connections, but apparently not for VLAN connections, right?

Unfortunately, nm-applet does not even show the connection at all. I hoped, one could at least activate or deactive the VLAN connection with nm-applet. Editing configuration would not have been necessary.

So, at the moment, am I right, that there is no other way than entering

nmcli con up id VLAN1

whenever I connect the cable?

Thanks again


Thomas Hood (jdthood) wrote :

Linked to a Debian bug report I just filed asking for a note to be added somewhere in the vlan package that vlan doesn't work with NetworkManager.

Changed in vlan (Debian):
status: Unknown → New

Thomas, it would be best to open a bug upstream for documentation for VLAN... and/or anyway file a new bug here for the documentation too rather than reusing old bugs.

Michael: I think all you need for this is that the top section ('[connection]') is set "autoconnect=true" or so. It does work properly here as soon as a cable is connected (though I didn't have to add autoconnect).

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.