WLC 2006 INTERNAL DHCP FOR GUESTS CLIENTS

Unanswered Question
Jun 11th, 2007
User Badges:

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................... E





  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)
Loading.
Matthew Fowler Mon, 06/11/2007 - 21:01
User Badges:
  • Cisco Employee,

Could you please provide the guest.data interface configuration? Is the DHCP server listed as the management address?


If so, I think this is working as intended. The management will be on a different subnet, and seeing as the WLC is a layer 2 device, it has to forward to the gateway.


After it forwards to the gateway, what happens?

tkuzma1022 Tue, 06/12/2007 - 06:54
User Badges:

when 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


Actions

This Discussion

 

 

Trending Topics: Other Wireless Mobility

client could not be authenticated
Network Analysis Module (NAM) Products
Cisco 6500 nam
reason 440 driver failure
Cisco password cracker
Cisco Wireless mode