Hacker News Reader

Comment by redundantly | Hacker News Reader

It's weird. Personally I've yet to make the jump to IPv6 because it seems too complex, doesn't make sense, so I don't want to spend the mental effort learning it when I have no need to switch.

However, looking decades back I realise I felt the same way when first learning about and working with networks. Nothing about it is intuitive. It's all complex, until it isn't through repetition and familiarity.

That said, I still don't want to spend the mental effort on IPv6 yet. I'll deal with it when I have a need for it.

View on HN

I think ipv4 is way more manageable.

One set of firewall rules, easy to view ip addresses, machines don't leak.

I would put the extra braincells to work learning vlans. putting machines in jail is a liberating experience.

You can also learn to use privoxy to control IF machines have internet access, who they talk to and when.

> I think ipv4 is way more manageable.

That's because it's familiar and comfortable. Once you get hang of IPv6 you dislike the idea of fiddling with numbers as protocol takes care of most of things.

don't you still have to do ipv4 too? my static ip addresses are ipv4.

> don't you still have to do ipv4 too?

This is quite a loaded question. You need some sort of IPv4 to access the IPv4 Internet. You need some sort of IPv4 if you have devices that don't support IPv6.

What you need in each case depends. If it's just to access the IPv4 Internet, you might get away with NAT64 and a single public IPv4 on the WAN interface.

> my static ip addresses are ipv4.

Ok? You can have static IPv6 addresses if you want.

The protocol takes care of most things if default settings (e.g dynamic addressing, subnetting) suit you.

Predictable addresses are messy. Changing ISPs is a nightmare unless you run NAT. Firewalling being decoupled from NAT is a more complex experience. Memorising addresses becomes much harder. Old devices have varying support and common brand routers still have various IPv6 bugs.

I have IPv6 running at home and love it, but familiarity and comfort aren't the primary reasons it's less managable. Many existing configurations simply don't translate across very well.

Maybe the answer is that you run NAT even with ipv6.

Im kind of in the same boat, I'm on a CGNAT with a apartment community, they don't have IPv6 at all, matter of fact they barely VLAN the apartments / wifi apart. I've rick rolled the entire complex's chromecasts before

I hate this trend. It's also impossible to get a static ip address.

I'm ok with the opinionated kind of ipv6 this guide puts forth. There are too many other ways to use it that have problems.

Reply on news.ycombinator.com