clients don't associate to 0.1.0 --> AP: drop packet to non-associated STA

[Jirka Bohac]

> > I've seen strange problems with client's not associating correctly to
> > the AP:
> 
> Could you and others reporting similar problems with Host AP driver
> v0.1.0 give some more details about the AP and STAs that failed to
> associate? I would like to know the NICID and firmware versions of each
> device, the driver version from the STAs and some information about what
> kind of wireless LAN configuration (plaintext / WEP / something special)
> was used. What is the distance between the AP and the STAs?

ok, right now I have access to two clients failing to associate. One
associates to my wlan0 and its MAC is 00:60:B3:6B:D0:C6:

Oct 17 15:40:59 sj-shark kernel: hostap_pci: 0.0.4 - 2003-07-27 (Jouni
Malinen <jkmaline at cc.hut.fi>)
Oct 17 15:40:59 sj-shark kernel: hostap_pci: Registered netdevice wlan0
Oct 17 15:40:59 sj-shark kernel: prism2_hw_init()
Oct 17 15:40:59 sj-shark kernel: prism2_hw_init: initialized in 200 ms
Oct 17 15:40:59 sj-shark kernel: wlan0: NIC: id=0x8013 v1.0.0
Oct 17 15:40:59 sj-shark kernel: wlan0: PRI: id=0x15 v1.0.7
Oct 17 15:40:59 sj-shark kernel: wlan0: STA: id=0x1f v1.3.6

The other one is a Cisco Aironet:
Sep 29 05:27:10 kulik kernel: airo:  Probing for PCI adapters
Sep 29 05:27:10 kulik kernel: airo: Doing fast bap_reads
Sep 29 05:27:10 kulik kernel: airo: MAC enabled eth1 0:b:be:4c:ee:33
Sep 29 05:27:10 kulik kernel: airo:  Finished probing for PCI adapters


my wlan0 only has a few denied MACs, unlike wlan2 which has closed MAC
policy and has only enabled a couple of MACs

We don't use WEP, nor hostapd, radius, or anything else like that ...


> I tried to reproduce association issues with Prism2.5 and Prism3 cards
> using STA f/w 1.7.4 (card NICIDs were 8013 and 801b; both with PRI f/w

I use 1.5.6, as you can see in the attached syslog

 
> The only IEEE 802.11 auth/assoc related change in the CVS between
> September 24 and v0.1.0 release was in making STAs authenticated before
> they ACKed authentication frame from the AP. I would not expect this to
> break association, but just to be sure, I've attached a patch to revert
> this change. Please try whether it changes the behavior of the v0.1.0
> release.

....

> Could you please send me full 'dmesg' output from the AP?

In the attachment, you can find 2 files. One is a portion of my syslog.
It starts with a system boot, with 0.1.0 modules (with your auth.
reverse patch). I left it running for a while, and just before
rebooting, I did "arp -n > arp", so you can see that MAC addresses of
unassociated clients get shown.

Then you can see a reboot with hostap-2003-09-27 (it has my txpower
patch applied, so you may find strange things in the syslog - the 0.1.0
I tested, however, is a vanilla 0.1.0 patched with your reverse patch)



> Were the clients sending anything? That should also trigger new
> authentication if AP does not think the STA is associated. You could
> also try running 'iwpriv wlan0 reset 2' in the client if it was using
> Host AP driver. This will make the card re-try association.

They sure were. When the link is down, I have no access to them so I
can't try resetting the cards


Thanks a lot for looking into this problem!


Jirka Bohac
CZFree.Net
-------------- next part --------------
A non-text attachment was scrubbed...
Name: syslog_and_arp.tbz
Type: application/octet-stream
Size: 5924 bytes
Desc: not available
Url : http://lists.shmoo.com/pipermail/hostap/attachments/20031018/ab89a8d2/attachment.obj