Add empty mqproxy database, just for reference
Add ARP fixer

This is yet another attempt to make it so we don't have 1RTT of overhead
in the tests on linux and windows (no clue why os x is so intelligent
about the whole process).
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
Fix whitespace pep8 issue
Make reporter more robust

Handle a couple exceptions that may happen with no worse loss of data
than if we crashed (will need to handle data loss some other time).
Merge branch 'master' into server_pcap
Add dns check process

This lets us make sure we won't run tests if the DNS failed to update.
This will be much better than having giant spikes in the graphs when
things go wonky. Also, this will email me, so I won't have to check the
graphs every day to see if something broke on the DNS side of things.
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!
Ignore faked-up run.ini file