WiFi troubles: Automatic name resolution does not work, manual does!

pentix · 2018-01-15 19:50:15

Hello guys!

Before talking too much about all the trouble, here's my lspci output so you know what hardware and possible driver I am talking about:

$ lspci -k
03:00.0 Network controller: Qualcomm Atheros QCA9377 802.11ac Wireless Network Adapter (rev 31)
        Subsystem: Lenovo QCA9377 802.11ac Wireless Network Adapter
        Kernel driver in use: ath10k_pci
        Kernel modules: ath10k_pci, wl
04:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. RTS5229 PCI Express Card Reader (rev 01)
        Subsystem: Lenovo RTS5229 PCI Express Card Reader
        Kernel driver in use: rtsx_pci
        Kernel modules: rtsx_pci

It might be that my problem is actually constructed out of several smaller problems. I always had a very poor connection, web sites did either slowly or
not at all load when connected to the WLAN network in my university. The wifi is a WPA-Enterprise solution on both 5GHz as well as on 2.4GHz and I also tried this 'eduroam' stuff...
( The connection is blazingly fast when I'm using my phone, also there are repeaters everywhere so I can't really blame the infrastructure ) Also I have to mention that I never had problems
before using the same hardware but different APs. (e.g. at home)

journalctl showed the following while "connecting":

Dez 12 13:48:18 ArchLinux kernel: ath10k_pci 0000:03:00.0: no channel configured; ignoring frame(s)!
Dez 12 13:48:18 ArchLinux kernel: ath10k_pci 0000:03:00.0: no channel configured; ignoring frame(s)!
Dez 12 13:48:18 ArchLinux NetworkManager[275]: <info>  [1513082898.8881] device (wlp3s0): supplicant interface state: disconnected -> scanning
Dez 12 13:48:18 ArchLinux wpa_supplicant[663]: wlp3s0: CTRL-EVENT-REGDOM-CHANGE init=BEACON_HINT type=UNKNOWN
Dez 12 13:48:19 ArchLinux kernel: ath10k_pci 0000:03:00.0: no channel configured; ignoring frame(s)!
Dez 12 13:48:20 ArchLinux kernel: ath10k_pci 0000:03:00.0: no channel configured; ignoring frame(s)!
Dez 12 13:48:20 ArchLinux kernel: ath10k_pci 0000:03:00.0: no channel configured; ignoring frame(s)!
Dez 12 13:48:20 ArchLinux kernel: ath10k_pci 0000:03:00.0: no channel configured; ignoring frame(s)!
Dez 12 13:48:26 ArchLinux kernel: ath10k_pci 0000:03:00.0: no channel configured; ignoring frame(s)!
Dez 12 13:48:27 ArchLinux kernel: ath10k_pci 0000:03:00.0: no channel configured; ignoring frame(s)!
Dez 12 13:48:27 ArchLinux kernel: ath10k_pci 0000:03:00.0: no channel configured; ignoring frame(s)!
Dez 12 13:48:29 ArchLinux wpa_supplicant[663]: wlp3s0: CTRL-EVENT-REGDOM-CHANGE init=BEACON_HINT type=UNKNOWN
Dez 12 13:48:29 ArchLinux wpa_supplicant[663]: wlp3s0: CTRL-EVENT-REGDOM-CHANGE init=BEACON_HINT type=UNKNOWN
Dez 12 13:48:32 ArchLinux wpa_supplicant[663]: wlp3s0: CTRL-EVENT-SSID-REENABLED id=0 ssid="eth-5"
Dez 12 13:48:32 ArchLinux wpa_supplicant[663]: wlp3s0: SME: Trying to authenticate with 98:4b:e1:2b:a7:e0 (SSID='eth-5' freq=5200 MHz)
Dez 12 13:48:32 ArchLinux kernel: wlp3s0: authenticate with 98:4b:e1:2b:a7:e0
Dez 12 13:48:32 ArchLinux NetworkManager[275]: <info>  [1513082912.7312] device (wlp3s0): supplicant interface state: scanning -> authenticating
Dez 12 13:48:32 ArchLinux wpa_supplicant[663]: wlp3s0: Trying to associate with 98:4b:e1:2b:a7:e0 (SSID='eth-5' freq=5200 MHz)
Dez 12 13:48:32 ArchLinux kernel: wlp3s0: send auth to 98:4b:e1:2b:a7:e0 (try 1/3)
Dez 12 13:48:32 ArchLinux kernel: wlp3s0: authenticated
Dez 12 13:48:32 ArchLinux wpa_supplicant[663]: wlp3s0: Associated with 98:4b:e1:2b:a7:e0
Dez 12 13:48:32 ArchLinux wpa_supplicant[663]: wlp3s0: CTRL-EVENT-EAP-STARTED EAP authentication started
Dez 12 13:48:32 ArchLinux kernel: wlp3s0: associate with 98:4b:e1:2b:a7:e0 (try 1/3)
Dez 12 13:48:32 ArchLinux kernel: wlp3s0: RX AssocResp from 98:4b:e1:2b:a7:e0 (capab=0x8011 status=0 aid=2)
Dez 12 13:48:32 ArchLinux kernel: wlp3s0: associated
Dez 12 13:48:32 ArchLinux kernel: wlp3s0: deauthenticating from 98:4b:e1:2b:a7:e0 by local choice (Reason: 3=DEAUTH_LEAVING)
Dez 12 13:48:32 ArchLinux wpa_supplicant[663]: wlp3s0: CTRL-EVENT-SUBNET-STATUS-UPDATE status=0
Dez 12 13:48:32 ArchLinux wpa_supplicant[663]: wlp3s0: CTRL-EVENT-DISCONNECTED bssid=98:4b:e1:2b:a7:e0 reason=3 locally_generated=1
Dez 12 13:48:32 ArchLinux wpa_supplicant[663]: wlp3s0: CTRL-EVENT-SSID-TEMP-DISABLED id=0 ssid="eth-5" auth_failures=2 duration=26 reason=CONN_FAILED
Dez 12 13:48:32 ArchLinux systemd-udevd[29611]: Process '/usr/bin/crda' failed with exit code 249.
Dez 12 13:48:32 ArchLinux wpa_supplicant[663]: wlp3s0: CTRL-EVENT-REGDOM-CHANGE init=CORE type=WORLD
Dez 12 13:48:32 ArchLinux NetworkManager[275]: <info>  [1513082912.7666] device (wlp3s0): supplicant interface state: authenticating -> associating
Dez 12 13:48:32 ArchLinux NetworkManager[275]: <info>  [1513082912.7667] device (wlp3s0): supplicant interface state: associating -> associated
Dez 12 13:48:32 ArchLinux NetworkManager[275]: <warn>  [1513082912.7668] sup-iface[0x55f3a52c36f0,wlp3s0]: connection disconnected (reason -3)
Dez 12 13:48:32 ArchLinux NetworkManager[275]: <info>  [1513082912.7668] device (wlp3s0): supplicant interface state: associated -> disconnected
Dez 12 13:48:32 ArchLinux NetworkManager[275]: <info>  [1513082912.8586] device (wlp3s0): supplicant interface state: disconnected -> scanning
Dez 12 13:48:32 ArchLinux wpa_supplicant[663]: wlp3s0: CTRL-EVENT-REGDOM-CHANGE init=BEACON_HINT type=UNKNOWN

As I read this https://wiki.archlinux.org/index.php/Wi … tion#ath9k article I thought that the problem would actually be the nohwcrypt option, so I set that up,
And now I have:

$ cat /etc/modprobe.d/ath10k.conf 
options ath10k_core nohwcrypt=1

The problem seemed to be gone. Seemed. Sometimes it worked really well, sometimes it didn't.

Now I noticed the following:

Pinging does often not work at all ("Host not found")
Pinging static IPs is not a problem at all

That's why I "acted manually" as the "DNS guy", e.g. by executing

$ dig www.archlinux.org
;; ANSWER SECTION:
www.archlinux.org.      2047    IN      CNAME   apollo.archlinux.org.
apollo.archlinux.org.   54843   IN      A       138.201.81.199

and then putting this manually into /etc/hosts. Then pages load quickly, pacman upgrades, whatever - it works! Therefore I guess the name resolution is the 'next main problem' now.
I just don't really understand why doing a DNS query myself (using the nameservers provided by the WIFI) works so fast but it doesn't work when the system does it.

The next thing I tried is to edit /etc/resolv.conf to only contain the nameserver 8.8.8.8.
Again, sometimes pages do load, sometimes they don't. I'm actually out of knowledge now, I can't trace my problem further and I don't know what I could try next.

Did anybody experience similar issues or do you have an idea what might be checked next?

Thanks!
Patrick

Last edited by pentix (2018-01-15 19:51:53)

seth · 2018-01-15 20:37:54

Your nsswitch.conf?
It's a bit weird indeed (drill ./. ping I'd understand, former doesn't use nsswitch), but ping unlike dig uses libnss_resolve, so there could be a bug/misconfig.

pentix · 2018-01-15 21:01:20

seth wrote:

Your nsswitch.conf?

Does the nsswitch.conf differ (just as the resolv.conf) whenever I use a different wifi or is it to be considered static?
This is how I have it set up at home:

$ cat /etc/nsswitch.conf 
# Name Service Switch configuration file.
# See nsswitch.conf(5) for details.

passwd: files mymachines systemd
group: files mymachines systemd
shadow: files

publickey: files

hosts: files mymachines resolve [!UNAVAIL=return] dns myhostname
networks: files

protocols: files
services: files
ethers: files
rpc: files

netgroup: files

seth · 2018-01-15 21:10:38

static - and boring (ie. just the default config)

Systemd issue? Did you conduct partial updates? Is systemd-resolved running?

pentix · 2018-01-15 22:14:46

seth wrote:

static - and boring (ie. just the default config)

I see.

seth wrote:

Systemd issue? Did you conduct partial updates? Is systemd-resolved running?

I never do partial updates. Uhm

$ systemctl status systemd-resolved.service
● systemd-resolved.service - Network Name Resolution
   Loaded: loaded (/usr/lib/systemd/system/systemd-resolved.service; disabled; vendor preset: enabled)
   Active: inactive (dead)
     Docs: man:systemd-resolved.service(8)
           https://www.freedesktop.org/wiki/Software/systemd/resolved
           https://www.freedesktop.org/wiki/Software/systemd/writing-network-configuration-managers
           https://www.freedesktop.org/wiki/Software/systemd/writing-resolver-clients

Should it be active then?

seth · 2018-01-16 09:58:58

Nope. At least not as long as you don't use systemd-networkd.

Let's tighten this a bit down:
Use 8.8.8.8 in resolve.conf (to rule out a crappy DNS) and just try to ping addresses (to rule out browser caches)
Also clean (comment entries) your /etc/hosts and ensure you're not running nscd (or other dns caches)

Then check how consistently you can ping a domain (google.com) or an IP (8.8.8.8)
Iff google always works, try on your other, more relevant IPs - maybe the ping just stalls (to domain or IP), then check tracepath/traceroute to see "where"

pentix · 2018-01-16 14:02:06

Okay, so systemd-resolved is okay then.

Uhm I've been using the wifi all day now, it's fast and stable (also no ping issues, etc.)
My resolv.conf contains the normal nameservers configured with the wifi as well as 8.8.8.8.

I'm a bit unsure whether it's just temporary fixed now or if all those changes in the settings actually changed something.
I guess I'll have to wait until I'm "blocked" again...

Arch Linux

#1 2018-01-15 19:50:15

WiFi troubles: Automatic name resolution does not work, manual does!

#2 2018-01-15 20:37:54

Re: WiFi troubles: Automatic name resolution does not work, manual does!

#3 2018-01-15 21:01:20

Re: WiFi troubles: Automatic name resolution does not work, manual does!

#4 2018-01-15 21:10:38

Re: WiFi troubles: Automatic name resolution does not work, manual does!

#5 2018-01-15 22:14:46

Re: WiFi troubles: Automatic name resolution does not work, manual does!

#6 2018-01-16 09:58:58

Re: WiFi troubles: Automatic name resolution does not work, manual does!

#7 2018-01-16 14:02:06

Re: WiFi troubles: Automatic name resolution does not work, manual does!

Board footer