192.0.2.0/24 is TEST-NET-1, per [1] I suspect that 127.0.0.0/8 breakage is related to IPv6's existence, since only in IPv4 is the whole class A network usable

192.0.2.0/24 is TEST-NET-1, per [1] I suspect that 127.0.0.0/8 breakage is related to IPv6's existence, since only in IPv4 is the whole class A network usable as loopback - at least, it's broken on Linux (you can't do `ping ::ffff:127.1.2.3` ... actually, now that I try it, it fails even for non-loopback addresses? I thought I tested that before) ... I haven't tried explicitly bind()ing the local socket before connect()ing though (most often, you only bind before listen, and let it autobind when you connect). Related, `gethostent` enumeration is completely broken for IPv6 under GLIBC at least. and while I'm ranting about networking, the latest Debian on my laptop "permanently" clobbers the default route (see `ip r`) when the rfkill button is pressed (thus leading to the weird situation where you can access the LAN but not anything beyond it) - to fix, `systemctl restart networking.service` [1]: https://www.iana.org/assignments/iana-ipv4-special-registry/iana-ipv4-special-registry.xhtml https://www.iana.org/assignments/iana-ipv4-special-registry/... ... huh, that's missing the multicast reservations though ... those are admittedly weird.