The ZeroShell Captive Portal is composed of two modules: the Web Login server and the Captive Gateway. What is the advantage of such modularity?
The Captive Gateway functionality acts as a gateway (router or bridge) which, for the yet to be authenticated clients, prevents access to a protected LAN zone and forwards only the requests on ports 80 (http) and 443 (https) to a Web Login server (also called the Authentication Server). The task of the latter is to present an authentication web page to the user to insert a username and password. If authentication has a positive outcome, the captive gateway removes the barriers for the authenticated client and allows access to the protected zone. Separating these two functionalities into distinct modules is advantageous because a multi-gateways structure can be created in which multiple captive gateways protect the different networks, which are also geographically distanced and which use the same web login server. By doing so, the customisation of the login and accounting web page take place in one place only instead of on each gateway. • I want to create a multi-gateway structure with
Related Questions
- I want to create a multi-gateway structure with the ZeroShell Captive Portal. What is the maximum number of captive gateways I can have on the same web login server?
- What are the authentication sources used by the ZeroShell Captive Portal web login server to validate users?
- Can the ZeroShell Captive Portal use a RADIUS server as an authentication source?
