[SOLVED] Internet connection issue after system upgrade

Stocke · 2018-09-21 15:39:31

Hello,

I've been using Arch Linux for about a year without too many issues, however yesterday I ran a system upgrade for the first time in a month which resulted in a fair few updates. Upon rebooting the laptop is no longer receiving internet.

The laptop is a Dell XPS 13.

I use networkmanager and the network-manager-applet, both of which were updated- I can provide a full update log if required:
networkmanager (1.12.3dev+1+g0a3755c17-1 -> 1.14.0-1)
network-manager-applet (1.8.16-1 -> 1.8.18-2)

According to the applet I am connected to my router, however I am not receiving internet (websites do not load, pings fail). Additionally, the applet's icon itself has changed and looks wrong. Instead of providing a signal information icon as it usually does, it's just showing a large circle.

Here are some logs:

 ip link show dev wlp58s0
2: wlp58s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP mode DORMANT group default qlen 1000
   link/ether 9c:b6:d0:d3:7a:bb brd ff:ff:ff:ff:ff:ff

 dmesg | grep wlp58s0
[    3.112454] ath10k_pci 0000:3a:00.0 wlp58s0: renamed from wlan0
[    3.380959] IPv6: ADDRCONF(NETDEV_UP): wlp58s0: link is not ready
[    4.156049] IPv6: ADDRCONF(NETDEV_UP): wlp58s0: link is not ready
[    4.999668] IPv6: ADDRCONF(NETDEV_UP): wlp58s0: link is not ready
[    5.116916] IPv6: ADDRCONF(NETDEV_UP): wlp58s0: link is not ready
[   14.851486] IPv6: ADDRCONF(NETDEV_UP): wlp58s0: link is not ready
[   19.733651] wlp58s0: authenticate with 48:d3:43:2e:29:e1
[   19.792076] wlp58s0: send auth to 48:d3:43:2e:29:e1 (try 1/3)
[   19.794779] wlp58s0: authenticated
[   19.805078] wlp58s0: associate with 48:d3:43:2e:29:e1 (try 1/3)
[   19.815125] wlp58s0: RX AssocResp from 48:d3:43:2e:29:e1 (capab=0x431 status=0 aid=1)
[   19.817538] wlp58s0: associated
[   19.849755] IPv6: ADDRCONF(NETDEV_CHANGE): wlp58s0: link becomes ready

 journalctl (after a reboot)
Sep 21 16:16:01 lt-dell systemd[407]: Reached target Paths.
Sep 21 16:16:01 lt-dell systemd[407]: Listening on GnuPG cryptographic agent (ssh-agent emulation).
Sep 21 16:16:01 lt-dell systemd[407]: Listening on p11-kit server.
Sep 21 16:16:01 lt-dell systemd[407]: Listening on Sound System.
Sep 21 16:16:01 lt-dell systemd[407]: Listening on GnuPG cryptographic agent and passphrase cache.
Sep 21 16:16:01 lt-dell systemd[407]: Reached target Timers.
Sep 21 16:16:01 lt-dell systemd[407]: Listening on GnuPG cryptographic agent and passphrase cache (restricted).
Sep 21 16:16:01 lt-dell systemd[407]: Starting D-Bus User Message Bus Socket.
Sep 21 16:16:01 lt-dell systemd[407]: Listening on GnuPG network certificate management daemon.
Sep 21 16:16:01 lt-dell systemd[407]: Listening on GnuPG cryptographic agent and passphrase cache (access for web browsers).
Sep 21 16:16:01 lt-dell systemd[407]: Listening on D-Bus User Message Bus Socket.
Sep 21 16:16:01 lt-dell systemd[407]: Reached target Sockets.
Sep 21 16:16:01 lt-dell systemd[407]: Reached target Basic System.
Sep 21 16:16:01 lt-dell systemd[407]: Starting Update XDG user dir configuration...
Sep 21 16:16:01 lt-dell systemd[407]: Started Update XDG user dir configuration.
Sep 21 16:16:01 lt-dell systemd[407]: Reached target Default.
Sep 21 16:16:01 lt-dell systemd[407]: Startup finished in 39ms.
Sep 21 16:16:02 lt-dell systemd[407]: Started D-Bus User Message Bus.
Sep 21 16:16:02 lt-dell gnome-keyring-daemon[468]: couldn't access control socket: /run/user/1000/keyring/control: No such file or directory
Sep 21 16:16:02 lt-dell systemd[407]: Starting Sound Service...
Sep 21 16:16:02 lt-dell dbus-daemon[461]: [session uid=1000 pid=461] Activating via systemd: service name='org.a11y.Bus' unit='at-spi-dbus-bus.service' requested by ':1.3' (uid=1000 pid=477 >
Sep 21 16:16:02 lt-dell systemd[407]: Starting Accessibility services bus...
Sep 21 16:16:02 lt-dell dbus-daemon[461]: [session uid=1000 pid=461] Successfully activated service 'org.a11y.Bus'
Sep 21 16:16:02 lt-dell systemd[407]: Started Accessibility services bus.
Sep 21 16:16:02 lt-dell at-spi-bus-launcher[526]: dbus-daemon[537]: Activating service name='org.a11y.atspi.Registry' requested by ':1.0' (uid=1000 pid=477 comm="nm-applet ")
Sep 21 16:16:02 lt-dell at-spi-bus-launcher[526]: dbus-daemon[537]: Successfully activated service 'org.a11y.atspi.Registry'
Sep 21 16:16:02 lt-dell at-spi-bus-launcher[526]: SpiRegistry daemon is running with well-known name - org.a11y.atspi.Registry
Sep 21 16:16:02 lt-dell systemd[407]: Started Sound Service.

Here are a few things I've tried so far:
- A different device to check the internet works
- USB tethering (same issue, connected with no internet). I am unable to test ethernet because the laptop doesn't have a slot for it.
- Rebooting, stopping/starting/disabling/renabling NetworkManager.service and connecting through wifi-menu (same issue)
- Downgrading the individual packages: networkmanager, network-manager-applet and nm-connection-editor. The last of which didn't downgrade, mentioning a conflict with libnm.

I would've liked to have run a fresh system upgrade, however I've yet to find a way to get the laptop back online.

Any help is much appreciated.

Edit: The issue seems to be related to a systemd update, see this post for solution.

Last edited by Stocke (2018-09-22 09:49:46)

seth · 2018-09-21 19:20:40

Looks like you got connected, but no lease.
Please provide the complete journal, yes - the posted bit is unrelated.
Also "ip a" and "ip r" outputs.

This is typically a dhcp issue and NM has a record for its internal dhcp implementation being … troublesome.
https://wiki.archlinux.org/index.php/Ne … HCP_client

Stocke · 2018-09-21 20:17:20

No luck unfortunately. I've changed NM to use dhcpcd since it was already installed and I'll leave it set to that for the time being.

ip a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host 
       valid_lft forever preferred_lft forever
2: wlp58s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
    link/ether 9c:b6:d0:d3:7a:bb brd ff:ff:ff:ff:ff:ff
    inet 192.168.0.10/24 brd 192.168.0.255 scope global dynamic noprefixroute wlp58s0
       valid_lft 863016sec preferred_lft 863016sec
    inet6 fe80::2664:d20f:e6ed:bba9/64 scope link noprefixroute 
       valid_lft forever preferred_lft forever

ip r
default via 192.168.0.1 dev wlp58s0 proto dhcp metric 20600 
192.168.0.0/24 dev wlp58s0 proto dhcp scope link src 192.168.0.10 metric 302 
192.168.0.0/24 dev wlp58s0 proto kernel scope link src 192.168.0.10 metric 600

As for the complete journal, I've output everything starting at the boot of the session in which I did the system update: https://pastebin.com/r21LCZ6u
The update completed at Sep 20 21:59, everything on Sep 21 is just me trying to troubleshoot the problem.

seth · 2018-09-21 20:25:18

You've a lease and a route, so that's not it.
The journal is rather sparse - "sudo journalctl -b"?

Try

ping -c4 192.168.0.1
ping -c4 8.8.8.8
dig google.com
dig @8.8.8.8 google.com

Stocke · 2018-09-21 20:55:58

My bad, I'm not too familiar with journalctl. The output is here: https://pastebin.com/ESmt4SH2

I don't have the required package for dig but I saw a post about drill being similar which I seem to have.

ping -c4 192.168.0.1
PING 192.168.0.1 (192.168.0.1) 56(84) bytes of data.
64 bytes from 192.168.0.1: icmp_seq=1 ttl=64 time=9.78 ms
64 bytes from 192.168.0.1: icmp_seq=2 ttl=64 time=8.25 ms
64 bytes from 192.168.0.1: icmp_seq=3 ttl=64 time=8.38 ms
64 bytes from 192.168.0.1: icmp_seq=4 ttl=64 time=6.93 ms

--- 192.168.0.1 ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 8ms
rtt min/avg/max/mdev = 6.931/8.332/9.775/1.012 ms

ping -c4 8.8.8.8
PING 8.8.8.8 (8.8.8.8) 56(84) bytes of data.
64 bytes from 8.8.8.8: icmp_seq=1 ttl=120 time=34.9 ms
64 bytes from 8.8.8.8: icmp_seq=2 ttl=120 time=36.2 ms
64 bytes from 8.8.8.8: icmp_seq=3 ttl=120 time=31.10 ms
64 bytes from 8.8.8.8: icmp_seq=4 ttl=120 time=35.4 ms

--- 8.8.8.8 ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 7ms
rtt min/avg/max/mdev = 31.986/34.623/36.198/1.606 ms

drill google.com
;; ->>HEADER<<- opcode: QUERY, rcode: NOERROR, id: 32890
;; flags: qr rd ra ; QUERY: 1, ANSWER: 6, AUTHORITY: 0, ADDITIONAL: 0 
;; QUESTION SECTION:
;; google.com.	IN	A

;; ANSWER SECTION:
google.com.	86	IN	A	74.125.205.102
google.com.	86	IN	A	74.125.205.113
google.com.	86	IN	A	74.125.205.100
google.com.	86	IN	A	74.125.205.101
google.com.	86	IN	A	74.125.205.139
google.com.	86	IN	A	74.125.205.138

;; AUTHORITY SECTION:

;; ADDITIONAL SECTION:

;; Query time: 74 msec
;; SERVER: 130.255.73.90
;; WHEN: Fri Sep 21 21:52:43 2018
;; MSG SIZE  rcvd: 124

drill @8.8.8.8 google.com
;; ->>HEADER<<- opcode: QUERY, rcode: NOERROR, id: 43345
;; flags: qr rd ra ; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0 
;; QUESTION SECTION:
;; google.com.	IN	A

;; ANSWER SECTION:
google.com.	299	IN	A	216.58.204.14

;; AUTHORITY SECTION:

;; ADDITIONAL SECTION:

;; Query time: 123 msec
;; SERVER: 8.8.8.8
;; WHEN: Fri Sep 21 21:52:53 2018
;; MSG SIZE  rcvd: 44

seth · 2018-09-21 21:09:32

Your internet works fine?
You can ping your gateway and google with reasonable latency and you also resolve googles domain through the default and googles DNS server.

What *exactly* fails atm?

Stocke · 2018-09-21 21:20:31

It's strange, both Firefox and Chrome are failing to load anything and are showing the standard "There is no Internet connection"-type messages.

Additionally, pacman isn't connecting to any of the mirrors which is preventing me from installing or updating packages.

Also a standard ping is failing:

ping google.com
ping: google.com: Name or service not known

seth · 2018-09-22 07:12:08

Some issue in the resolver config.
What does your /etc/nsswitch.conf look like and what's the output of "systemctl list-unit-files --state=enabled" ?

(drill, unlike dig, doesn't use libresolv)

bulletmark · 2018-09-22 07:19:11

seth wrote:

Some issue in the resolver config.

Isn't this the issue I described yesterday? See the solution there.

Last edited by bulletmark (2018-09-22 07:20:48)

seth · 2018-09-22 07:26:23

systemd-resolved should not be invoked at all by NM (at least to my knowledge it's exclusive to systemd-networkd), thus the question for the enabled services.
There're several ways to screw domain resolution, stray avahi entries come up every now and then.

Stocke · 2018-09-22 09:44:23

As you figured out, it was related to the resolver config and making the change bulletmark mentioned in the other thread has fixed the issue.

It seems systemd-resolved was being invoked one way or another:

systemctl list-unit-files --state=enabled
UNIT FILE                                   STATE  
autovt@.service                             enabled
dbus-org.freedesktop.NetworkManager.service enabled
dbus-org.freedesktop.nm-dispatcher.service  enabled
dbus-org.freedesktop.resolve1.service       enabled
getty@.service                              enabled
NetworkManager-dispatcher.service           enabled
NetworkManager-wait-online.service          enabled
NetworkManager.service                      enabled
systemd-resolved.service                    enabled
remote-fs.target                            enabled

10 unit files listed.

Thanks for all the help guys and thanks for keeping it easy to understand.

seth · 2018-09-22 13:14:17

What does your NetworkManager.conf look like?
According to https://wiki.archlinux.org/index.php?ti … omatically and https://wiki.gnome.org/Projects/NetworkManager/DNS one indeed can use resolved.
In case you actually really and intentionally want that, you should certainly read the entire arch wiki page and esp. ensure to symlink /etc/resolv.conf …

Arch Linux

#1 2018-09-21 15:39:31

[SOLVED] Internet connection issue after system upgrade

#2 2018-09-21 19:20:40

Re: [SOLVED] Internet connection issue after system upgrade

#3 2018-09-21 20:17:20

Re: [SOLVED] Internet connection issue after system upgrade

#4 2018-09-21 20:25:18

Re: [SOLVED] Internet connection issue after system upgrade

#5 2018-09-21 20:55:58

Re: [SOLVED] Internet connection issue after system upgrade

#6 2018-09-21 21:09:32

Re: [SOLVED] Internet connection issue after system upgrade

#7 2018-09-21 21:20:31

Re: [SOLVED] Internet connection issue after system upgrade

#8 2018-09-22 07:12:08

Re: [SOLVED] Internet connection issue after system upgrade

#9 2018-09-22 07:19:11

Re: [SOLVED] Internet connection issue after system upgrade

#10 2018-09-22 07:26:23

Re: [SOLVED] Internet connection issue after system upgrade

#11 2018-09-22 09:44:23

Re: [SOLVED] Internet connection issue after system upgrade

#12 2018-09-22 13:14:17

Re: [SOLVED] Internet connection issue after system upgrade

Board footer