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

I spent a week without IPv4 to understand IPv6 transition mechanisms

apalrd.net

Post reply on HN
Print view View original

31–40 of 511 posts

Re: I spent a week without IPv4 to understand IPv6 transition mechanisms

#31

Post by Godel_unicode »

nickstinemates wrote: post #10
soebbing wrote: post #8

I am quite happy that all those shady IoT devices cannot be reached from the internet directly when I am using IPv4 and NAT - what would be the best way forward to keep it that way in a IPv6-only future? The best idea I can come up with (at least right now) is: put all less trustworthy (read: Closed source) devices into a special legacy IPv4 network and only use IPv6 on my workstation and little Raspis?

Network segmentation, i.e use of vlans is the traditional way to solve this.

Not sure why you’re being downvoted, this is a very good answer. Maybe because you left out the implied “and then firewall off that vlan”?

Re: I spent a week without IPv4 to understand IPv6 transition mechanisms

#32

Post by screamingninja »

speedgoose wrote: post #3

Why should I spend the time and energy to deal with IPv6 when disabling it fix many issues ? The listed advantages are not worth the troubles in my experience.

Increased number of available IP addresses, improved security features, simplified network management, reduced network complexity, and support for new technologies. The adoption of IPv6 will lead to cost savings, improved network performance, and increased scalability. Scalability may not matter in the typical home network, but in an enterprise environment, the cost of up-keeping the network backbone is significant.

Re: I spent a week without IPv4 to understand IPv6 transition mechanisms

#33

Post by thesuitonym »

ArchOversight wrote: post #30
thesuitonym wrote: post #28

Everyone always goes with the "You don't need NAT, everything is globally routable!" argument, as if that's something that anybody wants. Everything on my network is going to go through my firewall anyway. I don't want anything on my network to be globally routable. Of course, this is not a good reason to not use IPv6, don't get me wrong. It's a problem that's easy to overcome, I just think it's not a good way to get…

That's what a firewall is for, NAT does nothing here.

I know, did you read my whole post?

Re: I spent a week without IPv4 to understand IPv6 transition mechanisms

#34

Post by mynameisvlad »

api wrote: post #19
speedgoose wrote: post #3

Why should I spend the time and energy to deal with IPv6 when disabling it fix many issues ? The listed advantages are not worth the troubles in my experience.

I've run dual stack at home and at work for years and have had no issues. You might have issues if you have really old junk that's just broken.

[flagged]

Re: I spent a week without IPv4 to understand IPv6 transition mechanisms

#35

Post by crest »

czbond wrote: post #4

Great idea. Now a question for the group. What are the non-network team business benefits to IPv6 over v4? That is what drives adoption.

Less operational complexity. VPN overlays for remote management, realtime peer to peer video and audio streaming, etc. just work reliably. You also get to build the address plan to fit your (business) requirements instead of working around which addressspace is available where.

Re: I spent a week without IPv4 to understand IPv6 transition mechanisms

#36

Post by teddyh »

bittermandel wrote: post #11

Is there any risks of nodes assigning same IP if there's no central DHCP?

Firstly, normally nodes base their automatic IPv6 address on their MAC address, so there will be no conflict between these, since MAC addresses are supposed to be unique to the hardware. Otherwise, it’s a random 64-bit number (actually a few less bits, but not many). It’s very unlikely a collision will happen. And even if it does, there is a protocol (Duplicate Address Detection) to detect it, and avoid it.

Re: I spent a week without IPv4 to understand IPv6 transition mechanisms

#37

Post by ip26 »

speedgoose wrote: post #3

Why should I spend the time and energy to deal with IPv6 when disabling it fix many issues ? The listed advantages are not worth the troubles in my experience.

The advantage mostly falls to the infrastructure. In theory it performs better, but only marginally, which is quickly overwhelmed by simple issues like inferior routes. As an end user, frankly I stopped caring long ago.

Re: I spent a week without IPv4 to understand IPv6 transition mechanisms

#38

Post by mgbmtl »

TekMol wrote: post #21

I still think IPv6 can be safely ignored. This articles section "here are some reasons you should start using IPv6 within your own network" seems to comfirm this. None of the 6 "reasons" speak to me.

Here's an easy one for you: if you have a gigabit connection, most home routers can barely handle the load of NAT. That's why gamers push for IPv6. It's mentioned in the article but few people realize how inefficient NAT can be at gigabit and more.

My ISP router could do max 800 mbps, which isn't so bad, but it degraded when we were multiple people using the link. With IPv6 it's much less of a problem, we can easily saturate the 1gbps without the router having a meltdown.

Re: I spent a week without IPv4 to understand IPv6 transition mechanisms

#39

Post by tenebrisalietum »

thesuitonym wrote: post #28

Everyone always goes with the "You don't need NAT, everything is globally routable!" argument, as if that's something that anybody wants. Everything on my network is going to go through my firewall anyway. I don't want anything on my network to be globally routable. Of course, this is not a good reason to not use IPv6, don't get me wrong. It's a problem that's easy to overcome, I just think it's not a good way to get…

> I don't want anything on my network to be globally routable.

Then... don't route anything on your network.

NAT is address translation, not routing.

NAT makes it difficult for you to host services on your network, forcing dependency on cloud services, and when ISPs do it (CGNAT), it makes it just about impossible unless you want to thread your traffic back through a third-party service. If you want a good chance of keeping some semblance of an Internet around that isn't dominated by huge centralized services, the cargo cult of "NAT is security" needs to die hard.

Re: I spent a week without IPv4 to understand IPv6 transition mechanisms

#40

Post by mavhc »

thesuitonym wrote: post #28

Everyone always goes with the "You don't need NAT, everything is globally routable!" argument, as if that's something that anybody wants. Everything on my network is going to go through my firewall anyway. I don't want anything on my network to be globally routable. Of course, this is not a good reason to not use IPv6, don't get me wrong. It's a problem that's easy to overcome, I just think it's not a good way to get…

NAT and a Firewall are two different concepts.

What's wrong with a firewall that blocks everything by default, yet all your devices have a public IP?

Post reply on HN