A couple of months ago or so I began experiencing connectivity issues with WiFi. WiFi would have problems reconnecting after suspend, and when the ISP went out. I’d resolve this in order by toggling airplane mode, forgetting the network, and finally rebooting. Not all three unless the former had failed to resolve the problem.
Now that I’ve moved to a new place with a new router, I’m experiencing a new problem. Even though the WiFi apparently is connecting it’ll repeatedly ask me for authentication. When the dialog for the key pops up, it is already populated. Sometimes it’ll connect when this is happening even if I press cancel. Other times I press cancel when this is occurring then ‘select network’ from the shell menu which so far always works.
I don’t remember even how to access relevant logs to begin troubleshooting this.
42: PCI 400.0: 0282 WLAN controller
[Created at pci.386]
Unique ID: YVtp.+cJ4EY4ENsA
Parent ID: yk9C.fA+tdbAkMSD
SysFS ID: /devices/pci0000:00/0000:00:01.7/0000:04:00.0
SysFS BusID: 0000:04:00.0
Hardware Class: network
Model: “Qualcomm Atheros QCA6174 802.11ac Wireless Network Adapter”
Vendor: pci 0x168c “Qualcomm Atheros”
Device: pci 0x003e “QCA6174 802.11ac Wireless Network Adapter”
SubVendor: pci 0x11ad “Lite-On Communications Inc”
SubDevice: pci 0x0807
Driver Modules: “ath10k_pci”
Device File: wlp4s0
Two things changed only the computer remained the same so it seems it has something to do with the new place/new router.
Can it be that the distance/path to the new router is bad so the connection is marginal?
I am assuming you are using NetworkManager, but can you please confirm, by showing the output of “sudo nmcli connection show” and “nmcli dev wifi”, also “/usr/sbin/hwinfo --wlan” would be good to have.
I am using NM.
Linksys02619_5GHz 84689a6b-aed6-40f9-8bef-8446143ddc9c wifi wlp4s0
I’ve had problems at both places. Of interest, often (usually) if I press cancel on the modal dialog then select the network from wifi settings it connects right away without asking for the key.
Okay, you are using NetworkManager and you are in 5G channel 36
It would be good to show the complete output of the commands including the command it self, Using Code Tags Around Your Paste, for example:
$ cat /proc/net/wireless
Inter-| sta-| Quality | Discarded packets | Missed | WE
face | tus | link level noise | nwid crypt frag retry misc | beacon | 22
wlp0s20u14: 0000 39. -71. -256 0 0 0 2 3 0
The more complete output of “nmcli dev wifi” would be interesting, how many more AP’s are on you channel and what is their/your power?
For the more complete network log use “sudo journalctl -b | grep wlp0s20u14”.
That can be a pretty long log, so you can redirect it to a file (add “> /tmp/wl.log” to the command) and post it using susepaste: “susepaste -n Shadowolf7 -e 604800 /tmp/wl.log” and share the link to the log
I’ve truncated the log to the last day as my system has shown the offending behavior within that time span.
In your log I see for Sep 19 02:05:35 that the connection is lost, likely because something is going to sleep:
device (p2p-dev-wlp4s0): state change: disconnected -> unmanaged (reason 'sleeping', sys-iface-state: 'managed')
From Sep 19 12:09:54 I see a successful connect.
Well, I put the computer to sleep. So that looked normal, and I do manage to connect but not without finagling.
The weirder part of all the behavior is the modal dialog asking for authentication to a memorized network that it is automatically connecting to. Stranger yet, the password is already in that modal dialog. Sometimes it will manage to connect if I click ‘connect’ on the dialog one or more times. Otherwise it always connects if I select it under WiFi settings.
Of note, I tried connecting to the 2.5Ghz signal. No anomalous UI action, but it is horribly flakey cutting out every few minutes and reestablishing about 30 seconds later. No indication that WiFi actually disconnects, but the GNOME shell indicator on the top bar isn’t fast to show changes. Also noteworthy is that I do not experience connectivity issues with other devices nor the Windows 10 installation on the same computer. That was also true of my last residence with the different router where I experienced other anomalous behavior with openSUSE.