log relaying
cosmetic
when forwarding frames, send icmp 3.4 packets back to the source
...instead of injecting them on the local interface.
fixes #2
eliminate dependency on pipework
...and docker-ns (though we still leave the script around since it's
handy for debugging), and arping (as I have yet to encounter a
situation where it was required)
r
refactor: reduce indentation
we only know that the build works under Ubuntu
container mobility feature
tweak intro
run weave in privileged container
...since on selinux (and possibly others) we encounter a "bind:
permission denied" error instead, most likely because weave is
attempting to bind a raw ip socket, which is a restricted operation on
those systems.

Fixes #7
explain that we need docker (yes, really)
and switch from 'curl' to 'wget' for installing weave, since the
latter is more widely installed. Also, make root use during that more
explicit.
add some basic error handling to 'weave' script
cosmetic: break overlong line
add Troubleshooting section
usability: check that script is being run as root
so we can display a nicer error if not
pay attention to EMSGSIZE errors when sending pmtu verification packets
and drop the pmtu accordingly
This way, when we actually *do* get pmtu info from the network/kernel
we can discover the correct pmtu much more quickly. Especially in the
absence of other traffic, forwarding of which was previously the only
place where we'd check for EMSGSIZE.

Fixes #12
drop maxpayload in conjunction with clientPMTU
Seems odd to do the latter w/o the former. And wrong.
8 is better than 10
It's quite common for the real pmtu to be 8 less than what was
advertised.
tiny refactor: rename, move
comment