LEAP network connection failure

Question

Level 1

15 points

LEAP network connection failure

Anyone able to connect to a LEAP network? When I try to connect, I get a dialog box that says "There was an error joining the AirPort network <Name>".

My MacBook Pro had no problem connecting to my WPA2 network at home. The network appears to be fine, as a coworker was able to connect with his Powerbook.

MacBook Pro 2.0 GHz, Mac OS X (10.4.5)

Posted on Feb 22, 2006 7:14 AM

Reply

Answer 1

Pete H

Level 3

570 points

Feb 22, 2006 1:12 PM in response to Paul Bielski

Try going through Internet Connect and creating an 802.1x connection with the network port set to AirPort.

Reply

Answer 2

Paul Bielski Author

Level 1

15 points

Feb 22, 2006 2:05 PM in response to Pete H

Thanks for the reply!

I tried that after I posted the original message. This does allow me to connect to the LEAP wireless network, but the machine never gets an IP address or any DNS servers assigned. I tried manually setting the IP, gateway and DNS to value appropriate for our network but I still can't get to any network services.

Any other ideas?

Reply

Answer 3

Pete H

Level 3

570 points

Feb 22, 2006 2:17 PM in response to Paul Bielski

Well that is odd. If Internet Connect is able to connect to the network, it means that the LEAP handshake completed and you should be authenticated. Do you see the connection timer start counting after click connect?

Reply

Answer 4

Paul Bielski Author

Level 1

15 points

Feb 22, 2006 2:50 PM in response to Pete H

Yes, the connection timer starts but I have a self-assigned IP. The behavior does get a little stranger - the signal strength will occasionally suddenly drop (4 "bars" to 1), and the laptop will re-authenticate. It will succeed most of the time, but occasionally not.

Tomorrow I plan to try connecting to another wireless router in a different part of the building to see if I end up with a different result. I'm starting to suspect that my local router is the problem; it turned out that the coworker who said he could connect was actually in another part of the building at the time.

Reply

Answer 5

Paul Bielski Author

Level 1

15 points

Feb 23, 2006 6:07 AM in response to Paul Bielski

I tested with a different router this morning and could not connect, but was able to access it with a Powerbook. It appears that there is a software bug of some sort that prevents the DHCP information from being transferred to the MBP.

Reply

Answer 6

Feb 23, 2006 10:47 AM in response to Paul Bielski

I'm in the same boat. My old 15" PB would talk to our Cisco wireless w/ LEAP no problem. I get the same error as the original post when I try with the MacBook.

Reply

Answer 7

Feb 23, 2006 4:34 PM in response to NetJunkie

Exactly the same problem. My powerbook works. My MacBook Pro doesn't.
Spent time with our IT department and Apple product specialists today. They're sending the details to the engineering folks.

I'm pretty sure there is a SW problem with the Airport driver in the intel version.

They're going to call me when they have a response from engineering.

I'm expecting a patch. I just hope it is soon.....

MacBook Pro, Power Mac Quad, Powerbook 17", Mac mini, 12 Powermac Mac OS X (10.4.5) Yes I'm an apple junky

Reply

Answer 8

Feb 23, 2006 5:50 PM in response to Paul Bielski

Not sure if this is related, but I have a similar problem connecting via PEAP to my companies wireless network. The same exact setting on my buddies old powerbook connect just fine, but the macbook pro does not seem to connect and get an IP via dhcp.

I hooked up a packet sniffer to see what was happeneing and I see more then a couple "malformed packets", this also does not happen on buddies g4 powerbok w/ the same configuration.

Here is a dump from the sniffer:
No. Time Source Destination Protocol Info
9 5.825325 Cisco_00:31:f0 00:14:51:ed:43:79 EAP Request, Identity [RFC3748]

Frame 9 (68 bytes on wire, 68 bytes captured)
Ethernet II, Src: 00:13:60:00:31:f0, Dst: 00:14:51:ed:43:79
802.1x Authentication

No. Time Source Destination Protocol Info
10 5.827077 00:14:51:ed:43:79 Cisco_00:31:f0 EAP Response, Identity [RFC3748]

Frame 10 (48 bytes on wire, 48 bytes captured)
Ethernet II, Src: 00:14:51:ed:43:79, Dst: 00:13:60:00:31:f0
802.1x Authentication

No. Time Source Destination Protocol Info
11 5.833015 Cisco_00:31:f0 00:14:51:ed:43:79 EAP Request, EAP-Cisco Wireless (LEAP) [Norman]

Frame 11 (60 bytes on wire, 60 bytes captured)
Ethernet II, Src: 00:13:60:00:31:f0, Dst: 00:14:51:ed:43:79
802.1x Authentication

No. Time Source Destination Protocol Info
12 5.834553 00:14:51:ed:43:79 Cisco_00:31:f0 EAP Response, Nak (Response only) [RFC3748]

Frame 12 (24 bytes on wire, 24 bytes captured)
Ethernet II, Src: 00:14:51:ed:43:79, Dst: 00:13:60:00:31:f0
802.1x Authentication

No. Time Source Destination Protocol Info
13 5.839589 Cisco_00:31:f0 00:14:51:ed:43:79 EAP Request, PEAP [Palekar]

Frame 13 (60 bytes on wire, 60 bytes captured)
Ethernet II, Src: 00:13:60:00:31:f0, Dst: 00:14:51:ed:43:79
802.1x Authentication

No. Time Source Destination Protocol Info
14 5.849683 00:14:51:ed:43:79 Cisco_00:31:f0 TLS Client Hello

Frame 14 (120 bytes on wire, 120 bytes captured)
Ethernet II, Src: 00:14:51:ed:43:79, Dst: 00:13:60:00:31:f0
802.1x Authentication

No. Time Source Destination Protocol Info
15 5.860320 Cisco_00:31:f0 00:14:51:ed:43:79 TLS Server Hello, Certificate[Malformed Packet]

Frame 15 (1030 bytes on wire, 1030 bytes captured)
Ethernet II, Src: 00:13:60:00:31:f0, Dst: 00:14:51:ed:43:79
802.1x Authentication
[Malformed Packet: SSL]

No. Time Source Destination Protocol Info
16 5.860828 00:14:51:ed:43:79 Cisco_00:31:f0 EAP Response, PEAP [Palekar]

Frame 16 (24 bytes on wire, 24 bytes captured)
Ethernet II, Src: 00:14:51:ed:43:79, Dst: 00:13:60:00:31:f0
802.1x Authentication

No. Time Source Destination Protocol Info
17 5.869295 Cisco_00:31:f0 00:14:51:ed:43:79 TLS Server Hello, Certificate[Malformed Packet]

Frame 17 (1026 bytes on wire, 1026 bytes captured)
Ethernet II, Src: 00:13:60:00:31:f0, Dst: 00:14:51:ed:43:79
802.1x Authentication
[Malformed Packet: SSL]

No. Time Source Destination Protocol Info
18 5.869779 00:14:51:ed:43:79 Cisco_00:31:f0 EAP Response, PEAP [Palekar]

Frame 18 (24 bytes on wire, 24 bytes captured)
Ethernet II, Src: 00:14:51:ed:43:79, Dst: 00:13:60:00:31:f0
802.1x Authentication

No. Time Source Destination Protocol Info
19 5.878652 Cisco_00:31:f0 00:14:51:ed:43:79 TLS Server Hello, Certificate[Malformed Packet]

Frame 19 (707 bytes on wire, 707 bytes captured)
Ethernet II, Src: 00:13:60:00:31:f0, Dst: 00:14:51:ed:43:79
802.1x Authentication
[Malformed Packet: SSL]

No. Time Source Destination Protocol Info
20 5.882101 00:14:51:ed:43:79 Cisco_00:31:f0 TLS Client Key Exchange, Change Cipher Spec, Encrypted Handshake Message

Frame 20 (214 bytes on wire, 214 bytes captured)
Ethernet II, Src: 00:14:51:ed:43:79, Dst: 00:13:60:00:31:f0
802.1x Authentication

No. Time Source Destination Protocol Info
21 5.895575 Cisco_00:31:f0 00:14:51:ed:43:79 TLS Change Cipher Spec, Encrypted Handshake Message

Frame 21 (75 bytes on wire, 75 bytes captured)
Ethernet II, Src: 00:13:60:00:31:f0, Dst: 00:14:51:ed:43:79
802.1x Authentication

No. Time Source Destination Protocol Info
22 5.949310 00:14:51:ed:43:79 Cisco_00:31:f0 EAP Response, PEAP [Palekar]

Frame 22 (24 bytes on wire, 24 bytes captured)
Ethernet II, Src: 00:14:51:ed:43:79, Dst: 00:13:60:00:31:f0
802.1x Authentication

No. Time Source Destination Protocol Info
23 5.955622 Cisco_00:31:f0 00:14:51:ed:43:79 TLS Application Data

Frame 23 (60 bytes on wire, 60 bytes captured)
Ethernet II, Src: 00:13:60:00:31:f0, Dst: 00:14:51:ed:43:79
802.1x Authentication

No. Time Source Destination Protocol Info
24 5.956229 00:14:51:ed:43:79 Cisco_00:31:f0 TLS Application Data

Frame 24 (67 bytes on wire, 67 bytes captured)
Ethernet II, Src: 00:14:51:ed:43:79, Dst: 00:13:60:00:31:f0
802.1x Authentication

No. Time Source Destination Protocol Info
25 5.961656 Cisco_00:31:f0 00:14:51:ed:43:79 TLS Application Data

Frame 25 (60 bytes on wire, 60 bytes captured)
Ethernet II, Src: 00:13:60:00:31:f0, Dst: 00:14:51:ed:43:79
802.1x Authentication

No. Time Source Destination Protocol Info
38 11.393590 00:14:51:ed:43:79 Cisco_00:31:f0 TLS Application Data

Frame 38 (66 bytes on wire, 66 bytes captured)
Ethernet II, Src: 00:14:51:ed:43:79, Dst: 00:13:60:00:31:f0
802.1x Authentication

No. Time Source Destination Protocol Info
39 11.557358 Cisco_00:31:f0 00:14:51:ed:43:79 TLS Application Data

Frame 39 (60 bytes on wire, 60 bytes captured)
Ethernet II, Src: 00:13:60:00:31:f0, Dst: 00:14:51:ed:43:79
802.1x Authentication

No. Time Source Destination Protocol Info
40 11.557919 00:14:51:ed:43:79 Cisco_00:31:f0 EAP Response, PEAP [Palekar]

Frame 40 (24 bytes on wire, 24 bytes captured)
Ethernet II, Src: 00:14:51:ed:43:79, Dst: 00:13:60:00:31:f0
802.1x Authentication

No. Time Source Destination Protocol Info
41 11.578881 Cisco_00:31:f0 00:14:51:ed:43:79 EAP Success

Frame 41 (60 bytes on wire, 60 bytes captured)
Ethernet II, Src: 00:13:60:00:31:f0, Dst: 00:14:51:ed:43:79
802.1x Authentication

No. Time Source Destination Protocol Info
42 11.579218 Cisco_00:31:f0 00:14:51:ed:43:79 EAPOL Key

Frame 42 (75 bytes on wire, 75 bytes captured)
Ethernet II, Src: 00:13:60:00:31:f0, Dst: 00:14:51:ed:43:79
802.1x Authentication

No. Time Source Destination Protocol Info
43 11.579549 Cisco_00:31:f0 00:14:51:ed:43:79 EAPOL Key[Malformed Packet]

Frame 43 (62 bytes on wire, 62 bytes captured)
Ethernet II, Src: 00:13:60:00:31:f0, Dst: 00:14:51:ed:43:79
802.1x Authentication
[Malformed Packet: EAPOL]

Pat

MacBook Pro 2.0 Mac OS X (10.4.5)

Reply

Answer 9

Pete H

Level 3

570 points

Feb 23, 2006 7:17 PM in response to Nicholas Dawes

Can you guys who are having trouble check with your network administrators to see if they are requiring the old style Cisco leap authentication value in the association request (0x0080)? If so, it might worth asking them to turn on open authentication with LEAP, and then check if that allows you to get on through Internet Connect.

Reply

Answer 10

Pete H

Level 3

570 points

Feb 23, 2006 7:25 PM in response to Paul Bielski

Can you run

sudo tcpdump -i en1

in terminal and paste the output from your connection attempt and a few seconds of what follows after you are authenticated?

Reply

Answer 11

Feb 23, 2006 11:02 PM in response to Nicholas Dawes

Exactly the same problem. My powerbook works. My
MacBook Pro doesn't.
Spent time with our IT department and Apple product
specialists today. They're sending the details to the
engineering folks.

I'm pretty sure there is a SW problem with the
Airport driver in the intel version.

They're going to call me when they have a response
from engineering.

I'm expecting a patch. I just hope it is
soon.....

I have exactly the same problem. Two machines (Macbook Pro, iBook G4) both running 10.4.5 and configured identically will respond differently.

The iBook connects fine.

The MacBook Pro "sees" the wireless, authenticates via LEAP (and starts the timer running) but is unable to get an IP address.
Setting an IP address manually doesn't fix the problem, as I get 'no route to host' messages.

Between this problem and the screeching/whining I'm really starting to regret getting rid of my PBG4. But, I'm willing to try working through it. I'd be glad to work with Nicholas or someone at Apple to provide more detailed debugging info.

nroach (at) stmarytx (dot) edu

Reply

Answer 12

Paul Bielski Author

Level 1

15 points

Feb 24, 2006 5:14 AM in response to Pete H

When I ran tcpdump and then tried logging on using the Airport menu item, there was no response at all. Here's the tcpdump output for the case where I connected through Internet Connect using the 802.1x pane:

tcpdump: WARNING: en1: no IPv4 address assigned
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on en1, link-type EN10MB (Ethernet), capture size 96 bytes
07:01:20.311319 EAP code=1 id=0 length=51
07:01:20.380508 IP 0.0.0.0.bootpc > broadcasthost.bootps: BOOTP/DHCP, Request
om 00:14:51:ed:18:f9 (oui Unknown), length: 300
07:01:20.381571 IP6 fe80::214:51ff:feed:18f9 > ff02::1:ffed:18f9: HBH ICMP6, m
ticast listener reportmax resp delay: 0 addr: ff02::1:ffed:18f9, length 24
07:01:20.381654 IP6 fe80::214:51ff:feed:18f9 > ff02::2:855:ebd6: HBH ICMP6, mu
icast listener reportmax resp delay: 0 addr: ff02::2:855:ebd6, length 24
07:01:20.505115 EAP code=1 id=0 length=13
07:01:20.509426 EAP code=1 id=0 length=24
07:01:20.513631 EAP code=1 id=0 length=40
07:01:20.570810 EAP code=1 id=0 length=4
07:01:20.570941 EAP code=1 id=0 length=24
07:01:20.576888 EAP code=1 id=0 length=40
07:01:20.577220 EAP code=1 id=3 length=57
07:01:20.577520 EAP code=1 id=3 length=44
07:01:20.721825 IP6 :: > ff02::1:ffed:18f9: ICMP6, neighbor solicitation, who
s fe80::214:51ff:feed:18f9, length 24
07:01:21.724196 IP6 fe80::214:51ff:feed:18f9 > ff02::2: ICMP6, router solicita
on, length 16
07:01:21.922687 IP6 fe80::214:51ff:feed:18f9.49188 > ff02::fb.mdns: 35902+[|d
ain]
07:01:22.095818 IP 0.0.0.0.bootpc > broadcasthost.bootps: BOOTP/DHCP, Request
om 00:14:51:ed:18:f9 (oui Unknown), length: 300
07:01:22.423427 IP6 fe80::214:51ff:feed:18f9.49188 > ff02::fb.mdns: 35902+[|d
ain]
07:01:23.670806 IP6 fe80::214:51ff:feed:18f9 > ff02::2: ICMP6, router solicita
on, length 16
07:01:23.725942 IP6 fe80::214:51ff:feed:18f9 > ff02::fb: HBH ICMP6, multicast
stener reportmax resp delay: 0 addr: ff02::fb, length 24
07:01:23.727445 IP6 fe80::214:51ff:feed:18f9.mdns > ff02::fb.mdns: 0 PTR (Cac
flush)? http.tcp.local. (34)
07:01:23.976304 IP6 fe80::214:51ff:feed:18f9.mdns > ff02::fb.mdns: 0 [4q] [4n
|domain]
07:01:24.104554 IP 0.0.0.0.bootpc > broadcasthost.bootps: BOOTP/DHCP, Request
om 00:14:51:ed:18:f9 (oui Unknown), length: 300
07:01:24.105257 arp who-has 169.254.101.236 tell 0.0.0.0
07:01:24.227249 IP6 fe80::214:51ff:feed:18f9.mdns > ff02::fb.mdns: 0 [4q] [4n
|domain]
07:01:24.405525 arp who-has 169.254.101.236 tell 0.0.0.0
07:01:24.478211 IP6 fe80::214:51ff:feed:18f9.mdns > ff02::fb.mdns: 0 [4q] [4n
|domain]
07:01:24.705834 arp who-has 169.254.101.236 tell 0.0.0.0
07:01:24.776365 IP6 fe80::214:51ff:feed:18f9.mdns > ff02::fb.mdns: 0 PTR? _ht
._tcp.local. (34)
07:01:24.776725 IP6 fe80::214:51ff:feed:18f9.mdns > ff02::fb.mdns: 0*- [0q] 1
0/0[|domain]
07:01:24.944802 IP6 fe80::214:51ff:feed:18f9.49190 > ff02::fb.mdns: 58087+[|d
ain]
07:01:25.006111 arp who-has 169.254.101.236 tell 0.0.0.0
07:01:25.306438 arp who-has 169.254.101.236 tell 169.254.101.236
07:01:25.445570 IP6 fe80::214:51ff:feed:18f9.49190 > ff02::fb.mdns: 58087+[|d
ain]
07:01:25.607138 arp who-has 169.254.101.236 tell 169.254.101.236
07:01:25.638085 IP 169.254.101.236.49191 > 224.0.0.251.mdns: 45561+ PTR? 236.
1.254.169.in-addr.arpa. (46)
07:01:25.638234 IP 169.254.101.236.49192 > 224.0.0.251.mdns: 61366+ PTR? 236.
1.254.169.in-addr.arpa. (46)

Reply

Answer 13

abrasif

Level 1

0 points

Feb 24, 2006 10:52 AM in response to Paul Bielski

I have the exact same problem. Let us know if you have any update.

Reply

Answer 14

Feb 24, 2006 2:35 PM in response to Paul Bielski

Ok this issue is killing me. I opnened a trouble ticket with apple about PEAP wireless networking not working (and filed a complaint I believe). Lets see what this gets us.

Its pretty clear to me that this works w/ the old G4 powerbooks and does not work w/ the macbook.

Pat

MacBook Pro Mac OS X (10.4.5)

Reply

Answer 15

Feb 27, 2006 9:17 PM in response to Patrick Doran

any updates?

Reply