group.of.nepali.translators team mailing list archive

[Launchpad Bug Tracker <1639754@xxxxxxxxxxxxxxxxxx>]

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: Introduce macros for commonly expected networkd output
  * networkd: Use NetworkManager compatible DHCP route metrics (LP: #1639754)
  * doc/netplan.md: Fix wrong wifi reference in "br0" example
  * doc/netplan.md: Clarify introduction
  * tests/integration.py: Fix race condition with waiting for networkd

 -- Martin Pitt <martin.pitt@xxxxxxxxxx>  Wed, 09 Nov 2016 17:00:31
+0100

** Changed in: nplan (Ubuntu Xenial)
       Status: Fix Committed => Fix Released

-- 
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/1639754

Title:
  Ethernet devices have higher metric than wlan or wwan ones

Status in snappy-hwe-snaps:
  New
Status in nplan package in Ubuntu:
  Fix Released
Status in nplan source package in Xenial:
  Fix Released

Bug description:
  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:

  ethernet -> 100
  wlan -> 600
  wwan -> 700

  This happens because ethernet devices are managed by default by
  networkd in ubuntu-core, while wlan and wwan are managed by network-
  manager if installed. It would make sense to either assign a metric of
  100 in networkd configuration file or change network-manager snap so
  it handles ethernet in all cases when installed.

  SRU TEST CASE:
   * Set up an ethernet and wifi connection using netplan, and check metrics in "ip route". With the current version they have "1024", with the proposed update the ethernet one will have 100, the wifi one 600.

  REGRESSION POTENTIAL: It could in principle happen that someone relies
  on the current high metric and this interferes with some custom
  routing. However, netplan has only been used in snappy on xenial since
  recently, and there is no other official way to configure routing on
  snappy than netplan. So in practice this should be very low.

To manage notifications about this bug go to:
https://bugs.launchpad.net/snappy-hwe-snaps/+bug/1639754/+subscriptions