No network connection after upgrade even though wifi is connected

Lyxmyx · 2022-03-22 12:01:07

I didn't use my laptop for the last few months. So today was the first time in 7 months that I pacman -Syu.

Since then my network connection has been really wanky.

I can connect to a wifi, I even get an IP and everything. Everything shows me that I'm successfully connected.
But I can't even ping my own router. Or anything else in my network. Let alone internet connection.
I also tried nmap to see if it finds any of my many devices in my network, but to no avail. Even though I'm supposedly connected to my router.

If I boot my laptop with a LAN-cable already connected to my ethernet port I also have the exact same problem with my wired connection. Even if I try unplugging and replugging it.
But if I boot my laptop without a LAN-cable attached and connect it once the laptop is booted up I have a normal wired connection and can even access the internet.

I saw that a few months ago the linux-firmware was split. The network controller in my laptop is from Qualcom, so I tried installing the linux-firmware-qcom package. But nothing changed.
Then I installed all linux-firmware-* packages out of desperation, but still nothing changed.

I also tried to replace linux with linux-lts because I've read somewhere that that can help. But didn't do anything for me.
And then I tried downgrading both linux and linux-firmware to what they were 7 months ago (wifi was still working back then) but even that didn't do anything at all.

lspci | grep Network
02:00.0 Network controller: Qualcomm Atheros QCA6174 802.11ac Wireless Network Adapter (rev 32)

ip link
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: wlp2s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP mode DORMANT group default qlen 1000
    link/ether 9c:b6:d0:89:50:21 brd ff:ff:ff:ff:ff:ff

ip addr
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
2: wlp2s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
    link/ether 9c:b6:d0:89:50:21 brd ff:ff:ff:ff:ff:ff
    inet 192.168.178.71/24 brd 192.168.178.255 scope global noprefixroute wlp2s0
       valid_lft forever preferred_lft forever

ip route
default via 192.168.178.1 dev wlp2s0 proto static metric 20600 
192.168.178.0/24 dev wlp2s0 proto kernel scope link src 192.168.178.71 metric 600

ping 192.168.178.1
PING 192.168.178.1 (192.168.178.1) 56(84) bytes of data.
^C
--- 192.168.178.1 ping statistics ---
25 packets transmitted, 0 received, 100% packet loss, time 24329ms

Last edited by Lyxmyx (2022-03-22 12:05:35)

V1del · 2022-03-22 12:35:00

Make sure you don't have conflicting network services enabled. Post/check

find /etc/systemd -type l -exec test -f {} \; -print | awk -F'/' '{ printf ("%-40s | %s\n", $(NF-0), $(NF-1)) }' | sort -f

Also check your environment, maybe try restarting the router or so.

Last edited by V1del (2022-03-22 12:35:52)

jakalof · 2022-03-22 12:36:39

See this topic: https://bugzilla.kernel.org/show_bug.cgi?id=215703

Probably your issue at it relates to ath9k

Lyxmyx · 2022-03-22 12:51:05

V1del wrote:

Also check your environment, maybe try restarting the router or so.

That was also my first thought.
Restarted router, didn't help.
All other wireless devices work flawlessly though. So I checked if there are IP address conflicts, but there were none.
Tried my laptop in two different networks (work + friends house) and the issue remained.
Booted a live Fedora version from a usb drive and it connected without issues.
So I think I'm save to say that the issue lies with the configuration of this arch linux installation.

find /etc/systemd -type l -exec test -f {} \; -print | awk -F'/' '{ printf ("%-40s | %s\n", $(NF-0), $(NF-1)) }' | sort -f
bluetooth.service                        | bluetooth.target.wants
dbus-org.bluez.service                   | system
dbus-org.freedesktop.nm-dispatcher.service | system
dbus-org.freedesktop.timesync1.service   | system
dirmngr.socket                           | sockets.target.wants
getty@tty1.service                       | getty.target.wants
gpg-agent-browser.socket                 | sockets.target.wants
gpg-agent-extra.socket                   | sockets.target.wants
gpg-agent.socket                         | sockets.target.wants
gpg-agent-ssh.socket                     | sockets.target.wants
NetworkManager.service                   | multi-user.target.wants
NetworkManager-wait-online.service       | network-online.target.wants
nordvpnd.service                         | default.target.wants
p11-kit-server.socket                    | sockets.target.wants
pipewire.socket                          | sockets.target.wants
pulseaudio.socket                        | sockets.target.wants
remote-fs.target                         | multi-user.target.wants
systemd-timesyncd.service                | sysinit.target.wants

Lyxmyx · 2022-03-22 12:58:22

jakalof wrote:

See this topic: https://bugzilla.kernel.org/show_bug.cgi?id=215703
Probably your issue at it relates to ath9k

Thanks, seems like I'm not the only one with issues.

But since I'm not planing on compiling my own kernel I guess I have to wait for them to patch it ....

And if it's an issue with the kernel, then why wasn't it fixed when I reverted to the kernel from 7 months ago?

jakalof · 2022-03-22 13:13:58

Sorry I can't answer your 7 months question because I don't know.

Turns out that this bug is in the linux-lts and linux kernel branches relating to recent commits on kernel.

Otherwise -- it sure does point to the kernel issue. https://bugzilla.kernel.org/show_bug.cgi?id=215703

Check your logs; probably you will see something like

Mar 19 14:17:51 r2d2 systemd[1]: NetworkManager-dispatcher.service: Deactivated successfully.
Mar 19 14:19:32 r2d2 wpa_supplicant[911]: wlp1s0: CTRL-EVENT-BEACON-LOSS 
Mar 19 14:19:33 r2d2 wpa_supplicant[911]: wlp1s0: CTRL-EVENT-BEACON-LOSS 
Mar 19 14:19:34 r2d2 wpa_supplicant[911]: wlp1s0: CTRL-EVENT-BEACON-LOSS 
Mar 19 14:19:35 r2d2 wpa_supplicant[911]: wlp1s0: CTRL-EVENT-BEACON-LOSS 
Mar 19 14:19:36 r2d2 wpa_supplicant[911]: wlp1s0: CTRL-EVENT-BEACON-LOSS 
Mar 19 14:19:36 r2d2 wpa_supplicant[911]: wlp1s0: CTRL-EVENT-DISCONNECTED bssid=50:d4:f7:71:cc:dc reason=4 locally_generated=1
Mar 19 14:19:36 r2d2 wpa_supplicant[911]: wlp1s0: CTRL-EVENT-REGDOM-CHANGE init=CORE type=WORLD
Mar 19 14:19:36 r2d2 NetworkManager[910]: <info>  [1647710376.5175] device (wlp1s0): supplicant interface state: completed -> disconnected

I did rollback to 5.15.28 on linux-lts and that worked for me. Apparently you can rollback to linux 5.16.14 but I didn't do that since I'm using linux-lts

I don't think I can help any more beyond this. good luck.

V1del · 2022-03-22 13:22:50

This is an ath10k chip, unless it has the same issue like ath9 which i somewhat doubt then this isn't the same issue.

I see nordvpn there, do you get a connection if you disable/stop it? What does your /etc/resolv.conf look like?

seth · 2022-03-22 13:55:32

Esp. since

If I boot my laptop with a LAN-cable already connected to my ethernet port I also have the exact same problem with my wired connection. Even if I try unplugging and replugging it.
But if I boot my laptop without a LAN-cable attached and connect it once the laptop is booted up I have a normal wired connection and can even access the internet.

NM is super-chatty, so please post a complete system journal.

@Videl, the OP has

ping 192.168.178.1
PING 192.168.178.1 (192.168.178.1) 56(84) bytes of data.
^C
--- 192.168.178.1 ping statistics ---
25 packets transmitted, 0 received, 100% packet loss, time 24329ms

that's not the resolver (and also the ip/r doesn't look VPN, though ip/a also doesn't have an ethernet device - so who knows…)

Edit: could be netfilter/iptables, though.

iptables -nvL
nft list tables

Last edited by seth (2022-03-22 13:57:30)

Th3Link · 2022-04-05 12:32:35

Hi,

I had a similar problem just solved yesterday. All IPv6 connections worked file, IPv4 out of the LAN did also fine but could not connect to anywhere in my LAN.

I noticed a weird entry in ip route:

default via 192.168.178.1 dev enp9s0 proto dhcp metric 100 
192.168.1.10 dev enp9s0 proto static scope link metric 100 
192.168.178.0/24 via 192.168.1.10 dev enp9s0 proto static metric 100 
192.168.178.0/24 dev enp9s0 proto kernel scope link src 192.168.178.22 metric 100

So I disabled NetworkManager and tested systemd-networkd and had no problems after that.
My solution to get NetworkManager running again:

sudo pacman -R networkmanager network-manager-applet
sudo rm -R /etc/NetworkManager # was still there after removal
sudo pacman -S networkmanager network-manager-applet

In nm-applet I had to remove the old "wired connection" and an enp9s0 appeared, I also had to activate IPv4 there. I dont know what was wrong, but it is maybe worth trying ;)

Cheers

Arch Linux

#1 2022-03-22 12:01:07

No network connection after upgrade even though wifi is connected

#2 2022-03-22 12:35:00

Re: No network connection after upgrade even though wifi is connected

#3 2022-03-22 12:36:39

Re: No network connection after upgrade even though wifi is connected

#4 2022-03-22 12:51:05

Re: No network connection after upgrade even though wifi is connected

#5 2022-03-22 12:58:22

Re: No network connection after upgrade even though wifi is connected

#6 2022-03-22 13:13:58

Re: No network connection after upgrade even though wifi is connected

#7 2022-03-22 13:22:50

Re: No network connection after upgrade even though wifi is connected

#8 2022-03-22 13:55:32

Re: No network connection after upgrade even though wifi is connected

#9 2022-04-05 12:32:35

Re: No network connection after upgrade even though wifi is connected

Board footer