kismet_drone
Wireless sniffing and monitoring remote drone
see also :
kismet
Synopsis
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
examples
source
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/
description
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.
encryption
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.
usage
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
author
Mike
Kershaw