I love my fleet of Comets! I was hoping to upgrade my “plain” Comets (RM-1) to Comet Pro for units but hit a bit of a snag - the wifi connection on the Pro is really barebones, especially for Enterprise environments… You can choose WPA-2-3 and nothing else, which is a problem in environments where other authentication protocols are used (like PEAP user based ones). If there is a different interface/config for such networks or I’m just missing something obvious, let me know.
FWIW I’m using fw 1.7.2 on the RM-10s
In my current setup the existing Comets (RM-1) are connected to an AX750, which I use as a wan/wifi/5G failover gateway, and even though the AX750 is a few years old it had more wifi auth options so I’m a bit bummed that the Pro is missing them
PEAP is an EAP certification method designed specifically for enterprise-grade WiFi.
The comet pro supports from WPA to WPA3, and it would match with the router that most of routers support the family standard(WPA2-PSK or WPA3-PSK).
After the match, the comet and router would make the best WIFI Security(most of time is WPA3).
Most of time, router as the AP would have more options of WIFI security.
Thank for your recommandation, more WIFI security would appear in our future product with the progress of WIFI security protocol.
Sure - I’m just thinking that Comet Pro has a significant enterprise / remote management appeal, so if there is a WiFi model, the need for supporting enterprise scenarios has a better RoI than an average WiFi client. EAP is not exactly dark magic, most of the gl.inet routers support it in client mode (hey, it’s all openwrt and wpa-supplicant right?), so it felt that it might be a low-hanging fruit.
I’m sure you have a feature priority list - just highlighting this (would have been) a very useful feature for those dealing with remote KVM scenarios in enterprise networks. For me it would have been a nifty way to reduce cabling/gear bulk, and/or avoid single points of failure (like with the AX750 setup I have).
