We use several (80) wireless bootp devices in our network. They of course have been running great on autonomous APs but refuse to work on our WLC wlans. I did a packet capture on the vlan only to find that the wlc 4404 is retagging the bootp packet source as it's own IP instead of 0.0.0.0 This of course causes the bootp server to send out a bootp reply specifically to that IP instead of a broadcast (where I hope the WLC would behave normally since broadcast forwarding has been enabled).
I'm running version 18.104.22.168 and the results are identical on our 4404 and 4402. I'm out of ideas guys any advice?
proper.pdf shows the process on an autonomous AP at packet 1 and 5. Other packets show the same process through a WLC.
Okay, well if your DHCP Server doesn't like proxied requests, you've got three options;
1 - Use a DHCP server that will accept proxied requests like a Cisco Switch, the WLC it's self, a Microsoft Server, etc...
2 - Scrap lightweight and go back to IOS
3 - Employ H-REAP, which will then bridge traffic straight on to a VLAN from the AP. This means it won't go via the WLC, and the requests will therefore go un-altered. H-REAP requires 1030, 1130, 1240 or 1250 APs, and the switchport to be altered to a Trunk port.
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...