Linux Commands Examples

A great documentation place for Linux commands


Wireless sniffing and monitoring remote drone

see also : kismet


kismet_drone [-svh] [-f config-file] [-c capture-source]
[-C enable-capture-sources] [-p port] [-a allowed-hosts]
[-N server-name]

add an example, a script, a trick and tips

: email address (won't be displayed)
: name

Step 2

Thanks for this example ! - It will be moderated and published shortly.

Feel free to post other examples
Oops ! There is a tiny cockup. A damn 404 cockup. Please contact the loosy team who maintains and develops this wonderful site by clicking in the mighty feedback button on the side of the page. Say what happened. Thanks!


cp ../kismet_drone dpkg/data/usr/bin/
cp ../man/kismet.1 dpkg/data/usr/man/man1/
cp ../man/kismet_drone.1 dpkg/data/usr/man/man1/
cp ../man/kismet_drone.1 dpkg/data/usr/man/man1/
cp ../man/kismet.conf.5 dpkg/data/usr/man/man5/
cp ../man/kismet_drone.conf.5 dpkg/data/usr/man/man5/


kismet_drone supports all the capture sources available to Kismet. Instead of processing packets locally, kismet_drone makes them available via TCP to a remote kismet_server using the ’drone’ capture source.


It may be desireable to encrypt the packet stream between the remote drone and the kismet system. Standard SSH packet tunneling or any other tunneling/forwarding system may be used, and is recommended.


kismet_drone should be configured as you would kismet_server. All logging, packet dissection, etc will take place on the remote kismet server using the ’drone’ capture source.

kismet_monitor should be used to place capture sources into rfmonitor mode as needed, and kismet_hopper should be used for channel hopping.

kismet_drone is controlled by the kismet_drone.conf config file.

see also

kismet , kismet_drone.conf


Mike Kershaw

How can this site be more helpful to YOU ?

give  feedback