← Back to team overview

desktop-packages team mailing list archive

[Bug 1436330] Re: Network Manager doesn't set metric for local networks any more, causing connection issues


This bug was fixed in the package network-manager -

network-manager ( vivid; urgency=medium

  * debian/patches/git_route_fixes_part1_207ab013.patch,
    really fix routing: both the default gateways and the network routes get
    to be installed with a device-type-based priority so that we can get
    multiple routes installed without conficting. (LP: #1436330)

network-manager ( vivid; urgency=medium

  * debian/patches/fix_default_routes.patch: rework routing priorities and how
    default routes are added for devices and VPNs so that we can successfully
    run multiple devices on the same subnet without packet loss. (LP: #1436330)

 -- Mathieu Trudel-Lapierre <mathieu-tl@xxxxxxxxxx>  Tue, 15 Sep 2015
10:10:50 -0400

** Changed in: network-manager (Ubuntu Vivid)
       Status: Fix Committed => Fix Released

You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.

  Network Manager doesn't set metric for local networks any more,
  causing connection issues

Status in NetworkManager:
  Fix Released
Status in network-manager package in Ubuntu:
  Fix Released
Status in network-manager source package in Vivid:
  Fix Released

Bug description:
  NM changed its method of setting routes on systems, and no longer attaches a metric value specific to the type of device being used. These values were used to prioritize connections, so that for example, when connected to both wired and wireless at the same time, wired can be used in priority over wireless without incurring packet loss.
  Currently, when connected to both wired and wireless are connected to the same subnet, the user may notice connectivity issues since packets are sent in a round-robin fashion over all default routes on the same subnet with the same metric.

  [Test Case]
  1- Connect to a wireless network.
  2- Connect to the same network over Ethernet both connections should come up on the same subnet.
  3- Make sure there is no packet loss, and that there are specific metric values for each default route, as displayed by 'ip route'.

  [Regression Potential]
  Since handling default routes properly involves correcting the behavior for all device types, VPN behavior may change to pick up the default routes in all cases, over a wired connection. It's also possible that a connection pick up the default route when it is not meant to.


  With Vivid, having two connections to the same network subnet is
  unstable due to missing metrics for local networks.


  Being connected to via both wired and wireless will
  cause connectivity issues as sent packets hop between the two

  It used to be that this wasn't an issue. I would go between work and
  home and plug in and my machine would automatically connect to
  wireless and it would use the lower metric ethernet interface for all
  communications, while the wlan interface would remain connected but

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: network-manager
  ProcVersionSignature: Ubuntu 3.19.0-9.9-generic 3.19.1
  Uname: Linux 3.19.0-9-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.16.2-0ubuntu4
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Wed Mar 25 09:17:27 2015
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2015-01-25 (58 days ago)
  InstallationMedia: Kubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
  SourcePackage: network-manager
  UpgradeStatus: Upgraded to vivid on 2015-03-17 (8 days ago)
  nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 2: Error: Object 'nm' is unknown, try 'nmcli help'.

To manage notifications about this bug go to: