This bug was fixed in the package nplan - 0.23~16.10.1
---
nplan (0.23~16.10.1) yakkety; urgency=medium
* Backport netplan 0.23 to 16.10. (LP: #1688632)
nplan (0.23) artful; urgency=medium
* Do not unbind brcmfmac, interface will be gone. (LP: #1696162)
nplan (0.22) artful;
Verification done on yakkety:
ubuntu@loved-bunny:~$ ip route
default via 192.168.253.1 dev ens3 proto dhcp src 192.168.253.9 metric 100
10.10.10.0/24 dev bond0 proto kernel scope link src 10.10.10.1 linkdown
192.168.253.0/24 dev ens3 proto kernel scope link src 192.168.253.9
Hello Alfonso, or anyone else affected,
Accepted nplan into yakkety-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/nplan/0.23~16.10.1 in
a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
** Description changed:
- In Ubuntu Core, in all supported devices ethernet devices have higher
- metric than wlan or wwan devices, so packets get routed to the latter
- always. The metric is 1024, while for instance network-manager assigns
- these numbers:
+ [Impact]
+ In Ubuntu Core, in all
As this has been fixed in netplan, I'm changing the status of the HWE
task to Invalid. If this is incorrect, or there's something else we
need to do in the NM snap, then feel free to re-open.
** Changed in: snappy-hwe-snaps
Status: New => Invalid
--
You received this bug notification
This bug was fixed in the package nplan - 0.14~16.04
---
nplan (0.14~16.04) xenial; urgency=medium
* Update to 0.14 for xenial.
* tests/integration.py: Re-enable search domain check, that fix landed in
xenial.
nplan (0.14) zesty; urgency=medium
* tests/generate.py:
@brian-murray, verified on xenial/kvm machine with configuration:
$ cat /etc/netplan/00-snapd-config.yaml
network:
ethernets:
eth0:
dhcp4: true
version: 2
With nplan 0.13~16.04:
$ ip route
default via 10.0.3.1 dev eth0
default via 10.0.3.1 dev eth0 proto dhcp src 10.0.3.223
Hello Alfonso, or anyone else affected,
Accepted nplan into xenial-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/nplan/0.14~16.04 in a
few hours, and then in the -proposed repository.
Please help us by testing this new package. See
This bug was fixed in the package nplan - 0.15
---
nplan (0.15) zesty; urgency=medium
* tests/generate.py: Fix PEP-8 error (newly detected by -proposed
pycodestyle).
-- Martin Pitt Wed, 09 Nov 2016 17:12:54
+0100
** Changed in: nplan (Ubuntu)
SRU uploaded to xenial.
** Changed in: nplan (Ubuntu Xenial)
Status: Triaged => Confirmed
** Changed in: nplan (Ubuntu Xenial)
Status: Confirmed => In Progress
** Description changed:
In Ubuntu Core, in all supported devices ethernet devices have higher
metric than wlan or
https://git.launchpad.net/~netplan-
developers/netplan/commit/?id=42eb0864
** Changed in: nplan (Ubuntu)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
> change network-manager snap so it handles ethernet in all cases when
installed.
FTR, I think this makes sense (independently of aligning the metrics in
networkd). It's still confusing to have to use two different sets of
tools/APIs to manage your network.
--
You received this bug notification
Agreed. I'll change the networkd backend to add [DHCP]\nRouteMetric=100
for ethernet and 600 for wlan interfaces, for NM compatibility.
** Project changed: netplan => nplan (Ubuntu)
** Changed in: nplan (Ubuntu)
Status: New => In Progress
** Changed in: nplan (Ubuntu)
Assignee:
13 matches
Mail list logo