I am really stuck on a DNS issue we have with our Wireless Guest Access setup.
Hope to keep it as short as possible..
Setup with one anchor controller v220.127.116.11 centrally placed in our DC and several controllers placed on site at our offices. The guest wlan has been setup and mobility groups are up/up.
The anchor controller has been setup with a dhcp scope with isp dns servers.
I made a custom web-auth page and successfully uploaded.
I also installed a web-auth certificate with the right CN that meets my virtual interface domain hostname.
When i make connection and try to surf my redirect doesn't work. When i then delete the hostname on the virtual inteface and just setup 18.104.22.168 the redirect works when i enter 22.214.171.124. Redirect then for and external url like for example google.com doens't work while the ext ip of a url redirects succesfull.
I setup the 126.96.36.199 on my internal dns server but i acctually don't know how this resolving takes place because you don't setup internal dns servers..
Also i checked the whole path after the controlllers to the internet and my dns request to the outside world is successfull so it seems a local resolving issue on my controller.
Hope anybody could help me out because i am stuck on this..
Insure that the client actually is showing on the anchor controller. If not, then your EoIP tunnel isn't up. Eping and Mping to verify that the tunnel is up. If you can Eping and Mping the tunnel is up and you likely are suffering from a known bug issue. Look up CSCsu82045 and I'm sorry to say that in 5.2 there is no work around.
Correct me if I'm wrong, but it isn't your clients DNS to the outside world that is a problem, it is that you assigned a dns name to your virtual IP?
If I understand what you're saying though, you are providing these clients with public dns servers, so they will not be able to resolve the dns name assigned to your virtual interface.
In order to have a dns on your virtual interface, you're going to need to specify your clients dhcp to provide the internal dns servers (and allow for proper routing). Otherwise, you'll have to get rid of the dns name on the virtual interface.
Or are you saying that the clients can't resolve any dns?
When i assign a DNS name to the VIP address the redirect doesn't work.
When i delete the hostname and just fill in 188.8.131.52 the redirect works directly to the VIP address BUT: when i then try to connect to for exmaple google.com dns also doesn't work, redirect only works when entering public ip's. But i am sure the route to the internet works because i see traffic going out to the right dns server of my isp. Maybe someone could explain how resolving of the VIP hostname works because i can't setup any dns servers on my management interface. I should say for the clients that only public dns servers should be needed.
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...