Closed renzenicolai closed 2 years ago
See also: https://wiki.mch2022.org/Network
Cool so we need enterprise WPA support :smile: , that's going to be fun
With the enterprise WPA2 enterprise support almost finished, i think we need to talk about storing networks. The firmware has references to a list of known networks, but currently there is no such thing. How would we go about making and keeping track of this list?
Storing the preferred wifi network in a file would help a lot. then the apps would be able to access the crendentials when connecting to wifi. Handling multiple networks would make things more complicated for 3rd party firmwares. That also means scanning the local network and selecting a matching SSID.
But on a day to day basis after the event it would be nice to handle different SSID's.
The credentials just changed:
MCH2022
mch2022
mch2022
The basic menu has been tested as well. Could anyone verify this?
Branch: https://github.com/badgeteam/mch2022-firmware-esp32/tree/wifi_test
I tested with FreeRadius and a NetGear R7000.
Network settings:
It has yet to be tested, but the latest commits on master have the new WiFi defaults, which comply with NOC requests.
I've contacted the NOC and it seems that we need to use the
MCH2022-legacy
network. This is because the ESP32-WROVER-E doesn't support 5GHz WiFi (the recommended type). The network will be encrypted usingWPA2 802.1X
, using any username and password (they don't check those).