11-25-2023 07:24 AM
~I have been struggling and failing to get a captive portal working on our 3 cisco wap150s.
I think I have set it up in accordance with the admin guide but it doesn’t work. The relevant SSID appears that when clicked displays a dialog box saying “Enter Network Security key” the key concerned being the wpa key, apparently, because using this it connects but has no connectivity. No signs of the portal web page.
I attached images of relevant parts of the configuration with names changed
I would be grateful for suggestions how to progress this.
BTW the enable check box for the various tables page appears to be permanently set – is this relevant?
11-25-2023 08:38 AM
- Check logs on the wap 150 when trying to connect ; as far as the captive portal being used is concerned check it's http or https logs (look for activity , if any) ; also advising to use the latest firmware on the wap 150 ,
M.
11-25-2023 12:51 PM
Thanks your suggestions but have set logging to debug, only items of any interest were client auth/deauth, connected/disconnected entries. Am running latest firmware 1.1.4.
11-26-2023 10:06 AM
- You didn't respond to this part of my question :
>as far as the captive portal being used is concerned check it's http or https logs (look for activity , if any)
M.
11-26-2023 11:41 AM
11-27-2023 01:04 AM
>....Sorry, I don't fully understand that suggestion
- Suppose the captive portal being used is called : mycaptiveportal.com ; what I was asking is to logon to mycaptiveportal.com , find where the logs from the webserver are and examine them if anything can be seen when a user tries to connect with WPA2 from the CBS.
M.
11-28-2023 07:32 AM
11-29-2023 05:30 PM - edited 11-29-2023 05:31 PM
Unfortunately very few of us here have used the WAP products so are not familiar with them.
Have you followed the admin guide?
https://www.cisco.com/c/en/us/td/docs/wireless/access_point/csbap/wap150_361/Administration/Guide/EN-US/b_WAP150_361_Admin_Guide/b_WAP150_Admin_Guide_chapter_0111.html#id_104281
11-30-2023 12:42 PM
12-01-2023 04:56 AM
Untagged = native VLAN. Meaning any untagged traffic will be treated as if it was in that VLAN. Generally speaking the untagged/native VLAN should match on both sides. Tagged VLAN 1 traffic should still be accepted even if it's configured as untagged but some devices may require it to be untagged, and could drop the frames if they are tagged, so best just to make sure the settings match on both sides.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide