- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
No IP as splash URL possible (WAX610)
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Dear Pro's,
yesterday I updated the FW on my WAX610 (10.8.6.3), since then I can no longer specify an IP for the splash URL for a captive portal (see error message in fig.1). Is that a bug? Before I did the update, I was able to specify an IP there and everything worked fine. The CP that has already been set up still works, but I can't set up a new one. How can you solve the problem?
fig.1
Solved! Go to Solution.
Accepted Solutions
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Dear Schumaku,
thank you for your reply.
Yes, you're right, there weren't enough details.
And yes, it is an external captive portal. With the previous FW version it wasn't a problem.
But I "solved" the problem differently by using an OPNsense device for it.
Thank you very much and kind regards
All Replies
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: No IP as splash URL possible (WAX610)
Just a little bit vague what exactly you wanted to configure. Reading about a Splash Page URL leads me to the idea you talk of an External Captive Portal config in a much less common way. Please also provide some sample URL you try to configure, using just an IP address, instead of the more common DNS name. The point is the plain error message does not say that much to the interested reader like me. Did the previous installed firmware allowed to configure this splash URL? Thank you for helping Netgear (I'm not Netgear) a little bit more.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Dear Schumaku,
thank you for your reply.
Yes, you're right, there weren't enough details.
And yes, it is an external captive portal. With the previous FW version it wasn't a problem.
But I "solved" the problem differently by using an OPNsense device for it.
Thank you very much and kind regards