Yes, I found and fixed the bug that you have all been complaining about. If you have all of the following...

• An ORiNOCO card
• NetStumbler version 0.3.30
• "Auto Reconfigure" switched on

... then the following sequence of events is likely to occur:

1. You eventually associate with an access point while you're scanning.
2. You go out of range, or in better range of a different AP.
3. "Auto reconfigure" kicks in to disassociate you (otherwise "get AP names" won't work)
4. In reconfiguring the card, it inadvertently puts it into a state where it will not discover any access points at all.

This has been fixed in version 0.4 (coming soon!)

There is now a Netstumbler mailing list. This list is intended for news and general discussion of NetStumbler, but not for FAQs or general wireless discussion.

To join, send mail to [email protected] with subscribe netstumbler yourfirstname in the body of the message. Many thanks to the folks at www.michiganwireless.org for hosting the list.

The list is archived at http://www.mail-archive.com/netstumbler%40mail.c2security.org/.