I set my wifi SSID and password with medkit
WPA3+WPA2 fallback sounds like a good solution. Medkit seems to hardcode “WPA2 only” though, which is of course an issue
Do you have any WPA3-only devices? If not, WPA2-only AP is the safer option. For example, my 10 year old notebook doesn’t see WPA3+WPA2 APs, only those with pure WPA2. So to have the largest chance that the user will be able to connect to a freshly flashed device, WPA2-only seems to me to be a better option.
2 Likes
I have no wpa2-only devices, so no idea. As WPA2 fallback is so common I assumed that this would make old devices work.
WPA3 is software not hardware, right? Is your laptop running EOL software?
I generally agree with that logic, as medkit seems to really only be made for setting up without ethernet. But it would be nice for faster deployments
Some devices are reported to have issues with WPA2/WPA3 mixed mode. I am using WPA2 only personally for best compatibility.
1 Like
I think this is a too big simplification. I think at least support in the card’s firmware (or even some HW circuitry) is needed. Of course, there were cards initially released with WPA2 only which got WPA3 support later, but I think that was exactly by a firmware or microcode update…
Define EOL 
Win 10 is not yet EOL. But the wifi card Intel AC7xxx definitely did not receive any update in the last few years…
This is exactly the problem I face with my laptop…
1 Like
This topic was automatically closed 3 days after the last reply. New replies are no longer allowed.