Our wireless adapter comes up, is configurable via iwconfig, can contact the access point (gets its MAC). But I can't ping (either direction) and can't even ARP. tcpdump -n shows nothing for incoming traffic, and only the unanswered ARP packets for outgoing.

More info:
Intel PXA255 (ARM XScale)
Linux 2.4.20
HP 11 Mbps wireless LAN PC Card
PC Card slot has a compact flash and the wireless card
drivers: orinoco.c 0.11 and orinoco_cs.c 0.11

Here's iwconfig output (essid and key are edited):

$ iwconfig eth1
eth1 IEEE 802.11-DS ESSID:"initech" Nickname:"HERMES I"
Mode:Managed Frequency:2.457GHz Access Point: 00:12:17:74:8A:E3
Bit Rate:11Mb/s Tx-Power=15 dBm Sensitivity:1/3
Retry limit:4 RTS thrff Fragment thrff
Encryption key:AA01-0203-0405-0607-0809-0A0B-A0
Power Managementff
Link Quality:50/92 Signal level:-44 dBm Noise level:-94 dBm
Rx invalid nwid:0 Rx invalid crypt:23935 Rx invalid frag:769
Tx excessive retries:0 Invalid misc:0 Missed beacon:0

"Rx Invalid crypt" number seems very high. Orinoco driver is using WEP as far as I know. Are there other diagnostics available?

The route is simple (192.168.1.0/24) and I'm just trying to ping a host on that same segment. But not even arps are getting through.

More stuff from /proc that might be of use:

$ cat /proc/bus/pccard/drivers
orinoco_cs 1 1
wavelan_cs 1 0
ide-cs 1 1

$ cat /proc/bus/pccard/00/status
k_flags : detect ready vs_3v
status : SS_DETECT SS_READY SS_POWERON SS_IOCARD SS_3VCARD
mask : SS_DETECT
cs_flags : SS_IOCARD SS_OUTPUT_ENA
Vcc : 33
Vpp : 0
irq : 42
I/O : 165 (180)
attribute: 300 (301)
common : 250 (271)

$ cat /proc/bus/pccard/01/status
k_flags : detect ready
status : SS_DETECT SS_READY SS_POWERON SS_IOCARD
mask : SS_DETECT
cs_flags : SS_IOCARD SS_OUTPUT_ENA
Vcc : 50
Vpp : 0
irq : 45
I/O : 165 (180)
attribute: 300 (301)
common : 300 (301)

Thanks!

I'd say that your encryption is configured wrong. You need to go though the card settings and access point settings side by side and ensure thay are the same.

Pay attention to things like WEP64 or 128, Open or shared keys etc. Make sure they are the same. The format of the WEP key. Did you cut and paste it complete with hyphens? Does iwconfig treat these as digit separators like the AP or as charachters in the KEY. That sort of stuff.

Sounds like you are almost there and its just going to be a tiny typo or something like I've mentioned above.

It's solved now.

It was an older card that only supports WEP64. iwconfig and driver operation implied WEP128 support; but when we backed down to 64 (40-bit key) and connected to another AP configured that way, we were now passing traffic.

The format of the WEP key. Did you cut and paste it complete with hyphens? Does iwconfig treat these as digit separators like the AP or as characters in the KEY.

I entered the key without hyphens, e.g. "iwconfig eth1 key 01234ABCDE". Hyphens are infixed by iwconfig for display only. (iwconfig will not accept any non-hex characters in the key argument.)

Thanks!

Scott

thats cool