Please post any responses you get offline. I have the same problem, and
others will. The solution from Cisco was to move the DHCP server to the same
subnet as the controllers (not possible for me).

 

-jcw

-------------------------------------
John Watters    UA: OIT  205-348-3992

  _____  

From: The EDUCAUSE Wireless Issues Constituent Group Listserv
[mailto:[EMAIL PROTECTED] On Behalf Of Jorge Bodden
Sent: Friday, September 19, 2008 10:55 AM
To: [email protected]
Subject: [WIRELESS-LAN] DHCP issues on Cisco Wireless Controllers

 

Hello All,

We have a Cisco infrastructure with several controllers on our network.  We
run a WPA-TKIP environment with EAP-TTLS auth.

The users are able to log into the network.  However they never get an IP
address.  This kind of thing never happened to us before, while running the
system for over three years.  This is a sample dpug output from the
controller;

Has anyone seen anything like this;

Fri Sep 19 10:49:09 2008: 00:40:96:a9:0b:96 DHCP REQUEST for autoconfig
address - clearing server ip 0.0.0.0 (old IP 0.0.0.0)
Fri Sep 19 10:49:09 2008: 00:40:96:a9:0b:96 DHCP selecting relay 1 - control
block settings:
                        dhcpServer: 0.0.0.0, dhcpNetmask: 0.0.0.0,
                        dhcpGateway: 0.0.0.0, dhcpRelay: 10.10.10.16  VLAN:
252
Fri Sep 19 10:49:09 2008: 00:40:96:a9:0b:96 DHCP selected relay 1 -
10.10.10.1 (local address 10.10.10.16, gateway 10.10.10.1, VLAN 252, port 2)
Fri Sep 19 10:49:09 2008: 00:40:96:a9:0b:96 DHCP transmitting DHCP DISCOVER
(1)
Fri Sep 19 10:49:09 2008: 00:40:96:a9:0b:96 DHCP   op: BOOTREQUEST, htype:
Ethernet, hlen: 6, hops: 1
Fri Sep 19 10:49:09 2008: 00:40:96:a9:0b:96 DHCP   xid: 0x11291079
(287903865), secs: 6912, flags: 8000
Fri Sep 19 10:49:09 2008: 00:40:96:a9:0b:96 DHCP   chaddr: 00:40:96:a9:0b:96
Fri Sep 19 10:49:09 2008: 00:40:96:a9:0b:96 DHCP   ciaddr: 0.0.0.0,  yiaddr:
0.0.0.0
Fri Sep 19 10:49:09 2008: 00:40:96:a9:0b:96 DHCP   siaddr: 0.0.0.0,  giaddr:
10.10.10.16
Fri Sep 19 10:49:09 2008: 00:40:96:a9:0b:96 DHCP   requested ip:
169.254.49.163
Fri Sep 19 10:49:09 2008: 00:40:96:a9:0b:96 DHCP sending REQUEST to
10.10.10.1 (len 350, port 2, vlan 252)
Fri Sep 19 10:49:09 2008: 00:40:96:a9:0b:96 DHCP selecting relay 2 - control
block settings:
                        dhcpServer: 0.0.0.0, dhcpNetmask: 0.0.0.0,
                        dhcpGateway: 0.0.0.0, dhcpRelay: 10.10.10.16  VLAN:
252
Fri Sep 19 10:49:09 2008: 00:40:96:a9:0b:96 DHCP selected relay 2 - NONE


Now what I do see, is that the client is trying to request a 169.254.49.163
address.  The router should still respond with a proper IP address
regardless of which one the client is asking for. 

Any help on this matter would be greatly appreciated.  Thanks.

Jorge Bodden

 
--------------------
 
This electronic message is intended to be for the use only of the named
recipient, and may contain information that is confidential or privileged.
If you are not the intended recipient, you are hereby notified that any
disclosure, copying, distribution or use of the contents of this message is
strictly prohibited.  If you have received this message in error or are not
the named recipient, please notify us immediately by contacting the sender
at the electronic mail address noted above, and delete and destroy all
copies of this message.  Thank you.
 
********** Participation and subscription information for this EDUCAUSE
Constituent Group discussion list can be found at
http://www.educause.edu/groups/. 



**********
Participation and subscription information for this EDUCAUSE Constituent Group 
discussion list can be found at http://www.educause.edu/groups/.

Reply via email to