Start work on doing the pcap from the servers

This is in place of doing it on the clients. Linux seems to be the only
stable OS for doing pcaps on programmatically, and all the servers are
linux, so let's do all our pcaps on linux!

This contains the server component that will actually be responsible for
running the pcaps, as well as a slight refactor to share some code
between that and the web-based MQ that windows uses.
Add client-side pcap program

This is what will call out to the server to get it to start our pcap
process for us.
Add example config entries for new config variables
Don't freak out if the pcap has already stopped

Chances are we just made a mistake somewhere, so we want to say "ok,
it's stopped", but send along a message, JUST in case.
Clean up after results are retrieved

Also, comments and docstrings, yay!
Run the pcap from the server
Merge branch 'master' into server_pcap
Merge branch 'master' into server_pcap
Add explanatory comments

This way, future versions of myself might be able to understand what and
why I'm doing bottle_inject.
Fix arg parsing on pcap
Fix json loading
Forgot these two json points
Get results from the right place in the dict

Results aren't at the top level, they're under data, silly!
Don't run tcpdump from runner

When we're running tcpdump on the server, running it on the client is
irrelephant!
Merge branch 'master' into server_pcap
Merge branch 'master' into server_pcap

Conflicts:
	srworker.py
Merge branch 'master' into server_pcap
Add more logging (and error handling) to client-side pcap
Add more logging in server-side pcap
Move arp fixer to just before runner

This way we don't run the risk of expiring our arp entry before the
tests have run.