02-15-2023, 01:04 PM
(This post was last modified: 02-15-2023, 02:23 PM by TheOldPresbyope.
Edit Reason: added ETA
)
@adam_zzz
My Pi3A+ Rev 1.0 has worked flawlessly for several years in WiFi client-mode against various access points from both my old and my new ISP, in both cases with WPA2-PSK. A quick check now with moOde 8.2.5 and I see the same firmware info in the dmesg output that you reported.
ETA I should have mentioned the connection is using CCMP Group and Pairwise ciphers, not TKIP. Some refer to this mode as WPA2-AES.
As suggested previously, this seems an issue better raised in the Raspberry Pi forum (or even their github repos) where the RPF's code jockeys hang out.
Regards,
Kent
My Pi3A+ Rev 1.0 has worked flawlessly for several years in WiFi client-mode against various access points from both my old and my new ISP, in both cases with WPA2-PSK. A quick check now with moOde 8.2.5 and I see the same firmware info in the dmesg output that you reported.
ETA I should have mentioned the connection is using CCMP Group and Pairwise ciphers, not TKIP. Some refer to this mode as WPA2-AES.
As suggested previously, this seems an issue better raised in the Raspberry Pi forum (or even their github repos) where the RPF's code jockeys hang out.
Regards,
Kent
