Prior to the VNET work, you would often do shenanigans with loopback adaptor to give each jail a separate IP on a FreeBSD machine. I had one setup where each jail had a different IP in the 127.0.0.1 subnet for its loopback adaptor and localhost set up to point to that address in /etc/hosts.
I dunno – I’m sure there’s amusing experimentation to be done there, but it also seems like the kind of thing where, in the rare cases in which it does happen, odds of it being unintentional might actually be quite high.
I worked on a multi-cpu system (connected via Ethernet over PCIe) that was logically one “system”, and we used a portion of 127.0.0.0/8 to direct traffic to the other CPUs. Unusual, perhaps, but it worked and was purely internal.
This change in curl wouldn’t have changed anything though, as 127.0.0.1 was still localhost.
Google cache version: http://webcache.googleusercontent.com/search?q=cache:Wl3OyvneK7kJ:https://daniel.haxx.se/blog/2021/05/31/curl-localhost-as-a-local-host/&hl=en&gl=uk&strip=1&vwsrc=0
Rerouting 127.0.0.0/8, now that would be a fun thing to expiriment with
Prior to the VNET work, you would often do shenanigans with loopback adaptor to give each jail a separate IP on a FreeBSD machine. I had one setup where each jail had a different IP in the 127.0.0.1 subnet for its loopback adaptor and
localhostset up to point to that address in/etc/hosts.In hindsight, it probably wasn’t a good idea.
TFA says:
I dunno – I’m sure there’s amusing experimentation to be done there, but it also seems like the kind of thing where, in the rare cases in which it does happen, odds of it being unintentional might actually be quite high.
I worked on a multi-cpu system (connected via Ethernet over PCIe) that was logically one “system”, and we used a portion of 127.0.0.0/8 to direct traffic to the other CPUs. Unusual, perhaps, but it worked and was purely internal.
This change in curl wouldn’t have changed anything though, as 127.0.0.1 was still localhost.