[Bug 1519120] [NEW] Xenial: VLAN interfaces don't work until after a reboot

Launchpad Bug Tracker 1519120 at bugs.launchpad.net
Tue Jun 21 16:39:23 UTC 2016


You have been subscribed to a public bug by Wesley Wiedenmeier (wesley-wiedenmeier):

I tried to use the network manager UI to define a VLAN interface, and
nothing happened. There are a few bugs here:

(1) When creating a VLAN interface through the UI, the "vlan interface
name" must be filled in. This should just default to <interface-
name>.<vid>, rather than being a required field. (I typed in "vlan100"
to get the "Save" button to activate.)

(2) After creating my VLAN interface, nothing happened. No new interface
appeared. I then realized that I had not installed the "vlan" package,
and assumed that NetworkManager therefore could not complete
configuration of the interface.

(3) After installing the 'vlan' package (and then telling NetworkManager
to disconnect and reconnect my Ethernet interface from the UI, just for
good measure), still no VLAN interfaces were present on my system.

I also tried editing the VLAN interface in the UI, and specifying
"enp4s0f1.100", but still no VLAN interface came online.

# apt-cache policy network-manager
network-manager:
  Installed: 1.0.4-0ubuntu6
  Candidate: 1.0.4-0ubuntu6
  Version table:
 *** 1.0.4-0ubuntu6 0
        500 http://172.16.42.88/ubuntu/ xenial/main amd64 Packages
        100 /var/lib/dpkg/status

# apt-cache policy vlan
vlan:
  Installed: 1.9-3.2ubuntu1
  Candidate: 1.9-3.2ubuntu1
  Version table:
 *** 1.9-3.2ubuntu1 0
        500 http://172.16.42.88/ubuntu/ xenial/main amd64 Packages
        100 /var/lib/dpkg/status

** Affects: network-manager (Ubuntu)
     Importance: Undecided
         Status: Confirmed

** Affects: vlan (Ubuntu)
     Importance: High
     Assignee: Wesley Wiedenmeier (wesley-wiedenmeier)
         Status: Invalid


** Tags: patch server-next
-- 
Xenial: VLAN interfaces don't work until after a reboot
https://bugs.launchpad.net/bugs/1519120
You received this bug notification because you are a member of Ubuntu Sponsors Team, which is subscribed to the bug report.



More information about the Ubuntu-sponsors mailing list