This bug was fixed in the package vlan - 1.9-3ubuntu10.4
---
vlan (1.9-3ubuntu10.4) trusty; urgency=medium
* Don't trust ifup return code, as it returns 0 on failure; call ip link
set up after ifup to force vlan raw device up. (LP: #1573272)
-- Dan Streetman
This bug was fixed in the package vlan - 1.9-3.2ubuntu2.17.04.2
---
vlan (1.9-3.2ubuntu2.17.04.2) zesty; urgency=medium
* Correct previous patch, to work for ifupdown configuration where a
vlan is configured but the vlan's raw device has no ifupdown config.
(LP: #1573272)
This bug was fixed in the package vlan - 1.9-3.2ubuntu4
---
vlan (1.9-3.2ubuntu4) artful; urgency=medium
* Correct previous patch, to work for ifupdown configuration where a
vlan is configured but the vlan's raw device has no ifupdown config.
(LP: #1573272)
-- Dan
** Changed in: vlan (Ubuntu Artful)
Status: Fix Released => New
--
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1573272
Title:
This bug was fixed in the package vlan - 1.9-3.2ubuntu3
---
vlan (1.9-3.2ubuntu3) artful; urgency=medium
* In vlan ifupdown pre-up script, instead of calling ip link up for
raw device before creating vlan interface, do a full ifup for raw
device. Otherwise, if raw device
** Also affects: vlan (Ubuntu Zesty)
Importance: Undecided
Status: New
** Also affects: vlan (Ubuntu Yakkety)
Importance: Undecided
Status: New
** Also affects: vlan (Ubuntu Xenial)
Importance: Undecided
Status: New
** Also affects: vlan (Ubuntu Trusty)
6 matches
Mail list logo
