On Tue, Jan 24, 2017 at 03:10:34PM -0500, mabi wrote: > Hi Stefan > Thanks for your input. It looks like the g2k16 modifications to the athn code > from awolk@ did not make it into the 6.0 release. So there is still hope for > 6.1 ;-)
There was a rabbit hole this diff by Adam fell into. I don't know what the current status of this is. Adam might know more. > I suppose here that running a wifi host access point from a USB key is not a > good idea. What a shame my firewall does not have any PCI or miniPCI > interfaces... Well, in general this can be made to work. But our driver has bugs with it. For example, when I last tested this, an athn(4) USB AP was not actually sending any beacons. It only answered to probe requests sent by clients. Which makes it work like it had a "hidden" SSID, but it does not work like a normal AP. Do you see beacons from your AP when you run something like this on an associated client? 'tcpdump -n -y IEEE802_11_RADIO -i iwn0' If that command does not show beacons, the athn driver is still broken.
