PEAP wireless @work ...

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

Reply

Answer 1

Feb 23, 2006 11:47 AM in response to BlackNTan

I have the same exact problem. My buddies old G4 power book connects fine, but my macbook with the EXACT same setting does not. ;-(

Pat

MacBook Pro Mac OS X (10.4.5)

Reply

Answer 2

JoeyMT

Level 1

85 points

Mar 3, 2006 11:34 AM in response to BlackNTan

Working on this roblem right now, I deleted all the configurations and then deleted all the keychain files related to wireless. server certificates Usually that will fix PEAP connectivity problems. but I am still struggling with this one. Hope someone jumps IN on this that can help.

Reply

Answer 3

Mar 6, 2006 9:49 AM in response to BlackNTan

I am having exactly the same issue. PEAP does not work. I can authenticate and connect to the Radius server. Unfortunately, the MacBook Pro never sends a DHCP request.

In the LEAP topic someone mentioned that interface robustness fixed their PEAP problem but it doesn't seem to help me.

Please post any ideas or fixes if you come across them.

Reply

Answer 4

Mar 6, 2006 10:14 AM in response to Micah Lamb

Yes, I am currently having the same problem. It fully connects, and the certificates are accepted, but I never get a real world IP address. I'v tried many things and nothing works. It looks to me like a problem with the OS on intel. Does this problem also occur on the intel iMacs?

Reply

Answer 5

Mar 6, 2006 11:48 AM in response to gizmo8599

I have the exact same problem. My (now sold) powerbook g4 worked fine with peap at my office. Now, I am able to show connected, and the timer is incrementing, but "ifconfig en1" shows no ip address.

This issue coupled with the 802.1q voip phone problem on the ethernet port makes like very difficult with my new MBP. $3000 is a lot of money to pay for a notebook that cannot connect to the internet at work.

PLEASE FIX THIS APPLE!!!

Reply

Answer 6

ledavis

Level 1

10 points

Mar 6, 2006 2:19 PM in response to Jimmy Oliver

I am having the same problem as well. I've spent several hours today with apple and with my network administrator and we still haven't resolved anything. Apple is saying that it is a problem with the network and using PEAP for authentication. He suggested getting the network admin. to change to another form of authentication. However, my conversation with my network administrator didnt go very well either. This was the first macbook pro he had seen and he had no idea what to do with it.

If you have this problem, please post to get this on the radar at apple.

macbook pro Mac OS X (10.4.5)

Reply

Answer 7

artodea

Level 1

0 points

Mar 7, 2006 5:24 AM in response to ledavis

Same problem here - PEAP authentication is successful, but no network connectivity.

Reply

Answer 8

Mar 7, 2006 9:00 AM in response to BlackNTan

Same problem here. Using MacBook trying to associate to Cisco AP infrastructure using 802.1X (PEAP) or LEAP. On my end, I don't see the client authenticate to my Cisco ACS radius server. Nor do I see the client attached to the AP. But the client thinks it is associated. The client shows a 169.x.x.x ip and of course, cannot communicate on the WLAN.

Reply

Answer 9

zmq503o1

Level 1

0 points

Mar 7, 2006 11:29 AM in response to BlackNTan

Same problem here. Works on a G4 powerbook running 10.4.5, but the MacBook Pro running the same MacOS version with the exact same settings does not work. Any idea when apple will fix this?

802.1x
PEAP
MSCHAPv2

Reply

Answer 10

Pete H

Level 3

570 points

Mar 7, 2006 11:35 PM in response to BlackNTan

You guys who are having problems, what kind of access points and radius servers are you using? I was able to connect my MBP to an AirPort Express using Elektron as its radius server with PEAP without any problem. Also, it might be helpful to see output from the following command in terminal, "sudo tcpdump -i en1", during and shortly after you successfully authenticate but can't get an IP address.

Reply

Answer 11

artodea

Level 1

0 points

Mar 8, 2006 4:56 AM in response to Pete H

Here's the output of "sudo tcpdump -i en1":

07:47:36.627898 IP 0.0.0.0.bootpc > broadcasthost.bootps: BOOTP/DHCP, Request from 00:14:51:ed:85:f4 (oui Unknown), length: 300
07:47:36.628950 IP6 shemp.local > ff02::2: ICMP6, router solicitation, length 16
07:47:36.629327 EAP code=1 id=0 length=5
07:47:37.043498 EAP code=1 id=0 length=10
07:47:37.047205 EAP code=1 id=0 length=6
07:47:37.060174 EAP code=1 id=0 length=102
07:47:37.069127 EAP code=1 id=0 length=695
07:47:37.072200 EAP code=1 id=0 length=208
07:47:37.084486 EAP code=1 id=0 length=53
07:47:37.137792 EAP code=1 id=0 length=6
07:47:37.140848 EAP code=1 id=0 length=32
07:47:37.141130 EAP code=1 id=0 length=37
07:47:37.144567 EAP code=1 id=0 length=72
07:47:37.171482 EAP code=1 id=0 length=91
07:47:37.409497 EAP code=1 id=0 length=78
07:47:37.409939 EAP code=1 id=0 length=33
07:47:37.413227 EAP code=1 id=0 length=42
07:47:37.413479 EAP code=1 id=0 length=42
07:47:37.416847 EAP code=1 id=0 length=4
07:47:37.418042 EAP code=1 id=3 length=57
07:47:37.419351 EAP code=1 id=3 length=57
07:47:37.586542 IP6 shemp.local.50450 > ff02::fb.mdns: 43226+[|domain]
07:47:38.087372 IP6 shemp.local.50450 > ff02::fb.mdns: 43226+[|domain]
07:47:38.277954 IP6 shemp.local > ff02::2: ICMP6, router solicitation, length 16
07:47:38.386978 IP 0.0.0.0.bootpc > broadcasthost.bootps: BOOTP/DHCP, Request from 00:14:51:ed:85:f4 (oui Unknown), length: 300
07:47:38.588187 IP6 shemp.local.50450 > ff02::fb.mdns: 43226+[|domain]
07:47:39.045606 IP6 shemp.local > ff02::fb: HBH ICMP6, multicast listener reportmax resp delay: 0 addr: ff02::fb, length 24
07:47:39.047090 IP6 shemp.local.mdns > ff02::fb.mdns: 0 [4q][|domain]
07:47:39.088988 IP6 shemp.local.50450 > ff02::fb.mdns: 43226+[|domain]
07:47:39.294936 IP6 shemp.local.mdns > ff02::fb.mdns: 0 [2q] [2n][|domain]
07:47:39.545007 IP6 shemp.local.mdns > ff02::fb.mdns: 0 [2q] [2n][|domain]
07:47:39.794849 IP6 shemp.local.mdns > ff02::fb.mdns: 0 [2q] [2n][|domain]
07:47:40.045786 IP6 shemp.local.mdns > ff02::fb.mdns: 0*- [0q] 7/0/0[|domain]
07:47:40.146505 IP6 shemp.local.mdns > ff02::fb.mdns: 0 [4q][|domain]
07:47:40.694774 IP 0.0.0.0.bootpc > broadcasthost.bootps: BOOTP/DHCP, Request from 00:14:51:ed:85:f4 (oui Unknown), length: 300
07:47:40.695474 arp who-has 169.254.155.120 tell 0.0.0.0
07:47:40.995721 arp who-has 169.254.155.120 tell 0.0.0.0
07:47:41.046483 IP6 shemp.local.mdns > ff02::fb.mdns: 0*- [0q] 7/0/0[|domain]
07:47:41.124580 IP6 shemp.local > ff02::2: ICMP6, router solicitation, length 16
07:47:41.296071 arp who-has 169.254.155.120 tell 0.0.0.0
07:47:41.342744 IP6 shemp.local.50454 > ff02::fb.mdns: 40726+[|domain]
07:47:41.596798 arp who-has 169.254.155.120 tell 0.0.0.0
07:47:41.843474 IP6 shemp.local.50454 > ff02::fb.mdns: 40726+[|domain]
07:47:41.897162 arp who-has 169.254.155.120 tell 169.254.155.120
07:47:42.146566 IP6 shemp.local.mdns > ff02::fb.mdns: 0 [4q][|domain]
07:47:42.197782 arp who-has 169.254.155.120 tell 169.254.155.120
07:47:42.222286 IP 169.254.155.120.50456 > 224.0.0.251.mdns: 64503+ PTR? 120.155.254.169.in-addr.arpa. (46)
07:47:42.222298 IP 169.254.155.120.50455 > 224.0.0.251.mdns: 33268+ PTR? 120.155.254.169.in-addr.arpa. (46)
07:47:42.473168 IP6 shemp.local.50457 > ff02::fb.mdns: 64503+[|domain]
07:47:42.473279 IP6 shemp.local.50458 > ff02::fb.mdns: 33268+[|domain]
07:47:42.723505 IP 169.254.155.120.50456 > 224.0.0.251.mdns: 64503+ PTR? 120.155.254.169.in-addr.arpa. (46)
07:47:42.723608 IP 169.254.155.120.50455 > 224.0.0.251.mdns: 33268+ PTR? 120.155.254.169.in-addr.arpa. (46)
07:47:42.974329 IP6 shemp.local.50458 > ff02::fb.mdns: 33268+[|domain]
07:47:42.974348 IP6 shemp.local.50457 > ff02::fb.mdns: 64503+[|domain]
07:47:43.224776 IP 169.254.155.120.50456 > 224.0.0.251.mdns: 64503+ PTR? 120.155.254.169.in-addr.arpa. (46)
07:47:43.224787 IP 169.254.155.120.50455 > 224.0.0.251.mdns: 33268+ PTR? 120.155.254.169.in-addr.arpa. (46)
07:47:43.271661 00:0c:f1:1c:80:94 (oui Unknown) Unknown SSAP 0x46 > Broadcast Unknown DSAP 0xc8 Supervisory, Receiver not Ready, rcv seq 112, Flags [Command], length 215
07:47:43.475519 IP6 shemp.local.50457 > ff02::fb.mdns: 64503+[|domain]
07:47:43.475746 IP6 shemp.local.50458 > ff02::fb.mdns: 33268+[|domain]
07:47:43.725778 IP 169.254.155.120.50456 > 224.0.0.251.mdns: 64503+ PTR? 120.155.254.169.in-addr.arpa. (46)
07:47:43.726057 IP 169.254.155.120.50455 > 224.0.0.251.mdns: 33268+ PTR? 120.155.254.169.in-addr.arpa. (46)
07:47:43.976364 IP6 shemp.local.50457 > ff02::fb.mdns: 64503+[|domain]
07:47:43.976671 IP6 shemp.local.50458 > ff02::fb.mdns: 33268+[|domain]
07:47:44.213546 IP6 shemp.local > ff02::fb: HBH ICMP6, multicast listener reportmax resp delay: 0 addr: ff02::fb, length 24
07:47:44.216273 IP6 shemp.local > ff02::2: HBH ICMP6, multicast listener donemax resp delay: 0 addr: ff02::fb, length 24
07:47:44.216458 IP6 shemp.local > ff02::fb: HBH ICMP6, multicast listener reportmax resp delay: 0 addr: ff02::fb, length 24
07:47:44.216606 IP 169.254.155.120 > 224.0.0.251: igmp v2 report 224.0.0.251
07:47:44.218190 IP 169.254.155.120.mdns > 224.0.0.251.mdns: 0 [9q] PTR (Cache flush)? afpovertcp.tcp.local. PTR (Cache flush)? nfs.tcp.local.[|domain]
07:47:44.218266 IP6 shemp.local.mdns > ff02::fb.mdns: 0 [9q][|domain]
07:47:44.465943 IP 169.254.155.120.mdns > 224.0.0.251.mdns: 0 [3q] [3n][|domain]
07:47:44.466047 IP6 shemp.local.mdns > ff02::fb.mdns: 0 [3q] [3n][|domain]
07:47:44.716794 IP 169.254.155.120.mdns > 224.0.0.251.mdns: 0 [3q] [3n][|domain]
07:47:44.716888 IP6 shemp.local.mdns > ff02::fb.mdns: 0 [3q] [3n][|domain]
07:47:44.967659 IP 169.254.155.120.mdns > 224.0.0.251.mdns: 0 [3q] [3n][|domain]
07:47:44.967747 IP6 shemp.local.mdns > ff02::fb.mdns: 0 [3q] [3n][|domain]
07:47:45.085904 IP 0.0.0.0.bootpc > broadcasthost.bootps: BOOTP/DHCP, Request from 00:14:51:ed:85:f4 (oui Unknown), length: 300
07:47:45.217485 IP 169.254.155.120.mdns > 224.0.0.251.mdns: 0*- [0q] 9/0/0[|domain]
07:47:45.217553 IP6 shemp.local.mdns > ff02::fb.mdns: 0*- [0q] 9/0/0[|domain]
07:47:45.222563 IP 169.254.155.120.50459 > 239.255.255.253.svrloc: UDP, length 36
07:47:45.222760 IP 169.254.155.120.50460 > 239.255.255.253.svrloc: UDP, length 36
07:47:45.223294 IP 169.254.155.120.50461 > 239.255.255.253.svrloc: UDP, length 36
07:47:45.223517 IP 169.254.155.120.50462 > 239.255.255.253.svrloc: UDP, length 36
07:47:45.263411 IP6 shemp.local > ff02::2: ICMP6, router solicitation, length 16
07:47:45.317246 IP 169.254.155.120.mdns > 224.0.0.251.mdns: 0 [9q] PTR? afpovertcp.tcp.local. PTR? nfs.tcp.local.[|domain]
07:47:45.317333 IP6 shemp.local.mdns > ff02::fb.mdns: 0 [9q][|domain]
07:47:46.217189 IP 169.254.155.120.mdns > 224.0.0.251.mdns: 0*- [0q] 9/0/0[|domain]
07:47:46.217286 IP6 shemp.local.mdns > ff02::fb.mdns: 0*- [0q] 9/0/0[|domain]
07:47:46.225262 IP 169.254.155.120 > 224.0.0.251: igmp v2 report 224.0.0.251
07:47:47.205311 IP 169.254.155.120.50463 > 239.255.255.253.svrloc: UDP, length 49
07:47:47.221170 IP 169.254.155.120.50463 > 239.255.255.253.svrloc: UDP, length 49
07:47:47.317340 IP 169.254.155.120.mdns > 224.0.0.251.mdns: 0 [9q] PTR? afpovertcp.tcp.local. PTR? nfs.tcp.local.[|domain]
07:47:47.317454 IP6 shemp.local.mdns > ff02::fb.mdns: 0 [9q][|domain]
07:47:48.217422 IP 169.254.155.120.mdns > 224.0.0.251.mdns: 0*- [0q] 9/0/0[|domain]
07:47:48.217525 IP6 shemp.local.mdns > ff02::fb.mdns: 0*- [0q] 9/0/0[|domain]
07:47:48.272224 IP 169.254.155.120.50464 > 169.254.255.255.netbios-ns: NBT UDP PACKET(137): QUERY; REQUEST; BROADCAST
07:47:48.411195 IP 169.254.155.120.50465 > 224.0.0.251.mdns: 11015+ PTR? 255.255.254.169.in-addr.arpa. (46)
07:47:48.543113 IP 169.254.155.120.50464 > 169.254.255.255.netbios-ns: NBT UDP PACKET(137): QUERY; REQUEST; BROADCAST
07:47:48.661764 IP6 shemp.local.50466 > ff02::fb.mdns: 11015+[|domain]
07:47:48.813836 IP 169.254.155.120.50464 > 169.254.255.255.netbios-ns: NBT UDP PACKET(137): QUERY; REQUEST; BROADCAST
07:47:48.912041 IP 169.254.155.120.50465 > 224.0.0.251.mdns: 11015+ PTR? 255.255.254.169.in-addr.arpa. (46)
07:47:49.162570 IP6 shemp.local.50466 > ff02::fb.mdns: 11015+[|domain]
07:47:49.227082 IP 169.254.155.120.50467 > 239.255.255.253.svrloc: UDP, length 36
07:47:49.229669 IP 169.254.155.120.50468 > 239.255.255.253.svrloc: UDP, length 36
07:47:49.229866 IP 169.254.155.120.50469 > 239.255.255.253.svrloc: UDP, length 36
07:47:49.229960 IP 169.254.155.120.50470 > 239.255.255.253.svrloc: UDP, length 36
07:47:49.274397 IP 169.254.155.120.50471 > 169.254.255.255.netbios-ns: NBT UDP PACKET(137): QUERY; REQUEST; BROADCAST
07:47:49.412901 IP 169.254.155.120.50465 > 224.0.0.251.mdns: 11015+ PTR? 255.255.254.169.in-addr.arpa. (46)
07:47:49.545217 IP 169.254.155.120.50471 > 169.254.255.255.netbios-ns: NBT UDP PACKET(137): QUERY; REQUEST; BROADCAST
07:47:49.663458 IP6 shemp.local.50466 > ff02::fb.mdns: 11015+[|domain]
07:47:49.815955 IP 169.254.155.120.50471 > 169.254.255.255.netbios-ns: NBT UDP PACKET(137): QUERY; REQUEST; BROADCAST
07:47:49.913818 IP 169.254.155.120.50465 > 224.0.0.251.mdns: 11015+ PTR? 255.255.254.169.in-addr.arpa. (46)
07:47:50.140790 IP 169.254.155.120.50472 > 169.254.255.255.netbios-ns: NBT UDP PACKET(137): QUERY; REQUEST; BROADCAST
07:47:50.164378 IP6 shemp.local.50466 > ff02::fb.mdns: 11015+[|domain]
07:47:50.222774 IP 169.254.155.120.50473 > 239.255.255.253.svrloc: UDP, length 68
07:47:50.411764 IP 169.254.155.120.50472 > 169.254.255.255.netbios-ns: NBT UDP PACKET(137): QUERY; REQUEST; BROADCAST
07:47:50.682525 IP 169.254.155.120.50472 > 169.254.255.255.netbios-ns: NBT UDP PACKET(137): QUERY; REQUEST; BROADCAST
07:47:51.260186 IP6 shemp.local > ff02::fb: HBH ICMP6, multicast listener reportmax resp delay: 0 addr: ff02::fb, length 24
07:47:51.317247 IP 169.254.155.120.mdns > 224.0.0.251.mdns: 0 [9q] PTR? afpovertcp.tcp.local. PTR? nfs.tcp.local.[|domain]
07:47:51.317316 IP6 shemp.local.mdns > ff02::fb.mdns: 0 [9q][|domain]
07:47:52.217151 IP 169.254.155.120.mdns > 224.0.0.251.mdns: 0*- [0q] 9/0/0[|domain]
07:47:52.217272 IP6 shemp.local.mdns > ff02::fb.mdns: 0*- [0q] 9/0/0[|domain]
07:47:52.223003 IP 169.254.155.120.50459 > 239.255.255.253.svrloc: UDP, length 36
07:47:52.223022 IP 169.254.155.120.50460 > 239.255.255.253.svrloc: UDP, length 36
07:47:52.223547 IP 169.254.155.120.50461 > 239.255.255.253.svrloc: UDP, length 36
07:47:52.223780 IP 169.254.155.120.50462 > 239.255.255.253.svrloc: UDP, length 36

MBP 1.83 Mac OS X (10.4.5)

Reply

Answer 12

Mar 8, 2006 10:25 AM in response to BlackNTan

Does anyone know if the airport extreme supports both versions of PEAP?
• PEAP Version 0 (Microsoft PEAP)
• PEAP Version 1 (Cisco PEAP)

Reply

Answer 13

zmq503o1

Level 1

0 points

Mar 8, 2006 10:36 AM in response to Pete H

Running Microsoft IAS Server 2003 SP1 with Cisco AireSpace AP's if that helps. No Windows Machines or older MacOSX machines are having troubles but I can not get any of these MacBook's on the wireless.

Reply

Answer 14

BlackNTan Author

Level 1

5 points

Mar 11, 2006 8:07 AM in response to BlackNTan

Yay! Someone from Apple shot me an email asking me if I was interested in helping the AirPort engineers out by running some debug apps and some terminal commands for them! They are aware of this thread and are interested in getting to the bottom of it!

Reply

Answer 15

Halcon

Level 1

5 points

Mar 12, 2006 7:07 AM in response to BlackNTan

Hi, I'm new to the laptop world so I'm preety green when it comes to wireless networking. I tried to connect to the network here at campus and I get the exactly same results as you guys. (connected but 169.* ip)

My windows loving brethren have their laptop's set up to use PEAP with (MS-CHAP-V2) authentication protocol.
On my machine it says it is connected with PEAP (GTC). The widows machine won't connect if they are set to GTC, and I haven't found a way to select (MS-CHAP-V2) on the mac.

My question is,
Am I having the same problem as you guys or am I missing some trick to force MS-CHAP-V2 ?

regards,

Reply