Re: [Madwifi-users] AR5212/madwifi-ng - can't associate to an AP

[David S. <dj...@bt...>]

On Sun, 2006-06-11 at 17:57 -0400, David R. Litwin wrote:

> On 11/06/06, David Seery <dj...@bt...> wrote:

> The interfaces wifi0 and ath0 are created, and I can scan for access
> points using iwlist or NetworkManager. In most cases, however, I can't
> associate to any access point.
> 
> This is trully going to sound stupid: Are you sure you have put in the correct WEP key? I know that I have made this mistake in the past: 
> My wireless refused to associate. I change the key and it worked.

Thanks very much for the suggestions.

As I explained, I've tried to rule out WEP issues by checking the
settings using Windows, and Linux with two different Prism-based devices
(in fact, I've tested this in combinations on four different computers
and with three different access points). I've also checked with a
non-WEP access point. The single access point I have had success with is
a WEP-enabled Airport Extreme. I do not think it is a WEP issue.

Since you think it will help, I use the following sequence to bring up
the interface:
	iwconfig ath0 essid salisbury
	iwconfig ath0 key s:<13-char ASCII string>
	iwconfig ath0 key open
	ifconfig ath0 up
This makes a correct association with the kernel orinoco/hermes drivers,
but madwifi-ng fails.

I'm particularly interested to try and understand the meaning of the
symbols * and ! which follow the received packets while the association
attempt is occuring. I reproduced these from my syslog in my previous
message, and they generally have the form:

16:59:06 ath_intr: status 0x4009
16:59:06 ath_rx_tasklet
16:59:06 R (f69d0030 369d0030) 369d0060 2d65f020 00000000 00000c60
1ffd0000 32811915 !
16:59:06 ath_intr: status 0x9
16:59:06 ath_rx_tasklet
16:59:06 R (f69d0060 369d0060) 369d0090 368dd020 00000000 00000c60
144d0042 3f4e0003 *

Can anyone explain the meaning of these?

Thanks very much

David