Closed martignoni closed 1 week ago
Tested on:
No error message on the RPi 3B, but no wireless client can connect.
However:
uap0: CTRL-EVENT-SUBNET-STATUS-UPDATE status=0
comes repeatedly, and connection doesn't complete.
This seems a bug with the AP protocol. Hot fix: launch following commands in MoodleBox terminal
sudo nmcli con mod WifiAP wifi-sec.proto rsn,wpa
sudo nmcli connection reload
This is fixed. Closing.
This issue is only fixed when the parameter wifi-sec.proto is set when starting the MoodleBox. The parameter should be set to wpa (for WPA) on a Raspberry Pi 3B and to rsn (for WPA2) on the newer models.
A microSD card working for a Raspberry Pi 3B can be moved to a Raspberry Pi 4 but the wifi only has WPA and not WPA2. Currently a microSD card working for a Raspberry Pi 4B with WPA2 would not work for a Raspberry Pi 3B without WPA2.
Reopening. See discussion in #150.
Now I installed the MoodleBox 4.5.1 image in a microSD card .... this is the last MoodleBox image with Bullseye.
I started the Raspberry Pi 3B with this microSD card and it works! The MoodleBox wifi uses the security protocol WPA2. So it could not be the hardware. It must be something wrong in the software. Does WPA2 have parameters for the crypto method or the crypto depth.
Now I installed the MoodleBox 4.5.1 image in a microSD card
This bug is present in Debian Bookworm only (MoodleBox image 4.6.0 or later).
Yes, I wanted to be sure that the Raspberry Pi 3B can be an access point with WPA2. So I tested MoodleBox 4.5.1 with Debian Bullseye.
See https://github.com/moodlebox/moodlebox/issues/354 for a definitive fix.
See https://discuss.moodlebox.net/d/428-moodlebox-460-connexion-wifi-impossible.