Date:Thu, 27 Aug 2009 15:58:39 -0500
From:Hector J Rios hr...@lsu.edu
Subject: Self-assigned IP on Macs...
Have you guys run into this issue? We run Cisco's lightweight APs on
WiSMs running code 5.2.193. Mac will associate to our APs but just won't
obtain an IP address. In the end it
Here are some numbers for the our first week of classes:
Average Number of Users by Protocol
802.11a: 772.2
802.11b: 32.2
802.11g: 3245.6
802.11n (5 GHZ): 189.7
802.11n (2.4 GHZ): 218.3
DHCP Active Leases Stats for Network in the Dorms (1hr leases; 4938
beds)
Wired: Average 1.02k
We have seen this issue to some degree. It did not happen
to all Macs but only to a small percentage of machines. In
case anyone should run into it though what I found was the
following...
It is normal for dhcp clients to request their last used IP.
Something about how the Mac dhcp
The IP theft function can't trigger until the controller
actually see an IP in use. So they wouldn't exclude the
client before it had even tried to use an address much less
completed the dhcp process. The exclusion triggered BECAUSE
of the 192.168.1.x address. I also believe in packet
captures
We also have DHCP required set to off as well as IP Theft and reuse off and
still have the problem show up. It seems after 1 to 5 tries the Mac will
finally get a lease and work. Not a very popular workaround.
Robert Owens
Kansas State University
- Original Message -
From: Hector J
