More informative error message
Note when proxying to a TLS home server
Use random outbound port for proxying.

It's safer than trying to force one, even if it is not as nice
looking at large numbers in the debug output
When a socket is dead, set it's state to EOL, not REMOVE_NOW

And for the readers / writers, refuse to do anything to the
socket if it's state is something other than KNOWN
Remove confusing error message

And replace it with more meaningful ones
Remove FDs from the FD list at EOL
Fix error message
Ensure we set packet->proto for packets to home servers