Problem appears like this - I can find wifi network without any problem, once I paste a password from keepassxc it tries to connect for quite long time and finally a window pops up saying, that password is incorrect.
How I tried to resolve this problem:
Manual configuration of wifi connection in network manager - no luck
Kernel update to 5.15.28 and reboot - no luck
I found tutorial covering similar situation, solution was to add wifi.scan-rand-mac-address=no to /etc/NetworkManager/NetworkManager.conf and restart NetworkManager service. I did that and what was surprising wifi connection established immediately after that, but after system reboot problem remains the same, even though an additional line is stil present in the NetworkManager.conf file.
What is even more confusing is a fact, that I had the same os version installed on the same computer 3 months ago and everything worked just fine, no problems with wifi connections.
I have no idea how to troubleshoot that, so if you need any other outputs I will be happy to provide.
You could have mentioned which tutorial …
The correct and full edit to this file are two lines
it should look like this:
[device]
wifi.scan-rand-mac-address=no
As for more pertinent logs, you could:
open a terminal - make it big
type: journalctl -f
then watch the output as you try to connect to your wifi
copy/paste that …
You can do a similar thing with: sudo dmesg -WH
and quit that with CTRL-c when done
Have you tried typing your password - instead of copy/pasting it?
Verify that the keys you press actually print the character you wanted to type.
It initially helped, so I don’t think that this problem is based on copy/pasting or manually typing. The password was provided correctly, because I managed to access wifi after completing said tutorial, but it all broke again after reboot.
I did the further investigation as you suggested (thanks for that), there is the output of journalctl recorded by the time of another wifi access attempt - pastebin.
Output of dmesg - pastebin. There is a part that looks intersting:
[ +0,187393] wlp3s0: authenticate with 3c:84:6a:bb:0f:c5
[ +0,005079] wlp3s0: send auth to 3c:84:6a:bb:0f:c5 (try 1/3)
[ +0,003851] wlp3s0: authenticated
[ +0,006926] wlp3s0: associate with 3c:84:6a:bb:0f:c5 (try 1/3)
[ +0,116719] wlp3s0: associate with 3c:84:6a:bb:0f:c5 (try 2/3)
[ +0,103282] wlp3s0: associate with 3c:84:6a:bb:0f:c5 (try 3/3)
[ +0,106661] wlp3s0: association with 3c:84:6a:bb:0f:c5 timed out
[ +13,044657] wlp3s0: authenticate with 3c:84:6a:bb:0f:c5
[ +0,005244] wlp3s0: send auth to 3c:84:6a:bb:0f:c5 (try 1/3)
[ +0,003857] wlp3s0: authenticated
[ +0,002884] wlp3s0: associate with 3c:84:6a:bb:0f:c5 (try 1/3)
[ +0,103371] wlp3s0: associate with 3c:84:6a:bb:0f:c5 (try 2/3)
[ +0,103328] wlp3s0: associate with 3c:84:6a:bb:0f:c5 (try 3/3)
[ +0,106713] wlp3s0: association with 3c:84:6a:bb:0f:c5 timed out
Here is my dmesg -WH
when I was disconnected - and connected again:
[Apr 8 19:54] wlan0: authenticate with 36:81:c4:b0:2a:64
[ +0.000015] wlan0: bad VHT capabilities, disabling VHT
[ +0.000001] wlan0: 80 MHz not supported, disabling VHT
[ +0.001349] wlan0: send auth to 36:81:c4:b0:2a:64 (try 1/3)
[ +0.003415] wlan0: authenticated
[ +0.000795] wlan0: associate with 36:81:c4:b0:2a:64 (try 1/3)
[ +0.016422] wlan0: RX AssocResp from 36:81:c4:b0:2a:64 (capab=0x431 status=0 aid=1)
[ +0.019913] wlan0: associated
[ +1.010818] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
The difference I see is this:
[ +0.000795] wlan0: associate with 36:81:c4:b0:2a:64 (try 1/3)
[ +0.016422] wlan0: RX AssocResp from 36:81:c4:b0:2a:64 (capab=0x431 status=0 aid=1)
[ +0.019913] wlan0: associated
[ +1.010818] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
in particular this line: [ +0.016422] wlan0: RX AssocResp from 36:81:c4:b0:2a:64 (capab=0x431 status=0 aid=1)
You never get that response from the device you try to connect to.
It’s missing in your logs.
Why you don’t get that response back … - I don’t know.
Just speculation: can they “hear” each other properly, or is the range/distance so far that that might cause this?
Check the wlan config of your router (if you can) - use not the newest WPA3 but restrict it to the older WPA2 (at least for testing whether it works …)
Sorry - I did not watch this.
(I might - it’s only 2 minutes …)
I’d rather follow the Arch wiki on how to set up and do stuff.
ps: yeah, I have seen it now - it’s … unhelpful (I first wanted to say “rubbish”)
… if you still have problems - let me know in the comments
is what he basically said …
