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

40% of Google users now connect via IPv6

google.com

Post reply on HN
Print view View original

181–190 of 353 posts

Re: 40% of Google users now connect via IPv6

#181

Post by sneak »

p1mrx wrote: post #49
sneak wrote: post #44

Earlier quoted context omitted.

Get a raspberry pi, set up two vlans, run wireguard, and send 100% of your uplink traffic to a remote vpn endpoint. This gets you off their IP, and also has the added benefit of not letting them analyze your traffic.

Having a non-residential IP address is likely to get you blocked from services like Netflix. It would be nice if there were some way to decouple connectivity from addressing, without becoming a second-class citizen of the internet.

A good way is to refuse to give money to such services, which being unable to access them, dovetails nicely.

Incidentally this also makes torrenting safe, and everything on Netflix can be downloaded via BitTorrent.

Re: 40% of Google users now connect via IPv6

#182

Post by oxplot »

doublerabbit wrote: post #175
oxplot wrote: post #168

Earlier quoted context omitted.

IPv6 amounts to a firmware update which the current hardware is and any future hardware will be capable of. The major hurdle in scaling Starlink is fast and cheap deployment of 1000s of satellite hardware. At the moment, the sole focus of SpaceX in relation to Starlink is to get their V2 satellites to orbit in order to keep up with bandwidth demands. V2 requires the Starship system which is yet to make it to orbit. T…

> no you don't need it right now. Yes we do. IPv4 exhaustion is a thing.

That's what CGNAT provides a temporary solution for.

Re: 40% of Google users now connect via IPv6

#183

Post by wongarsu »

TedDoesntTalk wrote: post #167
kazen44 wrote: post #143

Earlier quoted context omitted.

because maintaining state for GCNAT tables is far more complex then just forwarding packets. routers doing NAT are thus more expensive then those just doing simple forwarding. Also, in some countries ISP's need to map the use of a specific ip address to a specific subscriber for law enforcment purposes. GCNAT is no exception to this and creates a large amount of overhead because the public IPV4 prefix space is shared…

> because maintaining state for GCNAT tables is far more complex then just forwarding packets. But it’s a solved problem with mature solutions, decades old. Is it really financially expensive?

The same could be said about IPv6. I think the point is that IPv6 scales better with traffic increases, to the point where switching from CGNAT to IPv6 becomes financially attractive.

Re: 40% of Google users now connect via IPv6

#184

Post by 0x006A »

Its mostly impossible to run servers only with IPv6 since for some reason Canonical/Ubuntu decided to require IPv4 for snap, after years of not having any issues with IPv6 only deb mirrors.

Go is also basically bound to IPv4 since it depends on github to pull packages

its time to make hall of shame for software that does not allow developers to build IPv6 only going forward.

Re: 40% of Google users now connect via IPv6

#185

Post by oxplot »

tgflynn wrote: post #180
oxplot wrote: post #168

Earlier quoted context omitted.

IPv6 amounts to a firmware update which the current hardware is and any future hardware will be capable of. The major hurdle in scaling Starlink is fast and cheap deployment of 1000s of satellite hardware. At the moment, the sole focus of SpaceX in relation to Starlink is to get their V2 satellites to orbit in order to keep up with bandwidth demands. V2 requires the Starship system which is yet to make it to orbit. T…

I doubt there's much overlap between the people working on IPv6 and those working on getting Starship off the ground.

It's not a function of overlap. If they've determined IPv6 isn't a priority and instead a risk, then it makes no sense to dedicate resources to it right now. It's not as if everything else about the firmware/software is wrapped up and the software team is sitting on their hands doing nothing.

Re: 40% of Google users now connect via IPv6

#186

Post by wongarsu »

spookthesunset wrote: post #169
NelsonMinar wrote: post #35

I sure wish Starlink supported IPv6. They're a brand new ISP planning for millions of customers and decided from the start they couldn't get enough IPv4 addresses for everyone. Fair enough! But we're stuck with Carrier Grade NAT and it is a drag. On Starlink it's impossible to host a server socket directly, which makes any peer to peer networking a PITA. Geocoding IP addresses doesn't work so I have to bend over back…

Would them using CGNAT suggest they are tunneling your traffic as it goes between your station and the ground station? I wonder if they’ll go IPv6 once they are doing inter-satellite routing?

They could do CGNAT at each ground station, with IPs dedicated to each ground station

Re: 40% of Google users now connect via IPv6

#187

Post by ipython »

oxplot wrote: post #168
randmeerkat wrote: post #163

Earlier quoted context omitted.

> SpaceX'es focus is to scale up > Removing any unnecessary feature is a must in order to reduce risk. You can’t scale a space based planetary ISP without IPv6, this isn’t a feature, it’s a requirement.

IPv6 amounts to a firmware update which the current hardware is and any future hardware will be capable of. The major hurdle in scaling Starlink is fast and cheap deployment of 1000s of satellite hardware. At the moment, the sole focus of SpaceX in relation to Starlink is to get their V2 satellites to orbit in order to keep up with bandwidth demands. V2 requires the Starship system which is yet to make it to orbit. T…

It’s really too bad that ipv6 is only… checks notes… 26 years old now. I realize that may be an unreliable metric, so it’s roughly equivalent to 2.88 react.js lifetimes, or 3.25 vue.js lifetimes.

When the ipv6 spec was released, the latest python release did not yet support list comprehensions.

In other words, there is no reason to not support ipv6 out of the box in 2022.

Re: 40% of Google users now connect via IPv6

#188

Post by sneak »

NelsonMinar wrote: post #48
sneak wrote: post #44

Earlier quoted context omitted.

Get a raspberry pi, set up two vlans, run wireguard, and send 100% of your uplink traffic to a remote vpn endpoint. This gets you off their IP, and also has the added benefit of not letting them analyze your traffic.

And adds 20ms+ latency, another complex point of failure, and potential problems depending on the reputation of the IP address block of wherever you're hosting the endpoint. I've used VPNs to smooth over various Starlink problems since I got the service and it helps but it's not a great solution.

There is no other solution that doesn’t allow SpaceX to snoop on all your traffic, unfortunately.

Re: 40% of Google users now connect via IPv6

#190

Post by swinglock »

TedDoesntTalk wrote: post #167
kazen44 wrote: post #143

Earlier quoted context omitted.

because maintaining state for GCNAT tables is far more complex then just forwarding packets. routers doing NAT are thus more expensive then those just doing simple forwarding. Also, in some countries ISP's need to map the use of a specific ip address to a specific subscriber for law enforcment purposes. GCNAT is no exception to this and creates a large amount of overhead because the public IPV4 prefix space is shared…

> because maintaining state for GCNAT tables is far more complex then just forwarding packets. But it’s a solved problem with mature solutions, decades old. Is it really financially expensive?

What do you mean, solved problem?
Post reply on HN