After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 766786 - Dhcpdiscover loops on interval until network-manager restart on Ubuntu 16.04
Dhcpdiscover loops on interval until network-manager restart on Ubuntu 16.04
Status: RESOLVED DUPLICATE of bug 764803
Product: NetworkManager
Classification: Platform
Component: Wi-Fi
unspecified
Other Linux
: Normal normal
: ---
Assigned To: NetworkManager maintainer(s)
NetworkManager maintainer(s)
Depends on:
Blocks:
 
 
Reported: 2016-05-23 11:11 UTC by lotuspsychje
Modified: 2016-05-24 21:43 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
Tail of the syslog before and after network-manager restart (34.15 KB, text/plain)
2016-05-23 11:11 UTC, lotuspsychje 		Details

Description lotuspsychje 2016-05-23 11:11:08 UTC 
Created attachment 328378 [details]
Tail of the syslog before and after network-manager restart

UBUNTU VERSION: Ubuntu desktop 16.04 64bit, system is up to date to latest

KERNEL: Linux RooTBooK 4.4.0-22-generic #40-Ubuntu SMP Thu May 12 22:03:46 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux

DHCPDISCOVER keeps looping on intervals until i restart network-manager, the loops are not happening
at every boot, but only sometimes at boot

WIFI CHIPSET: product: BCM4313 802.11bgn Wireless Network Adapter
WIFI DRIVER: driver=wl0 driverversion=6.30.223.248 (r487574) ip=192.168.1.3

the problem gets solved on network-manager restart and can be reproduced.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: network-manager 1.1.93-0ubuntu4
ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
Uname: Linux 4.4.0-22-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.20.1-0ubuntu2
Architecture: amd64
CurrentDesktop: Unity
Date: Wed May 18 12:37:55 2016
IfupdownConfig:
 # interfaces(5) file used by ifup(8) and ifdown(8)
 auto lo
 iface lo inet loopback
InstallationDate: Installed on 2016-04-25 (22 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
IpRoute:
 default via 192.168.1.1 dev wlp7s0 proto static metric 600
 169.254.0.0/16 dev wlp7s0 scope link metric 1000
 192.168.1.0/24 dev wlp7s0 proto kernel scope link src 192.168.1.3 metric 600
NetworkManager.state:
 [main]
 NetworkingEnabled=true
 WirelessEnabled=true
 WWANEnabled=true
SourcePackage: network-manager
UpgradeStatus: No upgrade log present (probably fresh install)
nmcli-dev:
 DEVICE TYPE STATE DBUS-PATH CONNECTION CON-UUID CON-PATH
 wlp7s0 wifi connected /org/freedesktop/NetworkManager/Devices/1 belkin7 1 1042ceaf-e9a0-4db1-96dd-897213b0c61c /org/freedesktop/NetworkManager/ActiveConnection/0
 enp6s0 ethernet unavailable /org/freedesktop/NetworkManager/Devices/2 -- -- --
 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'.
Comment 1 Beniamino Galvani 2016-05-24 21:43:30 UTC 
May 18 12:35:36 RooTBooK NetworkManager[582]: <warn>  [1463567736.9384] device (wlp7s0): Activation: failed for connection 'Wired connection 2'

The root cause of the issue is that the interface is wrongly recognized as Ethernet due to a race with udev. This was fixed by commit:

https://cgit.freedesktop.org/NetworkManager/NetworkManager/commit/?h=nm-1-2&id=52fc28893f5df384ea3fd86ec4ca4860f1e0ec4b

Please test again with NM 1.2.2 and reopen if it still happens. Thanks for reporting this!

*** This bug has been marked as a duplicate of bug 764803 ***