There are a few problems here, all relating to the comment and case of "mixed"
First and most importantly, setting wpa=3 causes hostapd to exit with an error and not bring up any configured ssid on the given radio.
Second, this was found when trying to set wep+mixed, which matches on mixed and completely breaks not only the wep setting, but the entire radio config. this should likely be changed to {wpa,psk}-mixed* or something similar to avoid colliding with wep+mixed. This will still leave those settings broken (as wpa=3 appears to be invalid) but at least it won't improperly break wep+mixed as well.
Lastly, wpa3 is going to be a thing soon, so whatever is expecting wpa=3 is likely wrong and should be updated.
The text was updated successfully, but these errors were encountered:
respectfully, you are half correct. your second comment is correct, wpa=3 is valid and wasn't what caused my failure. in appropriately adding wpa=3 to a wep network caused the error.
ZeroChaos-:
In file lib/netifd/netifd-wireless.sh the following code is found:
There are a few problems here, all relating to the comment and case of "mixed"
First and most importantly, setting wpa=3 causes hostapd to exit with an error and not bring up any configured ssid on the given radio.
Second, this was found when trying to set wep+mixed, which matches on mixed and completely breaks not only the wep setting, but the entire radio config. this should likely be changed to {wpa,psk}-mixed* or something similar to avoid colliding with wep+mixed. This will still leave those settings broken (as wpa=3 appears to be invalid) but at least it won't improperly break wep+mixed as well.
Lastly, wpa3 is going to be a thing soon, so whatever is expecting wpa=3 is likely wrong and should be updated.
The text was updated successfully, but these errors were encountered: