As usual, I'm out of room before I'm out of ideas, so here are some quick hints for folks who want to set up a stationary Kismet drone network. This is a slick way to monitor your site all the time, without having to wander around looking like a war-walking dork. Drones need two NICs: one wireless interface for monitoring, and a second NIC for sending data to the server. Wired interfaces are good for this, though you can use wireless if you really really want.

Configure the drones in /etc/kismet/kismet_drone.conf. Configure them just like we did for kismet.conf last week. Then configure the drone with a different TCP port than your Kismet server with tcpport=3510, or some such. Check /etc/services to avoid duplication. Then configure allowedhosts= for your network segment, like 127.0.0.1,192.168.1.0/24.

Finally, configure /etc/kismet/kismet.conf on the Kismet server to pick up the drone's output:

source=kismet_drone,192.168.1.50:3510,drone1

Use one line per drone. The name field, as we learned last week, can be anything.

You are now well on your way to wireless wizardry, and foiling the forces of darkness who would dare to trespass and misuse your wireless network.

Resources

• Thank you to the LinuxChix gang for help with this article!
  
• Kismet documentation
  
• Tips and Tricks for Linux Admins: Discover, Map and Store
  
• Foil Wireless Poachers and Have Fun Doing It
  
• dsniff Frequently Asked Questions
  

This article originally appeared on Enterprise Networking Planet, a JupiterWeb site.

« Back: Killing and Slaying