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

So Long Last /8 and Thanks For All the Allocations

labs.ripe.net

Post reply on HN
Print view View original

41–50 of 201 posts

Re: So Long Last /8 and Thanks For All the Allocations

#41

Post by vbezhenar »

d3ckard wrote: post #27

Is it time to just admit IPv6 is a failure and move on to new standard? Adoption is very slow though economical needs are already here. Instead of complaining about users maybe we should do something so they actually want to switch?

IPv4 worked for a long time and works for majority of installations now. It's hard to migrate when advantages are not obvious. I'm not sure that IPv6 is very good, I'm always having problem with it, but any standard will have adoption problems when current solution is good enough. I don't think that there's need for new standard and I'm sure that new standard won't be adopted better than IPv6.

Re: So Long Last /8 and Thanks For All the Allocations

#42

Post by randomdestructn »

chrisper wrote: post #19
freeone3000 wrote: post #17

Earlier quoted context omitted.

What's wrong with IPv6? The only complaints I've seen are "the numbers are bigger", as if that's not the point, and that makes them harder to remember.

My "main issue" with it is that if people are used to being behind NAT, they now have to be a bit more careful about securing their computers (firewall etc.) because every computer now is publicly accessible. Most routers do not even seem to have an IPv6 firewall.

Same. And its only really an issue for me because around here the home/SOHO IPv6 rollout is transparent to clients.

So people who have been trusting NAT to be a firewall wake up one day to their network being directly routable, and are none the wiser.

Re: So Long Last /8 and Thanks For All the Allocations

#43

Post by toast0 »

chrisper wrote: post #19
freeone3000 wrote: post #17

Earlier quoted context omitted.

What's wrong with IPv6? The only complaints I've seen are "the numbers are bigger", as if that's not the point, and that makes them harder to remember.

My "main issue" with it is that if people are used to being behind NAT, they now have to be a bit more careful about securing their computers (firewall etc.) because every computer now is publicly accessible. Most routers do not even seem to have an IPv6 firewall.

The 'residential gateway' for my attached fiber connection doesn't allow incoming syns for the ipv6 addresses it hands out and I couldn't even find a way to tell it to let me actually use the internet as intended, other than bypassing it (which works fine).

Most endpoints these days don't have much if anything listening by default though. The reality is that even trusted local networks are hostile networks, and vendors have responded to that.

Re: So Long Last /8 and Thanks For All the Allocations

#44

Post by sp332 »

appdrag wrote: post #20

RIP ipv4 :p And ipv6 is still nearly nowhere...

Google says >30% of USA usage is over IPv6. https://www.google.com/intl/en/ipv6/statistics.html#tab=per-... Akamai says 40%. https://www.akamai.com/uk/en/about/our-thinking/state-of-the... But it shows a huge jump in May last year, not sure what that's about.

Re: So Long Last /8 and Thanks For All the Allocations

#46

Post by ahjaiM7r »

merb wrote: post #36
cptskippy wrote: post #31

Earlier quoted context omitted.

Support for IPv6 is weird. Comcast's IPv6 implementation is rock solid and faster than IPv4 most of the time. I've been running publicly accessible IPv6 HTTP hosts over it for several years now. The last two Motorola Modems I've had came with IPv6 support and were provisioned by Comcast out of the box. Access Points from D-Link will autoconfigure via SLAAC but DNS has to be hardcoded. It's 2018 and yet Ubiquiti's Uni…

> Windows just works seems to fuck with nonWindows clients so Enterprises disable it via Group Policy. well I've seen most enterprise networks with no IPv6 support. (mostly admins thing that this beast is hard to work with) Also Kubernetes has limited IPv6 support (mostly on the documentation site) (of course it's easier to support a IPv6 only cluster, because heck you wouldn't really need BGP or some wierd overlay n…

telekom has some IPv6 routing issues every now and then that I did not encounter with other ISPs. I believe it is because they peer more selectively at de-cix instead of having open peering.

Re: So Long Last /8 and Thanks For All the Allocations

#47

Post by rasz »

EE84M3i wrote: post #38

IPv4 address utilization is incredibly low. For example, consider 44.0.0.0/8 - it's sitting around almost entirely unallocated. UCSD Caida uses it for their network telescope (pretending to use it for amateur radio) and won't give it back. Just look at how dark it is: https://benjojo.co.uk/internet-2018.png (from https://blog.benjojo.co.uk/post/scan-ping-the-internet-hilbe... ) Discussion on r/amateurradio - https://…

Not to mention DOD, its not like they will one day plug all those intranet computers to the internet.

Re: So Long Last /8 and Thanks For All the Allocations

#48

Post by sp332 »

d3ckard wrote: post #27

Is it time to just admit IPv6 is a failure and move on to new standard? Adoption is very slow though economical needs are already here. Instead of complaining about users maybe we should do something so they actually want to switch?

I think you'd be surprised if you looked up actual adoption numbers. http://www.worldipv6launch.org/measurements/

Re: So Long Last /8 and Thanks For All the Allocations

#50

Post by Beltiras »

EE84M3i wrote: post #38

IPv4 address utilization is incredibly low. For example, consider 44.0.0.0/8 - it's sitting around almost entirely unallocated. UCSD Caida uses it for their network telescope (pretending to use it for amateur radio) and won't give it back. Just look at how dark it is: https://benjojo.co.uk/internet-2018.png (from https://blog.benjojo.co.uk/post/scan-ping-the-internet-hilbe... ) Discussion on r/amateurradio - https://…

Apple has an /8 but Microsoft does not? How did that happen?
Post reply on HN