Moode 8 slow boot

[Tim Curtis]

No need for anything in the WenUI. The workaround can be applied to the nmconnect file during startup based on pi model.

Does the Zero W also need the patch to 'wpa' applied?
Nvm, because only the 8 series is available for this pi model.

[philrandal]

I don't like forcing WPA in all cases on a Pi 3B when it's only needed if accessing from a mobile device.

I'll try to do some more testing this weekend to see if I can find a better fix.

[Opera]

I thank you for all your efforts and availability; for me it is very important to be able to use AP when I do not have internet available. Otherwise I would be forced to use exclusively Moode 8.
Thanks, thanks very much!

[Tim Curtis]

I don't like forcing WPA in all cases on a Pi 3B when it's only needed if accessing from a mobile device.

I'll try to do some more testing this weekend to see if I can find a better fix.

It would only be used for the Hotspot and not generally for WiFi so I think its prolly ok.

[TheOldPresbyope]

I don't like forcing WPA in all cases on a Pi 3B when it's only needed if accessing from a mobile device.

I'll try to do some more testing this weekend to see if I can find a better fix.

It would only be used for the Hotspot and not generally for WiFi so I think its prolly ok.

Nice detective work going on here. I wish I had time ATM to do more than drive-by posting

It's not that I disagree with your assessment, Tim, but it still makes me feel cringy to even say "WPA". Needs must, I suppose.
 
In the case of the Pi3B, at least, an easy workaround which works with an unmodified moOde 9.2.3 is to use an external USB-WiFi adaptor and disable the internal WiFi.  It has to be an adaptor which supports AP mode, of course. My old CanaKit adaptor works fine in this application.

ETA: looks like I have to eat crow on this one. It works fine with my Pi 400 as the connecting device. Turns out my Pixel 6a and iPad don't like it at all. Sorry.


Kent

[philrandal]

More testing.

What the Android WifiAnalyzer app reports:

With

group=ccmp
pairwise=ccmp
proto=rsn

Pi4 (can connect from Android):

WPA2-PSK+PSK-SHA256-CCMP
RSN-PSK+PSK-SHA256-CCMP

Pi 3B (cannot connect from Android)

WPA2-PSK-CCMP+TKIP
RSN-PSK+PSK-SHA256-CCMP+TKIP

PI 3B and pi 4 with proto=wpa (can connect from Android)

WPA-PSK-CCMP-TKIP

God only knows where the problem is. I don't know enough about wifi protocols to be able to understand a wireshark capture, so I'm unable to explore any deeper.

[philrandal]

It's frustrating when you find old threads on the Raspberry Pi forum which describe the issue but offer no solution apart from reverting to the old hostapd way of doing things:

https://forums.raspberrypi.com/viewtopic.php?t=341580

[Tim Curtis]

I still wouldn't worry about using wpa instead of rsn for Pi3B and Hotspot because it's a niche usage scenario. If it were Pi3B and General WiFi then it would be a no-go for me.

[the_bertrum]

Should this thread get a new name?

[TheOldPresbyope]

Whatever the thread title, I can confim git commit c017eb7121af612f..., "Fix for Hotspot fail on Pi-3", makes it possible for me to connect to an Pi 3B installation of moOde 9.2.3 from

- my laptop (Linux Mint 21.3, based on Ubuntu 22.04, on an old ThinkPad)
- my iPad (iPadOS 18.2.1)
- my Pixel 6a phone (Android 15)
- my Pi 400 (current Raspberry Pi PiOS Desktop edition)
(I'll get around to trying a Win10  laptop later but I expect it to work)

This is true whether I use the Pi's internal WiFi or disable it and use an external USB-WiFi adaptor (a CanaKit in this case).

To repeat myself, nice detective work, @philrandal )!

Regards,
Kent