12-06-2012 07:12 AM - edited 07-03-2021 11:11 PM
12-06-2012 07:33 AM
well if you disable proxy, than the interface 'bridges' the DHCP packet to the wire. with proxy enabled it sends the request as a unicast to the server.
you could disable proxy as well, if you have the ip helper configured at L3. The only time that proxy is required is if the WLC is acting as a DHCP server.
HTH,
Steve
------------------------------------------------------------------------------------------------
Please remember to rate useful posts, and mark questions as answered
12-06-2012 07:16 AM
Under your interfaces on the WLC, did you go in and change the DHCP server to point to the new one?
HTH,
Steve
------------------------------------------------------------------------------------------------
Please remember to rate useful posts, and mark questions as answered
12-06-2012 07:19 AM
Hmm not on the Controller > Interfaces and each vlan.
Is this eqivalant to ip-helper like one would use on a cisco switch stack?
Think that is the problem? If I make a change, how long is the wireless down? A few seconds? A few minutes? I'd love to try it.
12-06-2012 07:22 AM
when you make that change, the WLAN will blip, but it's only for a second or two.
And yes, if you have DHCP proxy enabled, and it is by default, this is like an ip helper
HTH,
Steve
------------------------------------------------------------------------------------------------
Please remember to rate useful posts, and mark questions as answered
12-06-2012 07:30 AM
Ok yup, Controller > Advanced > DHCP
Enable DHCP Proxy is checked.
I had my head buried in the WLAN side and also AAA side. Because of moving from 2003 IAS to 2008 R2 NPS, I was racking my head on the new configuration with 2008 R2, the cerificates, etc... The event log made it appear that they authenticated fine though. Took a little longer than I wanted so I had to revert just to get people online.
Even if its a second or two blip, we may just make the change tomorrow morning and thoroughly test it before people arrive.
I didn't even think to check the lan side of the controller interfaces. Didn't think it cared where the DHCP server was, thought it just passed traffic to the 3750 switch it has a lag group on.
Thanks for pointing this out for me. I bet it will work when I try it.
12-06-2012 07:33 AM
well if you disable proxy, than the interface 'bridges' the DHCP packet to the wire. with proxy enabled it sends the request as a unicast to the server.
you could disable proxy as well, if you have the ip helper configured at L3. The only time that proxy is required is if the WLC is acting as a DHCP server.
HTH,
Steve
------------------------------------------------------------------------------------------------
Please remember to rate useful posts, and mark questions as answered
12-06-2012 07:40 AM
Oh ok! Thanks!
It sounds like in our configuration there's no reason for the WLC to proxy DHCP requests. I'm more familior with ip-helper on the appropriate vlans on the 3750 switch stack that this connects to. I'd rather manage it there to be honest. The appropriate vlan's are already trunked over to the switch.
On the switch stack itself the WLC is connected to these ports
interface GigabitEthernet1/0/23, 25, 27, 29
description Trunk Port to Cisco WLC
switchport trunk encapsulation dot1q
switchport trunk allowed vlan 1,5,172
switchport mode trunk
ip access-group acl1 in
channel-group 4 mode on
Example of vlans
interface Vlan1
ip address 10.1.0.254 255.255.0.0 //this is where the dhcp server lives
!
interface Vlan5
description wifi-private
ip address 10.5.1.254 255.255.0.0
ip helper-address 10.1.1.1
no ip redirects
no ip unreachables
no ip proxy-arp
!
interface Vlan172
description wifi-public
no ip address
ip helper-address 10.1.1.1
no ip redirects
no ip unreachables
no ip proxy-arp
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