Date: Sat, 27 Aug 2005 21:09:28 +0000 From: Brad Schonhorst <bschonhorst@vcsnyc.org> To: freebsd-mobile@freebsd.org Subject: Re: kismet adn atheros Message-ID: <4310D688.40408@vcsnyc.org>
next in thread | raw e-mail | index | archive | help
>
> I just upgrade to the latest - 6 Beta 3 #1 and I'm still having trouble.
> If I start kismet, I still cannot get the ath0 interface out of promisc
> mode afterwards.
>
>I'm sorry, but that isn't really a useful problem report. What
commands are
>you trying, and what are the results?
Sorry. Here goes:
#uname -a
FreeBSD ender.plumblossom.org 6.0-BETA3 FreeBSD 6.0-BETA3 #1: Wed Aug 24
19:49:59 UTC 2005 root@ender.xxxxxxxx.org:/usr/obj/usr/src/sys/ENDER i386
#ifconfig ath0 up
#kismet
I see some access points, let kismet run for a minute and then quit out
of it
#ps -aux | egrep kismet
root 663 0.0 0.2 2860 2108 p1 S 8:39PM 0:01.41
/usr/local/bin/kismet_server --silent
Kismet_server hung on for some reason, lets kill it off
#kill -9 663
Lets see if that did the trick
#ifconfig
ath0:flags=28943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST,PPROMISC>
mtu 1500
inet6 fe80::211:f5ff:fe60:1764%ath0 prefixlen 64 scopeid 0x3
ether 00:11:f5:60:17:64
media: IEEE 802.11 Wireless Ethernet autoselect <monitor>
status: associated
ssid "" channel 11
authmode OPEN privacy OFF txpowmax 52 protmode CTS bintval 100
Not really, so lets try one of the suggested commands to pull out of
promisc and monitor modes
#ifconfig ath0 -promisc mediaopt -monitor
ifconfig: SIOCSIFMEDIA (media): Device not configured
Hmm, may not have need the mediaopt flag
#ifconfig ath0 -promisc -monitor
Did that do it?
#ifconfig
ath0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
inet6 fe80::211:f5ff:fe60:1764%ath0 prefixlen 64 scopeid 0x3
ether 00:11:f5:60:17:64
media: IEEE 802.11 Wireless Ethernet autoselect <monitor>
status: associated
ssid "" channel 11
authmode OPEN privacy OFF txpowmax 52 protmode CTS bintval 100
still in monitor mode, this should mean i can't connect to my access
point right?
#ifconfig ath0 ssid Ansible channel 10
#ifconfig
ath0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
inet6 fe80::211:f5ff:fe60:1764%ath0 prefixlen 64 scopeid 0x3
inet 0.0.0.0 netmask 0xff000000 broadcast 255.255.255.255
ether 00:11:f5:60:17:64
media: IEEE 802.11 Wireless Ethernet autoselect <monitor>
status: associated
ssid "" channel 10
So the channel changed but it didn't accept the new ssid
Maybe i can just clear out the interface
#ifconfig ath0 destroy
ifconfig: SIOCIFDESTROY: Invalid argument
nope, what if I bring it down?
#ifconfig ath0 down
#ifconfig
ath0: flags=8802<BROADCAST,SIMPLEX,MULTICAST> mtu 1500
inet6 fe80::211:f5ff:fe60:1764%ath0 prefixlen 64 scopeid 0x3
inet 0.0.0.0 netmask 0xff000000 broadcast 255.255.255.255
ether 00:11:f5:60:17:64
media: IEEE 802.11 Wireless Ethernet autoselect <monitor>
status: no carrier
ssid Ansible channel 10
authmode OPEN privacy OFF txpowmax 51 protmode CTS bintval 100
Strange, the ssid shows up now but I can't grab an IP address. Any
suggestions (other than simply not using kismet?)
Thanks all!
Brad
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4310D688.40408>