Heads Up :
The post you are writing will appear in a public forum. Please ensure all content is appropriate for public consumption. Review the employee guidelines for the community here.
Here's our topology:1130 series APs -> 4400 series WLC (mgmt vlan 51, client dynamic interface vlan 360) -> Catalyst 4500 series -> DHCP server (vlan id 11)We appear to be unable to relay DHCP requests from a wireless client on VLAN 360 to the DHCP s...
Well the option to have "disable dhcp proxy" as a configurable option on the WLC makes it just all the more confusing And just to report on what we're seeing: the virtual interface for the wireless VLAN is proxying the DHCP (say 10.5.18.2 on vlan id...
We resolved this yesterday too.That is exactly how the controller is behaving - as their own DHCP relays. The catalyst never participates as the ip address helper. (Basically the DHCP server sees the request as coming from the actual WLC virtual inte...
Because the interface dhcp settings didn't work, I added the same dhcp server to the dhcp override. I can back out this change, but obviously it still isn't working.At this point we're going to sniff between the WLC and the Catalyst to see if there a...
Since I can manually configure the wireless client to have an IP in vlan 360 and everything works fine that way, then it appears that vlan 360 is trunked correctly.
the DHCP server is ISC DHCPD 3.0.1. Now, I do have 'one-lease-per-client true' set on this pool, _but_ this does not explain why the dhcpd logs do not show any wlan-associated IPs trying to get an IP in the first place.
