4 ms·
I've used 127.0.0.0/16 for real work[1]. Keeping a /16 is not much cost and helps out a few more niche cases. Although, I guess if it wasn't available, I could
by toast0 2y ago
I've used 127.0.0.0/16 for real work[1]. Keeping a /16 is not much cost and helps out a few more niche cases. Although, I guess if it wasn't available, I could have used a /16 in private space that didn't overlap with my existing network.
[1] I needed a lot of localhost connections to run a TLS terminator separate from the underlying service which didn't support unix sockets. Using the 127.0.X.0 bits in addressing was very helpful for diversity in the hash used for kernel socket tables, otherwise most slots had few sockets and some slots had way too many and perf was bad. Configuring multiple loopback interfaces using more address space was a lot more tractable than changing the kernel hashing behavior, adding unix socket support to the underlying service, or adding good TLS to the underlying service. Although probably since then all three things have happened.
- nick238 2y agoWhat's the use for multiple local loopback IPs? I'm not a networking guy, just backend dev, so 99.99% of my 127.0... use is running applications locally. For your TLS thing, is it whatever application you were using expected to use a whole swath of TCP ports at whatever IP address, so expected separate IPs? Feels like dedicating some range of addresses to "private use" would have been useful, then if you needed a bunch of local loopbacks, could configure it so, or if your local network wants some magic, tada.