WLC an DHCP
Hi,
I am wondering if the folowing is a valid configuration:
WLC: 5508
software: 7.3.101
I have a subnet (VLAN130) for management interface and I have 2 SSID/VLAN, 1 for corporate devices (VLAN160) and 1 for guest(VLAN20).
Corp devices gets IP from an Windows DHCP. It is working as well.
Smartphones/guest is geting IP from the WLC. It is working as well too. But I need to change it.
I am deploying a WLC 5508-HA and when the feature HA is enable, the WLC does not support the DHCP server feature anymore.
Is there a way for the user from guest vlan to get an IP Address, doing the request for my windows server on corporate vlan through the management interface?
Regards,
Murilo
Steve
In the past, it didn´t work. My customer had a Proventia Firewall, and when we tried, it didn´t work. He said me that the firewall was receiving the requests through "guest interface", then we let the DHCP on the WLC.
When we tried to do it, we were using the software version 7.0.98. I have faced and I am still facing so many bugs on Wireless Lan Controller , maybe this was another one.
Right now, the firewall is a ASA 5525 and the WLC software version is 7.3.101. We tried to move the DHCP to new ASA firewall, but we found a limitation too. The ASA supports a maximum of 256 DHCP address.
I received a Service request to solve this big issue, because on HA deployment was found this limitation on WLC.
If I move on with the deploy, then it should work fine, doesn´t it? The DHCP messages requests and answers goes through the management interface, are you sure about this?
thanks and best regards,
Murilo
Similar Messages
-
WLC Dropping DHCP Discover Packets
Hello
I have following setup:
[Notebook]----wired connection----[Cisco Lynksys wlan ethernet bridge] )))))) wirelessConnection ((((( [AP]-----[switch]-----[Router]-----[WLC]
I use a seperat DHCP Server. so on the WLC the DHCP Proxy is disabled.
what i know is - the WLC should receive and forrward he DHCP Discover to the layer3 interface on the router, where the ip-Helper is configured. From there it should go to the DHCP Server.
BUT - here comes the problem -
The WLC Dropps the DHCP Discover.
*DHCP Socket Task: May 05 16:06:26.153: 88:ae:1d:b7:b7:c2 DHCP received op BOOTREQUEST (1) (len 308,vlan 253, port 13, encap 0xec03)
*DHCP Socket Task: May 05 16:06:26.153: 88:ae:1d:b7:b7:c2 DHCP option len (including the magic cookie) 72
*DHCP Socket Task: May 05 16:06:26.153: 88:ae:1d:b7:b7:c2 DHCP option: message type = DHCP DISCOVER
*DHCP Socket Task: May 05 16:06:26.153: 88:ae:1d:b7:b7:c2 DHCP option: 61 (len 7) - skipping
*DHCP Socket Task: May 05 16:06:26.153: 88:ae:1d:b7:b7:c2 DHCP option: hostname = Test (len 4)
*DHCP Socket Task: May 05 16:06:26.153: 88:ae:1d:b7:b7:c2 DHCP option: vendor class id = MSFT 5.0 (len 8)
*DHCP Socket Task: May 05 16:06:26.153: 88:ae:1d:b7:b7:c2 DHCP option: 55 (len 13) - skipping
*DHCP Socket Task: May 05 16:06:26.153: 88:ae:1d:b7:b7:c2 DHCP options end, len 72, actual 64
*DHCP Socket Task: May 05 16:06:26.153: 88:ae:1d:b7:b7:c2 DHCP dropping packet (no mscb) found - (giaddr 0.0.0.0, pktInfo->srcPort 68, op: 'BOOTREQUEST')
Can anyone tell me why this happens?HI Chris,
First enable DHCP Proxy on WLC.
(Cisco Controller) >config dhcp proxy enable
and make sure that For DHCP proxy to work, a primary DHCP server must be configured on each controller interface that requires DHCP services.
To kow more about DHCO on WLC:
http://www.cisco.com/c/en/us/support/docs/wireless/4400-series-wireless-lan-controllers/110865-dhcp-wlc.html#Internal-DHCP
Regards
Dont forget to rate helpful posts -
Hi
My 5508 WLC which runs version 7.4.100.60 is configured as a DHCP server for the AP management and here's my problem:
Client can not get the address,I am in location at 1F of AP, obtain an IP address and associated to this AP, but I got to address is the address section 2F instead of 1F address above. In this WLC the AP, power and channel have not been optimized, the adjacent channels are AP 1, the power display is 1.
Last night I test, disconnect reconnect several times, I was able to get to the same network to a different IP address.My AP is 1602I. LoaderVersion 15.2<2> JAX . This is why ?Cisco Controller) >show interface summ
Number of Interfaces.......................... 17
Interface Name Port Vlan Id IP Address Type Ap Mgr Guest
management LAG 421 10.217.147.45 Static Yes No
redundancy-management LAG 421 0.0.0.0 Static No No
redundancy-port - untagged 0.0.0.0 Static No No
service-port N/A N/A 10.215.29.165 Static No No
t2-2f LAG 608 10.215.69.125 Dynamic No No
t2-1f LAG 609 10.215.68.253 Dynamic No No -
5500 Series WLC internal DHCP Server - Exclusion?
Hi there,
We're using the internal DHCP server on our 5500 Series WLC which works fine.
However on one WLAN we ran out of addresses so changed the subnet from a /25 to a /24.
The problem is that the router/gateway is still in the middle (124/125/126) and not easily changed.
I've moved the WLC interface to the top of the subnet (251) but the router is more difficult as its externally managed/controlled.
So is there a way we can create a DHCP pool of .1 through 250 on a /24 mask but exclude 124/125/126?
Thanks
Mike
PS - Router subnet masks were changed so can see whole subnet.Mike,
The WLC isn't a fully functional DHCP server, it only allows you to define what is in scope, not what is out of scope. Now if you have a cisco router/switch, you could use that for the DHCP server and specifically exclude the necessary addresses.
HTH,
Steve -
We have a WLC 2006 that is setup to distribute IPs to wireless clients using the internal DHCP server. Occasionally, wireless clients can connect to the APs (four 1131AGs) but do not get IP addresses assigned.
Rebooting the WLC temporarily fixes the problem.
software version is 4.0.155.0
anyone experiencing this or know of a solution?
thanks!Apparently, others have observed similar DHCP behavior.
You may want to read a related thread ("Wireless Clients eventually not issued DHCP through WLC4404") in the "General" conversation section.
LINK:
http://forums.cisco.com/eforum/servlet/NetProf?page=netprof&forum=Wireless%20-%20Mobility&topic=General&CommCmd=MB%3Fcmd%3Ddisplay_location%26location%3D.1ddc63fc -
Hello,
If I set a primary DHCP server in the interface configuration, or if I override DHCP in the WLAN Configuration.
Which interface does the WLC use to try and connect to the DHCP on behalf of the wireless clients?
IF
A) The dhcp server is not on any of the configured subnets.
B) The DHCP server is on a different interface's subnet.
Sent from Cisco Technical Support iPad AppHello Stuart,
As per your query i can propose the following solution-
The interface will be Management interface
IF
A) The dhcp server is not on any of the configured subnets.
B) The DHCP server is on a different interface's subnet.
For more information you can go through the link-
http://www.cisco.com/en/US/products/ps6366/products_tech_note09186a0080af5d13.shtml
Hope this will work. -
Will the 2504 WLC internal DHCP give IP addresses to clients?
Is there a way to configure the 2504 WLC so that its internal DHCP only services the LAPs?
I don't want the controller to give out IP addressed to wireless clients.
ThanksNo.
DHCP on the WLC is never intended to offer DHCP services to any "wired" side devices, which includes your APs. These DHCP pools are specifically to hand addresses out to wireless clients attached to WLANs of the specific WLC it is configured on. Even then, unless you absolutely cannot offer DHCP somewhere else, DHCP on the WLC is not a suggested practice.
DHCP Pool Configuration and Restrictions.
http://www.cisco.com/c/en/us/td/docs/wireless/controller/7-6/configuration-guide/b_cg76/b_cg76_chapter_01000110.html -
WLC 5508, DHCP Problem after Update Cisco ASA(DHCP-Server)
Hello,
our Problem is, our Apple Devices get no ip adress from our Cisco ASA Cluster(ASA 9.1.2) over Wireless(Cisco WLC 5508). All other devices(Windows, Android,...) work correct, without problems. Our WLC is in HA-Mode.
Does anybody have an Idea?
Thank you very much and Best regards,
StefanHello again,
I hope this case is the solution.
https://supportforums.cisco.com/message/3942112#3942112
I will let you know after downgrade.
Best regards,
Stefan -
WLC 5508 Internal DHCP server issues
Hi,
I am hoping to get your feedback around the dhcp issues I am facing with Two Centrally Switched Wireless LANs. I have tried to explain the setup and the problems below and would appreciate it if anyone can suggest a solution for the problems I am facing:
The setup is as follows:
- I have a WLC 5508 which has been configured with 4 SSIDs, out of which 2 are using Central Authentication and Switching.
- I have an LWAP connected to the WLC in HREAP mode.
- WLC is configured as the DHCP server for clients connecting to the SSID 'Guest'. For the rest, I am using external dhcp server.
- Only one scope for Guest Interface is setup on the WLC.
Problems:
1. As far as I know, for WLC to act as internal dhcp server, it is mandatory to have the proxy enabled, but the Clients connecting to SSID 'Internet' are
unable to get an ip address from the external dhcp server, if dhcp proxy is enabled on the WLC. If i disable the proxy, it all works fine.
2. DHCP does not release the ip addresses assigned to clients even after they are logged out.
3. If a machine which was earlier connected to 'Guest' SSID connects to the 'Internet' SSID, it requests the same ip it was assigned by the WLC which it was assigned under 'Guest', but gets tagged with the Vlan configured on the management interface.
************Output from the Controller********************
(Cisco Controller) >show sysinfo
Manufacturer's Name.............................. Cisco Systems Inc.
Product Name..................................... Cisco Controller
Product Version.................................. 7.0.116.0
Bootloader Version............................... 1.0.1
Field Recovery Image Version..................... 6.0.182.0
Firmware Version................................. FPGA 1.3, Env 1.6, USB console 1.27
Build Type....................................... DATA + WPS + LDPE
(Cisco Controller) >show interface summary
Interface Name Port Vlan Id IP Address Type Ap Mgr Gu
est
guest 1 301 10.255.255.30 Dynamic No No
management 1 100 172.17.1.30 Static Yes No
service-port N/A N/A 192.168.0.1 Static No No
virtual N/A N/A 10.0.0.1 Static No No
(Cisco Controller) >show wlan summary
Number of WLANs.................................. 4
WLAN ID WLAN Profile Name / SSID Status Interface Name
1 LAN Enabled management
2 Internet Enabled management
3 Managment Assets Enabled management
4 Guest Enabled guest
(Cisco Controller) >show dhcp detailed guest
Scope: guest
Enabled.......................................... Yes
Lease Time....................................... 86400 (1 day )
Pool Start....................................... 10.255.255.31
Pool End......................................... 10.255.255.254
Network.......................................... 10.255.255.0
Netmask.......................................... 255.255.255.0
Default Routers.................................. 10.255.255.1 0.0.0.0 0.0.0.0
DNS Domain.......................................
DNS.............................................. 8.8.8.8 8.8.4.4 0.0.0.0
Netbios Name Servers............................. 0.0.0.0 0.0.0.0 0.0.0.0
(Cisco Controller) >show interface detailed management
Interface Name................................... management
MAC Address...................................... e8:b7:48:9b:84:20
IP Address....................................... 172.17.1.30
IP Netmask....................................... 255.255.255.0
IP Gateway....................................... 172.17.1.1
External NAT IP State............................ Disabled
External NAT IP Address.......................... 0.0.0.0
VLAN............................................. 100
Quarantine-vlan.................................. 0
Active Physical Port............................. 1
Primary Physical Port............................ 1
Backup Physical Port............................. Unconfigured
Primary DHCP Server.............................. 172.30.50.1
Secondary DHCP Server............................ Unconfigured
DHCP Option 82................................... Disabled
ACL.............................................. Unconfigured
AP Manager....................................... Yes
Guest Interface.................................. No
L2 Multicast..................................... Enabled
(Cisco Controller) >show interface detailed guest
Interface Name................................... guest
MAC Address...................................... e8:b7:48:9b:84:24
IP Address....................................... 10.255.255.30
IP Netmask....................................... 255.255.255.0
IP Gateway....................................... 10.255.255.1
External NAT IP State............................ Disabled
External NAT IP Address.......................... 0.0.0.0
VLAN............................................. 301
Quarantine-vlan.................................. 0
Active Physical Port............................. 1
Primary Physical Port............................ 1
Backup Physical Port............................. Unconfigured
Primary DHCP Server.............................. Unconfigured
Secondary DHCP Server............................ Unconfigured
DHCP Option 82................................... Disabled
ACL.............................................. Unconfigured
AP Manager....................................... No
Guest Interface.................................. No
L2 Multicast..................................... Enabled
(Cisco Controller) >show dhcp leases
MAC IP Lease Time Remaining
00:21:6a:9c:03:04 10.255.255.46 23 hours 52 minutes 42 seconds <<<<<<< lease remains even when the client is disconnected.
*********Example of Client connected to the right Vlan with an ip address from the incorrect interface. *************
(Cisco Controller) >show client detail 00:21:6a:9c:03:04
Client MAC Address............................... 00:21:6a:9c:03:04
Client Username ................................. N/A
AP MAC Address................................... a0:cf:5b:00:49:c0
AP Name.......................................... mel
Client State..................................... Associated
Client NAC OOB State............................. Access
Wireless LAN Id.................................. 2 <<<<<<<< 'Internet' SSID
BSSID............................................ a0:cf:5b:00:49:ce
Connected For ................................... 319 secs
Channel.......................................... 36
IP Address....................................... 10.255.255.46 <<<<<<< IP address assigned from the 'Guest' Interface or dhcp scope on the WLC
Association Id................................... 1
Authentication Algorithm......................... Open System
Reason Code...................................... 1
Status Code...................................... 0
Session Timeout.................................. 1800
Client CCX version............................... 4
Client E2E version............................... 1
QoS Level........................................ Silver
802.1P Priority Tag.............................. disabled
WMM Support...................................... Enabled
Power Save....................................... OFF
Mobility State................................... Local
Mobility Move Count.............................. 0
Security Policy Completed........................ Yes
Policy Manager State............................. RUN
Policy Manager Rule Created...................... Yes
ACL Name......................................... none
ACL Applied Status............................... Unavailable
Policy Type...................................... N/A
Encryption Cipher................................ None
Management Frame Protection...................... No
EAP Type......................................... Unknown
H-REAP Data Switching............................ Central <<<<<<<<<
H-REAP Authentication............................ Central <<<<<<<<<<
Interface........................................ management
VLAN............................................. 100 <<<<<<<<<<< right Vlan
Quarantine VLAN.................................. 0
Access VLAN...................................... 100Hi All,
I have a similar issue where Wireless clients are not receiving automatic addressing from an internal DHCP server. I have multiple interfaces configured on the WLC which are connected to separate VLANS. The manually specified DHCP primary server entry is the same on all interfaces. Some clients are able to authenticate and receive automatic IP configuration but some clients are failing the address assignment process. I have checked connectivity between the WLC and DHCP server, this is confirmed as working. When I carry out a "debug dhcp packet enable", I get the following outputs which seems as if the DHCP discover request from the client is skipped. Your thoughts and inputs on this are appreciated.
DHCP Socket Task: Nov 07 11:16:09.174: 00:22:fb:7b:37:32 DHCP option len (including the magic cookie) 76
*DHCP Socket Task: Nov 07 11:16:09.174: 00:22:fb:7b:37:32 DHCP option: message type = DHCP DISCOVER
*DHCP Socket Task: Nov 07 11:16:09.174: 00:22:fb:7b:37:32 DHCP option: 116 (len 1) - skipping
*DHCP Socket Task: Nov 07 11:16:09.174: 00:22:fb:7b:37:32 DHCP option: 61 (len 7) - skipping
*DHCP Socket Task: Nov 07 11:16:09.174: 00:22:fb:7b:37:32 DHCP option: requested ip = 169.254.223.5
*DHCP Socket Task: Nov 07 11:16:09.174: 00:22:fb:7b:37:32 DHCP option: 12 (len 13) - skipping
*DHCP Socket Task: Nov 07 11:16:09.174: 00:22:fb:7b:37:32 DHCP option: vendor class id = MSFT 5.0 (len 8)
*DHCP Socket Task: Nov 07 11:16:09.174: 00:22:fb:7b:37:32 DHCP option: 55 (len 11) - skipping
*DHCP Socket Task: Nov 07 11:16:09.174: 00:22:fb:7b:37:32 DHCP option: 43 (len 2) - skipping
*DHCP Socket Task: Nov 07 11:16:09.174: 00:22:fb:7b:37:32 DHCP options end, len 76, actual 68
*DHCP Socket Task: Nov 07 11:16:09.174: 00:22:fb:7b:37:32 DHCP Forwarding DHCP packet (332 octets) packet DHCP Socket Task: Nov 07 11:16:09.174: 00:22:fb:7b:37:32 DHCP option len (including the magic cookie) 76
Thanks,
Raj Sandhu -
Wireless dhcp issue after upgrading WLC to 7.6.100
Hi All,
We have upgraded our controllers to version 7.6.100. After upgrading, the access points also upgraded their version to 15.2(4)JB3. But, the problem is that after this process the APs do not get IP. It stays on this state:
*Sep 26 03:55:36.334: %CAPWAP-3-DHCP_RENEW: Could not discover WLC using DHCP IP. Renewing DHCP IP.
Not in Bound state.
The DCHP configuration is OK, since it is working in other two controllers we have and that we are not upgrading untill this issue is solved.
If we connect the APs via console and configure a static IP and controller's IP, the AP registers and works fine. But, the access points are located in 20 remote sites, so we would like to avoid going site by site.
Has anyone suffered this issue and knows how to "recover" those access points?
Thank you very mucho for your help!Hi,
Thank you for your answer conraddaniel.
But, our issue was an error on the DHCP. The DHCP server pool for the APs was configured with lease time infinite (on a Cisco 6500). After capturing the packets and debugging on the AP we realized that the AP were receiving wrong values:
DHCP: Scan: Renewal time: 2147483647
DHCP: Scan: Rebind time: 536870911
So, on the AP debugging we saw:
DHCP: Scan: Renewal time larger than Rebind time
On Cisco documentation:
T1 Timer(Renewal) After a certain portion of the lease time has expired, you attempt to contact the server that initially granted the lease in order to renew the lease so its IP address can still be used.
T2 Timer(Rebinding) If renewal with the original leasing server fails, because, for example, the server was taken offline, then you ideally try to rebind to any active DHCP server and try to extend its current lease with any server that allows it to do so.
These T1 and T2 timers can be any values, but must be less than the IP address lease duration. T1 Timer must be less than T2. Generally T1 is set to 50 percent of the lease duration and T2 is set to 87.5 percent of the lease duration. Use this rule to set T1 and T2 timers.
On the previous version of the WLC, the DHCP was configured in the same way and we confirmed that the APs received same times, but they ignored those wrong values.
The workaround was to modify the lease time of the DHCP pool (1 day). This way, both timers had valid values and the APs accepted the DHCP OFFER. We still do not know why with lease infinite these timers have wrong values (a bug?). -
Internal DHCP scope for AP on WLC 7.0 (on diff subnet)
hi All,
I would like to know if it is possible to assign dhcp pool on a different subnet to the WLC management interface?
Eg: Management Interface is on 172.16.4.100 /24
I would like to use the WLC Internal DHCP to assign IP to my APs on the a different range 172.16.2.x /24
Is that possible?
I have tried assigning dhcp scope for the AP within the same subnet as the management interface and it works. But that is not my requirement
Apparently i need my AP to be sitting on a different vlan
please adviseNo its not possible.. this works only if the AP and the WLC management interface is in the same subnet!! to ur issue we use something called as DHCP OPTION 43, google search DHCP OPTION 43 + cisco, the first link that u get wil help you!!
Please dont forget to rate the usefull posts!!
Regards
Surendra -
WLC 2006 INTERNAL DHCP FOR GUESTS CLIENTS
I would like to use the internal DHCP to issue ipaddress to the guest wireless clients.
However; when i setup the wlc internal DCHP scope and try to connect to the wireless guest vlan the WLC debug DHCP reads ...forwarding to 192.168.255.2 which i have listed as the gateway to the pix
any examples on how to do this would be great.
here is what i have for the dhcp scope:
Dhcp Scope Info
Scope: Guest.Data.DHCP
Enabled.......................................... Yes
Lease Time....................................... 86400 (1 day )
Pool Start....................................... 192.168.255.17
Pool End......................................... 192.168.255.30
Network.......................................... 192.168.255.0
Netmask.......................................... 255.255.255.0
Default Routers.................................. 192.168.255.2 0.0.0.0 0.0.0.0
DNS Domain.......................................
DNS.............................................. 0.0.0.0 0.0.0.0 0.0.0.0
Netbios Name Servers............................. 0.0.0.0 0.0.0.0 0.0.0.0
Here is what i have for the wlan
WLAN Identifier.................................. 2
Network Name (SSID).............................. Guest.Data
Status........................................... Disabled
MAC Filtering.................................... Disabled
Broadcast SSID................................... Enabled
AAA Policy Override.............................. Disabled
Number of Active Clients......................... 0
Exclusionlist Timeout............................ 60 seconds
Session Timeout.................................. Infinity
Interface........................................ guest.data
WLAN ACL......................................... unconfigured
DHCP Server...................................... Default
DHCP Address Assignment Required................. Enabled
Quality of Service............................... Silver (best effort)
WMM.............................................. Disabled
CCX - AironetIe Support.......................... Enabled
CCX - Gratuitous ProbeResponse (GPR)............. Disabled
Dot11-Phone Mode (7920).......................... Disabled
Wired Protocol................................... None
IPv6 Support..................................... Disabled
--More-- or (q)uit
Radio Policy..................................... All
Security
802.11 Authentication:........................ Open System
Static WEP Keys............................... Disabled
802.1X........................................ Disabled
Wi-Fi Protected Access (WPA/WPA2)............. Disabled
CKIP ......................................... Disabled
IP Security Passthru.......................... Disabled
Web Based Authentication...................... Disabled
Web-Passthrough............................... Disabled
Auto Anchor................................... Disabled
H-REAP Local Switching........................ Disabled
Management Frame Protection................... Ewhen i try to assocate the dhcp scope to wireless.guest.data interface using 192.168.255.1 which is the ip of the that interface it will not let me. I would have thought since i was using the interal dhcp that the .1 address would be the dhcp scope address also. i can assign 192.168.255.0 or 192.168.255.2(gateway)if i use .0 or .2 the dhcp request (discovery) process starts and then will forward to .2 (gateway) and never assign an address. the only thing that happens is that the client wireless interface will get 255.255.255.255 for a few seconds then go away.
what i am trying to accomplish is to connect the wlc port 2 directly to a pix 506 which goes to the internet so the guest traffice is not on our vlan.
any other suggestions on guest vlans would be appricated....
Tom
Interface Name................................... wireless.guest.data
IP Address....................................... 192.168.255.1
IP Netmask....................................... 255.255.255.0
IP Gateway....................................... 192.168.255.2
VLAN............................................. 150
Quarantine-vlan.................................. no
Physical Port.................................... 2
Primary DHCP Server.............................. Unconfigured
Secondary DHCP Server............................ Unconfigured
DHCP Option 82................................... Disabled
ACL.............................................. Unconfigured
AP Manager....................................... No
Scope: wireless.guest.data.dhcp.server
Enabled.......................................... Yes
Lease Time....................................... 86400 (1 day )
Pool Start....................................... 192.168.255.17
Pool End......................................... 192.168.255.30
Network.......................................... 192.168.255.0
Netmask.......................................... 255.255.255.0
Default Routers.................................. 192.168.255.2 0.0.0.0 0.0.0.0
DNS Domain.......................................
DNS.............................................. 0.0.0.0 0.0.0.0 0.0.0.0
Netbios Name Servers............................. 0.0.0.0 0.0.0.0 0.0.0.0 -
WLC "DHCP Option 82 Remote Id field format"
On WLC, does "DHCP Option 82 Remote Id field format" show client hostname on wlc monitor
Hi Jonathan with sub option 2, from your example D is the node identifier.
When seeing the variable per connection type, I would give a safe assumption it is verbose padding the sub type 1.
The verbose pad formatting for the packet should contain
sub option
length
node identifier
port type
interface number
vlan id
For normal pad format it should contain
sub option
length
circuit
length
vlan id
interface number
-Tom
Please mark answered for helpful posts -
WLC 2100 and DHCP strange issue.
Hi,
i have this scenario: 1 WLC 2100 and two LW AP 3500 connected. If the access points are connected via external switch evrything works well - AP and Clients get IP address from external DHCP and this is ok but when im connecting AP 3500 directly to one of ports on WLC i need to chceck in controller web Controller -> Advanced -> DHCP -> Enable DHCP proxy - after that AP get IP addres and clients get too but ip is assigned from external dhcp but the gateway is set as controller IP address (!!!) so clients not works. I want to configure access points connected directly do WLC.
I have small setup and i have configured all in the one vlan - management dla users are in the same vlan.
And the second is - for what usage is internal DHCP server - and how to use it?When "Enable DHCP Proxy" is not enabled tha LW AP 3500 cannot get IP address if it is connected directly to LWC... when i add this option then on both LW AP 3500 - one connected to WLC and second directly to switch give me DHCP address from external DHCP but gateway sets as LWC management IP.
I made test - connected client witout "Enable DHCP Proxy":
Client IP 192.168.1.201 (correct in dhcp server logs), default GW 192.168.1.1 (correct gateway for this DHCP) correct dnses and in windws ipconfig i see "Server DHCP 192.168.1.1" all is correct.
Disconnected client and clicked "Enable DHCP Proxy":
Client IP 192.168.1.201 (correct in dhcp server logs), default GW 192.168.1.252 incorrect gateway - ip of WLC management interface) correct dnses and in windws ipconfig i see "Server DHCP 1.1.1.1" that shows that WLC modified DHCP packets... but what it try to set default GW as WLC?
WLC data:
Software Version
7.0.98.0
I can attach screenshots and any other configutation if you need. -
WLC DHCP Proxy - To Do or Not to Do?
What is the upside/downside of turning of the WLC's DHCP Proxy setting? I know the option is there now, but it still defaults to proxy mode, so whats the issues? I ask, because, I could make a current issue of a guest wlan getting to a dhcp server a lot easier, if the client requests it. I can then dhcp relay off of a pix and to my enterprise dhcp/dns server. But I'm concerned what effect this may have on my other wlans.
Dhcp proxy is required if the WLC is the dhcp server, if you disable this remember to add the ip-helper address to your L3 interfaces.
That part of the config is a holdover from the Airespace days that helped the WLC learn the ip access of the clients. This has been fixed updated in later releases of code. So to proxy or not to proxy is really up to if the WLC is the dhcp or not. Unless yopu are running 6.0.196.0 or 7.0.980. Where you could hit CSCth68708
Sent from Cisco Technical Support iPad App
Maybe you are looking for
-
Localejbs/Seeburger/AttribMapper issue
Hi all, we are using "localejbs/Seeburger/AttribMapper" module in SFTP adapter to add the Date stamp to file name. Module Name Type Module Key localejbs/Seeburger/Attrib
-
Enter run time in hours / mins / secs on the front pannel
I am trying to get a pop up VI to run alongside my main program. While the measurment parts of my software run I want a VI to pop up and display the run time in hours / mins / secs. Once the main VI ends its sequence, I want the timer VI to close dow
-
Update 6.13 just killed two of my iPhone 4 what to do now?
Today I decided to update my iPhone 4 phones, both went trough with update, but then iTunes gave error msg. and doesn't recognise phone anymore. Both phones are stuck on iTunes and plug screen. Please help
-
New MBP wifi connectivity issues
Recently bought a new MBP about 2-3 months ago and I've noticed almost the entire time I've had it I have always had issues with the wifi constantly timing itself out. I know for a fact that this is not related to my router or ISP as I have other com
-
Lightroom Mobile says unsubscribed.
I currently have the Photoshop Photography Program plan which is suppose to include Lightroom Mobile. However within Lightroom Mobile its says I am unsubscribed. Can anyone help?