Live data from Hacker News

New patches allow building Linux IPv6-only

phoronix.com

41–50 of 198 posts

Re: New patches allow building Linux IPv6-only

#41
post #11

Earlier quoted context omitted.

Please no. I used to have a Dutch ISP a few months ago that did not support IPv6 yet. (Odido. Same ISP that leaked my data in a big hack.)

Odido is the cheapest ISP for a reason. They refuse to implement anything that isn't strictly required. Perhaps implementing an Odido tax might actually make Odido care enough to throw the switch on IPv6. They bought 2a02:4240::/32, they just refuse to make use of it.

they do use it in their speedtest server.

  curl -v https://speedtest.ams.t-mobile.nl.prod.hosts.ooklaserver.net:8080
  ...
  * Connected to speedtest.ams.t-mobile.nl.prod.hosts.ooklaserver.net (2a02:4240::e) port 8080

Re: New patches allow building Linux IPv6-only

#42
This may be a “joke”, but it’s disturbing to see people clamoring to deny others their freedom in a FOSS context.

Want to use IPv6? Fine. But don’t try to remove v4 support from people who have built stable networks around it.

You won’t be able to force the world to switch to IPv6 with tricks like this, any more than you can force old industrial machines to stop using ancient 486es as controllers. There is a lot of old equipment in the world.

IPv6 was built to work alongside v4, and there is no reason to change that.

Re: New patches allow building Linux IPv6-only

#43
post #11

As it should. Date notwithstanding, I would actually enjoy if there was a manually induced latency penalty for "legacy IP" that needs to be manually turned off on Linux. I know some people don't care at all, but the internet was made to be addressable. IPv6 is the only shot we have to go back to that.

Please no. I used to have a Dutch ISP a few months ago that did not support IPv6 yet. (Odido. Same ISP that leaked my data in a big hack.)

Canadian ISPs are also extremely far behind on IPv6. Bell is the largest ISPs in the country and they still don't have IPv6. I'm with one of their wholly owned subsidiaries (EBOX) which offers static /56 allocations, but good luck trying to find anyone in tech support who understands WTF you're talking about.

Re: New patches allow building Linux IPv6-only

#44
post #27
post #5

great, now can we convince the rest of the internet to start adding AAAA records and ipv6 endpoints for things. Github is still a nightmare to use DNS64 and NAT64 to access those from IPv6 only machines. Or all the Container based stuff that still falls flat with ipv6 only modes. Docker still shits the bed if you dont give it ipv4 unless you do a lot of manual overrides to things. A bunch of Envoy based gateway proxi…

I honestly think GitHub and AWS are the two biggest blockers to IPv6 left. Sure your public web servers might need IPv4 for a long while yet, but all these backend microservices and CI builds etc could all be v6 only, except they need to pull stuff from GitHub or certain AWS services.

It's particularly aggravating with AWS, since they charge for IPv4 addresses yet many of their services aren't IPv6 capable.

Re: New patches allow building Linux IPv6-only

#45

This may be a “joke”, but it’s disturbing to see people clamoring to deny others their freedom in a FOSS context. Want to use IPv6? Fine. But don’t try to remove v4 support from people who have built stable networks around it. You won’t be able to force the world to switch to IPv6 with tricks like this, any more than you can force old industrial machines to stop using ancient 486es as controllers. There is a lot of o…

> it’s disturbing to see people clamoring to deny others their freedom in a FOSS context

How does "allow building Linux to be IPv6-only" somehow "deny others their freedom" exactly? I'm willing to wager most distributions will still be dual v4+v6, but if they aren't, isn't that something for you to bring up with your distribution rather than that the kernel just allows something?

Re: New patches allow building Linux IPv6-only

#46
post #11

Earlier quoted context omitted.

Please no. I used to have a Dutch ISP a few months ago that did not support IPv6 yet. (Odido. Same ISP that leaked my data in a big hack.)

Odido is the cheapest ISP for a reason. They refuse to implement anything that isn't strictly required. Perhaps implementing an Odido tax might actually make Odido care enough to throw the switch on IPv6. They bought 2a02:4240::/32, they just refuse to make use of it.

> They refuse to implement anything strictly required

This describes a lot of businesses ngl.

Bell in Canada is one huge head scratcher. They are one of the largest ISPs here and I can even buy 8 gig internet to my house if I want but they don't support IPv6.

Re: New patches allow building Linux IPv6-only

#47
post #37

Earlier quoted context omitted.

- I don't want my interfaces to have multiple IP addresses - I don't want my devices to have public, discoverable IPs - I like NAT and it works fine - I don't want to use dynamic DNS just so I have set up a single home server without my ISP rotating my /64 for no reason (and no SLAAC is not an answer because I don't want multiple addresses per interface) - I don't need an entire /48 for my home network IPv6 won't hel…

Why don't you want every device to have a public IP? There seems to be a perception that this is somehow insecure, but the default configuration of any router is to firewall everything. And one small bonus of the huge size of a /64 is that port scanning is not feasible, unlike in the old days when you could trivially scan a whole IPv4 /24 of a company that forgot to configure their firewall. NAT may work fine for you…

I don’t want some of my devices to be publicly addressable at all, even if I mess up something at the firewall while updating the rules. NAT provides this by default.

I don’t want a static address either (although static addresses should be freely available to those who want them). Having a rotating IP provides a small privacy benefit. People who have upset other people during an online gaming session will understand; revenge DDoS is not unheard of in the gaming world.

Re: New patches allow building Linux IPv6-only

#48
post #24

Earlier quoted context omitted.

> Having a public address doesn't worry me. At home I have a firewall at the edge. It is set to block everything incoming. Concern is privacy, not security. Publicly addressable machine is a bit worse for security (IoT anyone?), but it is a lot worse for privacy.

You already have a public IP address the only difference is if you have a rotating IP address which is orthogonal to IPv6. The only difference is most ISPs rotate IPv4 but not IPv6. Heck IPv6 allows more rotation of IPs since it has larger address spaces.

IPv6 can "leak" MAC addresses of connected devices "behind the firewall" if you don't have the privacy extensions / random addresses in use.

There are a number of footguns for privacy with IPv6 that you need to know enough to avoid.

Re: New patches allow building Linux IPv6-only

#49

As it should. Date notwithstanding, I would actually enjoy if there was a manually induced latency penalty for "legacy IP" that needs to be manually turned off on Linux. I know some people don't care at all, but the internet was made to be addressable. IPv6 is the only shot we have to go back to that.

As sad as it makes me to admit, I don't think IPv6 is ever going to happen without government intervention. Adoption is flat at under 50% over the past year. IPv6 doesn't benefit big tech. SNI routing and NAT work pretty well for centralized platforms. AWS will gladly rent us IPv4 addresses until the end of time.

Re: New patches allow building Linux IPv6-only

#50

This may be a “joke”, but it’s disturbing to see people clamoring to deny others their freedom in a FOSS context. Want to use IPv6? Fine. But don’t try to remove v4 support from people who have built stable networks around it. You won’t be able to force the world to switch to IPv6 with tricks like this, any more than you can force old industrial machines to stop using ancient 486es as controllers. There is a lot of o…

*removed comment. I didn't know this was an April fools joke. sorry for my lack of a clue....
Post reply on HN