RE: [WIRELESS-LAN] Self-assigned IP on Macs
We encountered the same issue. However, not all snow leopard clients have this problem. Some of them work well; some of them could not get IP address from DHCP server occasionally; and some of them could not get IP address for the whole day. We contacted with Apple, they said they noticed this problem, and a new patch will be published in the middle or end of November. Linchuan Yang Wireless Networking Analyst Network Assessment and Integration, IITS-Concordia University Tel: (514)848-2424 ext. 7664 -Original Message- From: The EDUCAUSE Wireless Issues Constituent Group Listserv [mailto:wireless-...@listserv.educause.edu] On Behalf Of Anthony Croome Sent: October 28, 2009 6:26 PM To: WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU Subject: Re: [WIRELESS-LAN] Self-assigned IP on Macs Update for my uni's problem. Our engineers are 100% convinced it's a MAC OS issue. We are not sure when the problem was introduced. When it is working we see the discover, offer, ack, in the DHCP daemon logs. Then at a random, intermittent time the DHCP daemon will decide to stop listening to dhcp packets being received on wireless, it logs the discover but not the offer. Wireshark is showing the offers being received but the DHCP daemon doesn't log them. There is no difference in the contents of the DHCP offer when it is working vs when it isn't. We are going to escalate it to Apple, as there isn't anything else we can see to try. Anthony -Original Message- From: The EDUCAUSE Wireless Issues Constituent Group Listserv [mailto:wireless-...@listserv.educause.edu] On Behalf Of Lee H Badman Sent: Friday, 16 October 2009 10:16 AM To: WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU Subject: Re: [WIRELESS-LAN] Self-assigned IP on Macs Has anyone gotten any approved suggestions for how to deal with these Apple issues from Cisco, beyond just trying things that seem to sometimes help? It is frustrating how the friendly and trouble-free Apple devices tend to be the least friendly and most troubling devices on the WLAN. A little bit of techno-irony to this:) -Lee From: The EDUCAUSE Wireless Issues Constituent Group Listserv [wireless-...@listserv.educause.edu] On Behalf Of Jeffrey Sessler [j...@scrippscollege.edu] Sent: Thursday, October 15, 2009 7:56 PM To: WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU Subject: Re: [WIRELESS-LAN] Self-assigned IP on Macs In 6.0, the code for world-mode didn't make it into the controller, but I believe it's in the AP's IOS commands, so it can be toggled but takes a little more effort. Jeff Garry Peirce 10/15/09 2:16 PM Perhaps I was erroneous in equating the two through a Cisco doc referencing DTPC to world-mode. 'When you enable Dynamic Transmit Power Control (DTPC), access points add channel and transmit power information to beacons. (On access points that run Cisco IOS software, this feature is called world mode.)' DTPC does appear to be CCX related, so it is likely irrelevant with regard to the mentioned Apple/Broadcom bug. Running 6.0.182, 'config 802.11a world-mode' is not an available option. 'config 802.11a dtpc' is. 'show 802.11a' will show the status of DTPC. I'll inquire w/Cisco. -- -Original Message- From: The EDUCAUSE Wireless Issues Constituent Group Listserv [mailto:wireless-...@listserv.educause.edu] On Behalf Of Matt Grover Sent: Thursday, October 15, 2009 2:51 PM To: WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU Subject: Re: [WIRELESS-LAN] Self-assigned IP on Macs It's under: show 802.11a(or b) -Matt Bob Richman wrote: So, how about the show command that displays the current setting? -Original Message- From: The EDUCAUSE Wireless Issues Constituent Group Listserv [mailto:wireless-...@listserv.educause.edu] On Behalf Of Matt Grover Sent: Thursday, October 15, 2009 1:21 PM To: WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU Subject: Re: [WIRELESS-LAN] Self-assigned IP on Macs Actually, if you are talking about specifically world-mode it's under: CLI: config 802.11a world-mode orconfig 802.11b world-mode -Matt -- Matt Grover === University of Florida Sr. Network Engineer=== http://net-services.ufl.edu m...@ufl.edu=== Florida Lambda Rail (352)273-1061 === http://www.flrnet.org/ ** 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/. ** 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
RE: [WIRELESS-LAN] Self-assigned IP on Macs
Update for my uni's problem. Our engineers are 100% convinced it's a MAC OS issue. We are not sure when the problem was introduced. When it is working we see the discover, offer, ack, in the DHCP daemon logs. Then at a random, intermittent time the DHCP daemon will decide to stop listening to dhcp packets being received on wireless, it logs the discover but not the offer. Wireshark is showing the offers being received but the DHCP daemon doesn't log them. There is no difference in the contents of the DHCP offer when it is working vs when it isn't. We are going to escalate it to Apple, as there isn't anything else we can see to try. Anthony -Original Message- From: The EDUCAUSE Wireless Issues Constituent Group Listserv [mailto:wireless-...@listserv.educause.edu] On Behalf Of Lee H Badman Sent: Friday, 16 October 2009 10:16 AM To: WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU Subject: Re: [WIRELESS-LAN] Self-assigned IP on Macs Has anyone gotten any approved suggestions for how to deal with these Apple issues from Cisco, beyond just trying things that seem to sometimes help? It is frustrating how the friendly and trouble-free Apple devices tend to be the least friendly and most troubling devices on the WLAN. A little bit of techno-irony to this:) -Lee From: The EDUCAUSE Wireless Issues Constituent Group Listserv [wireless-...@listserv.educause.edu] On Behalf Of Jeffrey Sessler [j...@scrippscollege.edu] Sent: Thursday, October 15, 2009 7:56 PM To: WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU Subject: Re: [WIRELESS-LAN] Self-assigned IP on Macs In 6.0, the code for world-mode didn't make it into the controller, but I believe it's in the AP's IOS commands, so it can be toggled but takes a little more effort. Jeff Garry Peirce 10/15/09 2:16 PM Perhaps I was erroneous in equating the two through a Cisco doc referencing DTPC to world-mode. 'When you enable Dynamic Transmit Power Control (DTPC), access points add channel and transmit power information to beacons. (On access points that run Cisco IOS software, this feature is called world mode.)' DTPC does appear to be CCX related, so it is likely irrelevant with regard to the mentioned Apple/Broadcom bug. Running 6.0.182, 'config 802.11a world-mode' is not an available option. 'config 802.11a dtpc' is. 'show 802.11a' will show the status of DTPC. I'll inquire w/Cisco. -- -Original Message- From: The EDUCAUSE Wireless Issues Constituent Group Listserv [mailto:wireless-...@listserv.educause.edu] On Behalf Of Matt Grover Sent: Thursday, October 15, 2009 2:51 PM To: WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU Subject: Re: [WIRELESS-LAN] Self-assigned IP on Macs It's under: show 802.11a(or b) -Matt Bob Richman wrote: So, how about the show command that displays the current setting? -Original Message- From: The EDUCAUSE Wireless Issues Constituent Group Listserv [mailto:wireless-...@listserv.educause.edu] On Behalf Of Matt Grover Sent: Thursday, October 15, 2009 1:21 PM To: WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU Subject: Re: [WIRELESS-LAN] Self-assigned IP on Macs Actually, if you are talking about specifically world-mode it's under: CLI: config 802.11a world-mode orconfig 802.11b world-mode -Matt -- Matt Grover === University of Florida Sr. Network Engineer=== http://net-services.ufl.edu m...@ufl.edu=== Florida Lambda Rail (352)273-1061 === http://www.flrnet.org/ ** 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/. ** 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/. ** Participation and subscription information for this EDUCAUSE Constituent Group discussion list can be found at http://www.educause.edu/groups/.
RE: [WIRELESS-LAN] Self-assigned IP on Macs
Well good luck with that, escalating it Apple I mean. : ) Pete M. -Original Message- From: The EDUCAUSE Wireless Issues Constituent Group Listserv [mailto:wireless-...@listserv.educause.edu] On Behalf Of Anthony Croome Sent: Wednesday, October 28, 2009 6:26 PM To: WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU Subject: Re: [WIRELESS-LAN] Self-assigned IP on Macs Update for my uni's problem. Our engineers are 100% convinced it's a MAC OS issue. We are not sure when the problem was introduced. When it is working we see the discover, offer, ack, in the DHCP daemon logs. Then at a random, intermittent time the DHCP daemon will decide to stop listening to dhcp packets being received on wireless, it logs the discover but not the offer. Wireshark is showing the offers being received but the DHCP daemon doesn't log them. There is no difference in the contents of the DHCP offer when it is working vs when it isn't. We are going to escalate it to Apple, as there isn't anything else we can see to try. Anthony -Original Message- From: The EDUCAUSE Wireless Issues Constituent Group Listserv [mailto:wireless-...@listserv.educause.edu] On Behalf Of Lee H Badman Sent: Friday, 16 October 2009 10:16 AM To: WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU Subject: Re: [WIRELESS-LAN] Self-assigned IP on Macs Has anyone gotten any approved suggestions for how to deal with these Apple issues from Cisco, beyond just trying things that seem to sometimes help? It is frustrating how the friendly and trouble-free Apple devices tend to be the least friendly and most troubling devices on the WLAN. A little bit of techno-irony to this:) -Lee From: The EDUCAUSE Wireless Issues Constituent Group Listserv [wireless-...@listserv.educause.edu] On Behalf Of Jeffrey Sessler [j...@scrippscollege.edu] Sent: Thursday, October 15, 2009 7:56 PM To: WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU Subject: Re: [WIRELESS-LAN] Self-assigned IP on Macs In 6.0, the code for world-mode didn't make it into the controller, but I believe it's in the AP's IOS commands, so it can be toggled but takes a little more effort. Jeff Garry Peirce 10/15/09 2:16 PM Perhaps I was erroneous in equating the two through a Cisco doc referencing DTPC to world-mode. 'When you enable Dynamic Transmit Power Control (DTPC), access points add channel and transmit power information to beacons. (On access points that run Cisco IOS software, this feature is called world mode.)' DTPC does appear to be CCX related, so it is likely irrelevant with regard to the mentioned Apple/Broadcom bug. Running 6.0.182, 'config 802.11a world-mode' is not an available option. 'config 802.11a dtpc' is. 'show 802.11a' will show the status of DTPC. I'll inquire w/Cisco. -- -Original Message- From: The EDUCAUSE Wireless Issues Constituent Group Listserv [mailto:wireless-...@listserv.educause.edu] On Behalf Of Matt Grover Sent: Thursday, October 15, 2009 2:51 PM To: WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU Subject: Re: [WIRELESS-LAN] Self-assigned IP on Macs It's under: show 802.11a(or b) -Matt Bob Richman wrote: So, how about the show command that displays the current setting? -Original Message- From: The EDUCAUSE Wireless Issues Constituent Group Listserv [mailto:wireless-...@listserv.educause.edu] On Behalf Of Matt Grover Sent: Thursday, October 15, 2009 1:21 PM To: WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU Subject: Re: [WIRELESS-LAN] Self-assigned IP on Macs Actually, if you are talking about specifically world-mode it's under: CLI: config 802.11a world-mode orconfig 802.11b world-mode -Matt -- Matt Grover === University of Florida Sr. Network Engineer=== http://net-services.ufl.edu m...@ufl.edu=== Florida Lambda Rail (352)273-1061 === http://www.flrnet.org/ ** 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/. ** 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/. ** 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/.
Re: [WIRELESS-LAN] Self-assigned IP on Macs
Since moving to 6.0, I've not run into any Apple-related issues on the WLAN. I believe the only changes from default are disabling world-mode in 5GHz, and not running with the require DHCP setting enabled. best, Jeff Lee H Badman lhbad...@syr.edu 10/15/2009 5:16 PM Has anyone gotten any approved suggestions for how to deal with these Apple issues from Cisco, beyond just trying things that seem to sometimes help? It is frustrating how the friendly and trouble-free Apple devices tend to be the least friendly and most troubling devices on the WLAN. A little bit of techno-irony to this:) -Lee From: The EDUCAUSE Wireless Issues Constituent Group Listserv [wireless-...@listserv.educause.edu] On Behalf Of Jeffrey Sessler [j...@scrippscollege.edu] Sent: Thursday, October 15, 2009 7:56 PM To: WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU Subject: Re: [WIRELESS-LAN] Self-assigned IP on Macs In 6.0, the code for world-mode didn't make it into the controller, but I believe it's in the AP's IOS commands, so it can be toggled but takes a little more effort. Jeff Garry Peirce 10/15/09 2:16 PM Perhaps I was erroneous in equating the two through a Cisco doc referencing DTPC to world-mode. 'When you enable Dynamic Transmit Power Control (DTPC), access points add channel and transmit power information to beacons. (On access points that run Cisco IOS software, this feature is called world mode.)' DTPC does appear to be CCX related, so it is likely irrelevant with regard to the mentioned Apple/Broadcom bug. Running 6.0.182, 'config 802.11a world-mode' is not an available option. 'config 802.11a dtpc' is. 'show 802.11a' will show the status of DTPC. I'll inquire w/Cisco. -- -Original Message- From: The EDUCAUSE Wireless Issues Constituent Group Listserv [mailto:wireless-...@listserv.educause.edu] On Behalf Of Matt Grover Sent: Thursday, October 15, 2009 2:51 PM To: WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU Subject: Re: [WIRELESS-LAN] Self-assigned IP on Macs It's under: show 802.11a(or b) -Matt Bob Richman wrote: So, how about the show command that displays the current setting? -Original Message- From: The EDUCAUSE Wireless Issues Constituent Group Listserv [mailto:wireless-...@listserv.educause.edu] On Behalf Of Matt Grover Sent: Thursday, October 15, 2009 1:21 PM To: WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU Subject: Re: [WIRELESS-LAN] Self-assigned IP on Macs Actually, if you are talking about specifically world-mode it's under: CLI: config 802.11a world-mode orconfig 802.11b world-mode -Matt -- Matt Grover === University of Florida Sr. Network Engineer=== http://net-services.ufl.edu m...@ufl.edu=== Florida Lambda Rail (352)273-1061 === http://www.flrnet.org/ ** 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/. ** 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/. ** Participation and subscription information for this EDUCAUSE Constituent Group discussion list can be found at http://www.educause.edu/groups/.
RE: [WIRELESS-LAN] Self-assigned IP on Macs
Have you defined the out identity under PEAP configuration? -Original Message- From: The EDUCAUSE Wireless Issues Constituent Group Listserv on behalf of gwill...@uccs.edu Sent: Wed 10/14/2009 12:16 PM To: WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU Subject: Re: [WIRELESS-LAN] Self-assigned IP on Macs We have the second to latest version of Aruba OS and it's still an issue on some Macbook Pro's running either 10.5.8 or 10.6.x. We require 802.1x with PEAP on our WPA2 network. To fix the problem we have to create a new location under the network preferences. This is the only thing that works 100% of the time. It isn't an issue on the open SSID for us either. -Original Message- From: The EDUCAUSE Wireless Issues Constituent Group Listserv [mailto:wireless-...@listserv.educause.edu] On Behalf Of Marcelo Lew Sent: Wednesday, October 14, 2009 9:59 AM To: WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU Subject: Re: [WIRELESS-LAN] Self-assigned IP on Macs We have seen this with our Aruba system, but only on our 802.1x/wpa2 SSID. We usually uncheck PEAP on the 802.1x profile of MACs, so they use TTLS, which seems to work better. If this fails, we then delete the 802.1x profile and anything related in the keychain. Usually that works. Unchecking IPv6 (enabled by default) seemed to have helped in the past. After a code upgrade in our system the problem went away, however, we have seen issues again with Snow Leopard (won't get an IP address, they end up with a self-assigned. But if you look at logs, they really haven't authenticated successfully, but for some reason they won't see an error message). This doesn't happen on an open SSID of course. Marcelo Lew Wireless Network Specialist University Technology Services University of Denver Desk: (303) 871-6523 Cell: (303) 669-4217 Fax: (303) 871-5900 Email: m...@du.edu -Original Message- From: The EDUCAUSE Wireless Issues Constituent Group Listserv [mailto:wireless-...@listserv.educause.edu] On Behalf Of Anthony Croome Sent: Tuesday, October 13, 2009 10:30 PM To: WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU Subject: Re: [WIRELESS-LAN] Self-assigned IP on Macs Hi We are having this problem too. Is there any new information from people? We currently run Cisco wireless and have upgraded some locations to the new N standard. The problem appears to be isolated in the locations where we have upgraded but we can't be 100% sure. It is only appearing on macs, and they claim it works in one place but not another. All we can see is that it appears to be rejecting the dhcpoffer from the dhcp server. We haven't tried disabling dhcp proxy as discussed earlier in this thread, but others have said it didn't help. The latest temporary solution that has worked on two out of two macs is === All commands required at the command line: sudo ipconfig set en1 BOOTP (case sensitive and en1 is generally the wireless adapter on macs but it could possibly be different?) wait 5 seconds and then enter: sudo ipconfig set en1 DHCP === Anthony Croome QUT -Original Message- From: The EDUCAUSE Wireless Issues Constituent Group Listserv [mailto:wireless-...@listserv.educause.edu] On Behalf Of Earl Barfield Sent: Friday, 28 August 2009 11:39 PM To: WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU Subject: Re: [WIRELESS-LAN] Self-assigned IP on Macs 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 assigns itself a self-assigned IP. We are seeing this on a lot of new MacBooks and MacBookPros running 10.5.8. If we associate the computer to an autonomous AP it works fine. If we boot it in safe mode it works fine too. Everything else it just fails. I had the same problem after ugrading from 4.2.something to 5.2.193.0. Uncheck Enable DHCP Proxy under controller-advanced-DHCP and see if that fixes it. It worked for me. -- Earl Barfield -- Academic Research Tech / Information Technology Georgia Institute of Technology, Atlanta Georgia, 30332 Internet: earl.barfi...@oit.gatech.edue...@gatech.edu ** 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/. ** 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/. ** Participation and subscription information for this EDUCAUSE Constituent Group discussion list can
RE: [WIRELESS-LAN] Self-assigned IP on Macs
Is this a change Cisco recommended, or more like an experiment that worked? Just wondering... Lee H. Badman Wireless/Network Engineer Information Technology and Services Syracuse University 315 443-3003 Sent from a device that is much nicer than your Blackberry or iPhone -Original Message- From: The EDUCAUSE Wireless Issues Constituent Group Listserv [mailto:wireless-...@listserv.educause.edu] On Behalf Of Garry Peirce Sent: Thursday, October 15, 2009 12:22 PM To: WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU Subject: Re: [WIRELESS-LAN] Self-assigned IP on Macs Under WCS, within the 802.11b/g or A Parameters, it's called: 'Dynamic Tx Power Control'. On a controller, it's under: Wireless...802.11a...Network...DTPC support. Via CLI: 'config 802.11a dtpc' -- -Original Message- From: The EDUCAUSE Wireless Issues Constituent Group Listserv [mailto:wireless-...@listserv.educause.edu] On Behalf Of Bob Richman Sent: Thursday, October 15, 2009 12:02 PM To: WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU Subject: Re: [WIRELESS-LAN] Self-assigned IP on Macs Can you tell us the 'show command' or where in the GUI you find if this is set? Is it per wlan or AP? -Original Message- From: The EDUCAUSE Wireless Issues Constituent Group Listserv [mailto:wireless-...@listserv.educause.edu] On Behalf Of Garry Peirce Sent: Thursday, October 15, 2009 11:36 AM To: WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU Subject: Re: [WIRELESS-LAN] Self-assigned IP on Macs We also use Cisco and were seeing this issue earlier. It appears to have been significantly decreased after I disabled the IPTheft exclusion policy in lieu of Apple's aforementioned DHCP adherence to RFC4436. On Cisco controllers, the capability described below appears to be called 'Dynamic Tx Power Control DTPC' When you enable Dynamic Transmit Power Control (DTPC), access points add channel and transmit power information to beacons. (On access points that run Cisco IOS software, this feature is called world mode.) It is enabled by default (at least in 6.0.182). Given Jeff's message below I'm thinking of disabling it. Is there any further info on this Broadcom driver bug/status? -- -Original Message- From: The EDUCAUSE Wireless Issues Constituent Group Listserv [mailto:wireless-...@listserv.educause.edu] On Behalf Of Jeffrey Sessler Sent: Wednesday, October 14, 2009 4:00 PM To: WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU Subject: Re: [WIRELESS-LAN] Self-assigned IP on Macs Are the Macs in question associating at 802.11a/n (5GHz)? I've posted before about a bug in the Mac Broadcom driver which will cause the client to continuously adjust it's power and may result in an association to the AP but random communication issues (like failure to get an IP). Cisco added a command to disable the World Mode IE feature in the beacons until Apple fixes the problem. config 802.11a(or 802.11b) world-mode disable I think the above is in 5.2.193 but I'm not sure if it made it into 6.0. I believe however that there is an equivalent individual AP cli command for it. Oh, and world mode IE is disabled by default on Cisco autonomous AP's, thus you'll likely not encounter the issue with them. Jeff Anthony Croome a.cro...@qut.edu.au 10/13/2009 9:30 PM Hi We are having this problem too. Is there any new information from people? We currently run Cisco wireless and have upgraded some locations to the new N standard. The problem appears to be isolated in the locations where we have upgraded but we can't be 100% sure. It is only appearing on macs, and they claim it works in one place but not another. All we can see is that it appears to be rejecting the dhcpoffer from the dhcp server. We haven't tried disabling dhcp proxy as discussed earlier in this thread, but others have said it didn't help. The latest temporary solution that has worked on two out of two macs is === All commands required at the command line: sudo ipconfig set en1 BOOTP (case sensitive and en1 is generally the wireless adapter on macs but it could possibly be different?) wait 5 seconds and then enter: sudo ipconfig set en1 DHCP === Anthony Croome QUT -Original Message- From: The EDUCAUSE Wireless Issues Constituent Group Listserv [mailto:wireless-...@listserv.educause.edu] On Behalf Of Earl Barfield Sent: Friday, 28 August 2009 11:39 PM To: WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU Subject: Re: [WIRELESS-LAN] Self-assigned IP on Macs 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 assigns itself a self-assigned IP. We are seeing this on a lot of new
Re: [WIRELESS-LAN] Self-assigned IP on Macs
I could be mistaken, but DTPC is specific to CCX capable clients. While it offers similar function to world-mode, they are not mutually exclusive. In the case of the Mac/Broadcom issue, it's the world-mode function, and not DTCP, that is the issue. Also, since the Apple doesn't support CCX, DTCP enabled/disabled should not influence them. Jeff Garry Peirce 10/15/09 9:23 AM Under WCS, within the 802.11b/g or A Parameters, it's called: 'Dynamic Tx Power Control'. On a controller, it's under: Wireless...802.11a...Network...DTPC support. Via CLI: 'config 802.11a dtpc' -- -Original Message- From: The EDUCAUSE Wireless Issues Constituent Group Listserv [mailto:wireless-...@listserv.educause.edu] On Behalf Of Bob Richman Sent: Thursday, October 15, 2009 12:02 PM To: WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU Subject: Re: [WIRELESS-LAN] Self-assigned IP on Macs Can you tell us the 'show command' or where in the GUI you find if this is set? Is it per wlan or AP? -Original Message- From: The EDUCAUSE Wireless Issues Constituent Group Listserv [mailto:wireless-...@listserv.educause.edu] On Behalf Of Garry Peirce Sent: Thursday, October 15, 2009 11:36 AM To: WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU Subject: Re: [WIRELESS-LAN] Self-assigned IP on Macs We also use Cisco and were seeing this issue earlier. It appears to have been significantly decreased after I disabled the IPTheft exclusion policy in lieu of Apple's aforementioned DHCP adherence to RFC4436. On Cisco controllers, the capability described below appears to be called 'Dynamic Tx Power Control DTPC' When you enable Dynamic Transmit Power Control (DTPC), access points add channel and transmit power information to beacons. (On access points that run Cisco IOS software, this feature is called world mode.) It is enabled by default (at least in 6.0.182). Given Jeff's message below I'm thinking of disabling it. Is there any further info on this Broadcom driver bug/status? -- -Original Message- From: The EDUCAUSE Wireless Issues Constituent Group Listserv [mailto:wireless-...@listserv.educause.edu] On Behalf Of Jeffrey Sessler Sent: Wednesday, October 14, 2009 4:00 PM To: WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU Subject: Re: [WIRELESS-LAN] Self-assigned IP on Macs Are the Macs in question associating at 802.11a/n (5GHz)? I've posted before about a bug in the Mac Broadcom driver which will cause the client to continuously adjust it's power and may result in an association to the AP but random communication issues (like failure to get an IP). Cisco added a command to disable the World Mode IE feature in the beacons until Apple fixes the problem. config 802.11a(or 802.11b) world-mode disable I think the above is in 5.2.193 but I'm not sure if it made it into 6.0. I believe however that there is an equivalent individual AP cli command for it. Oh, and world mode IE is disabled by default on Cisco autonomous AP's, thus you'll likely not encounter the issue with them. Jeff Anthony Croome 10/13/2009 9:30 PM Hi We are having this problem too. Is there any new information from people? We currently run Cisco wireless and have upgraded some locations to the new N standard. The problem appears to be isolated in the locations where we have upgraded but we can't be 100% sure. It is only appearing on macs, and they claim it works in one place but not another. All we can see is that it appears to be rejecting the dhcpoffer from the dhcp server. We haven't tried disabling dhcp proxy as discussed earlier in this thread, but others have said it didn't help. The latest temporary solution that has worked on two out of two macs is === All commands required at the command line: sudo ipconfig set en1 BOOTP (case sensitive and en1 is generally the wireless adapter on macs but it could possibly be different?) wait 5 seconds and then enter: sudo ipconfig set en1 DHCP === Anthony Croome QUT -Original Message- From: The EDUCAUSE Wireless Issues Constituent Group Listserv [mailto:wireless-...@listserv.educause.edu] On Behalf Of Earl Barfield Sent: Friday, 28 August 2009 11:39 PM To: WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU Subject: Re: [WIRELESS-LAN] Self-assigned IP on Macs Date:Thu, 27 Aug 2009 15:58:39 -0500 From:Hector J Rios 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 assigns itself a self-assigned IP. We are seeing this on a lot of new MacBooks and MacBookPros running 10.5.8. If we associate the computer to an autonomous AP it works fine. If we boot it in safe mode it works fine too. Everything else it just fails. I had the same problem
Re: [WIRELESS-LAN] Self-assigned IP on Macs
Actually, if you are talking about specifically world-mode it's under: CLI: config 802.11a world-mode orconfig 802.11b world-mode -Matt Garry Peirce wrote: Under WCS, within the 802.11b/g or A Parameters, it's called: 'Dynamic Tx Power Control'. On a controller, it's under: Wireless...802.11a...Network...DTPC support. Via CLI: 'config 802.11a dtpc' -- -Original Message- From: The EDUCAUSE Wireless Issues Constituent Group Listserv [mailto:wireless-...@listserv.educause.edu] On Behalf Of Bob Richman Sent: Thursday, October 15, 2009 12:02 PM To: WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU Subject: Re: [WIRELESS-LAN] Self-assigned IP on Macs Can you tell us the 'show command' or where in the GUI you find if this is set? Is it per wlan or AP? -Original Message- From: The EDUCAUSE Wireless Issues Constituent Group Listserv [mailto:wireless-...@listserv.educause.edu] On Behalf Of Garry Peirce Sent: Thursday, October 15, 2009 11:36 AM To: WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU Subject: Re: [WIRELESS-LAN] Self-assigned IP on Macs We also use Cisco and were seeing this issue earlier. It appears to have been significantly decreased after I disabled the IPTheft exclusion policy in lieu of Apple's aforementioned DHCP adherence to RFC4436. On Cisco controllers, the capability described below appears to be called 'Dynamic Tx Power Control DTPC' When you enable Dynamic Transmit Power Control (DTPC), access points add channel and transmit power information to beacons. (On access points that run Cisco IOS software, this feature is called world mode.) It is enabled by default (at least in 6.0.182). Given Jeff's message below I'm thinking of disabling it. Is there any further info on this Broadcom driver bug/status? -- -Original Message- From: The EDUCAUSE Wireless Issues Constituent Group Listserv [mailto:wireless-...@listserv.educause.edu] On Behalf Of Jeffrey Sessler Sent: Wednesday, October 14, 2009 4:00 PM To: WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU Subject: Re: [WIRELESS-LAN] Self-assigned IP on Macs Are the Macs in question associating at 802.11a/n (5GHz)? I've posted before about a bug in the Mac Broadcom driver which will cause the client to continuously adjust it's power and may result in an association to the AP but random communication issues (like failure to get an IP). Cisco added a command to disable the World Mode IE feature in the beacons until Apple fixes the problem. config 802.11a(or 802.11b) world-mode disable I think the above is in 5.2.193 but I'm not sure if it made it into 6.0. I believe however that there is an equivalent individual AP cli command for it. Oh, and world mode IE is disabled by default on Cisco autonomous AP's, thus you'll likely not encounter the issue with them. Jeff Anthony Croome a.cro...@qut.edu.au 10/13/2009 9:30 PM Hi We are having this problem too. Is there any new information from people? We currently run Cisco wireless and have upgraded some locations to the new N standard. The problem appears to be isolated in the locations where we have upgraded but we can't be 100% sure. It is only appearing on macs, and they claim it works in one place but not another. All we can see is that it appears to be rejecting the dhcpoffer from the dhcp server. We haven't tried disabling dhcp proxy as discussed earlier in this thread, but others have said it didn't help. The latest temporary solution that has worked on two out of two macs is === All commands required at the command line: sudo ipconfig set en1 BOOTP (case sensitive and en1 is generally the wireless adapter on macs but it could possibly be different?) wait 5 seconds and then enter: sudo ipconfig set en1 DHCP === Anthony Croome QUT -Original Message- From: The EDUCAUSE Wireless Issues Constituent Group Listserv [mailto:wireless-...@listserv.educause.edu] On Behalf Of Earl Barfield Sent: Friday, 28 August 2009 11:39 PM To: WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU Subject: Re: [WIRELESS-LAN] Self-assigned IP on Macs 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 assigns itself a self-assigned IP. We are seeing this on a lot of new MacBooks and MacBookPros running 10.5.8. If we associate the computer to an autonomous AP it works fine. If we boot it in safe mode it works fine too. Everything else it just fails. I had the same problem after ugrading from 4.2.something to 5.2.193.0. Uncheck Enable DHCP Proxy under controller-advanced-DHCP and see if that fixes it. It worked for me. -- Earl Barfield -- Academic Research Tech / Information Technology Georgia Institute of Technology, Atlanta Georgia, 30332 Internet: earl.barfi...@oit.gatech.edue...@gatech.edu ** Participation
RE: [WIRELESS-LAN] Self-assigned IP on Macs
Perhaps I was erroneous in equating the two through a Cisco doc referencing DTPC to world-mode. 'When you enable Dynamic Transmit Power Control (DTPC), access points add channel and transmit power information to beacons. (On access points that run Cisco IOS software, this feature is called world mode.)' DTPC does appear to be CCX related, so it is likely irrelevant with regard to the mentioned Apple/Broadcom bug. Running 6.0.182, 'config 802.11a world-mode' is not an available option. 'config 802.11a dtpc' is. 'show 802.11a' will show the status of DTPC. I'll inquire w/Cisco. -- -Original Message- From: The EDUCAUSE Wireless Issues Constituent Group Listserv [mailto:wireless-...@listserv.educause.edu] On Behalf Of Matt Grover Sent: Thursday, October 15, 2009 2:51 PM To: WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU Subject: Re: [WIRELESS-LAN] Self-assigned IP on Macs It's under: show 802.11a(or b) -Matt Bob Richman wrote: So, how about the show command that displays the current setting? -Original Message- From: The EDUCAUSE Wireless Issues Constituent Group Listserv [mailto:wireless-...@listserv.educause.edu] On Behalf Of Matt Grover Sent: Thursday, October 15, 2009 1:21 PM To: WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU Subject: Re: [WIRELESS-LAN] Self-assigned IP on Macs Actually, if you are talking about specifically world-mode it's under: CLI: config 802.11a world-mode orconfig 802.11b world-mode -Matt -- Matt Grover === University of Florida Sr. Network Engineer=== http://net-services.ufl.edu m...@ufl.edu=== Florida Lambda Rail (352)273-1061 === http://www.flrnet.org/ ** 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/.
Re: [WIRELESS-LAN] Self-assigned IP on Macs
In 6.0, the code for world-mode didn't make it into the controller, but I believe it's in the AP's IOS commands, so it can be toggled but takes a little more effort. Jeff Garry Peirce 10/15/09 2:16 PM Perhaps I was erroneous in equating the two through a Cisco doc referencing DTPC to world-mode. 'When you enable Dynamic Transmit Power Control (DTPC), access points add channel and transmit power information to beacons. (On access points that run Cisco IOS software, this feature is called world mode.)' DTPC does appear to be CCX related, so it is likely irrelevant with regard to the mentioned Apple/Broadcom bug. Running 6.0.182, 'config 802.11a world-mode' is not an available option. 'config 802.11a dtpc' is. 'show 802.11a' will show the status of DTPC. I'll inquire w/Cisco. -- -Original Message- From: The EDUCAUSE Wireless Issues Constituent Group Listserv [mailto:wireless-...@listserv.educause.edu] On Behalf Of Matt Grover Sent: Thursday, October 15, 2009 2:51 PM To: WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU Subject: Re: [WIRELESS-LAN] Self-assigned IP on Macs It's under: show 802.11a(or b) -Matt Bob Richman wrote: So, how about the show command that displays the current setting? -Original Message- From: The EDUCAUSE Wireless Issues Constituent Group Listserv [mailto:wireless-...@listserv.educause.edu] On Behalf Of Matt Grover Sent: Thursday, October 15, 2009 1:21 PM To: WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU Subject: Re: [WIRELESS-LAN] Self-assigned IP on Macs Actually, if you are talking about specifically world-mode it's under: CLI: config 802.11a world-mode orconfig 802.11b world-mode -Matt -- Matt Grover === University of Florida Sr. Network Engineer=== http://net-services.ufl.edu m...@ufl.edu=== Florida Lambda Rail (352)273-1061 === http://www.flrnet.org/ ** 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/. ** Participation and subscription information for this EDUCAUSE Constituent Group discussion list can be found at http://www.educause.edu/groups/.
RE: [WIRELESS-LAN] Self-assigned IP on Macs
Has anyone gotten any approved suggestions for how to deal with these Apple issues from Cisco, beyond just trying things that seem to sometimes help? It is frustrating how the friendly and trouble-free Apple devices tend to be the least friendly and most troubling devices on the WLAN. A little bit of techno-irony to this:) -Lee From: The EDUCAUSE Wireless Issues Constituent Group Listserv [wireless-...@listserv.educause.edu] On Behalf Of Jeffrey Sessler [j...@scrippscollege.edu] Sent: Thursday, October 15, 2009 7:56 PM To: WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU Subject: Re: [WIRELESS-LAN] Self-assigned IP on Macs In 6.0, the code for world-mode didn't make it into the controller, but I believe it's in the AP's IOS commands, so it can be toggled but takes a little more effort. Jeff Garry Peirce 10/15/09 2:16 PM Perhaps I was erroneous in equating the two through a Cisco doc referencing DTPC to world-mode. 'When you enable Dynamic Transmit Power Control (DTPC), access points add channel and transmit power information to beacons. (On access points that run Cisco IOS software, this feature is called world mode.)' DTPC does appear to be CCX related, so it is likely irrelevant with regard to the mentioned Apple/Broadcom bug. Running 6.0.182, 'config 802.11a world-mode' is not an available option. 'config 802.11a dtpc' is. 'show 802.11a' will show the status of DTPC. I'll inquire w/Cisco. -- -Original Message- From: The EDUCAUSE Wireless Issues Constituent Group Listserv [mailto:wireless-...@listserv.educause.edu] On Behalf Of Matt Grover Sent: Thursday, October 15, 2009 2:51 PM To: WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU Subject: Re: [WIRELESS-LAN] Self-assigned IP on Macs It's under: show 802.11a(or b) -Matt Bob Richman wrote: So, how about the show command that displays the current setting? -Original Message- From: The EDUCAUSE Wireless Issues Constituent Group Listserv [mailto:wireless-...@listserv.educause.edu] On Behalf Of Matt Grover Sent: Thursday, October 15, 2009 1:21 PM To: WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU Subject: Re: [WIRELESS-LAN] Self-assigned IP on Macs Actually, if you are talking about specifically world-mode it's under: CLI: config 802.11a world-mode orconfig 802.11b world-mode -Matt -- Matt Grover === University of Florida Sr. Network Engineer=== http://net-services.ufl.edu m...@ufl.edu=== Florida Lambda Rail (352)273-1061 === http://www.flrnet.org/ ** 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/. ** 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/.
RE: [WIRELESS-LAN] Self-assigned IP on Macs
We had a similar problem with clients assigning themselves a self-assigned ip address. We had this problem on all of our Cisco 1252 antonomous mode dual radio APs. The problem was that on the 2.4 ghz radio the AP after a given time would stop sending client traffic to the assigned VLAN. The clients could still authenticate and the AP wouldn't drop the client, but they could move onto the VLAN. A re-boot would temporarily solve it. The fix was to upgrade the firmware of the 1252 APs to IOS 12.4(21a)JA1. When Cisco shipped the 1252 APs they had firmware 12.4(10b)JA. Nicholas Urrea Information Technology UC Hastings College of the Law urr...@uchastings.edu x4718 -Original Message- From: The EDUCAUSE Wireless Issues Constituent Group Listserv [mailto:wireless-...@listserv.educause.edu] On Behalf Of Anthony Croome Sent: Tuesday, October 13, 2009 9:30 PM To: WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU Subject: Re: [WIRELESS-LAN] Self-assigned IP on Macs Hi We are having this problem too. Is there any new information from people? We currently run Cisco wireless and have upgraded some locations to the new N standard. The problem appears to be isolated in the locations where we have upgraded but we can't be 100% sure. It is only appearing on macs, and they claim it works in one place but not another. All we can see is that it appears to be rejecting the dhcpoffer from the dhcp server. We haven't tried disabling dhcp proxy as discussed earlier in this thread, but others have said it didn't help. The latest temporary solution that has worked on two out of two macs is === All commands required at the command line: sudo ipconfig set en1 BOOTP (case sensitive and en1 is generally the wireless adapter on macs but it could possibly be different?) wait 5 seconds and then enter: sudo ipconfig set en1 DHCP === Anthony Croome QUT -Original Message- From: The EDUCAUSE Wireless Issues Constituent Group Listserv [mailto:wireless-...@listserv.educause.edu] On Behalf Of Earl Barfield Sent: Friday, 28 August 2009 11:39 PM To: WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU Subject: Re: [WIRELESS-LAN] Self-assigned IP on Macs 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 assigns itself a self-assigned IP. We are seeing this on a lot of new MacBooks and MacBookPros running 10.5.8. If we associate the computer to an autonomous AP it works fine. If we boot it in safe mode it works fine too. Everything else it just fails. I had the same problem after ugrading from 4.2.something to 5.2.193.0. Uncheck Enable DHCP Proxy under controller-advanced-DHCP and see if that fixes it. It worked for me. -- Earl Barfield -- Academic Research Tech / Information Technology Georgia Institute of Technology, Atlanta Georgia, 30332 Internet: earl.barfi...@oit.gatech.edue...@gatech.edu ** 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/. ** Participation and subscription information for this EDUCAUSE Constituent Group discussion list can be found at http://www.educause.edu/groups/.
RE: [WIRELESS-LAN] Self-assigned IP on Macs
We have seen this with our Aruba system, but only on our 802.1x/wpa2 SSID. We usually uncheck PEAP on the 802.1x profile of MACs, so they use TTLS, which seems to work better. If this fails, we then delete the 802.1x profile and anything related in the keychain. Usually that works. Unchecking IPv6 (enabled by default) seemed to have helped in the past. After a code upgrade in our system the problem went away, however, we have seen issues again with Snow Leopard (won't get an IP address, they end up with a self-assigned. But if you look at logs, they really haven't authenticated successfully, but for some reason they won't see an error message). This doesn't happen on an open SSID of course. Marcelo Lew Wireless Network Specialist University Technology Services University of Denver Desk: (303) 871-6523 Cell: (303) 669-4217 Fax: (303) 871-5900 Email: m...@du.edu -Original Message- From: The EDUCAUSE Wireless Issues Constituent Group Listserv [mailto:wireless-...@listserv.educause.edu] On Behalf Of Anthony Croome Sent: Tuesday, October 13, 2009 10:30 PM To: WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU Subject: Re: [WIRELESS-LAN] Self-assigned IP on Macs Hi We are having this problem too. Is there any new information from people? We currently run Cisco wireless and have upgraded some locations to the new N standard. The problem appears to be isolated in the locations where we have upgraded but we can't be 100% sure. It is only appearing on macs, and they claim it works in one place but not another. All we can see is that it appears to be rejecting the dhcpoffer from the dhcp server. We haven't tried disabling dhcp proxy as discussed earlier in this thread, but others have said it didn't help. The latest temporary solution that has worked on two out of two macs is === All commands required at the command line: sudo ipconfig set en1 BOOTP (case sensitive and en1 is generally the wireless adapter on macs but it could possibly be different?) wait 5 seconds and then enter: sudo ipconfig set en1 DHCP === Anthony Croome QUT -Original Message- From: The EDUCAUSE Wireless Issues Constituent Group Listserv [mailto:wireless-...@listserv.educause.edu] On Behalf Of Earl Barfield Sent: Friday, 28 August 2009 11:39 PM To: WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU Subject: Re: [WIRELESS-LAN] Self-assigned IP on Macs 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 assigns itself a self-assigned IP. We are seeing this on a lot of new MacBooks and MacBookPros running 10.5.8. If we associate the computer to an autonomous AP it works fine. If we boot it in safe mode it works fine too. Everything else it just fails. I had the same problem after ugrading from 4.2.something to 5.2.193.0. Uncheck Enable DHCP Proxy under controller-advanced-DHCP and see if that fixes it. It worked for me. -- Earl Barfield -- Academic Research Tech / Information Technology Georgia Institute of Technology, Atlanta Georgia, 30332 Internet: earl.barfi...@oit.gatech.edue...@gatech.edu ** 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/. ** Participation and subscription information for this EDUCAUSE Constituent Group discussion list can be found at http://www.educause.edu/groups/.
RE: [WIRELESS-LAN] Self-assigned IP on Macs
We have the second to latest version of Aruba OS and it's still an issue on some Macbook Pro's running either 10.5.8 or 10.6.x. We require 802.1x with PEAP on our WPA2 network. To fix the problem we have to create a new location under the network preferences. This is the only thing that works 100% of the time. It isn't an issue on the open SSID for us either. -Original Message- From: The EDUCAUSE Wireless Issues Constituent Group Listserv [mailto:wireless-...@listserv.educause.edu] On Behalf Of Marcelo Lew Sent: Wednesday, October 14, 2009 9:59 AM To: WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU Subject: Re: [WIRELESS-LAN] Self-assigned IP on Macs We have seen this with our Aruba system, but only on our 802.1x/wpa2 SSID. We usually uncheck PEAP on the 802.1x profile of MACs, so they use TTLS, which seems to work better. If this fails, we then delete the 802.1x profile and anything related in the keychain. Usually that works. Unchecking IPv6 (enabled by default) seemed to have helped in the past. After a code upgrade in our system the problem went away, however, we have seen issues again with Snow Leopard (won't get an IP address, they end up with a self-assigned. But if you look at logs, they really haven't authenticated successfully, but for some reason they won't see an error message). This doesn't happen on an open SSID of course. Marcelo Lew Wireless Network Specialist University Technology Services University of Denver Desk: (303) 871-6523 Cell: (303) 669-4217 Fax: (303) 871-5900 Email: m...@du.edu -Original Message- From: The EDUCAUSE Wireless Issues Constituent Group Listserv [mailto:wireless-...@listserv.educause.edu] On Behalf Of Anthony Croome Sent: Tuesday, October 13, 2009 10:30 PM To: WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU Subject: Re: [WIRELESS-LAN] Self-assigned IP on Macs Hi We are having this problem too. Is there any new information from people? We currently run Cisco wireless and have upgraded some locations to the new N standard. The problem appears to be isolated in the locations where we have upgraded but we can't be 100% sure. It is only appearing on macs, and they claim it works in one place but not another. All we can see is that it appears to be rejecting the dhcpoffer from the dhcp server. We haven't tried disabling dhcp proxy as discussed earlier in this thread, but others have said it didn't help. The latest temporary solution that has worked on two out of two macs is === All commands required at the command line: sudo ipconfig set en1 BOOTP (case sensitive and en1 is generally the wireless adapter on macs but it could possibly be different?) wait 5 seconds and then enter: sudo ipconfig set en1 DHCP === Anthony Croome QUT -Original Message- From: The EDUCAUSE Wireless Issues Constituent Group Listserv [mailto:wireless-...@listserv.educause.edu] On Behalf Of Earl Barfield Sent: Friday, 28 August 2009 11:39 PM To: WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU Subject: Re: [WIRELESS-LAN] Self-assigned IP on Macs 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 assigns itself a self-assigned IP. We are seeing this on a lot of new MacBooks and MacBookPros running 10.5.8. If we associate the computer to an autonomous AP it works fine. If we boot it in safe mode it works fine too. Everything else it just fails. I had the same problem after ugrading from 4.2.something to 5.2.193.0. Uncheck Enable DHCP Proxy under controller-advanced-DHCP and see if that fixes it. It worked for me. -- Earl Barfield -- Academic Research Tech / Information Technology Georgia Institute of Technology, Atlanta Georgia, 30332 Internet: earl.barfi...@oit.gatech.edue...@gatech.edu ** 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/. ** 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/.
RE: [WIRELESS-LAN] Self-assigned IP on Macs
I've been trying to follow this explanation, and I can't. Sending a response as unicast implies nothing about whether it is layer 2 or layer 3, and routing at layer 3 to a device that doesn't have a layer 3 address yet strikes me as Black Magic of the most heretical sort. I am not saying that the difference between DHCP and BOOTP, even perhaps specifically the difference between their use of broadcast and unicast, is not relevant to the issue being encountered. I am, however, saying that the reference to gratuitous ARP is at odds with what I think I know about TCP/IP, and that the only time a router should participate in the conversation is if DHCP/BOOTP requests are being relayed between the client subnet and a server on some other segment. (In fact, a gratuitous ARP is an unsolicited ARP *response* sent as a broadcast to inform clients that an IP address they may already have cached information for is associated with a new MAC address. It would be appropriate for a BOOTP client to advertise its newly-granted address that way since other devices should not have seen the unicast OFFER; it would be appropriate for a DHCP client to advertise its newly-granted address that way since other devices should not want or need to guess which of several offers it chose to accept. But in both cases it would come from the client after accepting an address offer, and not from a router as part of delivering one.) David Gillett CISSP CCNP -Original Message- From: Marcelo Lew [mailto:m...@du.edu] Sent: Wednesday, October 14, 2009 3:21 PM To: WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU Subject: Re: [WIRELESS-LAN] Self-assigned IP on Macs Looking for something else on the Aruba knowledge base, I found this article, which might help out explain some of the issues with MACs and IP addresses: There is a primary difference between Windows-based and Linux/Unix-based (this includes Apple OS X) DHCP clients. 1) Windows uses the newer DHCP DISCOVER process which is sent out as a broadcast (Layer 2). This broadcast is then responded to with a DHCP OFFER which is also broadcast back to the potential client. The client then sends back a DHCP REQUEST via unicast (Layer 3). The DHCP server then ACK (acknowledges) the request and normal TCP/IP communications can commence for the client. 2) Linux/Unix-based clients (including MAC OS X) use the older BOOTP method. The BOOTP DISCOVER is broadcast (Layer 2) out. The BOOTP OFFER is then sent back via unicast (Layer 3). This is the main difference between the two protocols. Being that the BOOTP OFFER is sent via Layer 3 instead of Layer 2, certain network topologies need to be considered. 3) When a BOOTP OFFER is sent back to the originating client, a gratuitous ARP must be done along the Layer 3 path. This is most important as it pertains to routers or Layer 3 switches. Since the client does not officially have an IP address yet, the Layer 3 device must populate its ARP cache with the MAC address of the client which is determined by the header of the BOOTP OFFER header. 4) In an instance where a BOOTP OFFER is made, but not accepted by the client, the MAC address of the client is still associated to the non-accepted IP address in all Layer 3 devices in the path. Where this becomes significant is when a BOOTP offer is made, not accepted, and then re-offered to another client within the ARP timeout period of a Layer 3 device. The BOOTP DISCOVER will be sent by a new client, but the OFFER will be sent via Layer 3 to the first device that had been offered the address. 5) Default values for industry routers and other network devices that support IP routing vary from vendor to vendor. Some ARP timeouts can be very low, and some users manually configure low ARP timeout values. If the scenario in item four happens within a timeout value of 4 minutes, this anomaly may present itself. 6) If your network has more than one DHCP/BOOTP server that is issuing offers, this may occur on a regular basis. When this is the case, you will notice that Windows clients are not having issues, but Mac and Linux clients are experiencing the issue. To circumvent or correct this potential problem, simply lower the ARP cache timeout on the Layer 3 devices in your network path. Remember, Layer 2 switches do not perform ARP, but simply cache the MAC address of directly connected devices. If you are using RADIUS to assign DHCP/BOOTP addresses, this anomaly will not occur. Marcelo Lew Wireless Network Specialist University Technology Services University of Denver Desk: (303) 871-6523 Cell: (303) 669-4217 Fax: (303) 871-5900 Email: m...@du.edu -Original Message- From: Marcelo Lew Sent: Wednesday, October 14, 2009 9:59 AM To: 'The EDUCAUSE Wireless Issues Constituent Group Listserv' Subject: RE: [WIRELESS-LAN] Self-assigned IP on Macs
RE: [WIRELESS-LAN] Self-assigned IP on Macs
Hi We are having this problem too. Is there any new information from people? We currently run Cisco wireless and have upgraded some locations to the new N standard. The problem appears to be isolated in the locations where we have upgraded but we can't be 100% sure. It is only appearing on macs, and they claim it works in one place but not another. All we can see is that it appears to be rejecting the dhcpoffer from the dhcp server. We haven't tried disabling dhcp proxy as discussed earlier in this thread, but others have said it didn't help. The latest temporary solution that has worked on two out of two macs is === All commands required at the command line: sudo ipconfig set en1 BOOTP (case sensitive and en1 is generally the wireless adapter on macs but it could possibly be different?) wait 5 seconds and then enter: sudo ipconfig set en1 DHCP === Anthony Croome QUT -Original Message- From: The EDUCAUSE Wireless Issues Constituent Group Listserv [mailto:wireless-...@listserv.educause.edu] On Behalf Of Earl Barfield Sent: Friday, 28 August 2009 11:39 PM To: WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU Subject: Re: [WIRELESS-LAN] Self-assigned IP on Macs 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 assigns itself a self-assigned IP. We are seeing this on a lot of new MacBooks and MacBookPros running 10.5.8. If we associate the computer to an autonomous AP it works fine. If we boot it in safe mode it works fine too. Everything else it just fails. I had the same problem after ugrading from 4.2.something to 5.2.193.0. Uncheck Enable DHCP Proxy under controller-advanced-DHCP and see if that fixes it. It worked for me. -- Earl Barfield -- Academic Research Tech / Information Technology Georgia Institute of Technology, Atlanta Georgia, 30332 Internet: earl.barfi...@oit.gatech.edue...@gatech.edu ** 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/.
RE: [WIRELESS-LAN] Self-assigned IP on Macs...
Goolgle for RFC 4436, Apple, and wireless, you'll find much more on the topic. This is worth reading, too: http://lists.sans.org/pipermail/unisog/2007-January/027056.html Frank -Original Message- From: The EDUCAUSE Wireless Issues Constituent Group Listserv [mailto:wireless-...@listserv.educause.edu] On Behalf Of Jeffrey Sessler Sent: Thursday, August 27, 2009 10:56 PM To: WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU Subject: Re: [WIRELESS-LAN] Self-assigned IP on Macs... It's likely that you have require DHCP enabled on the Cisco controller. This is akin to Cisco DHCP Snooping with IP Source Verify. Once the Mac tries to use the same IP address without a DHCP request, it gets excluded. I'd try disabling the Require DHCP on the Cisco controller and see what happens. Jeff Hector J Rios hr...@lsu.edu 08/27/09 6:58 PM Brian, We are seeing the same thing. Running tcpdump on the Mac computer we see the last known address and we also see the address that our DHCP server offers but the client continues to use its last IP. Hector From: The EDUCAUSE Wireless Issues Constituent Group Listserv [mailto:wireless-...@listserv.educause.edu] On Behalf Of Fruits, Brian Sent: Thursday, August 27, 2009 7:51 PM To: WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU Subject: Re: [WIRELESS-LAN] Self-assigned IP on Macs... I have seen similar behavior with Macs and iPhones where the first DHCP request is for (and sometimes from) their last known IP address. If DHCP fails they will sometimes continue to use their last IP. --- Brian Fruits UNC Charlotte ITS, Network Services bdfru...@uncc.edu --- If you are not the intended recipient of this transmission or a person responsible for delivering it to the intended recipient, any disclosure, copying, distribution, or other use of any of the information in this transmission is strictly prohibited. If you have received this transmission in error, please notify me immediately by reply email or by telephone at 704-687-3100. Thank you. From: The EDUCAUSE Wireless Issues Constituent Group Listserv [mailto:wireless-...@listserv.educause.edu] On Behalf Of Robert Owens Sent: Thursday, August 27, 2009 5:36 PM To: WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU Subject: Re: [WIRELESS-LAN] Self-assigned IP on Macs... We have seen a number of Mac's getting put into exclusion because they are trying to use an IP address that has already been assigned to another device. at least that is the implication from looking at the WISM logs. Does anyone know how apple handles DHCP leasing? Especially when they are just being powered up? We speculate that they are trying to attach to their previous IP when in the world of large networks that IP could be handed out to another client but don't know for sure. Bob Owens Kansas State University - Original Message - From: Hector J Rios mailto:hr...@lsu.edu To: WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU Sent: Thursday, August 27, 2009 3:58 PM Subject: [WIRELESS-LAN] 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 assigns itself a self-assigned IP. We are seeing this on a lot of new MacBooks and MacBookPros running 10.5.8. If we associate the computer to an autonomous AP it works fine. If we boot it in safe mode it works fine too. Everything else it just fails. Thanks, Hector Rios Louisiana State University ** 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/. ** 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/. /mailto:hr...@lsu.edu/hr...@lsu.edu ** 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/.
RE: [WIRELESS-LAN] Self-assigned IP on Macs...
Google for RFC 4436, Apple, and wireless, you'll find much more on the topic. This is worth reading, too: http://lists.sans.org/pipermail/unisog/2007-January/027056.html Frank -Original Message- From: The EDUCAUSE Wireless Issues Constituent Group Listserv [mailto:wireless-...@listserv.educause.edu] On Behalf Of Jeffrey Sessler Sent: Thursday, August 27, 2009 10:56 PM To: WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU Subject: Re: [WIRELESS-LAN] Self-assigned IP on Macs... It's likely that you have require DHCP enabled on the Cisco controller. This is akin to Cisco DHCP Snooping with IP Source Verify. Once the Mac tries to use the same IP address without a DHCP request, it gets excluded. I'd try disabling the Require DHCP on the Cisco controller and see what happens. Jeff Hector J Rios hr...@lsu.edu 08/27/09 6:58 PM Brian, We are seeing the same thing. Running tcpdump on the Mac computer we see the last known address and we also see the address that our DHCP server offers but the client continues to use its last IP. Hector From: The EDUCAUSE Wireless Issues Constituent Group Listserv [mailto:wireless-...@listserv.educause.edu] On Behalf Of Fruits, Brian Sent: Thursday, August 27, 2009 7:51 PM To: WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU Subject: Re: [WIRELESS-LAN] Self-assigned IP on Macs... I have seen similar behavior with Macs and iPhones where the first DHCP request is for (and sometimes from) their last known IP address. If DHCP fails they will sometimes continue to use their last IP. --- Brian Fruits UNC Charlotte ITS, Network Services bdfru...@uncc.edu --- If you are not the intended recipient of this transmission or a person responsible for delivering it to the intended recipient, any disclosure, copying, distribution, or other use of any of the information in this transmission is strictly prohibited. If you have received this transmission in error, please notify me immediately by reply email or by telephone at 704-687-3100. Thank you. From: The EDUCAUSE Wireless Issues Constituent Group Listserv [mailto:wireless-...@listserv.educause.edu] On Behalf Of Robert Owens Sent: Thursday, August 27, 2009 5:36 PM To: WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU Subject: Re: [WIRELESS-LAN] Self-assigned IP on Macs... We have seen a number of Mac's getting put into exclusion because they are trying to use an IP address that has already been assigned to another device. at least that is the implication from looking at the WISM logs. Does anyone know how apple handles DHCP leasing? Especially when they are just being powered up? We speculate that they are trying to attach to their previous IP when in the world of large networks that IP could be handed out to another client but don't know for sure. Bob Owens Kansas State University - Original Message - From: Hector J Rios mailto:hr...@lsu.edu To: WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU Sent: Thursday, August 27, 2009 3:58 PM Subject: [WIRELESS-LAN] 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 assigns itself a self-assigned IP. We are seeing this on a lot of new MacBooks and MacBookPros running 10.5.8. If we associate the computer to an autonomous AP it works fine. If we boot it in safe mode it works fine too. Everything else it just fails. Thanks, Hector Rios Louisiana State University ** 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/. ** 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/. /mailto:hr...@lsu.edu/hr...@lsu.edu ** 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/.
Re: [WIRELESS-LAN] Self-assigned IP on Macs
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 assigns itself a self-assigned IP. We are seeing this on a lot of new MacBooks and MacBookPros running 10.5.8. If we associate the computer to an autonomous AP it works fine. If we boot it in safe mode it works fine too. Everything else it just fails. I had the same problem after ugrading from 4.2.something to 5.2.193.0. Uncheck Enable DHCP Proxy under controller-advanced-DHCP and see if that fixes it. It worked for me. -- Earl Barfield -- Academic Research Tech / Information Technology Georgia Institute of Technology, Atlanta Georgia, 30332 Internet: earl.barfi...@oit.gatech.edue...@gatech.edu ** Participation and subscription information for this EDUCAUSE Constituent Group discussion list can be found at http://www.educause.edu/groups/.
Re: [WIRELESS-LAN] Self-assigned IP on Macs...
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 clients were doing it seemed to be different though. I haven't had time to do a thorough analysis of Mac dhcp behavior. That aside, what I noticed was that the clients having the trouble showed up in the controller logs as being put into an Exclusion state. This was because the controllers security mechanism was kicking in and excluding the client because of IP theft or reuse. By disabling the IP theft or Reuse under security, wireless protection policies, client exclusion policies caused it to stop happening. Looking into it further, the clients that were being blocked were coming in with addresses in the 192.168.1.x range. This is probably the most common range for home networking so it's no surprise they would have that address range coming in from home. I see two possibilities why it triggered IP theft. The first possibility is that another client had come in under that address and the second one gets blocked. The more likely cause I think is that we have the service vlan on the controllers numbered in the 192.168.1.0/24 subnet just as the wism setup docs show. I think this IP space is colliding with the clients coming in and trying to use it. My guess is that the controllers see the space in use by themselves and flag it. I have not had time however to test this theory. I also do not know why the problem was only exhibited by Macs. Seems to be something different in their dhcp client behavior. -Matt - Original Message - *From:* Hector J Rios mailto:hr...@lsu.edu *To:* WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU mailto:WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU *Sent:* Thursday, August 27, 2009 3:58 PM *Subject:* [WIRELESS-LAN] 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 assigns itself a self-assigned IP. We are seeing this on a lot of new MacBooks and MacBookPros running 10.5.8. If we associate the computer to an autonomous AP it works fine. If we boot it in safe mode it works fine too. Everything else it just fails. Thanks, Hector Rios Louisiana State University -- Matt Grover === University of Florida Sr. Network Engineer=== http://net-services.ufl.edu m...@ufl.edu=== Florida Lambda Rail (352)273-1061 === http://www.flrnet.org/ ** Participation and subscription information for this EDUCAUSE Constituent Group discussion list can be found at http://www.educause.edu/groups/.
Re: [WIRELESS-LAN] Self-assigned IP on Macs...
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 that we saw DHCPREQUEST packets from the client asking for a specifc 192.168.1.x address. This seems to indicate it was using the address previously. The server answered with an DHCPOFFER from a different configured range. The client however would not take it or did not get it. When the IP theft function was turned off the client would then complete the dhcp process normally. Also, this did not always happen. From talking to one student it was generally exhibited when he first came in and had used the host on his home network previously. -Matt Methven, Peter J wrote: Just for information MAC OS/X Leopard (and probably Tiger) both default to an IP Address in the 192.168.1.n range when they cannot acquire an IP address, like windows machines default to a 169.254.n.n ip address. Presumably if they are being excluded from network access and not acquiring an IP address from DHCP they will fall back to a self-assigned IP address. Many Thanks Peter -Original Message- From: The EDUCAUSE Wireless Issues Constituent Group Listserv [mailto:wireless-...@listserv.educause.edu] On Behalf Of Matt Grover Sent: 28 August 2009 15:10 To: WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU Subject: Re: [WIRELESS-LAN] Self-assigned IP on Macs... 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 clients were doing it seemed to be different though. I haven't had time to do a thorough analysis of Mac dhcp behavior. That aside, what I noticed was that the clients having the trouble showed up in the controller logs as being put into an Exclusion state. This was because the controllers security mechanism was kicking in and excluding the client because of IP theft or reuse. By disabling the IP theft or Reuse under security, wireless protection policies, client exclusion policies caused it to stop happening. Looking into it further, the clients that were being blocked were coming in with addresses in the 192.168.1.x range. This is probably the most common range for home networking so it's no surprise they would have that address range coming in from home. I see two possibilities why it triggered IP theft. The first possibility is that another client had come in under that address and the second one gets blocked. The more likely cause I think is that we have the service vlan on the controllers numbered in the 192.168.1.0/24 subnet just as the wism setup docs show. I think this IP space is colliding with the clients coming in and trying to use it. My guess is that the controllers see the space in use by themselves and flag it. I have not had time however to test this theory. I also do not know why the problem was only exhibited by Macs. Seems to be something different in their dhcp client behavior. -Matt - Original Message - *From:* Hector J Rios mailto:hr...@lsu.edu *To:* WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU mailto:WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU *Sent:* Thursday, August 27, 2009 3:58 PM *Subject:* [WIRELESS-LAN] 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 assigns itself a self-assigned IP. We are seeing this on a lot of new MacBooks and MacBookPros running 10.5.8. If we associate the computer to an autonomous AP it works fine. If we boot it in safe mode it works fine too. Everything else it just fails. Thanks, Hector Rios Louisiana State University -- Matt Grover === University of Florida Sr. Network Engineer=== http://net-services.ufl.edu m...@ufl.edu=== Florida Lambda Rail (352)273-1061 === http://www.flrnet.org/ ** Participation and subscription information for this EDUCAUSE Constituent Group discussion list can be found at http://www.educause.edu/groups/.
Re: [WIRELESS-LAN] Self-assigned IP on Macs...
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 Rios To: WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU Sent: Friday, August 28, 2009 12:51 PM Subject: Re: [WIRELESS-LAN] Self-assigned IP on Macs... IP Theft and DHCP required are all turned off. We've never had them enabled. Still no luck. I've even tried it with the internal DHCP server in the WiSMs and it doesn't make a difference. We have Cisco and Apple involved. We'll give you guys an update if we find something. Hector ** 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/.
Re: [WIRELESS-LAN] Self-assigned IP on Macs...
We have seen a number of Mac's getting put into exclusion because they are trying to use an IP address that has already been assigned to another device. at least that is the implication from looking at the WISM logs. Does anyone know how apple handles DHCP leasing? Especially when they are just being powered up? We speculate that they are trying to attach to their previous IP when in the world of large networks that IP could be handed out to another client but don't know for sure. Bob Owens Kansas State University - Original Message - From: Hector J Rios To: WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU Sent: Thursday, August 27, 2009 3:58 PM Subject: [WIRELESS-LAN] 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 assigns itself a self-assigned IP. We are seeing this on a lot of new MacBooks and MacBookPros running 10.5.8. If we associate the computer to an autonomous AP it works fine. If we boot it in safe mode it works fine too. Everything else it just fails. Thanks, Hector Rios Louisiana State University ** 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/.
Re: [WIRELESS-LAN] Self-assigned IP on Macs...
It's likely that you have require DHCP enabled on the Cisco controller. This is akin to Cisco DHCP Snooping with IP Source Verify. Once the Mac tries to use the same IP address without a DHCP request, it gets excluded. I'd try disabling the Require DHCP on the Cisco controller and see what happens. Jeff Hector J Rios hr...@lsu.edu 08/27/09 6:58 PM Brian, We are seeing the same thing. Running tcpdump on the Mac computer we see the last known address and we also see the address that our DHCP server offers but the client continues to use its last IP. Hector From: The EDUCAUSE Wireless Issues Constituent Group Listserv [mailto:wireless-...@listserv.educause.edu] On Behalf Of Fruits, Brian Sent: Thursday, August 27, 2009 7:51 PM To: WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU Subject: Re: [WIRELESS-LAN] Self-assigned IP on Macs... I have seen similar behavior with Macs and iPhones where the first DHCP request is for (and sometimes from) their last known IP address. If DHCP fails they will sometimes continue to use their last IP. --- Brian Fruits UNC Charlotte ITS, Network Services bdfru...@uncc.edu --- If you are not the intended recipient of this transmission or a person responsible for delivering it to the intended recipient, any disclosure, copying, distribution, or other use of any of the information in this transmission is strictly prohibited. If you have received this transmission in error, please notify me immediately by reply email or by telephone at 704-687-3100. Thank you. From: The EDUCAUSE Wireless Issues Constituent Group Listserv [mailto:wireless-...@listserv.educause.edu] On Behalf Of Robert Owens Sent: Thursday, August 27, 2009 5:36 PM To: WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU Subject: Re: [WIRELESS-LAN] Self-assigned IP on Macs... We have seen a number of Mac's getting put into exclusion because they are trying to use an IP address that has already been assigned to another device. at least that is the implication from looking at the WISM logs. Does anyone know how apple handles DHCP leasing? Especially when they are just being powered up? We speculate that they are trying to attach to their previous IP when in the world of large networks that IP could be handed out to another client but don't know for sure. Bob Owens Kansas State University - Original Message - From: Hector J Rios mailto:hr...@lsu.edu To: WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU Sent: Thursday, August 27, 2009 3:58 PM Subject: [WIRELESS-LAN] 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 assigns itself a self-assigned IP. We are seeing this on a lot of new MacBooks and MacBookPros running 10.5.8. If we associate the computer to an autonomous AP it works fine. If we boot it in safe mode it works fine too. Everything else it just fails. Thanks, Hector Rios Louisiana State University ** 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/. ** 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/. /mailto:hr...@lsu.edu/hr...@lsu.edu ** Participation and subscription information for this EDUCAUSE Constituent Group discussion list can be found at http://www.educause.edu/groups/.
