touch-packages team mailing list archive

[Chris Peschke <hoosierpeschke@xxxxxxxxx>]

I have experienced the same bug on multiple brands of NIC hardware both
wired and wireless.  Observing the live log, it always occurs 30 minutes
after boot.  My DHCP server renews leases after an hour so I did not see
a correlation with the network configuration.

Googling this error reveals similar issues across several major distros
so this may be an upstream bug.

My early Virtualbox tests did not show an issue with a bridged adapter.
Re-running those tests again to verify.

I also disabled Avahi-daemon in a troubleshooting attempt and NM still
failed with the same error.

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

Title:
  Wired disconnects due to add_object(): Netlink error adding 0.0.0.0/0

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  I have a Lenovo Thinkpad E540 with r8169 wired onboard networking.
  After 15-30 minutes use the network stops working. There are no
  messages in dmesg, link stays up etc.

  This is output to journal:

  kesä 02 12:59:42 villenthinkpad avahi-daemon[925]: Withdrawing address record for 192.168.125.60 on eth0.
  kesä 02 12:59:42 villenthinkpad avahi-daemon[925]: Leaving mDNS multicast group on interface eth0.IPv4 with address 192.168.125.60.
  kesä 02 12:59:42 villenthinkpad avahi-daemon[925]: Interface eth0.IPv4 no longer relevant for mDNS.
  kesä 02 12:59:42 villenthinkpad NetworkManager[921]: <error> [1433239182.454827] [platform/nm-linux-platform.c:1714] add_object(): Netlink error adding 0.0.0.0/0 via 192.168.125.1 dev eth0 metric 1024 mss 0 src 
  kesä 02 12:59:42 villenthinkpad NetworkManager[921]: inet default table main
  kesä 02 12:59:42 villenthinkpad NetworkManager[921]: priority 0x400 protocol static
  kesä 02 12:59:42 villenthinkpad NetworkManager[921]: nexthop via 192.168.125.1 dev 2

  Disconnecting and reconnecting the cable solves the issue until next
  reboot, so I don't think it's a DHCP configuration issue. Other PC's
  on the network work fine.

  This has also been reported as kernel bug #1459985 as it's still
  unknown what causes the issue.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: network-manager 0.9.10.0-4ubuntu15.1
  ProcVersionSignature: Ubuntu 3.19.0-18.18-generic 3.19.6
  Uname: Linux 3.19.0-18-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.17.2-0ubuntu1.1
  Architecture: amd64
  CurrentDesktop: X-Cinnamon
  Date: Tue Jun  2 13:09:36 2015
  EcryptfsInUse: Yes
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2015-02-12 (109 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
  IpRoute:
   default via 192.168.125.1 dev eth0  proto static  metric 1024 
   169.254.0.0/16 dev eth0  scope link  metric 1000 
   192.168.125.0/24 dev eth0  proto kernel  scope link  src 192.168.125.60 
   192.168.135.1 dev wlan0  proto static  scope link  metric 1024
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
   WimaxEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: Upgraded to vivid on 2015-05-12 (20 days ago)
  nmcli-dev:
   DEVICE  TYPE      STATE      DBUS-PATH                                  CONNECTION          CON-UUID                              CON-PATH                                           
   eth0    ethernet  connected  /org/freedesktop/NetworkManager/Devices/1  Wired connection 1  2ef5399f-13a6-4337-9f55-d0d2e44cc43b  /org/freedesktop/NetworkManager/ActiveConnection/2 
   wlan0   wifi      connected  /org/freedesktop/NetworkManager/Devices/2  T2                  a59517ed-1d2b-4c2e-99a5-ee1f3afdc311  /org/freedesktop/NetworkManager/ActiveConnection/1 
   lo      loopback  unmanaged  /org/freedesktop/NetworkManager/Devices/0  --                  --                                    --
  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:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1461015/+subscriptions