Comment 64 for bug 1573272

Revision history for this message
Dan Streetman (ddstreet) wrote :

Testing on xenial, same e/n/i config and ifup@.service change:

$ dpkg -l | grep vlan
ii vlan 1.9-3.2ubuntu1.16.04.1

$ ip r
default via 192.168.122.1 dev ens3
default via 1.2.3.1 dev ens7.100 metric 1000 onlink
default via 4.5.6.1 dev bond0 metric 2000 onlink
1.2.3.0/24 dev ens7.100 proto kernel scope link src 1.2.3.5
4.5.6.0/24 dev bond0 proto kernel scope link src 4.5.6.8
9.8.7.0/24 dev bond0.200 proto kernel scope link src 9.8.7.7
192.168.122.0/24 dev ens3 proto kernel scope link src 192.168.122.11

After upgrading to -proposed vlan:

$ dpkg -l | grep vlan
ii vlan 1.9-3.2ubuntu1.16.04.3

$ ip r
default via 192.168.122.1 dev ens3
default via 1.2.3.1 dev ens7.100 metric 1000 onlink
default via 4.5.6.1 dev bond0 metric 2000 onlink
default via 9.8.7.1 dev bond0.200 metric 3000 onlink
1.2.3.0/24 dev ens7.100 proto kernel scope link src 1.2.3.5
4.5.6.0/24 dev bond0 proto kernel scope link src 4.5.6.8
9.8.7.0/24 dev bond0.200 proto kernel scope link src 9.8.7.7
192.168.122.0/24 dev ens3 proto kernel scope link src 192.168.122.11

bond0.200 gw present, ens7.100 vlan present