[tor-dev] Reproducing #33598 "chutney does not fail on some SOCKS errors"

[c]

On Mon, 15 Jun 2020 14:06:37 -0400
Nick Mathewson <nickm at freehaven.net> wrote:

> This seems plausible, though 0.0.0.0:x will just be the local computer as well.
> 
> Maybe you could try routing to a known-unassigned address, or one that
> Tor simply won't support, like the one from RFC 6666? 

From my understanding 0.0.0.0/32 is a special address that is not
supposed to be routable. But `ping 0.0.0.0` does seem to redirect it to
127.0.0.1 for whatever reason; it might be some odd Linux-specific
behaviour. I'll check for other known-unroutable addresses and try one
of them.

> [...]
> 
> It's in Traffic.py, Source.handle_connect(), in this line:

Thanks, I'll take a look at it.

Caitlin