| View previous topic :: View next topic |
| Author |
Message |
solamour
l33t
Joined: 21 Dec 2004
Posts: 698
Location: San Diego, CA
|
 Posted: Fri Dec 22, 2023 6:21 pm Post subject: [Solved] Not able to connect Wi-Fi |
 |
|
Here is what my system has.
| Code: | # lspci | grep -i wireless
02:00.0 Network controller: Intel Corporation Wireless 7265 (rev 59)
|
| Code: | # tree /sys/class/net/
/sys/class/net/
├── enp3s0 -> ../../devices/pci0000:00/0000:00:01.4/0000:03:00.0/net/enp3s0
├── enp4s0 -> ../../devices/pci0000:00/0000:00:01.5/0000:04:00.0/net/enp4s0
├── lo -> ../../devices/virtual/net/lo
├── sit0 -> ../../devices/virtual/net/sit0
└── wlp2s0 -> ../../devices/pci0000:00/0000:00:01.2/0000:02:00.0/net/wlp2s0
|
| Code: | # ip addr show dev wlp2s0
5: wlp2s0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN group default qlen 1000
link/ether 68:3e:26:c3:ec:fe brd ff:ff:ff:ff:ff:ff
|
I'm not seeing anything unusual, but when I try to connect to an access point, I get the following.
| Code: | # wpa_supplicant -i wlp2s0 -c /etc/wpa_supplicant/wpa_supplicant.conf
Successfully initialized wpa_supplicant
nl80211: kernel reports: Match already configured
...
nl80211: kernel reports: Match already configured
wlp2s0: CTRL-EVENT-REGDOM-CHANGE init=DRIVER type=WORLD
wlp2s0: CTRL-EVENT-REGDOM-CHANGE init=DRIVER type=COUNTRY alpha2=US
wlp2s0: Failed to initiate sched scan
wlp2s0: Failed to initiate sched scan
wlp2s0: CTRL-EVENT-SCAN-FAILED ret=-16 retry=1
wlp2s0: Failed to initiate sched scan
wlp2s0: Failed to initiate sched scan
wlp2s0: Reject scan trigger since one is already pending
wlp2s0: Failed to initiate AP scan
wlp2s0: Reject scan trigger since one is already pending
wlp2s0: Failed to initiate AP scan
wlp2s0: CTRL-EVENT-SCAN-FAILED ret=-16 retry=1
|
I'd appreciate any suggestions on what to look for.
__
sol
Last edited by solamour on Fri Dec 22, 2023 8:26 pm; edited 1 time in total |
|
| Back to top |
|
 |
grknight
Retired Dev
Joined: 20 Feb 2015
Posts: 1693
|
| Posted: Fri Dec 22, 2023 7:05 pm Post subject: |
|
|
First, ensure that WPA and TKIP are disabled in the router (use WPA2 and AES instead).
If you don't have access to the router, wpa_supplicant has the tkip USE disabled by default. It has a weird quirk of seeing a mixed mode TKIP and balking when it is disabled. Try enabling the tkip USE when the router cannot be changed. |
|
| Back to top |
|
|
solamour
l33t
Joined: 21 Dec 2004
Posts: 698
Location: San Diego, CA
|
| Posted: Fri Dec 22, 2023 8:26 pm Post subject: |
|
|
| grknight wrote: | First, ensure that WPA and TKIP are disabled in the router (use WPA2 and AES instead).
If you don't have access to the router, wpa_supplicant has the tkip USE disabled by default. It has a weird quirk of seeing a mixed mode TKIP and balking when it is disabled. Try enabling the tkip USE when the router cannot be changed. |
That must have been the missing ingredient; I tried a different access point, and it worked as expected. Not sure why it didn't occurred to me. Thanks for taking time to provide a valuable suggestion.
__
sol |
|
| Back to top |
|
|
|
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
Networking & Security
