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.
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'
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.
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.