Re:History of 127/8 as localhost/loopback addresses (2021)
by zinekeller on Wednesday May 25, 2022 @10:33AM
(#31505111)
Everyone suggesting that ::ffff:0:0/96 is a solution should note that not all network stacks are "unified". Windows' stack isn't unified (try accessing http://[::ffff:7f00:1]/ while having a loopback server and it won't work) and most non-Linux embedded OSes separate the network stack for size reasons (to the chagrin of IPv6 promoters, but most of them are simply trying to fit something into the half-MB EEPROMS like how most IoT devices don't have 5GHz Wifi support).
[ Parent
| on HN ]
Re:History of 127/8 as localhost/loopback addresses (2021)
by X-Istence on Wednesday May 25, 2022 @01:03PM
(#31507280)
The server would need to bind to that address, and then it should work fine as long as that address is assigned to a loopback interface.
That's the same as any system right now. If I bind to 127.0.0.1 I don't automatically get traffic for or listen on 127.0.0.2
Re:History of 127/8 as localhost/loopback addresses (2021)
by zinekeller on Friday May 27, 2022 @04:36PM
(#31534568)
> The server would need to bind to that address, and then it should work fine as long as that address is assigned to a loopback interface.
... you haven't worked on Linux or Windows networking stacks. On Linux, typing http://[::ffff:7f00:1]/ when you have a bound server on 127.0.0.1 will automatically connect to 127.0.0.1. Conversely, it's a illegal operation in Windows: you cannot legally bind even with SYSTEM privileges.