CM3 WiFi Seeing APs but not connecting

[manyxcxi]

Apologies if I’ve missed the obvious, but I can’t seem to connect to any of my WiFi access points. I’ve tried with WPA supplicant config, with raspi-config, and manually at the command line. The radio is able to see my access point when scanning, it’s just unable to connect.

Steps I’ve gone through:

- Radio country set to US
- Locale changed to en_US UTF-8
- Used most recent OS image
- Re-flashed on a different card and tried again
- Not seeing anything obvious in syslog
- Tried /boot/wpa_supplicant.conf
- Tried raspi-config
- Tried manually configuring

My access points
- 5GHz and 2.4GHz
- WPA PSK
- Apple and Ubiquiti APs
- 16-24 char passwords

[kite]

Without changing the localle, are you able to use the onscreen keyboard to type out passwd? Or, drop to shell and type your password to make sure it is sending the right presses?

You can probably check the logs in /var/log/messages or /var/log/syslog for more information on what is going on when you try and connect, it might give a little more insight

[manyxcxi]

Kite,
Do you recommend I change the locale back to en_UK or just reflash the image? I don’t think either WiFi password has any symbols in it that differ between US and UK layouts.

I haven’t found any smoking guns in syslog, is there something I may want to grep for that you’d be looking for?

[kite]

Try a re-image just to be sure. You're looking for any reason that you were deauthed from the network or that it wouldn't connect. The fact that you can see the APs means the wifi module is functional at least. If you could upload the logs i can take a peek

[manyxcxi]

With a clean image still no luck, here’s some relevant data from syslog though:

Code: Select all

RTL8732BS: start auth
RTL8732BS: auth success, start assoc
RTL8732BS: rtw_set_802_11_connect(wlan0) fw_state = 0x00000008
RTL8732BS: start auth
RTL8732BS: auth success, start assoc
RTL8732BS: rtw_set_802_11_connect(wlan0) fw_state = 0x00000008
RTL8732BS: start auth
RTL8732BS: auth success, start assoc
RTL8732BS: rtw_set_802_11_connect(wlan0) fw_state = 0x00000008
RTL8732BS: start auth
RTL8732BS: auth success, start assoc
RTL8732BS: no linked power save enter

So it looks like it’s authenticating against my AP, but is having trouble joining for some reason. Do you know what “no linked power save enter” means?

[kite]

That message is from the kernel/driver of the module, pretty typical to see that. How far from the AP are you? Can you go like literally right next to it? Do you have any other AP or like a phone AP or something else to test with?

[manyxcxi]

I’ve tried it at various distances. I’m currently about 3 feet away from it. I’ve tried with and without security enabled on the network.

I can currently connect to it with my phone, computers, R PI 3, and Pi Zero W.

It’s operating in 2.4 and 5GHz channels with the same SSID, is that a potential issue?

EDIT: I just tried connecting to my iPhone as a hotspot and it connects. I’ll investigate further and see if multi-channel SSID causes the issue or if it’s because Apple Airports are dumb.

[kite]

Ok that's progress! The module and kernel drivers are from the 'staging' directory meaning they're not necessarily 100% perfect. This could be one of those corner cases. You might be able to add a guest/other AP in your router that can report on a single frequency (at least on the ubiquiti ones)

[manyxcxi]

I think for whatever reason it simply doesn't like my Apple Airport Express...

I split 2.4/5GHz channels into different SSIDs, tried adding a guest network with no password... It just won't associate with it.
I'll go dig out an old TP-Link or something and see if that has more luck.

[manyxcxi]

I got it on the WiFi! I'm not sure the _exact_ cause but I believe it had to do with being double NATed.

When I was digging through the settings on my Airport Express I realized it was set to handle DHCP w/ NAT and my cable modem router was also setup to do the DHCP. I flipped settings on the Airport Express to put it in bridge mode and let the cable modem do all the DHCP and voila... it got online.

So either the WiFi driver didn't play well with DHCP on the Airport Express (which went away when I put it in bridge mode) or the driver wasn't able to finish the assoc process because of some NAT/double NAT issue.

Either way, I cleaned up my AP configs and it got online. It's been the only thing picky enough in the last three years to make me go review my AP settings.