Custom webauth settings in between Anchor & Foreign
We have implemented a new wireless mobility guest SSID in between the anchor and multiple foreign controllers.
We are using a custom webauth page, written by the customer, which was working great.
Since we've upgraded to 184.108.40.206, we receive a couple of complaints from users saying that they receive the default Cisco web auth login page, instead of the custom. But, after they successfully logged on, they see the successfull page of the custom webauth package? Which seems quite strange. It seems like the webauth pages from the default Cisco one and our custom are getting mixed during the authentication process.
I have read in the mobility design guide about which settings should be absolutely identical in between the anchor & foreign controller(s).
So I've checked them and I see a difference in the web auth settings, under the security tab in the WLC, which tells the controller if it must use the default internal page, or a custom one. We've uploaded the custom web-auth package only to the anchor controller. The foreign controller have this option set to "Internal (default)".
Do we need to upload the same custom webauth .tar package to all of the foreign controllers to mitigate this?
It seems I can't find it in any ofthe cisco docs available..
Transferring Crash file from standby: Login to the Active WLC in HA.
From CLI: (Cisco Controller) >transfer upload datatype crash (Cisco
Controller) >transfer upload filename (Cisco
Controller) >transfer upload mode tftp (Cisco Controller) >transfer
This is the start of a display filter cross reference between Wireshark
and OmniPeek. The 1st installment is a table of advanced filters. More
filters will be added as time allows. It is a living doc, so check back
for changes every so often Please feel f...