5 ms·
>I just want my devices connected. Which IPv6 does pretty well even if you aren't a network engineer. More than 40% of all requests to google are from IPv6 and
by bauruine 4y ago
>I just want my devices connected.
Which IPv6 does pretty well even if you aren't a network engineer. More than 40% of all requests to google are from IPv6 and the vast majority of those connections are from people that never heard of IPv6.
- magicalhippo 4y agoWell I had to do some deep dives to get IPv6 working, and it really didn't work until I got rid of pfSense and switched to OpenWRT. I'm not just talking about connected to Google, I mean to each other. So ULA, DNS, DHCPv6 vs SLAAC etc is in play.
- JohnFen 4y ago> Which IPv6 does pretty well even if you aren't a network engineer. Outside of smartphones (in the US, apparently), moving from IPv4 to IPv6 is genuinely painful and often requires deeper knowledge of networking to accomplish. Yes, if you're using a smartphone or your needs are otherwise trivial (for instance, you don't have a real network at home but just have one or two devices connected to your modem), then none of this is a big deal. But outside of that, things can be very different.
- bauruine 4y agoWe have millions of customers of which most don't know what an IP is. They mostly have a standard network, wired PCs, wifi devices, consoles etc. like 99% of all people. They browse facebook and instagram, search on google and watch youtube videos all over IPv6 without even knowing. Yes there where network engineers involved to make this work but without some engineers you wouldn't have IPv4 either.
- JohnFen 4y ago> They mostly have a standard network, wired PCs, wifi devices, consoles etc. like 99% of all people. Right. Those are the "trivial" cases I mentioned.
- bauruine 4y agoSetting up a non trivial network requires a deep understanding of networkig whether it is v4 or v6. I don't get your point.
- JohnFen 4y agoThe IPv4 knowledge already exists. For people who aren't network engineers, the fact that they have to learn an entirely new, complex, networking protocol and associated services is a huge pain point. I think a lot of actual experts really underestimate how much friction that presents. And that level of pain means that those people are very resistant to moving to IPv6. That was the only point I was making.
- bauruine 4y agoValid point but all those "not network engineers" that build networks can either fight it or implement it. Either way they have to learn it because they get exposed to it at least passively as the article calls it.
- JohnFen 4y agoWell, they clearly have a third option because that's the one they've been taking: neither fighting nor implementing it. Thus the slow pace of adoption. That's not an endorsement on my part at all, just a recognition of what has happened. I confess that I'm doing the same thing in my home network -- I won't move to IPv6 until I have no other choice, because that move will take a ton of time, sweat, and tears. Just to stave off misguided attacks on me: I am not saying IPv6 sucks and we shouldn't move to it. Not at all. But moving to it is a very expensive proposition.
- bauruine 4y agoTrue I should have written "They should learn" or they could open security holes. Now I'm interested on what kind of "home network" you have that makes v6 that hard.