Currently, the Omada Controller manages WLAN networks on a per-site basis, where each site typically operates with its own gateway. However, many real-world deployments—such as city-wide public Wi-Fi or campus networks—require multiple physically separate sites (each with its own router) to be managed under a single controller, while providing a seamless guest Wi-Fi experience across all sites.

Example Scenario:
A user connects and authenticates to the guest Wi-Fi network at Site A (Downtown). Later, the same user moves to Site B (Bus Terminal), losing connection in between. Upon arrival at Site B, the system should recognize the previous authentication and grant access without requiring the user to log in again.

In addition to the current per-site captive portal model, introduce the option to design and manage a single, centralized captive portal that can be applied across multiple sites.

Benefits:

• Improved user experience: Log in once, stay connected across locations.

• Ideal for city-wide networks, transport hubs, campuses, or event venues.

• Reduced administrative effort and fewer helpdesk tickets due to login issues.

• Simplified portal management through centralized configuration.

Use Cases:

• Public city Wi-Fi (e.g., downtown, parks, bus stops)

• Transportation networks (e.g., train stations, bus terminals)

• Enterprise campuses with multiple physical locations

• Distributed events with shared internet infrastructure