Live data from Hacker News

IPv6 is the only way forward

ankshilp.in

161–170 of 350 posts

Re: IPv6 is the only way forward

#162

The main complaint I have against IPv6 is the addresses are so unwieldy. When I look at them I have the same reaction as when I look at some kind of complex scientific formula comprised of operators and symbols that are unfamiliar. It also takes extra mental effort to expand the compressed zeros and interpret what I'm viewing. Even after reading about them many times and using them in (an albeit limited) fashion, the…

This is without even getting into learning the new (old?) paradigm of "exposing" all addresses to the whole internet. I realize "NAT" is not equivalent to "firewall", but placing them at the same boundary made things simple to understand conceptually. I for one never had trouble opening/forwarding ports (and liked the control it provided over what goes in and out, especially in the days before it all just became HTTP…

NAT also solves the dynamic address issue. With GUA I need to deal with both dynamic prefix and randomised suffix that can be changed by seemingly unrelated things when opening ports to the internet.

Re: IPv6 is the only way forward

#164

Earlier quoted context omitted.

This is without even getting into learning the new (old?) paradigm of "exposing" all addresses to the whole internet. I realize "NAT" is not equivalent to "firewall", but placing them at the same boundary made things simple to understand conceptually. I for one never had trouble opening/forwarding ports (and liked the control it provided over what goes in and out, especially in the days before it all just became HTTP…

NAT also solves the dynamic address issue. With GUA I need to deal with both dynamic prefix and randomised suffix that can be changed by seemingly unrelated things when opening ports to the internet.

Does your ISP not offer static prefixes?

For 5€/mo additional I get a static /32 v4 (for NAT64) and a /60 v6 prefix.

Re: IPv6 is the only way forward

#166
post #61

Earlier quoted context omitted.

Having 2 sockets for loopback or multiple interfaces is a huge pain

Bind to '::' and you can get v4 and v6 traffic on one socket.

Not on all OSes. And it's not all good to have one less socket, there are still issues with people not expecting v4 traffic on a v6-capable socket, like described here:

https://radar.offseq.com/threat/ipv4-mapped-ipv6-addresses-t...

If you want to handle two protocols, it is not unreasonable to use two sockets.

Re: IPv6 is the only way forward

#168

I don't understand why people are so negative about IPv6. I have done essentially zero home networking work and I just ran this successfully. It just works! ``` > ping6 google.com PING6(56=40+8+8 bytes) 2605:59c0:236f:3a08:7883:9d04:c26d:5fa1 --> 2607:f8b0:4005:806::200e 16 bytes from 2607:f8b0:4005:806::200e, icmp_seq=0 hlim=117 time=22.262 ms 16 bytes from 2607:f8b0:4005:806::200e, icmp_seq=1 hlim=117 time=26.124 m…

> I don't understand why people are so negative about IPv6. [...] It just works! Networking is a lot more than being able to ping a single host. As a concrete counter-example, IPv6 routinely broke for me when I was using pfSense as a router. Why? Because pfSense, with no way of disabling this behavior, published its public IP as the DNS server for internal clients. So each time I got a new prefix from my ISP, which h…

> As a concrete counter-example, IPv6 routinely broke for me when I was using pfSense as a router. Why? Because pfSense, does really bad things.

I mean, I have a router that is trash with IP4. Therefore IP4 is trash!

Re: IPv6 is the only way forward

#169

Earlier quoted context omitted.

> I don't understand why people are so negative about IPv6. [...] It just works! Networking is a lot more than being able to ping a single host. As a concrete counter-example, IPv6 routinely broke for me when I was using pfSense as a router. Why? Because pfSense, with no way of disabling this behavior, published its public IP as the DNS server for internal clients. So each time I got a new prefix from my ISP, which h…

> As a concrete counter-example, IPv6 routinely broke for me when I was using pfSense as a router. Why? Because pfSense, does really bad things. I mean, I have a router that is trash with IP4. Therefore IP4 is trash!

Please don't put words in my mouth. I did not say "Because pfSense, does really bad things."

How pfSense works is fairly reasonable if every IPv6 deployment had been as the original designers intended, ie you have a static prefix.

It's just that the way IPv6 ended up getting deployed in practice was often not aligned with that original vision. And that has been a large source of IPv6 frustration.

Re: IPv6 is the only way forward

#170

Earlier quoted context omitted.

That's literally impossible, to hear some people tell it. "And also, look how hard it'd be to memorize that address", say the people who remember like 2 IPv4 addresses, one of them being 127.0.0.1.

Tailscale, perhaps ironically in this context, has shown me the value of not caring about an IP address. I used to. When I had a home network I'd carefully assign `10.52.1.x` where `x` was the periodic number corresponding to the machine name! (I write from `lutetium`.) Now, with Tailscale's magic DNS – `lutetium` being all I need – why on Earth would I give a crap about an IP address? I've gone from being obsessed t…

It's akin to remembering the phone numbers. Even 20 years ago I had like 10-20 of most important ones memorized despite some of them not used often ie once in a years. Nowadays I have 'me myself' in the Contacts because I can't remember it despite using it for 5+ years nor I care.
Post reply on HN