Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Show HN: A Short IPv6 Guide for Home IPv4 Admins

gist.github.com

Post reply on HN
Print view View original

41–50 of 56 posts

Re: Show HN: A Short IPv6 Guide for Home IPv4 Admins

#41

Post by m463 »

jetbalsa wrote: post #20
redundantly wrote: post #3

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 s…

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.

Re: Show HN: A Short IPv6 Guide for Home IPv4 Admins

#42

Post by anthropodie »

m463 wrote: post #40
redundantly wrote: post #3

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 s…

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.

Re: Show HN: A Short IPv6 Guide for Home IPv4 Admins

#43

Post by m463 »

anthropodie wrote: post #42
m463 wrote: post #40

Earlier quoted context omitted.

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.

Re: Show HN: A Short IPv6 Guide for Home IPv4 Admins

#44

Post by averageRoyalty »

anthropodie wrote: post #42
m463 wrote: post #40

Earlier quoted context omitted.

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.

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.

Re: Show HN: A Short IPv6 Guide for Home IPv4 Admins

#45

Post by imoverclocked »

move-on-by wrote: post #38
wmf wrote: post #12

Earlier quoted context omitted.

It sounds like you're talking about running a router behind a router which you should try to avoid. If you want to run your own router you should try to put your modem/dish in passthrough mode. Once you do that Starlink works fine.

This assumes your ISP provided modem isn’t straight up user hostile and provides a pass through mode. I’m convinced t-mobile’s awful home internet modem/router is intentionally designed to make using your own router difficult and specifically only provides a /64 prefix delegation to prevent any router-behind-router setups from getting globally routed IPv6 addresses. Not to mention no port forwarding capabilities.

My blogpost shows how to get around that using an ndp proxy. All my hosts have global IPv6 behind my own router+firewall with only an advertised /64 in front of it. :)

Re: Show HN: A Short IPv6 Guide for Home IPv4 Admins

#46

Post by cqqxo4zV46cp »

philsnow wrote: post #33
anthropodie wrote: post #23

Earlier quoted context omitted.

> Why have globally-routable IPv6 addresses if you're not going to use them? Because globally routable addresses are not static. Your prefix may change.

I guess I mean, the gist only motivates the use of globally-routable addresses for externally accessible services. If a particular service/device isn't going to be accessed externally, there's no need to give it one.

A big part of why I see people talking past each other on this is, IMO, because the solution that seems ‘cleaner’ depends on one’s mental model of networks / IPv6. These can and do differ. One person’s “I need justification to have non-globally-routed addresses” is another person’s “I need justification to have anything else”.

Re: Show HN: A Short IPv6 Guide for Home IPv4 Admins

#47

Post by mannyv »

hairyplanter wrote: post #10
mannyv wrote: post #6

How do you run a DNS server when your address isn't technically static? How do clients discover the DNS server in a SLAAC environment?

RA message can specify a DNS server. Mine specifies the router's ULA, which is effectively static, and it runs unbounded.

How do you authenticate RA messages? I mean, can anyone just throw RA messages onto the network?

This seems like the "rogue DHCP" problem in v4.

Re: Show HN: A Short IPv6 Guide for Home IPv4 Admins

#48

Post by hot_gril »

averageRoyalty wrote: post #44
anthropodie wrote: post #42

Earlier quoted context omitted.

> 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.

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 lov…

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

Re: Show HN: A Short IPv6 Guide for Home IPv4 Admins

#50

Post by cassianoleal »

m463 wrote: post #43
anthropodie wrote: post #42

Earlier quoted context omitted.

> 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.

Post reply on HN