kismet and atheros

[Dan Olson]

Dan Olson wrote:
> 
> 
> Brad Schonhorst wrote:
> 
>> I have been using an iBook since OS X came about but recently decided it
>> was time to give BSD a try.  I picked up a new TINY Fujitsu P7010 and now
>> have it running FreeBSD 6 - current circa July
>>
>> Wireless support was obviously a must for the laptop ( hence running
>> CURRENT to get support for my Atheros card. )  As someone new to BSD
>> wireless I was wondering if you guys could share with me some of your
>> favorite tools for wireless use.  I have been somewhat frustrated with 
>> the
>> steps I currently take to discover new wireless access points.
>>
>> To get wireless access:
>>
>> 1) Run Kismet, find some SSIDs that are open
>> 2) Reboot!  I can't seem to get my card out of Promisc mode otherwise
>> 3) run ifconfig ath0 ssid = ENTERNAME (other commands as needed)
>> 4) run dhclient
>>
>> Are there any other options, I'd like to avoid rebooting after running
>> Kismet.  I feel like I must be missing something.  ifconfig destroy won't
>> work for some reason, I'm guessing its because the entry comes from 
>> Kismet
>> rather than the ifconfig create command.  Any other tools to see what
>> access points are floating around out there?
>>
>> I understand the bsd airtools contains dstumbler but it won't work with
>> the Atheros chipset.  Curious though, do you need to reboot after using
>> dstumbler?
>>
>> I've configured the kernel with ath_rate_onoe, using ATHEROS 5212 
>> Super AG
>> card.
>>
>> -brad
> 
> 
> I had this problem with Kismet. An upgrade solved it. I now run 6 Beta2 
> from Aug 17.
> 
> Dan
> 

I guess I spoke to soon. I am experiencing this problem too and it is 
interfering with my wireless setup. I have a non-standard kernel config 
and load if_ath as a module.

Once loaded 'ifconfig ath0' shows:
ath0: flags=8802<BROADCAST,SIMPLEX,MULTICAST> mtu 1500
         ether 00:05:4e:46:c8:3c
         media: IEEE 802.11 Wireless Ethernet autoselect
         status: no carrier
         ssid ""
         authmode OPEN privacy OFF txpowmax 100

Which looks normal.  After kismet is run and exited, 'ifconfig ath0' shows:
ath0: 
flags=28943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST,PPROMISC> mtu 
1500
         inet6 fe80::205:4eff:fe46:c83c%ath0 prefixlen 64 scopeid 0x2
         ether 00:05:4e:46:c8:3c
         media: IEEE 802.11 Wireless Ethernet autoselect <monitor>
         status: associated
         ssid "" channel 52
         authmode OPEN privacy OFF txpowmax 34

Please note PROMISC, PPRROMISC, and the monitor. If I run 'ifconfig ath0 
-promisc', 'ifconfig ath0' shows:
ath0: flags=8943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST> mtu 1500
         inet6 fe80::205:4eff:fe46:c83c%ath0 prefixlen 64 scopeid 0x2
         ether 00:05:4e:46:c8:3c
         media: IEEE 802.11 Wireless Ethernet autoselect <monitor>
         status: associated
         ssid "" channel 52
         authmode OPEN privacy OFF txpowmax 34

Note PPROMISC is gone but PROMISC is still in the flags. If I do 
'ifconfig ath0 mediaopt -monitor', I get:
ifconfig: SIOCSIFMEDIA (media): Device not configured
If I do 'ifconfig ath0 -monitor' and then 'ifconfig ath0' I get:
ath0: flags=8943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST> mtu 1500
         inet6 fe80::205:4eff:fe46:c83c%ath0 prefixlen 64 scopeid 0x2
         ether 00:05:4e:46:c8:3c
         media: IEEE 802.11 Wireless Ethernet autoselect <monitor>
         status: associated
         ssid "" channel 6
         authmode OPEN privacy OFF txpowmax 34 protmode CTS

But I can reset ath0 by unloading and reloading the kernel module if_ath 
and then I can run my wireless setup script and connect. But if i don't 
reload the module I can't connect.  I think the PROMISC flag and the 
<monitor> are interfering.

How can we remove them?

Dan