Looks like no one’s replied in a while. To start the conversation again, simply ask a new question.

Level 1

5 points

PEAP wireless @work ...

Has anyone successfully setup an 802.1x configuration for PEAP on their MacBook Pro? I have a PEAP config that works for my PowerBook, but the EXACT SAME configuration is not working for the MacBook Pro. It looks as if everything is fine (no authentication errors or anything), but no dhcp IP address is ever assigned to the wireless (en1); instead it has a 169.x.x.x address??

Any ideas?

PowerBook G4/Sager 5600/Custom Intel Machines/NEW MACBOOK PRO 2.16/7200rpm/2gb, Mac OS X (10.4.5)

Posted on Feb 23, 2006 10:29 AM

52 replies

Mar 30, 2006 11:11 PM in response to trygve

I've been having this problem as well (same circumstances as
everybody else above, PEAP shows connected but I receive no IP).

yep...and often times internet connect hangs at "authenticating". when it manages to get past the authentication phase, it displays "connected" info...but we don't get a valid ip address (ends up with 169.254.xx.xx).

bummer...i would LOVE to help test the fix for this.

don

Mar 30, 2006 11:33 PM in response to don montalvo

There is a fix for it, check out my thread in this forum:
http://discussions.apple.com/thread.jspa?threadID=425113&tstart=0

Mar 31, 2006 1:27 AM in response to BlackNTan

To be technically correct, it's not PEAP that's broken. It's connection with WEP with a dynamic key that is broken. The symtom is that 802.1x authentication is successful. Afterwards, the wireless network (Access Point) will generate a pair of dynamic WEP keys (one for unicast and the other one for multicast) for use as the encryption keys between the 802.1x supplicant (the MBP) and the AP.

I have tried successfully with MBP connecting to a network using WPA/PEAP/MS-ChapV2, and WPA2/PEAP/MS-ChapV2 successfully. (Haven't tried TTLS or TLS yet but I assume that it should work.

sveckers

Level 1

0 points

Mar 31, 2006 5:16 AM in response to Anthony Romano

Thank you! Thank you! Thank you!

Works great on my MBP 1.8 PEAEP wireless at school.

Apr 3, 2006 6:33 PM in response to Albert Pang

FYI, looks like that this problem has been fixed with the 10.4.6 upgrade (Airport driver version 0.1.17) for the MacBook Pro.

BlackNTan Author

Level 1

5 points

Apr 3, 2006 7:43 PM in response to Albert Pang

Yes. The latest OSX update has fixed the PEAP issue.

Apr 4, 2006 9:15 AM in response to BlackNTan

I am in contact with an Apple System Engineer who sent me this yesterday:

--begin e-mail thread--

The just released 10.4.6 update should address this.

I should note that any systems that were modified by the process listed in the enclosed URL may not upgrade properly. Since it recommended a non-Apple modification to an Apple file, the behavior may not be what was desired.

On Mar 31, 2006, at 10:29 AM, Steve Giessler wrote:

Check it out:

http://discussions.apple.com/thread.jspa?threadID=425113&tstart=0

Apple needs to provide a real fix though.

Steve

=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=

Apple
Systems Engineer

--end e-mail thread--

Based on what Brett said above, it may be prudent to restore the broken /System/Library/Extensions/IO80211Family.kext before running the 10.4.6 update on your MBP. That's what I did and the result was that 10.4.6 update did in fact fix the original problem.

PEAP wireless @work ...