Arch Linux

^-Ubermensch-^

Member

Registered: 2008-07-08

Posts: 58

Kismet why not start?

Kismet why not start?

[ubermensch@tux-devil ~]$ sudo kismet -n
Password: 
Launching kismet_server: /usr/bin/kismet_server
Not logging any data
Will drop privs to ubermensch (1000) gid 100
No specific sources given to be enabled, all will be enabled.
Non-RFMon VAPs will be destroyed on multi-vap interfaces (ie, madwifi-ng)
Enabling channel hopping.
Enabling channel splitting.
NOTICE: Disabling channel hopping, no enabled sources are able to change channel.
Source 0 (Railink): Enabling monitor mode for rt73 source interface rausb0 channel 6...
Source 0 (Railink): Opening rt73 source interface rausb0...
FATAL: Can't get USB bus index from rausb0
Done.
[ubermensch@tux-devil ~]$

:cool:

.:B:.

Forum Fellow

Registered: 2006-11-26

Posts: 5,819

Website

Re: Kismet why not start?

Did it work before? If not - did you try su'ing first? I know e.g. pacman doesn't like you sudo'ing with some of its stuff (can't remember what exactly but I think install scripts give errors with it during upgrade/installation).

---

Got Leenucks? :: Arch: Power in simplicity :: Get Counted! Registered Linux User #392717 :: Blog thingy

ammon

Member

Registered: 2008-12-11

Posts: 413

Re: Kismet why not start?

your Railink does not support monitor mode. Google it to find driver that can do that, like madwifi

^-Ubermensch-^

Member

Registered: 2008-07-08

Posts: 58

Re: Kismet why not start?

No before worked!!     I have taken my driver on AUR.

[ubermensch@tux-devil ~]$ kismet -n
Launching kismet_server: /usr/bin/kismet_server
Not logging any data
Will drop privs to ubermensch (1000) gid 100
Done.
[ubermensch@tux-devil ~]$

:rolleyes: