Remix.run Logo
para_parolu 21 hours ago

I can’t understand benefits of having ipv6. The only one is public ips but rest is just headache. In my home network I specify disabled v6 everywhere.

kalleboo 21 hours ago | parent | next [-]

Where I live, the benefit of IPv6 is it's a lot faster than IPv4. All of IPv4 goes through various centralized tunnels and CG-NAT which adds bottlenecks and latency.

webstrand 21 hours ago | parent | prev | next [-]

IPv4 pricing isn't a good enough reason? If all of my devices had nice ipv6 connectivity I could ditch the public ipv4 addresses, but I have to keep them so that my ipv4-only devices can still reach them.

arhue 20 hours ago | parent | prev | next [-]

For home use biggest advantage is that it avoids NAT, which breaks end to end connectivity. Lot of services use hacks to try to mitigate broken connectivity.

compounding_it 20 hours ago | parent [-]

video games

baq 21 hours ago | parent | prev | next [-]

It doesn’t matter in home networks, it’s a major pain in the ass if you are a Fortune 500 company and want to set up more intercompany vpn links

mr_mitm 21 hours ago | parent | prev | next [-]

A site-to-site VPN of two previously unrelated local networks is a pure gamble with IPv4. It would be almost straight forward with IPv6.

wolvoleo 20 hours ago | parent [-]

Yes but these days overlay networks are a way more common practice for that, with their own benefits (overlay IPs are always encrypted)

functional_dev 19 hours ago | parent | prev | next [-]

imo one huge benefit is that ipv6 is much easer for hardware to process.. ipv4 headers are messy and change size.

ipv6 headers are 40 bytes! routers have less thinking.

this visualisation might help to dive deeper - https://vectree.io/c/ipv6

bigstrat2003 17 hours ago | parent | prev | next [-]

Public IPs are a huge benefit and are enough to justify the switch. And there really aren't any headaches in this day and age with IPv6. Once you set it up it works just fine.

gzread 20 hours ago | parent | prev | next [-]

Public IPs is a huge huge huge benefit. Your connection is also faster because your IPv6 packets don't have to be processed by a centralised CGNAT.

wolvoleo 20 hours ago | parent [-]

That's only if you are behind CGNAT though. My fixed ISP doesn't use it.

Plasmoid 20 hours ago | parent | next [-]

Yet.

Many ISPs are pushing v4 users into CGNAT so they're easier and cheaper to manage.

This is a big reason why Netflix and YouTube are on v6. To avoid the cost of service over v4.

mrsssnake 20 hours ago | parent | prev [-]

Even without CGNAT you'll only get one IPv4 address forcing a absurd amount of workarounds to be usable, that are mostly hidden in firmwares but sill there.

iknowstuff 21 hours ago | parent | prev [-]

Ipv4 is the headache. What are you talking about, ipv6 is simpler in my experience.

chungy 21 hours ago | parent [-]

IPv4 is pretty simple and good for LANs. Nothing wrong with sticking to it.

cesarb 19 hours ago | parent | next [-]

> IPv4 is pretty simple and good for LANs.

Until the place you're VPNing to happens to use the same RFC1918 network address as your LAN (that is, your LAN is 192.168.10.x and the network on the other side of your work's VPN is also 192.168.10.x). Or either of them use the same RFC1918 network address libvirt is using for its virtual network. Or you want to route between several LANs (for instance, after a company merger) and some of them (but not all) were using the same RFC1918 network addresses.

All of this is avoided by using public addresses for LANs, but address scarcity makes that hard with IPv4 (unless it's a legacy LAN from the 1900s which happens to still use public addresses form the pre-NAT era).

chungy 8 hours ago | parent [-]

Don't confuse "simple and good" with "flawless" :-)

There are indeed only a few private-reserved IPv4 ranges, and almost everyone prefers to keep things memorable and easy to type; you get a lot of 10.0.0.0/24, 192.168.0.0/24, 192.168.1.0/24 as a result. That, and common household routers tend to default to one of these three /24 subnets. (Hardly anyone seems to remember that 172.16.0.0/12 exists, feel free to use that if it happens to work for you.)

IPv6 does solve this issue in a few major ways, one of which is the greater expectation to rely on globally routable addresses, of which every one of your devices will have at least one such address. There's also fc00::/7 which is fairly equivalent to the IPv4 private ranges, though to avoid conflicts in random VPNs you should generate a random /64 prefix inside of this, otherwise you run the risk of everyone picking fc00::/64 because it's easy to remember/type (I'm guilty of this myself, but the VPNs I've configured just go into a random 172.16.0.0/12 subnet and no v6 assigned. I have the liberty that I currently don't need/use any VPNs that I haven't personally configured, and that may not hold true in the future.)

iknowstuff 21 hours ago | parent | prev [-]

Matter requires IPv6

wolvoleo 20 hours ago | parent [-]

Huh, I have matter devices working here and IPv6 is off on my router and DHCP. And on home assistant too which does the matter router. Does it use link local or something?