WiFiLAN deployment scenarios

WiFiLAN is a hosted, centralized software solution for managing public access networks. WiFiLAN is generally deployed in the cloud or on a server in the data center. WiFiLAN is multi-tenant application so it can support several customers on the same server. 

We generally deploy WiFiLAN is a redundant architecture to ensure maximum uptime and failover in case of problem with the primary server. The diagram below shows a typical WiFiLAN architecture.


Distributed Architecture

When deployed in distributed architecture, WiFiLAN is responsible for providing centralized hotspot management services to remote gateways or controllers. Each hotspot venue contains one or more hotspot gateway/controller, which is responsible for managing the hotspot service at the venue. The gateway is also responsible for issues DHCP leases and handling user sessions.



WiFiLAN is deployed in the primary NOC behind a firewall. The secondary NOC hosts the backup instance for failover and redundancy. Hotspot gateways are configured to work with the WiFiLAN services. These gateways communicate with the WiFiLAN servers over the Internet.


Centralized Architecture

In case of centralized architecture, WiFiLAN is deployed in a central NOC / data center along with a central access controller. Each hotspot venue contains one or more access points which communicate with the central controller over the Internet or private network. 

Centralized architecture requires access controllers that can manage access points over the Internet (Layer 3) and a single DHCP service running in the data center. The traffic from the access point is routed through the access controller to the Internet. 

The diagram below shows the centralized architecture in more detail.


Have more questions? Submit a request


Please sign in to leave a comment.