Reset Search
 

 

Article

External Captive Portal Redirection fails because of Static Route configuration

« Go Back

Information

 
TitleExternal Captive Portal Redirection fails because of Static Route configuration
Symptoms
  • External Captive Portal Redirection fails because of Static Route configuration
  • ECP redirection fails but using the IP address of the web server works
  • We see some DNS responses working, but others failing on the same Topology
  • One ECP WLAN is working while a new ECP WLAN is failng
Environment
  • ExtremeWireless
  • Version 10.41.14
  • All versions
  • ECP
  • Captive Portal
  • Redirection fails
Cause
  • Invalid Static Route configuration was causing the client to fail to communicate to the ECP and be redirected from the Controller
Resolution
  • Deleting the static route resolved this issue and the client was redirected
Additional notes
Recommendation: When you create the Captive Portal WLAN and associated configuration, use the VNS Wizard.  This will add in the Topology that is used and the routes will show as "Connected" in the forwarding table. Creating static routes is not necessary. 

Feedback

 

Was this article helpful?


   

Feedback

Please tell us how we can make this article more useful.

Characters Remaining: 255