Which is configuration that's requires arcane invocations and permissions I might not have.
As opposed to IPv4, where everything Just Works™.
…until it doesn't, when something looks at the configured addresses. The "other" addresses in 127.0/8 will easily have weird behavior in nontrivial setups.
I wish that were true. MacOS for example only assigns 127.0.0.1/32. You have to assign extra IPs manually, the same way you would on IPv6.
Re:IPv6 Is Hard
by procaryote on Monday February 17, 2025 @05:01AM
(#43077116)
that is a mac problem, not an ipv4 problem. The mac does a lot of pretty stupid things
Re:IPv6 Is Hard
by selfhoster on Monday February 17, 2025 @10:24AM
(#43079901)
As someone who used Windows and Linux my whole career and now am forced to use Mac for a new job; I completely agree, I was right, Mac is a very weird thing overall.
Same thing on FreeBSD. It's just not something you can rely on and the spec doesn't say it needs to be assigned.
Re:IPv6 Is Hard
by paulddraper on Monday February 17, 2025 @04:02PM
(#43083271)
Yeah, and I always do.
Because parent is right, having multiple loopback addresses is just so nice for a lot of things.
Re:IPv6 Is Hard
by paulddraper on Sunday February 16, 2025 @11:44PM
(#43075241)
> waste thousands
Yeah would hate to run out
Just assign multiple IPv6 to your loopback interface and everything will work as expected. You can use either private IPv6 or even link-local IPv6 range.
There’s no need to waste thousands of addresss on this use case.