Your message dated Sat, 12 Feb 2022 21:36:03 +0100
with message-id <[email protected]>
and subject line Re: network-manager: connectivity check fails on first run
with dns=dnsmasq
has caused the Debian Bug report #866689,
regarding network-manager: connectivity check fails on first run with
dns=dnsmasq
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
866689: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=866689
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: network-manager
Version: 1.8.0-5
Severity: minor
Dear Maintainer,
With NetworkManager.conf containing
[main]
dns=dnsmasq
[connectivity]
uri=http://network-test.debian.org/nm
the first connection after a full restart of NetworkManager always
reports connection status as "limited".
After some small amount of time elapses, and forcing a second
connectivity check with "nmcli net con check", the connection status is
reported to be "full".
Looks very similar to this bug report:
https://bugzilla.gnome.org/show_bug.cgi?id=727616
With the debug log enabled, it looks to me like the connection is
established but dnsmasq has not fully started before the connectivity
check is run. Possibly racy, but I was able to reproduce it several
times in a row by restarting NetworkManager.service.
The libcurl error code in the log is 6 (CURLE_COULDNT_RESOLVE_HOST).
I have now switched to dns=systemd-resolved and this issue is no longer
present, this is as good a solution as any to me with full support for
systemd-resolved in 1.8.
I think this bug only appeared with 1.8.0.
-- System Information:
Debian Release: 9.0
APT prefers testing
APT policy: (900, 'testing'), (800, 'unstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 4.9.0-3-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8),
LANGUAGE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages network-manager depends on:
ii adduser 3.115
ii dbus 1.10.18-1
ii init-system-helpers 1.48
ii libaudit1 1:2.7.7-1+b1
ii libbluetooth3 5.43-2
ii libc6 2.24-12
ii libcurl3-gnutls 7.52.1-5
ii libglib2.0-0 2.52.3-1
ii libgnutls30 3.5.13-2
ii libjansson4 2.9-1
ii libmm-glib0 1.6.8-1
ii libndp0 1.6-1+b1
ii libnewt0.52 0.52.20-1+b1
ii libnl-3-200 3.2.27-2
ii libnm0 1.8.0-5
ii libpam-systemd 233-9
ii libpolkit-agent-1-0 0.105-18
ii libpolkit-gobject-1-0 0.105-18
ii libpsl5 0.17.0-4
ii libreadline7 7.0-3
ii libselinux1 2.6-3+b2
ii libsystemd0 233-9
ii libteamdctl0 1.26-1+b1
ii libudev1 233-9
ii libuuid1 2.29.2-1
ii lsb-base 9.20161125
ii policykit-1 0.105-18
ii udev 233-9
ii wpasupplicant 2:2.4-1
Versions of packages network-manager recommends:
ii crda 3.18-1
ii dnsmasq-base 2.77-2
ii iptables 1.6.0+snapshot20161117-6
ii iputils-arping 3:20161105-1
ii isc-dhcp-client 4.3.5-3
ii modemmanager 1.6.8-1
ii ppp 2.4.7-1+4
Versions of packages network-manager suggests:
pn libteam-utils <none>
-- Configuration Files:
/etc/NetworkManager/NetworkManager.conf changed [not included]
-- no debconf information
--- End Message ---
--- Begin Message ---
On Fri, 30 Jun 2017 17:02:15 -0700 Mike Miller <[email protected]> wrote:
Package: network-manager
Version: 1.8.0-5
Severity: minor
Dear Maintainer,
With NetworkManager.conf containing
[main]
dns=dnsmasq
[connectivity]
uri=http://network-test.debian.org/nm
the first connection after a full restart of NetworkManager always
reports connection status as "limited".
After some small amount of time elapses, and forcing a second
connectivity check with "nmcli net con check", the connection status is
reported to be "full".
Looks very similar to this bug report:
https://bugzilla.gnome.org/show_bug.cgi?id=727616
With the debug log enabled, it looks to me like the connection is
established but dnsmasq has not fully started before the connectivity
check is run. Possibly racy, but I was able to reproduce it several
times in a row by restarting NetworkManager.service.
The libcurl error code in the log is 6 (CURLE_COULDNT_RESOLVE_HOST).
I have now switched to dns=systemd-resolved and this issue is no longer
present, this is as good a solution as any to me with full support for
systemd-resolved in 1.8.
I think this bug only appeared with 1.8.0.
Can't seem to reproduce this problem (anymore). Thus closing.
Please reopen if you still encounter it with a recent version of NM.
Michael
OpenPGP_signature
Description: OpenPGP digital signature
--- End Message ---
