09-24-2019 01:01 PM - edited 07-05-2021 11:02 AM
Hi Gents,
Hope you can help me out here... Hope to friday when i left the WIFI was working fine, but when i got in yesterday i found out that guest WIFI doesn't work.
Client gets IP address provided by the WLC, associate with the controller but never get to the web auth. In fact the client keeps re-assocaited and never get connected.
A quick background here: The guest clients go straight to the internet via a dedicated interface on the ASA. Therefore, the traffic does not touch our internal network. However, when checking the ASA interface associate with the WLC, it says 0 packet which means the traffic never makes it to the ASA. But debug on the WLC shows the traffic from one remote site all the way to the WLC at the DC.
Any ideas, suggestion will be greatly appreciate.
Thanks,
Solved! Go to Solution.
09-24-2019 02:26 PM
Quick update here gents.
It appears our ASA has failed over the weekend and the config of the guest wireless interface does not have a stanby IP address; therfore, that interface does not received traffic when the device failover! The issue now, i can fail back since i don't know why the primary device has failed. Will wait after hours to test and update all of you.
Thanks,
09-24-2019 02:17 PM
Hi
If client does not receive portal, soon they will not be authenticated and consequently no traffic will be generated. Considering we are talking about only Guest network here.
One reason client does not get the portal is DNS. If DNS fail or is no properly configured, then, portal does not pop up.
Another reason is ACL. Depending on how guest is configured, it is expected that AP push an ACL to the client in order to guest work properly. If that does not happen, then, client will not be redirected.
-If I helped you somehow, please, rate it as useful.-
09-24-2019 02:39 PM
09-24-2019 02:26 PM
Quick update here gents.
It appears our ASA has failed over the weekend and the config of the guest wireless interface does not have a stanby IP address; therfore, that interface does not received traffic when the device failover! The issue now, i can fail back since i don't know why the primary device has failed. Will wait after hours to test and update all of you.
Thanks,
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