Aironet 1231 with Apple Macbook and iPhone 3G - no ip address

Unanswered Question

I'm having trouble with Apple products connecting to a Aironet 1231 using WEP. Apple products seem to complete the association process:

*May 26 17:01:23.647: %DOT11-6-ASSOC: Interface Dot11Radio0, Station 001e.5271.1890 Associated KEY_MGMT[NONE]

But never get an IP address from DHCP:

ap1#sh dot11 associations

802.11 Client Stations on Dot11Radio0:

SSID [dnet] :

MAC Address IP address Device Name Parent State

000e.357b.1cb3 unknown - self Assoc

000e.9bba.3001 unknown - self Assoc

000e.9bbf.aeda unknown - self Assoc

001e.5271.1890 unknown - self Assoc

Windows XP machines have no trouble associating and getting IP addresses.

IOS image is c1200-k9w7-mx.123-2.JA2:

IOS (tm) C1200 Software (C1200-K9W7-M), Version 12.3(2)JA2, RELEASE SOFTWARE (fc1)

tcpdump on the macbook reveals that DHCP discover packets are going out the wireless interface, but DHCP offers are never received from the Aironet:

IP > BOOTP/DHCP, Request from 00:1e:52:71:18:90, length 300

IP > BOOTP/DHCP, Request from 00:1e:52:71:18:90, length 300

00:12:7f:1c:cd:a8 Unknown SSAP 0x72 > 00:1e:52:71:18:90 Unknown DSAP 0xb0 Supervisory, ?, rcv seq 22, Flags [Response], length 58

00:0e:84:83:f4:96 NetBeui > 01:80:c2:00:00:00 Unknown DSAP 0x4c Information, send seq 74, rcv seq 17, Flags [Response], length 38

IP > BOOTP/DHCP, Request from 00:1e:52:71:18:90, length 300

arp who-has tell

arp who-has tell

arp who-has tell

00:0e:84:83:f4:96 Unknown SSAP 0x2c > 01:80:c2:00:00:00 Unknown DSAP 0xec Supervisory, ?, rcv seq 115, Flags [Poll], length 38

00:1b:63:b1:aa:a3 Unknown SSAP 0xf4 > ff:ff:ff:ff:ff:ff STP Information, send seq 73, rcv seq 2, Flags [Response], length 86

Anyone aware of issues with Apple products and Cisco Aironet 1231?

I have this problem too.
0 votes
  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)
jeff.kish Tue, 03/31/2009 - 07:57

WEP is a bit different in how it handles authentication. Clients connect to an AP even if they have the wrong WEP key, and they'll show up in the clients table. But the AP will block clients from the LAN without the proper WEP key.

In other words, clients that are unable to get DHCP via WEP generally have the wrong key configured. Check the key one more time, maybe it was put in wrong.


This Discussion



Trending Topics: Other Wireless Mobility

client could not be authenticated
Network Analysis Module (NAM) Products
Cisco 6500 nam
reason 440 driver failure
Cisco password cracker
Cisco Wireless mode