Public bug reported:

Occasionally, after a resume from an update, network manager starts
behaving strangely, not setting the DomainServer for the network.

This happens when resuming the laptop to a location where:
- an additional ethernet card (which is the one to use) is attached via USB
- configuring that ethernet card NM is set up to clone a given mac address and 
get addresses only from dhcp, while the dns server is set manually in the 
network manager configuration
- there are also free wifi signals to which NM tends to connect

In this setup, NM fails to set the dns name in dnsmasq

The issue gets worked around by either

1) Using qdbus to call the dnsmasq dbus method to set the domain server.
In this case the solution is temporary. Namely when NM is asked to
disconnect from the net and then to reconnect, the issue comes again; or

2) Killing dnsmasq. In this case, dnsmasq ia automatically restarted and
everything starts working fine; or

3) Restarting NM itself.

ProblemType: Bug
DistroRelease: Ubuntu 16.10
Package: network-manager 1.2.6-0ubuntu1
ProcVersionSignature: Ubuntu 4.8.0-42.45-generic 4.8.17
Uname: Linux 4.8.0-42-generic x86_64
ApportVersion: 2.20.3-0ubuntu8.2
Architecture: amd64
CurrentDesktop: KDE
Date: Fri Mar 24 16:22:43 2017
EcryptfsInUse: Yes
InstallationDate: Installed on 2013-12-12 (1197 days ago)
InstallationMedia: Kubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1)
IpRoute:
 default via 10.143.1.254 dev enx0050b61af5c1  proto static  metric 100 
 10.143.0.0/19 dev enx0050b61af5c1  proto kernel  scope link  src 10.143.20.139 
 metric 100
SourcePackage: network-manager
UpgradeStatus: Upgraded to yakkety on 2017-01-10 (73 days ago)
nmcli-nm:
 RUNNING  VERSION  STATE      STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  WIFI  
   WWAN-HW  WWAN     
 running  1.2.6    connected  started  full          enabled     enabled  
enabled  enabled  disabled

** Affects: network-manager (Ubuntu)
     Importance: Undecided
         Status: New


** Tags: amd64 apport-bug third-party-packages yakkety

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1675820

Title:
  Network manager fails to set domain server in some circumstances

Status in network-manager package in Ubuntu:
  New

Bug description:
  Occasionally, after a resume from an update, network manager starts
  behaving strangely, not setting the DomainServer for the network.

  This happens when resuming the laptop to a location where:
  - an additional ethernet card (which is the one to use) is attached via USB
  - configuring that ethernet card NM is set up to clone a given mac address 
and get addresses only from dhcp, while the dns server is set manually in the 
network manager configuration
  - there are also free wifi signals to which NM tends to connect

  In this setup, NM fails to set the dns name in dnsmasq

  The issue gets worked around by either

  1) Using qdbus to call the dnsmasq dbus method to set the domain
  server. In this case the solution is temporary. Namely when NM is
  asked to disconnect from the net and then to reconnect, the issue
  comes again; or

  2) Killing dnsmasq. In this case, dnsmasq ia automatically restarted
  and everything starts working fine; or

  3) Restarting NM itself.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: network-manager 1.2.6-0ubuntu1
  ProcVersionSignature: Ubuntu 4.8.0-42.45-generic 4.8.17
  Uname: Linux 4.8.0-42-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Fri Mar 24 16:22:43 2017
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2013-12-12 (1197 days ago)
  InstallationMedia: Kubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  IpRoute:
   default via 10.143.1.254 dev enx0050b61af5c1  proto static  metric 100 
   10.143.0.0/19 dev enx0050b61af5c1  proto kernel  scope link  src 
10.143.20.139  metric 100
  SourcePackage: network-manager
  UpgradeStatus: Upgraded to yakkety on 2017-01-10 (73 days ago)
  nmcli-nm:
   RUNNING  VERSION  STATE      STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI     WWAN-HW  WWAN     
   running  1.2.6    connected  started  full          enabled     enabled  
enabled  enabled  disabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1675820/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to     : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

Reply via email to