> > To summarize: For best hostap experience use a supported athn(4) > > device on PCI. That's what I use at home and it just works. > > Avoid USB for hostap if at all possible. > > Thank you very much for the answer. > > There is the usual problem that many of the devices listed are not > available anymore, or there are numerous versions with the same device > name where the manufacturer altered the chipset. I sometimes wish that > store pages would be as clear as OpenBSD man pages.
That's a serious problem for hardware buyers especially first time or off bidding sites, beware sometimes they sell crap that does not pass factory quality control. Posting success stories with correct technical details on personal pages related to OpenBSD for the search engine to find is a step forward, but best is a follow up on the mail lists so archives have these details for others (the usual place to search for tech insight). > So, Stuart's comment is still valid. I will stop looking for a USB > solution, and instead see if I can find a low power chassis with a PCI > slot. While more expensive, it is probably money well invested. Yes, indeed. Just a small suggestion, there are PCI(e) to mini-PCI converters which can hold a laptop form factor wireless card in a regular PCI(e) slot, not sure if these are electrical only or have a chip on them that might not be supported, but an option worth checking. Another idea may be to temporarily reuse an old access point and connect that to an existing OpenBSD system over Ethernet, to give you wireless coverage, but in my opinion the wireless card as hostap is always the better solution. One can even use a spare (old) portable (netbook) laptop with an included athn(4) in hostap mode as a device to provide wireless access to others. Please post back info when you sort it out, experience, comments, and possibly links to helpful past threads in the mail archives.
