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

United States IPv6 adoption over 50%

google.com

Post reply on HN
Print view View original

101–110 of 164 posts

Re: United States IPv6 adoption over 50%

#101

Post by eximius »

cbdumas wrote: post #37
eximius wrote: post #12

I'm pretty sure I have IPv6, I just haven't figured out how to set it up on my Mikrotik router :/

I got IPv6 working via 6rd on my Mikrotik router a few weeks ago following this forum post https://forum.mikrotik.com/viewtopic.php?t=160314#p788221 If you don't need a tunnel it should be pretty painless, just set up firewall rules and enable IPv6 forwarding

My devices never seemed to pick up the announcement.. I think. Admittedly it was close to two years ago, last I played with it.

I'll check it out!

Re: United States IPv6 adoption over 50%

#102

Post by kaashif »

scoopertrooper wrote: post #83
kstrauser wrote: post #70

Earlier quoted context omitted.

According to back-of-the-napkin math, my home NAS has more storage than was manufactured globally in the year I bought my first computer. It doesn’t seem impossible that someone might have a single pool too big for 2^64 by the end of ZFS’s useful life.

I did some calculations of my own. Assuming a index of size 2^64 and a block size of 256 KB, you could store 6,949,999,424,954 hours of 4k REDCODE36 RAW 4K video @ 120 fps before you ran into problems.

But if proof of space cryptocurrency takes off, who knows how much of the world's disk production it'll use? ZFScoin to the moon!

Just kidding, but maybe not.

Re: United States IPv6 adoption over 50%

#103

Post by bombcar »

floatboth wrote: post #87
geodel wrote: post #76

Earlier quoted context omitted.

I have checked it many times before and score was reliably 0/10 before. Seeing your comment I decided to check it out on this site and guess what today score is 9/10.

What is the missing 1 point?

Iirc it’s usually IPv6 pure dns (ie not getting IPv6 addresses I’ve IPv4)

Re: United States IPv6 adoption over 50%

#104

Post by bombcar »

vidanay wrote: post #8

About 5 years ago, I asked the owner of my fixed wireless ISP if he was planning to support IPv6 and I received a 500 word email rant about the uselessness of v6. I haven't asked again. (I still get a 0/10 score at https://test-ipv6.com/ )

I was up to 9/10 and then our ISP replaced something and we lost our IPv6 addresses.

Re: United States IPv6 adoption over 50%

#105

Post by bombcar »

stingraycharles wrote: post #82
Latty wrote: post #32

Earlier quoted context omitted.

Maybe a bit glib, but I see this as a good thing: a reason to finally fix whatever process requires you to transcribe IP addresses, which is a pain to do even with v4 ones.

Definitely not a pain for a LAN. Case in point: navigating to your router’s web interface. Very easy to do with IPv4 to do, a pain with IPv6. As my home router only supports stateless auto configuration, it’s an additional friction point to have stable addresses. Oh, and since the /56 is assigned by my ISP, it sometimes changes, so I can’t just rely on addresses being stable. I’m not saying that IPv6 is necessarily b…

Link-local addresses are what you want, and “fixed” endings or whatever they’re called - so the router is always ::1 for example.

Or just have IPv4 on the LAN.

Re: United States IPv6 adoption over 50%

#106

Post by dehrmann »

deadbunny wrote: post #96
drsnow wrote: post #86

Earlier quoted context omitted.

Because a firewall exploit means your thermostat is now controllable over the internet and you can conveniently preheat your oven over the internet too and now your house is burning down

No different than NAT and forwarding a port which people have been doing for decades. Hell if you have a firewall exploit then exposing stuff to the internet doesn't matter.

It's very different because NAT blocks by default. You either need to manually set up a forwarded port or the app needs to use UPNP.

Re: United States IPv6 adoption over 50%

#107

Post by bombcar »

eximius wrote: post #101
cbdumas wrote: post #37

Earlier quoted context omitted.

I got IPv6 working via 6rd on my Mikrotik router a few weeks ago following this forum post https://forum.mikrotik.com/viewtopic.php?t=160314#p788221 If you don't need a tunnel it should be pretty painless, just set up firewall rules and enable IPv6 forwarding

My devices never seemed to pick up the announcement.. I think. Admittedly it was close to two years ago, last I played with it. I'll check it out!

I had to have the dhcp client request something to get it to start working when our ISP provided them.

Re: United States IPv6 adoption over 50%

#108

Post by bdd »

FWIW as a content provider to mobile heavy eyeball networks, Facebook has been clocking US v6 adoption consistently over 50% since Sep 2018.

Traffic stats encompass all Facebook properties, FB, Instagram, WhatsApp (hence India topping adoption charts), Oculus, and all smaller things that used some kind service delivery tech of Facebook infrastructure (DNS, web—not limited to CDN, MQTT, etc)

https://www.facebook.com/ipv6/?tab=ipv6_country

Re: United States IPv6 adoption over 50%

#109

Post by deadbunny »

dehrmann wrote: post #106
deadbunny wrote: post #96

Earlier quoted context omitted.

No different than NAT and forwarding a port which people have been doing for decades. Hell if you have a firewall exploit then exposing stuff to the internet doesn't matter.

It's very different because NAT blocks by default. You either need to manually set up a forwarded port or the app needs to use UPNP.

Every consumer router/firewall drops incoming packets by default, why would this be different for ipv6?

Re: United States IPv6 adoption over 50%

#110

Post by dane-pgp »

Gigachad wrote: post #52
dijit wrote: post #48

Earlier quoted context omitted.

Just don’t want it forced on me and by its nature it becomes a hard dependency over time, thus, it does. I’m not interested in another argument but calling my position “pitchforks” is a bit disengenuous and irritating (which is why I’m replying, off-topic, to you). While I think it has something to offer I would like potentially better alternatives to be able to exist in future, this is not “pitchforks”.

>Just don’t want it forced on me and by its nature it becomes a hard dependency over time, thus, it does. systemd is the choice of basically everyone who builds distros, so of course it's going to be hard to avoid unless you volunteer to do all of that work yourself. When you take work from someone else, that comes with taking on the choices that they make.

> systemd is the choice of basically everyone who builds distros

Even if we ignore the fact that systemd made it artificially difficult* for distros to support other init systems (so it wasn't a freely made "choice"), have you never encountered a situation where the popular choice turned out to be the wrong one? Think, for example, of people throwing their trash into nearby rivers, or developers using 2 digits to store year values.

(* Imagine being a volunteer for a distro and having to deal with bugs like "I installed my new printer and it changed my init system[0] / my system no longer boots").

[0] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=863974

Post reply on HN