Network Manager does not show VLANs

Bug #1637878 reported by Brandon Bell on 2016-10-30
28
This bug affects 6 people
Affects Status Importance Assigned to Milestone
plasma-nm (Ubuntu)
Undecided
Unassigned

Bug Description

In a fresh install of Ubuntu Yakkety, VLAN connection types are no longer offered as potential connections in the various GUI applets even after the parent Ethernet connection is established.

I've checked in KDE Plasma (plasma-nm 5.7.5-0ubuntu1), Gnome (1.2.4-0ubuntu2), and Cinnamon.

However, they are shown and usable via the command-line utility, nmcli. So I have to assume that the problem is in the libnm0 library in some sort of function that tests what connections should be available based upon what parent connection is established.

ProblemType: Bug
DistroRelease: Ubuntu 16.10
Package: libnm0 1.2.4-0ubuntu1
ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0
Uname: Linux 4.8.0-22-generic x86_64
ApportVersion: 2.20.3-0ubuntu8
Architecture: amd64
CurrentDesktop: KDE
Date: Sun Oct 30 15:59:13 2016
IfupdownConfig:
 # interfaces(5) file used by ifup(8) and ifdown(8)
 auto lo
 iface lo inet loopback
InstallationDate: Installed on 2016-01-31 (272 days ago)
InstallationMedia: Kubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
IpRoute:
 default via 10.10.10.1 dev wlp3s0 proto static metric 600
 10.10.10.0/24 dev wlp3s0 proto kernel scope link src 10.10.10.245 metric 600
 169.254.0.0/16 dev wlp3s0 scope link metric 1000
NetworkManager.state:
 [main]
 NetworkingEnabled=true
 WirelessEnabled=true
 WWANEnabled=true
 WimaxEnabled=true
SourcePackage: network-manager
UpgradeStatus: Upgraded to yakkety on 2016-10-16 (13 days ago)
nmcli-nm:
 RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN
 running 1.2.4 connected started full enabled enabled enabled enabled enabled

Brandon Bell (brandonbell) wrote :
Brandon Bell (brandonbell) wrote :

I should add that this issue occurs on the latest Ubuntu and Kubuntu 16.10 Live DVDs, so it shouldn't be hard to reproduce.

Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in network-manager (Ubuntu):
status: New → Confirmed
Alex Cucu (Work) (alexcucuwork) wrote :

Also having this issue in Xenial.

network-manager 1.2.2-0ubuntu0.16.04.3
libnm0 1.2.2-0ubuntu0.16.04.3
network-manager-gnome 1.2.0-0ubuntu0.16.04.4
libnm-gtk0 1.2.0-0ubuntu0.16.04.4

Brandon Bell (brandonbell) wrote :

Alex, were you able to use VLANs prior this issue?

I think I incorrectly attributed the problem to network-manager when it may simply be KDE Plasma's network manager applet. My stating that it affected Gnome and Cinnamon was based on my presumption that those environments had shown VLANs like Plasma did, but I'm not certain they ever did.

When I simply downgraded plasma-nm to version 5.5.5, I was able to see my VLANs again. Looking through that package's patches from there to 5.7.5, I saw the relevant changes that caused this issue but don't quite understand why those changes were made or if this symptom was intentional or not.

I haven't looked through the changelogs for Gnome's NM applet, but it could be the case that the same types of patches were applied there around the same timeframe.

Brandon Bell (brandonbell) wrote :

This problem has gotten even worse in Zesty. In addition to VLANs no longer being available in the Plasma Network Manager applet (plasma-nm), they are now no longer available in the connections editor either.

In Yakkety, I was at least able to open the connections editor and enable the VLAN connection from there. Now there is no option to do that nor is there an option to add a VLAN connection type.

I am now required to use the command-line (nmcli) to manage VLAN connections. This seems like a huge step backward.

no longer affects: network-manager (Ubuntu)
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in plasma-nm (Ubuntu):
status: New → Confirmed
Lars Scheiter (lscheiter) wrote :

Plasma-nm has VLAN Support but it is not visible by default.

You have to enable "Show and configure virtual connections" in Network settings (right click on plasma-nm icon in panel.

You now have the option to add a vlan interface as a "virtual connection" (Connections editor).

Working in 4:5.11.4+p16.04+git20171223.0044-0, but i guess its present in previous versions also.

Brandon Bell (brandonbell) wrote :

I confirmed it is resolved in 4:5.11.4-0ubuntu1 (available in the bionic testing release).

However, the "Network Settings" is not available in the right-click menu of version 4:5.10.5-0ubuntu1 which is the current version for artful.

So it looks like it will be released in the next version of Ubuntu (or possibly in a backport for artful).

Thank you for finding this, Lars!

dino99 (9d9) wrote :

This is an unsupported release now. Please think to install the next LTS 'Bionic 18.04'

http://cdimage.ubuntu.com/ubuntu-next/daily-live/current/
https://www.omgubuntu.co.uk/2018/02/ubuntu-18-04-minimal-install-option

Changed in plasma-nm (Ubuntu):
status: Confirmed → Invalid
Simon Quigley (tsimonq2) wrote :

Marking as Invalid because the release is EOL is not correct. Marking as Incomplete. Also, 18.04 is (at the time of writing) still in development, and you should expect some breakage.
https://wiki.ubuntu.com/Bugs/Responses#Release_has_reached_End_of_Life_.28EOL.29

Reporter, is this still present on 17.10 or 16.04?

Changed in plasma-nm (Ubuntu):
status: Invalid → Incomplete
Brandon Bell (brandonbell) wrote :

The issue is still present in 17.10.

The "Network settings..." right-click-menu item is not present and, thus, "virtual" connections like VLAN, Bridge, etc. cannot be seen, activated, or configured via GUI.

On a separate (but related) note: checking the "Show and configure virtual connections" option in the network settings dialog takes immediate effect for the Connections dialog but requires a restart of plasmashell before it takes effect for the plasmoid left-click popup. I consider this is a separate bug, though, and I'll file it against 18.04 since it seems to still be present there as well.

Launchpad Janitor (janitor) wrote :

[Expired for plasma-nm (Ubuntu) because there has been no activity for 60 days.]

Changed in plasma-nm (Ubuntu):
status: Incomplete → Expired
OIiver (euro-cent) wrote :

They removed VLAN support in KDE's network manager in KDE Plasma version 5.9.0

Read here:
https://www.kde.org/announcements/plasma-5.8.5-5.9.0-changelog.php

A developer thought that no one will be using VLAN configurations on a desktop machine, because he doesn't use it. Thus he removed that feature on 2017-01-06:

"Don't allow to create bond, bridge, vlan and team connections
These connection have never been properly tested and supported and they
are not used on desktop anyway. Since we already filter these out, there
is no reason to allow to create them."
https://cgit.kde.org/plasma-nm.git/commit/?id=aae4b7886bcf865d976e98910e24b13436521f8f

I suggest everyone under this bug report writes him an email and tell him, that he is wrong about his assumptions. Thus he has a reason to reimplement that feature again.
His email can be read in the commit message of that change.

Changed in plasma-nm (Ubuntu):
status: Expired → Confirmed
Brandon Bell (brandonbell) wrote :

I agree that s/he was wrong for assuming nobody used that feature, but the feature was returned in Plasma as of Ubuntu 18.04 and is still there in 18.10 (plasma-nm: 5.13.5-1ubuntu1).

If you're not seeing the virtual connections, then right-click on the network manager applet, select "Configure Networks" and then check the box for "Show and configure virtual connections."

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

Other bug subscribers