cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
Announcements
1361
Views
5
Helpful
2
Replies
Highlighted
Beginner

WAP371 Captive Portal cluster not syncing authentication

Hi All

problem - user has to re-authentication when passing from one AP to the next, from one floor to the next.

Set up is WAP371 Cluster between 3 APs on 3 floors through a Single switch, it has a Single SSID and the endpoints can maintain connectivity between APs when roaming between floors, but not with Captive portal on. 

Problem is when I activate the Captive Portal, every time the device moves to another AP, it has to re-authenticate. I am only using basic GUEST authentication and default group.

Do the APs have to have a strong overlapping signal for the authentication to flow through from AP to AP?   

2 REPLIES 2
Highlighted
Enthusiast

Did you manage to find a solution to this issue?

Highlighted
Cisco Employee

Hello,

 

At first sight, there should be no problem with the WAP371 clustering and the Captive Portal reauthentication since the Captive Portal settings are propagated through the cluster (Single Point Setup). 

A possible solution would be on the Guest network (Captive Portal) to use WPA Enterprise authentication with enabled pre-authentication. This way WPA2 wireless clients will send pre-authentication packets so the pre-authentication information is relayed from the WAP device that the client is currently using to the target WAP device. Enabling this feature can help speed up authentication for roaming clients who connect to multiple APs. Also, make sure you have checked Session Timeout and Away Timeout settings on the instance configuration of your Captive Portal.

 

Hope this help,

Regards,

Martin