Explanation/Alt text: The tuxedo Winnie the Pooh meme showing more and more abstract representation of “home”.
- The literal word “Home”
- 127.0.0.1, the IP address of your current device
- ~/, the Unix home directory
- A Nintendo Switch RCM clip, which is used to short pin 1 and 10 of the Joycon railing in order to enter recovery mode (RCM) for softmodding. The pin 1 and 10 combination is known as the “hardware home button”
I’m not, and I’ll never give it up on any network i control. It’s simple, easy to remember, i don’t personally need 255 ip addresses so ipv4 space is just fine for me. And i don’t need my devices to be individually addressable globally i can port forward if something needs to be accessed externally.
IPv6 makes sense at the carrier level but at the endpoint networks especially just for homes there is literally nothing wrong with ipv4
From the home network standpoint what good is having IPv6 on WAN if you don’t have IPv6 internally? One of the main selling points is not having to put up with the bullshit we all know as NAT — it’s weird you’d actively go against having it internally.
It just creates unnecessary complication. It’s not particularly memorable, it’s a pain to even just lookup tye syntax imo compared with v4, and I genuinely do not see the benefit at the home level to getting rid of NAT. Carrier and backhaul? Oh yeah nat is a fucking plague. But home level? Literally causes no issues it’s trivial to work with, 98% of people do not need ports forwarded ever. Those that do it’s not hard. IPV6 necessitates more careful control of a firewall now that every device is globally reachable and means that it won’t even make opening a service any easier. It’s just firewall instead of NAT forward which on most routers will more or less be the same process
6to4 exists and could handle translation of the backhaul 6 to a local 4. Only the router itself need be directly addressable imo.