From: Jouni Malinen (jkmaline_at_cc.hut.fi)
Date: 2002-06-17 16:59:50 UTC
On Fri, Jun 14, 2002 at 07:42:01PM -0400, Pavel Roskin wrote:
> In the first case, we have a similar card (ZoomAir, 0.8.3) on the AP side.
> The association takes sime time. I bring the interface on the station
> side down and up before it accosiates. Slow association is a separate
This is somewhat odd.. I do not remember seeing such behavior. Raw dump in Ethereal-readable format of the really sent 802.11 frames would be useful in determining what might the reason for this. If we ignore the slow association, are there other problems with this configuration?
> In the second case, the card on the AP side is also ZoomAir, but with the
> 1.3.5 firmware. Whatever I do on either side, there is no association.
> You can see failed attempts to set frequency and low rate (there are no
> such errors with 0.8.3). I also tried to cards on both sides - they still
> don't associate.
> wlan0: NIC: id=0x8003 v1.0.0
> wlan0: PRI: id=0x15 v0.3.0
> wlan0: STA: id=0x1f v1.3.5
This is something that I have never seen before.. STA f/w v1.3.x is usually used with primary v1.0.x. Is this an upgraded firmware are those cards delivered with such configuration? I don't remember what requirements STA f/w v1.3.5 has for primary firmware, but the errors look so odd that it might be worthwhile to check this out.
You could comment TX Rate Control setting from prism2_setup_rids() and test what happens. However, the log you sent indicated problems also with FC03 (cnfOwnChannel)..
-- Jouni Malinen PGP id EFC895FA