[Bug 1130002] New: It takes 20 s NetworkManager to connect network
http://bugzilla.suse.com/show_bug.cgi?id=1130002 Bug ID: 1130002 Summary: It takes 20 s NetworkManager to connect network Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Network Assignee: os.gnome.maintainers@gmail.com Reporter: jslaby@suse.com QA Contact: qa-bugs@suse.de Found By: --- Blocker: --- Created attachment 800773 --> http://bugzilla.suse.com/attachment.cgi?id=800773&action=edit NetworkManager log of the last connection Since some of the past updates in the last month or two, it takes quite some time NetworkManager to connect after resume. It receives the reply from the DHCP server, ping works on the command line, but nm-applet still shows checking internet connectivity and won't finish for 15 more seconds. Excerpt from the NM log:
06:15:41 manager: (eth1): new Ethernet device (/org/freedesktop/NetworkManager/Devices/51) 06:15:41 device (eth1): carrier: link connected 06:15:41 dhcp4 (eth1): dhclient started with pid 12103 06:15:45 device (eth1): carrier: link connected 06:15:46 dhcp4 (eth1): address 192.168.1.49 06:15:46 dhcp4 (eth1): state changed unknown -> bound 06:15:46 device (eth1): state change: ip-config -> ip-check (reason 'none', sys-iface-state: 'managed') 06:15:47 dhcp6 (eth1): activation: beginning transaction (timeout in 45 seconds) 06:15:47 dhcp6 (eth1): dhclient started with pid 12198 06:15:48 dhcp6 (eth1): address 2a0b:e7c0:... 06:15:48 dhcp6 (eth1): state changed unknown -> bound, event ID="f3:f6:6d:0c|1553145348" 06:16:06 device (eth1): state change: ip-check -> secondaries (reason 'none', sys-iface-state: 'managed') 06:16:06 device (eth1): state change: secondaries -> activated (reason 'none', sys-iface-state: 'managed') 06:16:06 device (eth1): Activation: successful, device activated.
Happens both on ethernet and wifi. $ rpm -q NetworkManager NetworkManager-1.14.6-1.1.x86_64 zypp history:
2018-11-30 19:49:02|install|NetworkManager|1.14.4-2.1|x86_64||repo-oss|ac355937f547f10bda531645819813c20069d6a3d5812df91bbaa22a91430e99| 2019-02-23 13:44:06|install|NetworkManager|1.14.4-3.1|x86_64||repo-oss|2d19a157c2a954ca014f4d435a62a1d7432939cef923e97ec890b56c30f519b3| 2019-03-04 07:31:32|install|NetworkManager|1.14.6-1.1|x86_64|root@anemoi2|repo-oss|ae703147f10dbce9c69b2851be54393952bed12898377c297a4d83fda3cc2281|
-- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=1130002
http://bugzilla.suse.com/show_bug.cgi?id=1130002#c1
Jiri Slaby
06:15:40 dnsmasq: no servers found in /var/run/dnsmasq-forwarders.conf, will retry ... 06:16:06 dnsmasq: reading /var/run/dnsmasq-forwarders.conf
dnsmasq tries to read forwarders written by NM, but the forwarders file is empty initially and is only available when dnsmasq retries which takes those 26 seconds. So either dnsmasq should not have been woken at 6:15:40 or it should be woken at 06:15:46 -- when DHCP reply was received and network configured. Not sure whether this is a NM or dnsmasq issue. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=1130002
http://bugzilla.suse.com/show_bug.cgi?id=1130002#c2
--- Comment #2 from Jiri Slaby
So either dnsmasq should not have been woken at 6:15:40 or it should be woken at 06:15:46 -- when DHCP reply was received and network configured.
OK, but /var/run/dnsmasq-forwarders.conf has no servers for the whole period since the DHCP reply up to the point when the network starts working. Doing # echo 'nameserver 192.168.1.1' >> /var/run/dnsmasq-forwarders.conf after the DHCP reply, brings the network up immediately. So I don't know why netconfig does not write the file with the DHCP reply. It seems it waits for something to happen and writes it after some timeout. Does netconfig/NM wait for nscd? As I disabled nscd on 24th Feb due to issues it causes and that could be the point in time this started happening... -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=1130002
http://bugzilla.suse.com/show_bug.cgi?id=1130002#c3
--- Comment #3 from Jiri Slaby
http://bugzilla.suse.com/show_bug.cgi?id=1130002
http://bugzilla.suse.com/show_bug.cgi?id=1130002#c4
Jiri Slaby
participants (1)
-
bugzilla_noreply＠novell.com