Thank you for looking into this.
I will give it a try.


Note, previously I saw the bug not on the eduroam wireless network, but only on Wifi from my Vodafone mobile router.
It is possible that vodafone does more content filtering than eduroam.
Yet as I reported, I could access network-test.debian.org/nm fine with both.


What logs are you exactly looking for?

This is what I saw in user.log LAST TIME IT HAPPENED.

Jul 17 22:22:18 x220 NetworkManager[3365]: <info> [1531862538.1466] manager: NetworkManager state is now CONNECTED_LOCAL Jul 17 22:22:18 x220 NetworkManager[3365]: <info> [1531862538.1556] manager: NetworkManager state is now CONNECTED_SITE Jul 17 22:22:18 x220 NetworkManager[3365]: <info> [1531862538.1558] policy: set 'VodafoneMobileWiFi-8C5908' (wlp3s0) as default for IPv6 routing and DNS Jul 17 22:22:18 x220 NetworkManager[3365]: <info> [1531862538.1671] device (wlp3s0): Activation: successful, device activated. Jul 17 22:22:18 x220 org.kde.kdeconnect[1852]: kdeconnect.core: Broadcasting identity packet Jul 17 22:22:18 x220 /usr/lib/gdm3/gdm-x-session[1835]: [2093:2238:0717/222218.551578:ERROR:connection_factory_impl.cc(403)] Failed to connect to MCS endpoint with error -109 Jul 17 22:22:18 x220 goa-daemon[2014]: goa_http_client_check() failed: 2 — Error resolving “datasync.ed.ac.uk”: Name or service not known Jul 17 22:22:19 x220 org.kde.kdeconnect[1852]: kdeconnect.core: Broadcasting identity packet Jul 17 22:22:22 x220 NetworkManager[3365]: <info> [1531862542.5287] dhcp4 (wlp3s0): address 192.168.0.100 Jul 17 22:22:22 x220 NetworkManager[3365]: <info> [1531862542.5288] dhcp4 (wlp3s0): plen 24 (255.255.255.0) Jul 17 22:22:22 x220 NetworkManager[3365]: <info> [1531862542.5288] dhcp4 (wlp3s0): gateway 192.168.0.1 Jul 17 22:22:22 x220 NetworkManager[3365]: <info> [1531862542.5289] dhcp4 (wlp3s0): lease time 604800 Jul 17 22:22:22 x220 NetworkManager[3365]: <info> [1531862542.5289] dhcp4 (wlp3s0): nameserver '192.168.0.1' Jul 17 22:22:22 x220 NetworkManager[3365]: <info> [1531862542.5290] dhcp4 (wlp3s0): domain name 'wifi' Jul 17 22:22:22 x220 NetworkManager[3365]: <info> [1531862542.5290] dhcp4 (wlp3s0): state changed unknown -> bound Jul 17 22:22:22 x220 NetworkManager[3365]: <info> [1531862542.5318] policy: set 'VodafoneMobileWiFi-8C5908' (wlp3s0) as default for IPv4 routing and DNS Jul 17 22:22:22 x220 NetworkManager[3365]: <info> [1531862542.5419] manager: startup complete Jul 17 22:22:29 x220 NetworkManager[3365]: <info> [1531862549.3987] manager: NetworkManager state is now CONNECTED_GLOBAL Jul 17 22:22:34 x220 NetworkManager[3365]: <error> [1531862554.4848] connectivity: connectivity check failed: 4 Jul 17 22:22:34 x220 NetworkManager[3365]: <error> [1531862554.4850] connectivity: connectivity check failed: 4 Jul 17 22:22:34 x220 NetworkManager[3365]: <error> [1531862554.4850] connectivity: connectivity check failed: 4





Please install those packages, re-enable connectivity checking and
report back with your results.

I'm interested, if you still get this error and with what frequency.
The exact error message would be helpful. So if you can attach
(excerpts) of the log file, this would be great.


--
Mark van Rossum,
Professor, Schools of Psychology and Maths, U Nottingham
Psych Bldg Rm LG.19, 44-115-74 86851, 44-7722049644



This message and any attachment are intended solely for the addressee
and may contain confidential information. If you have received this
message in error, please contact the sender and delete the email and
attachment.
Any views or opinions expressed by the author of this email do not
necessarily reflect the views of the University of Nottingham. Email
communications with the University of Nottingham may be monitored where permitted by law.

Reply via email to