-
Domácí síť
Spolehlivá a rychlá Wi-Fi síť
Snadná cesta k rozšíření dosahu vaší Wi-Fi sítě.
Spolehlivé připojení kabelem pro každou aktivitu.
Vše ostatní, co se vám bude hodit pro život online.
-
Chytrá domácnost
Dohlížejte na vše na čem vám záleží.
Povýší elektrická zařízení na vyšší level.
Speciální osvětlení pro každou příležitost.
-
Business
Vysokorychlostní kabelové sítě od L3 managed až po unmanaged
Business Wi-Fi řešení s centralizovanou správou
Chytřejší cloudové řešení pro podnikové sítě
Ideální pro bezdrátové širokopásmové sítě na velké vzdálenosti
-
ISP
Spolehlivá volba pro Wi-Fi do domácností.
Jednoduché a inteligentní řešení pro větší prostory.
Vstupní brána k internetovému připojení.
Malé switche pro snadné pokrytí A-ISP potřeb.
Do I need to keep controller running when using portal authentication?
Available portal authentication methods in EAP/Omada Controller include No Authentication, Simple Password, Local User, Voucher, SMS, Facebook, External Radius Server and External Portal Server. If you are not familiar with the configuration please refer to FAQ 896.
After the configuration, you may raise the question whether you should keep the EAP/Omada controller running. The simple answer is yes. To make the most use of portal authentication; you should keep it running.
The table below lists the behaviors of each authentication type when controller is online and offline.
Authentication Type |
Controller Online |
Controller Offline |
No Authentication |
|
|
Simple Password |
|
|
Voucher |
|
pass the authentication
|
Local User |
|
pass the authentication
|
SMS |
|
pass the authentication
|
|
|
pass the authentication
|
External Radius Server |
|
|
External Portal Server |
Portal page and authentication both provided by portal server |
pass the authentication
|
Summary:
- For Voucher, Local User, SMS, Facebook and External Portal Server authentication the controller should stay running since all client keep the previous authenticated states or it would no longer provide authentication. Clients who have passed the authentication before the Controller is down can access the Internet while the rest client devices have no means to finish the authentication and cannot access the internet.
- For other authentication types, it works to some extent when EAP/Omada controller is offline. But the clients will not be able to see the customized logo and background image. When client moves from one EAP to another, the portal page will pop out again even the authentication do not “time out”. So, to make the best use of portal authentication, please keep the controller running.
Note: The mechanism of portal has been changed, when EAP is disconnected from the Omada Controller, clients cannot authenticate successfully. (This change only takes effect on the firmware which are released after July 2019. )
Your feedback helps improve this site.