RPi 3B vs RPi Zero W aren't able to connect to LAP or create a LAP

CamDavidsonPilon commented 10 months ago

Here's what works: changing proto=rsn to proto=wpa, but that has security problems.

Very similar issues:

When the default security rsn, I'm not able to connect to hotspots hosted on a RPi 3B. Likely related to the above, too.

CamDavidsonPilon commented 10 months ago

With `proto=rsn`

On the Pi3B, I see the following nm logs when I try to connect to the AP:

audit: op="connection-update" uuid="4c69c6ef-1df4-4cd3-a04f-be44b8daf28a" name="pioreactor4" pid=2325 uid=0 resu>
device (wlan0): Activation: starting connection 'pioreactor4' (4c69c6ef-1df4-4cd3-a04f-be44b8daf28a)
audit: op="connection-activate" uuid="4c69c6ef-1df4-4cd3-a04f-be44b8daf28a" name="pioreactor4" pid=2325 uid=0 re>
device (wlan0): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed')
device (wlan0): state change: prepare -> config (reason 'none', sys-iface-state: 'managed')
device (wlan0): Activation: (wifi) access point 'pioreactor4' has security, but secrets are required.
device (wlan0): state change: config -> need-auth (reason 'none', sys-iface-state: 'managed')
sup-iface[c6eafa7ceb9baeae,1,wlan0]: wps: type pbc start...
device (wlan0): state change: need-auth -> prepare (reason 'none', sys-iface-state: 'managed')
device (wlan0): state change: prepare -> config (reason 'none', sys-iface-state: 'managed')
device (wlan0): Activation: (wifi) connection 'pioreactor4' has security, and secrets exist.  No new secrets nee>
Config: added 'ssid' value 'pioreactor4'
Config: added 'scan_ssid' value '1'
Config: added 'bgscan' value 'simple:30:-70:86400'
Config: added 'key_mgmt' value 'WPA-PSK WPA-PSK-SHA256 FT-PSK'
Config: added 'auth_alg' value 'OPEN'
Config: added 'psk' value '<hidden>'
device (wlan0): supplicant interface state: disconnected -> scanning
device (wlan0): supplicant interface state: scanning -> associating
device (wlan0): supplicant interface state: associating -> disconnected
device (wlan0): supplicant interface state: disconnected -> scanning
device (wlan0): supplicant interface state: scanning -> associating
device (wlan0): supplicant interface state: associating -> disconnected
device (wlan0): supplicant interface state: disconnected -> scanning
device (wlan0): Activation: (wifi) association took too long
device (wlan0): state change: config -> need-auth (reason 'none', sys-iface-state: 'managed')
sup-iface[c6eafa7ceb9baeae,1,wlan0]: wps: type pbc start...
device (wlan0): Activation: (wifi) asking for new secrets
device (wlan0): no secrets: No agents were available for this request.
device (wlan0): state change: need-auth -> failed (reason 'no-secrets', sys-iface-state: 'managed')
device (wlan0): Activation: failed for connection 'pioreactor4'
device (wlan0): state change: failed -> disconnected (reason 'none', sys-iface-state: 'managed')
device (wlan0): supplicant interface state: scanning -> disconnected

And here are logs connecting to another local wifi, succesfully:

device (wlan0): Activation: starting connection 'FigsHouse' (59506077-ac5c-47e8-85b2-4ff1e6b1979b)
audit: op="connection-add-activate" uuid="59506077-ac5c-47e8-85b2-4ff1e6b1979b" name="FigsHouse" pid=2372 uid=0 >
device (wlan0): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed')
device (wlan0): state change: prepare -> config (reason 'none', sys-iface-state: 'managed')
device (wlan0): Activation: (wifi) access point 'FigsHouse' has security, but secrets are required.
device (wlan0): state change: config -> need-auth (reason 'none', sys-iface-state: 'managed')
sup-iface[c6eafa7ceb9baeae,1,wlan0]: wps: type pbc start...
device (wlan0): state change: need-auth -> prepare (reason 'none', sys-iface-state: 'managed')
device (wlan0): state change: prepare -> config (reason 'none', sys-iface-state: 'managed')
device (wlan0): Activation: (wifi) connection 'FigsHouse' has security, and secrets exist.  No new secrets neede>
Config: added 'ssid' value 'FigsHouse'
Config: added 'scan_ssid' value '1'
Config: added 'bgscan' value 'simple:30:-70:86400'
Config: added 'key_mgmt' value 'WPA-PSK WPA-PSK-SHA256 FT-PSK'
Config: added 'auth_alg' value 'OPEN'
Config: added 'psk' value '<hidden>'
device (wlan0): supplicant interface state: disconnected -> scanning
device (wlan0): supplicant interface state: scanning -> inactive
device (wlan0): supplicant interface state: inactive -> associating
device (wlan0): supplicant interface state: associating -> completed
device (wlan0): Activation: (wifi) Stage 2 of 5 (Device Configure) successful. Connected to wireless network "Fi>
device (wlan0): state change: config -> ip-config (reason 'none', sys-iface-state: 'managed')
dhcp4 (wlan0): activation: beginning transaction (timeout in 45 seconds)
dhcp4 (wlan0): state changed new lease, address=192.168.2.18
device (wlan0): state change: ip-config -> ip-check (reason 'none', sys-iface-state: 'managed')
device (wlan0): state change: ip-check -> secondaries (reason 'none', sys-iface-state: 'managed')
device (wlan0): state change: secondaries -> activated (reason 'none', sys-iface-state: 'managed')
device (wlan0): Activation: successful, device activated.

CamDavidsonPilon commented 1 month ago

Is this 3B only or also 3B+ too?

Pioreactor / pioreactor