|
From: Michael B. <mb...@fe...> - 2002-10-15 23:51:20
|
On Wed, 16 Oct 2002, Ken Yap wrote: > >OK, this issue is now resolved. A working version for 5.0 is in CVS. The > >fix has been ported to 5.1 and checked in but not yet tested (it's simple > >enough that I don't expect any problems). > Thanks Michael, good work. Will check out the source shortly. There's one more fix in as well now. I've just got a new access point (a Linksys WAP11) and discovered that the Prism2 driver had problems doing repeated autojoins. The first join would succeed, subsequent attempts would fail until the *access point* was reset. Resetting (or even powering down) the workstation containing the Prism2 card had no effect. Eventually traced this down to a behavioural quirk of the Linksys WAP11: when a card attempts to join to it, if the AP thinks the card is already joined then it will send a "you are disconnected" notification and wait a few seconds before sending the "you are now connected" notification. The Prism2 driver was receiving the "you are disconnected" notification and assuming it represented a failure to join (the message that appears is "Link not connected (status 0x0006)". The Prism2 driver (in both 5.0 and 5.1) will now listen for up to MAX_JOIN_INFO_COUNT INFO packets before finally giving up. I've set MAX_JOIN_INFO_COUNT to 2, which solves the problem for the Linksys WAP11. I'm puzzled by the fact that no-one else seems to have reported this problem. Is this really a quirk of just this one model of access point? I'm going to contact Linksys tomorrow, so it would be helpful to know if anyone else has experienced similar "Link not connected (status 0x0006)" problems and, if so, with which makes of access point. Michael Brown http://www.fensystems.co.uk |
