Skip to content

Check the connection method and validation evidence for every available WiFi integration path. Open the compatibility centre

Product
All features How it works Guest WiFi portal Campaigns & automations Reviews Analytics All integrations
Solutions
Restaurants Cafés Hotels Bars & pubs Retail Gyms Salons
Hardware Pricing
Resources
Resources Guides Launch checklist Glossary Help centre
Log in Start free

Step-by-step guide

CoovaChilli UAM setup

Connect a compatible CoovaChilli gateway with a UAM-secret-bound challenge and RADIUS-backed access.

Guide 8 of 8 5-10 minute read Operator checklist

Before you change anything

  • Confirm the correct venue
  • Keep current settings handy
  • Test with one device first

Connect CoovaChilli UAM

Use this beta integration for a compatible CoovaChilli gateway using its standard external UAM flow. openNDS FAS is a different protocol and is not represented by this adapter.

Setup

  1. Install CoovaChilli on the router.
  2. Create a separate guest interface and DHCP network.
  3. Open WeefyBox Setup and choose CoovaChilli UAM.
  4. Copy the portal URL and walled-garden list. Get the public RADIUS host and ports from the RADIUS operator.
  5. Set the external UAM portal URL to the WeefyBox value.
  6. Enter the same UAM secret on the router and in WeefyBox.
  7. Configure RADIUS authentication on UDP 1812.
  8. Configure RADIUS accounting on UDP 1813.
  9. Add every walled-garden domain.
  10. Use the CHAP challenge flow. WeefyBox derives the response from the challenge and matching UAM secret and never puts the generated RADIUS password in the browser URL.
  11. Restart the hotspot service.
  12. Run Test my setup in WeefyBox.
  13. Join the guest SSID and complete the portal within five minutes.
  14. Confirm the authorization and accounting result in Portal debugger.

Troubleshooting

| Problem | Check | |---|---| | Portal loops | UAM URL, walled garden, and guest-interface DNS | | Challenge rejected | UAM secret, clock, and the five-minute state lifetime | | Login succeeds without internet | Firewall forwarding and RADIUS acceptance | | Returning guest is unknown | Stable private MAC setting and captive-browser cookie handling |