Setup module to support WPA3 Wi-Fi networks #555
Conversation
corneliusclaussen
force-pushed
the
feat-support-wpa3
branch
from
71d8e75 to
2959b26
Compare
james-ctc
force-pushed
the
feat-support-wpa3
branch
from
2959b26 to
7febcb5
Compare
|
Not sure if related to this PR, but during testing I found that configured networks often publishes empty messages in between: |
Not a bug, I had a second wireless device that had no configured networks |
|
Tested on WPA3 and WPA2 and mixed WPA3/2 networks |
|
re-reading the README for the Setup module and the configured networks list should be a single list rather than a list per wifi network device. |
No a joined list of all interface is returned as described in the README |
Signed-off-by: James Chapman <[email protected]>
WpaCliSetup extended to support open, WPA2 and WPA3. By default it attempts to configure based on the existing arguments. set_network can take an additional argument to explicitly choose the network security type. (this could be an additional parameter over MQTT). Note: WPA3 doesn't support pre shared key (64 hex ditits), it requires the password/passphrase. Hence over MQTT a quoted "psk": "\"thePassphrase\"" is required and not the output from the wpa_passphrase command. Signed-off-by: James Chapman <[email protected]>
Signed-off-by: James Chapman <[email protected]>
Signed-off-by: James Chapman <[email protected]>
Previously configured_networks published an array per wifi device which resulted in empty arrays where a device had no configured networks. Signed-off-by: James Chapman <[email protected]>
corneliusclaussen
force-pushed
the
feat-support-wpa3
branch
from
a27f7bc to
571eaf4
Compare
background
wpa_clisupports the configuration of WPA2 and WPA3 networks. However WPA3 doesn't support a pre-shared key (the output from the wpa_passphrase command), it always requires the plain text passphrase.By default the update will try and configure dual support for WPA2 and WPA3 based on the "psk": "" MQTT parameter
i.e.
additional
it is common for WiFi configuration to require the security being applied. Adding an additional parameter would allow EVerest to fully configure the network (and perhaps support more options: WEP, WPA2 Enterprise mode ...)
The WpaCliSetup has been updated to support network configuration with an additional parameter to indicate the network security to apply. This should make it easier to support new modes alongside an MQTT interface update.