3 ms·
Unrelated to code, but related to IP space - there are at least two "reserved IP spaces" that look like they are completely usable by private networks, not incl
by unethical_ban 7y ago
Unrelated to code, but related to IP space - there are at least two "reserved IP spaces" that look like they are completely usable by private networks, not included in RFC1918.
198.18.0.0/15, reserved for benchmarking devices across subnetworks.
100.64.0.0/10, reserved for carrier-grade NAT. This one might have the higher chance of a collision depending on your use case or if it's part of a VPN pool.
Several ISPs I have tested all drop them when you traceroute.
So if your organization can't switch to IPv6 internally and has performed horrible IPAM on RFC1918, here is a last chance... don't screw it up.
- zonidjan 7y agoYou could also (ab)use the TEST-NET ranges as private address space.
- jlgaddis 7y agoI've been (ab)using 198.18/15 (also reserved, cf. RFC2544) at home for years. It works just as any other network would and is a perfect solution for me. (Previously, I abused TEST-NET-2 and TEST-NET-3 and both of those worked fine as well.)
- inopinatus 7y agoIANA’s special-purpose address registries are the canonical reference. https://www.iana.org/assignments/iana-ipv4-special-registry/iana-ipv4-special-registry.xhtml https://www.iana.org/assignments/iana-ipv4-special-registry/... https://www.iana.org/assignments/iana-ipv6-special-registry/iana-ipv6-special-registry.xhtml https://www.iana.org/assignments/iana-ipv6-special-registry/...