Wifi connected but no internet access

I guess there is some comfort to be found in finding out I'm not the only one.

Please post the output of the following command:

cat /var/log/pacman.log | grep -i "d systemd (\|ed linux\|mware\|twork\|dkms ins\|a-nm\|nm-c\|ufw\|dhc\|dns\|wpa" | grep -v "head\|nvidia"  | tail -n 30

This will output a list of packages that were updated on your system recently that can affect networking.

If you have tried all the kernels and others are now experiencing the same issue this points to a driver/firmware or some networking component has recently changed.

Here you go

[2019-04-30 16:05] [ALPM-SCRIPTLET] Certificate added: C=US, O=Network Solutions L.L.C., CN=Network Solutions Certificate Authority
[2019-04-30 16:05] [ALPM-SCRIPTLET] Certificate added: C=US, S=New Jersey, L=Jersey City, O=The USERTRUST Network, CN=USERTrust ECC Certification Authority
[2019-04-30 16:05] [ALPM-SCRIPTLET] Certificate added: C=US, S=New Jersey, L=Jersey City, O=The USERTRUST Network, CN=USERTrust RSA Certification Authority
[2019-04-30 16:05] [ALPM-SCRIPTLET] Certificate added: C=US, O="VeriSign, Inc.", OU=VeriSign Trust Network, OU="(c) 1999 VeriSign, Inc. - For authorized use only", CN=VeriSign Class 3 Public Primary Certification Authority - G3
[2019-04-30 16:05] [ALPM-SCRIPTLET] Certificate added: C=US, O="VeriSign, Inc.", OU=VeriSign Trust Network, OU="(c) 2007 VeriSign, Inc. - For authorized use only", CN=VeriSign Class 3 Public Primary Certification Authority - G4
[2019-04-30 16:05] [ALPM-SCRIPTLET] Certificate added: C=US, O="VeriSign, Inc.", OU=VeriSign Trust Network, OU="(c) 2006 VeriSign, Inc. - For authorized use only", CN=VeriSign Class 3 Public Primary Certification Authority - G5
[2019-04-30 16:05] [ALPM-SCRIPTLET] Certificate added: C=US, O="VeriSign, Inc.", OU=VeriSign Trust Network, OU="(c) 2008 VeriSign, Inc. - For authorized use only", CN=VeriSign Universal Root Certification Authority
[2019-04-30 16:05] [ALPM-SCRIPTLET] Certificate added: C=US, O=Network Solutions L.L.C., CN=Network Solutions Certificate Authority
[2019-04-30 16:05] [ALPM-SCRIPTLET] Certificate added: C=US, S=New Jersey, L=Jersey City, O=The USERTRUST Network, CN=USERTrust ECC Certification Authority
[2019-04-30 16:05] [ALPM-SCRIPTLET] Certificate added: C=US, S=New Jersey, L=Jersey City, O=The USERTRUST Network, CN=USERTrust RSA Certification Authority
[2019-04-30 16:05] [ALPM-SCRIPTLET] Certificate added: C=US, O="VeriSign, Inc.", OU=VeriSign Trust Network, OU="(c) 1999 VeriSign, Inc. - For authorized use only", CN=VeriSign Class 3 Public Primary Certification Authority - G3
[2019-04-30 16:05] [ALPM-SCRIPTLET] Certificate added: C=US, O="VeriSign, Inc.", OU=VeriSign Trust Network, OU="(c) 2007 VeriSign, Inc. - For authorized use only", CN=VeriSign Class 3 Public Primary Certification Authority - G4
[2019-04-30 16:05] [ALPM-SCRIPTLET] Certificate added: C=US, O="VeriSign, Inc.", OU=VeriSign Trust Network, OU="(c) 2006 VeriSign, Inc. - For authorized use only", CN=VeriSign Class 3 Public Primary Certification Authority - G5
[2019-04-30 16:05] [ALPM-SCRIPTLET] Certificate added: C=US, O="VeriSign, Inc.", OU=VeriSign Trust Network, OU="(c) 2008 VeriSign, Inc. - For authorized use only", CN=VeriSign Universal Root Certification Authority
[2019-05-12 15:22] [PACMAN] Running 'pacman --color auto -S extra/networkmanager'
[2019-05-12 15:22] [ALPM] installed networkmanager (1.18.0-1)
[2019-05-13 07:45] [PACMAN] Running 'pacman --color auto -S extra/nm-connection-editor'
[2019-05-13 07:45] [ALPM] installed nm-connection-editor (1.8.21dev+3+gb4c365b1-1)
[2019-05-23 16:07] [PACMAN] Running 'pacman -R networkmanager'
[2019-05-23 16:08] [ALPM] warning: /etc/NetworkManager/NetworkManager.conf saved as /etc/NetworkManager/NetworkManager.conf.pacsave
[2019-05-23 16:08] [ALPM] removed networkmanager (1.18.0-1)
[2019-05-23 16:08] [PACMAN] Running 'pacman --color auto -S extra/networkmanager'
[2019-05-23 16:08] [ALPM] installed networkmanager (1.18.0-1)
[2019-05-23 16:13] [PACMAN] Running 'pacman -R networkmanager'
[2019-05-23 16:13] [ALPM] removed networkmanager (1.18.0-1)
[2019-05-23 17:59] [PACMAN] Running 'pacman --color auto -S extra/networkmanager'
[2019-05-23 17:59] [ALPM] installed networkmanager (1.18.0-1)
[2019-05-23 18:00] [PACMAN] Running 'pacman --color auto -S extra/networkmanager'
[2019-05-23 18:00] [ALPM] reinstalled networkmanager (1.18.0-1)
[2019-05-23 18:13] [ALPM] installed linux50-r8168 (8.047.01-1)

I should back up the old firmware files, yes?

Went ahead and backed them up. Installed the new firmware with makepkg -si. Same result.

Update: decided to go for some relatively drastic measures and disabled TLP entirely. So far it seems like it's working. Though I guess disabling TLP isn't much of a solution. Will keep you updated.

All tlp settings are stored in the config file /etc/default/tlp.

The tlp configuration file can be changed with any text editor (root privilege is needed).

Make a backup of the tlp configuration file before making any changes, (so it can be reverted, if required).

cp /etc/default/tlp /etc/default/tlp.bak

There is also tlpui available in the manjaro repo, (if you prefer a gui).

Changes to tlp settings take effect after a reboot.

Parameters ending with "_AC" are activated when the power supply is connected.

Parameters ending with "_BAT" are activated when running on battery.

Reference sources:

https://wiki.archlinux.org/index.php/TLP
https://linrunner.de/en/tlp/docs/tlp-configuration.html

The author of tlp is now recommending that tlp be disabled via its configuration file (not by disabling the tlp service).

Set to "0" to disable TLP, (reboot required).

TLP_ENABLE=0

Set to "1" to enable TLP, (reboot required).

TLP_ENABLE=1

Default when unconfigured is: 0

Did you do this?

If you can connect to wifi but can't connect to web sites that would point towards a DNS resolution issue.

Also try

ping -c3 192.168.2.1
ping -c3 1.1.1.1
ping -c3 8.8.8.8

to check you can access a DNS resolver.

Yeah it's definitely a TLP thing. I enabled it and the problem resurfaced. Disabling it again got rid of the issue.

I could not find a NetworkManager.state file to move at all.

Also checked which settings could be responsible in the TLP settings file and everything related to power managing WiFi is commented out.

1 Like

It definitely resolves correctly. Pinging anything works for a bit until the issue happens.

See my edits above regarding disabling tlp.

You will need to choose whether to leave tlp disabled, or dignose which setting is causing the problem. The best long term solution is to figure out which tlp setting is causing your issue, (and only disable that individual setting). It is best not to leave tlp disabled on a laptop as it is important for managing power saving, fan speeds, etc.

If you have not done so already you could also enable the power management kernel parameter listed on the other links I posted.

1 Like

Here's a new one. When I reboot there's a chance it'll work and a chance it won't. So TLP wasn't much of a factor after all.

dmesg -w | grep ath

gives me this

[    2.765550] systemd[1]: /usr/lib/systemd/system/virtlogd.socket:5: ListenStream= references a pat  below legacy directory /var/run/, updating /var/run/libvirt/virtlogd-sock → /run/libvirt/virtlogd-sock; please update the unit file accordingly.
[    2.766547] systemd[1]: /usr/lib/systemd/system/virtlogd-admin.socket:5: ListenStream= references a path below legacy directory /var/run/, updating /var/run/libvirt/virtlogd-admin-sock → /run/libvirt/virtlogd-admin-sock; please update the unit file accordingly.
[    2.773191] systemd[1]: /usr/lib/systemd/system/virtlockd.socket:5: ListenStream= references a path below legacy directory /var/run/, updating /var/run/libvirt/virtlockd-sock → /run/libvirt/virtlockd-sock; please update the unit file accordingly.
[    2.773807] systemd[1]: /usr/lib/systemd/system/virtlockd-admin.socket:5: ListenStream= references a path below legacy directory /var/run/, updating /var/run/libvirt/virtlockd-admin-sock → /run/libvirt/virtlockd-admin-sock; please update the unit file accordingly.
[    4.065735] ath10k_pci 0000:02:00.0: pci irq msi oper_irq_mode 2 irq_mode 0 reset_mode 0
[    4.582273] ath10k_pci 0000:02:00.0: qca6174 hw3.2 target 0x05030000 chip_id 0x00340aff sub 11ad:0807
[    4.582279] ath10k_pci 0000:02:00.0: kconfig debug 1 debugfs 1 tracing 1 dfs 0 testmode 0
[    4.583608] ath10k_pci 0000:02:00.0: firmware ver WLAN.RM.2.0-00180-QCARMSWPZ-1 api 4 features wowlan,ignore-otp,no-4addr-pad crc32 75dee6c5
[    4.649532] ath10k_pci 0000:02:00.0: board_file api 2 bmi_id N/A crc32 4ed3569e
[    4.720896] ath10k_pci 0000:02:00.0: unsupported HTC service id: 1536
[    4.740957] ath10k_pci 0000:02:00.0: htt-ver 3.26 wmi-op 4 htt-op 3 cal otp max-sta 32 raw 0 hwcrypto 1
[    4.811313] ath: EEPROM regdomain: 0x6c
[    4.811314] ath: EEPROM indicates we should expect a direct regpair map
[    4.811316] ath: Country alpha2 being used: 00
[    4.811316] ath: Regpair used: 0x6c
[    4.818957] ath10k_pci 0000:02:00.0 wlp2s0: renamed from wlan0
[    6.498211] ath10k_pci 0000:02:00.0: unsupported HTC service id: 1536
[    6.683224] ath10k_pci 0000:02:00.0: failed to parse tlv: -22
[    6.683227] ath10k_pci 0000:02:00.0: failed to parse chan info event: -22
[    6.733226] ath10k_pci 0000:02:00.0: failed to parse tlv: -22
[    6.733228] ath10k_pci 0000:02:00.0: failed to parse chan info event: -22
[    6.735610] ath10k_pci 0000:02:00.0: failed to parse tlv: -22
[    6.735612] ath10k_pci 0000:02:00.0: failed to parse chan info event: -22
[    6.785323] ath10k_pci 0000:02:00.0: failed to parse tlv: -22
[    6.785325] ath10k_pci 0000:02:00.0: failed to parse chan info event: -22
[    9.842136] ath10k_warn: 104 callbacks suppressed
[    9.842160] ath10k_pci 0000:02:00.0: failed to parse tlv: -22
[    9.842169] ath10k_pci 0000:02:00.0: failed to parse chan info event: -22
[    9.844253] ath10k_pci 0000:02:00.0: failed to parse tlv: -22
[    9.844275] ath10k_pci 0000:02:00.0: failed to parse chan info event: -22
[    9.994293] ath10k_pci 0000:02:00.0: failed to parse tlv: -22
[    9.994314] ath10k_pci 0000:02:00.0: failed to parse chan info event: -22
[    9.996439] ath10k_pci 0000:02:00.0: failed to parse tlv: -22
[    9.996460] ath10k_pci 0000:02:00.0: failed to parse chan info event: -22
[   10.146420] ath10k_pci 0000:02:00.0: failed to parse tlv: -22
[   10.146442] ath10k_pci 0000:02:00.0: failed to parse chan info event: -22

which doesn't seem all that exciting.

The command below will output a live log detailng your wifi's current activities:

journalctl -u NetworkManager -f   

Let the command run in the terminal and log all current wifi activity.

Log at least 50-100 lines of output around times when your connection is failing.

Post important excerpts from the log around failure events.

Apologies for the delay. I went to bed.

Will do so tonight and post any interesting logs.

May 24 20:12:53 jamil-pc NetworkManager[567]: <info>  [1558717973.5868] dhcp4 (wlp2s0): state changed
May 24 20:12:53 jamil-pc NetworkManager[567]: <info>  [1558717973.5887] device (wlp2s0): state change
May 24 20:12:53 jamil-pc NetworkManager[567]: <info>  [1558717973.5900] device (wlp2s0): state change
May 24 20:12:53 jamil-pc NetworkManager[567]: <info>  [1558717973.5905] device (wlp2s0): state change
May 24 20:12:53 jamil-pc NetworkManager[567]: <info>  [1558717973.5914] manager: NetworkManager state
May 24 20:12:53 jamil-pc NetworkManager[567]: <info>  [1558717973.5944] manager: NetworkManager state
May 24 20:12:53 jamil-pc NetworkManager[567]: <info>  [1558717973.5944] policy: set 'BlinkC6CCED' (wl
May 24 20:12:53 jamil-pc NetworkManager[567]: <info>  [1558717973.5965] device (wlp2s0): Activation: 
May 24 20:12:53 jamil-pc NetworkManager[567]: <info>  [1558717973.5972] manager: startup complete
May 24 20:12:53 jamil-pc NetworkManager[567]: <info>  [1558717973.9191] manager: NetworkManager state
May 24 20:19:18 jamil-pc NetworkManager[567]: <info>  [1558718358.9774] dhcp6 (wlp2s0): activation: beginning transaction (timeout in 45 seconds)
May 24 20:20:04 jamil-pc NetworkManager[567]: <warn>  [1558718404.3780] dhcp6 (wlp2s0): request timed out
May 24 20:20:04 jamil-pc NetworkManager[567]: <info>  [1558718404.3781] dhcp6 (wlp2s0): state changed unknown -> timeout
May 24 20:20:04 jamil-pc NetworkManager[567]: <info>  [1558718404.3782] dhcp6 (wlp2s0): canceled DHCP transaction
May 24 20:20:04 jamil-pc NetworkManager[567]: <info>  [1558718404.3782] dhcp6 (wlp2s0): state changed timeout -> done
May 24 21:13:13 jamil-pc NetworkManager[567]: <info>  [1558721593.6189] manager: NetworkManager state is now CONNECTED_SITE

Here are the logs from the last run. I started a download around 20:20. Came back around 21:30 and found it with no access again. From the amount it downloaded it seems to have been around the time the last line was logged.

This might be systemd-resolved playing up.

To check, run journalctl -fu systemd-resolved and systemctl restart systemd-resolved.

If you get a connection back that means systemd-resolved doesn't like your DNS resolver.

I'll not go into steps to fix yet in case it's not this issue.

Currently not at home so I can't test it, so I'll do that as soon as I get back, but here's something interesting.

I reinstalled Manjaro yesterday night and it worked fine until today when I used nmcli to connect to my router (had previously just added the connection using nm-connection-editor.)

As soon as I used nmcli it connected for a minute then it started happening all over again.

I think you're onto something here.

I ran the commands and it started working without needing to restart. Going to keep testing it. Here are the logs

-- Logs begin at Fri 2019-05-24 23:29:39 EEST. --
May 25 21:38:27 jamil-pc systemd-resolved[1306]: Using system hostname 'jamil-pc'.
May 25 21:38:27 jamil-pc systemd[1]: Started Network Name Resolution.
May 25 21:38:47 jamil-pc systemd-resolved[1306]: Using degraded feature set (UDP+EDNS0+DO) for DNS server 192.168.2.1.
May 25 21:39:02 jamil-pc systemd[1]: Stopping Network Name Resolution...
May 25 21:39:02 jamil-pc systemd-resolved[1306]: DNSSEC validation failed for question archlinux.org IN DS: failed-auxiliary
May 25 21:39:02 jamil-pc systemd-resolved[1306]: DNSSEC validation failed for question archlinux.org IN SOA: failed-auxiliary
May 25 21:39:02 jamil-pc systemd-resolved[1306]: DNSSEC validation failed for question www.archlinux.org IN AAAA: failed-auxiliary
May 25 21:39:02 jamil-pc systemd-resolved[1306]: Failed to send hostname reply: Transport endpoint is not connected
May 25 21:39:02 jamil-pc systemd-resolved[1306]: DNSSEC validation failed for question e6653.f.akamaiedge.net IN DS: failed-auxiliary
May 25 21:39:02 jamil-pc systemd-resolved[1306]: DNSSEC validation failed for question e6653.f.akamaiedge.net IN SOA: failed-auxiliary
May 25 21:39:02 jamil-pc systemd-resolved[1306]: DNSSEC validation failed for question e6653.f.akamaiedge.net IN A: failed-auxiliary
May 25 21:39:02 jamil-pc systemd-resolved[1306]: Failed to send hostname reply: Transport endpoint is not connected
May 25 21:39:02 jamil-pc systemd-resolved[1306]: Failed to send hostname reply: Transport endpoint is not connected
May 25 21:39:02 jamil-pc systemd-resolved[1306]: Failed to send hostname reply: Transport endpoint is not connected
May 25 21:39:02 jamil-pc systemd-resolved[1306]: DNSSEC validation failed for question ssl-google-analytics.l.google.com IN A: failed-auxiliary
May 25 21:39:02 jamil-pc systemd-resolved[1306]: Failed to send hostname reply: Transport endpoint is not connected
May 25 21:39:02 jamil-pc systemd-resolved[1306]: Failed to send hostname reply: Transport endpoint is not connected
May 25 21:39:02 jamil-pc systemd-resolved[1306]: Failed to send hostname reply: Transport endpoint is not connected
May 25 21:39:02 jamil-pc systemd-resolved[1306]: DNSSEC validation failed for question mobile-gtalk.l.google.com IN A: failed-auxiliary
May 25 21:39:02 jamil-pc systemd-resolved[1306]: Failed to send hostname reply: Transport endpoint is not connected
May 25 21:39:02 jamil-pc systemd-resolved[1306]: Failed to send hostname reply: Transport endpoint is not connected
May 25 21:39:02 jamil-pc systemd-resolved[1306]: Failed to send hostname reply: Transport endpoint is not connected
May 25 21:39:02 jamil-pc systemd-resolved[1306]: DNSSEC validation failed for question googleapis.l.google.com IN A: failed-auxiliary
May 25 21:39:02 jamil-pc systemd-resolved[1306]: Failed to send hostname reply: Transport endpoint is not connected
May 25 21:39:02 jamil-pc systemd-resolved[1306]: Failed to send hostname reply: Transport endpoint is not connected
May 25 21:39:02 jamil-pc systemd-resolved[1306]: Failed to send hostname reply: Transport endpoint is not connected
May 25 21:39:02 jamil-pc systemd-resolved[1306]: DNSSEC validation failed for question www-google-analytics.l.google.com IN SOA: failed-auxiliary
May 25 21:39:02 jamil-pc systemd-resolved[1306]: DNSSEC validation failed for question www-google-analytics.l.google.com IN A: failed-auxiliary
May 25 21:39:02 jamil-pc systemd-resolved[1306]: Failed to send hostname reply: Transport endpoint is not connected
May 25 21:39:02 jamil-pc systemd-resolved[1306]: Failed to send hostname reply: Transport endpoint is not connected
May 25 21:39:02 jamil-pc systemd-resolved[1306]: Failed to send hostname reply: Transport endpoint is not connected
May 25 21:39:02 jamil-pc systemd-resolved[1306]: DNSSEC validation failed for question oaiew.info IN DS: failed-auxiliary
May 25 21:39:02 jamil-pc systemd-resolved[1306]: DNSSEC validation failed for question oaiew.info IN SOA: failed-auxiliary
May 25 21:39:02 jamil-pc systemd-resolved[1306]: DNSSEC validation failed for question oaiew.info IN A: failed-auxiliary
May 25 21:39:02 jamil-pc systemd-resolved[1306]: Failed to send hostname reply: Transport endpoint is not connected
May 25 21:39:02 jamil-pc systemd-resolved[1306]: Failed to send hostname reply: Transport endpoint is not connected
May 25 21:39:02 jamil-pc systemd-resolved[1306]: Failed to send hostname reply: Transport endpoint is not connected
May 25 21:39:02 jamil-pc systemd[1]: systemd-resolved.service: Succeeded.
May 25 21:39:02 jamil-pc systemd[1]: Stopped Network Name Resolution.
May 25 21:39:02 jamil-pc systemd[1]: Starting Network Name Resolution...
May 25 21:39:02 jamil-pc systemd-resolved[2120]: Positive Trust Anchors:
May 25 21:39:02 jamil-pc systemd-resolved[2120]: . IN DS 19036 8 2 49aac11d7b6f6446702e54a1607371607a1a41855200fd2ce1cdde32f24e8fb5
May 25 21:39:02 jamil-pc systemd-resolved[2120]: . IN DS 20326 8 2 e06d44b80b8f1d39a95c0b0d7c65d08458e880409bbc683457104237c7f8ec8d
May 25 21:39:02 jamil-pc systemd-resolved[2120]: Negative trust anchors: 10.in-addr.arpa 16.172.in-addr.arpa 17.172.in-addr.arpa 18.172.in-addr.arpa 19.172.in-addr.arpa 20.172.in-addr.arpa 21.172.in-addr.arpa 22.172.in-addr.arpa 23.172.in-addr.arpa 24.172.in-addr.arpa 25.172.in-addr.arpa 26.172.in-addr.arpa 27.172.in-addr.arpa 28.172.in-addr.arpa 29.172.in-addr.arpa 30.172.in-addr.arpa 31.172.in-addr.arpa 168.192.in-addr.arpa d.f.ip6.arpa corp home internal intranet lan local private test
May 25 21:39:02 jamil-pc systemd-resolved[2120]: Using system hostname 'jamil-pc'.
May 25 21:39:02 jamil-pc systemd[1]: Started Network Name Resolution.
May 25 21:39:03 jamil-pc systemd-resolved[2120]: Using degraded feature set (UDP) for DNS server 192.168.2.1.
May 25 21:39:03 jamil-pc systemd-resolved[2120]: Using degraded feature set (UDP) for DNS server 192.168.2.1.
May 25 21:39:03 jamil-pc systemd-resolved[2120]: Server 192.168.2.1 does not support DNSSEC, downgrading to non-DNSSEC mode.
May 25 21:39:03 jamil-pc systemd-resolved[2120]: Server 192.168.2.1 does not support DNSSEC, downgrading to non-DNSSEC mode.

Option 1:

Edit /etc/systemd/resolved.conf and set

DNSSEC=no

then systemctl restart systemd-resolved .

Option 2:

Switch the management of /etc/resolv.conf from systemd-resolved back to Network Manager.

systemctl stop systemd-resolved
systemctl disable systemd-resolved
rm /etc/resolv.conf
systemctl restart NetworkManager

and ensure /etc/resolv.conf has been recreated containing your nameserver 192.168.2.1 .

Option 1 did nothing for me. Tried option 2. Working so far. Went ahead and used cloudflare servers as well. Will keep it going for a while to make sure it's all good.

Every time I feel like it's all good it happens again. This time I looked at journalctl and found lines stating the firmware crashed. Since I reinstalled Manjaro I it reverted back to the old one, so I installed the firmware that was suggested here again.

No crashes so far, but it's only been 15 minutes. I'm gonna try to be optimistic. Will update in the morning.

1 Like

Forum kindly sponsored by Bytemark