5 ms·

Would be interesting to know which applications actually have problems with v6 - the example with directly using a v4 IP is more a user error, not an applicatio

Would be interesting to know which applications actually have problems with v6 - the example with directly using a v4 IP is more a user error, not an application issue. I pretty much stopped submitting patches enabling v6 functionality to various projects back in 2005 as everything I cared about was working at that point. (Side note, I was just trying to search a few of those - but seems that period pretty much doesn't exist in search engine caches anymore. I knew the state of preserving internet history is bad, but I didn't expect it to be _that_ bad)

yetanotherloss 3y ago
There seem to be hard cuts in search returns at 5 and 10 years, it's been really difficult to find anything from before 2012 without incredibly specific searches. Lots and lots of link rot too so it's hard to say how much of that is google/bing/etc.
Faaak 3y ago
The folding@home client, for example, is written in C with a "does everything" library (called cbang if I recall correctly). The library only uses sockets with AF_INET and thus it doesn't work even with AAAA records..
nova77hn 3y ago
WSL2 famously doesn’t support ipv6 (because of NAT) which is mightily annoying.
- ajsnigrutin 3y ago
  Why is NAT a problem here? IPv6 supports full NAT (no matter that the basic idea of ipv6 is "no nat").
- uxp8u61q 3y ago
  The prerelease finally supports ipv6: https://github.com/microsoft/WSL/releases https://github.com/microsoft/WSL/releases
josephcsible 3y ago
Docker's support for IPv6 is really poor. Basics are still gated behind the "experimental" flag, and there are bugs that have been open for years preventing very common configurations from working.
- mmis1000 3y ago
  It don't even support dynamically assigned ipv6 address. And ipv6 prefix need to be hardcoded into config. And even worse , ipv6 address(not suffix) is bounded directly to the container at creation time. If your ipv6 prefix changed for whatever reason.(laptop is a thing since 20 years ago, you know) Best you can do is scrap the container and make a new one. I would say keep it experimental at current status is a good decision. It's simply not usable currently.
dementik 3y ago
Colima on mac is struggling with ipv6. Not sure what component is responsible, but I have been unable to connect ipv6 hosts from colima containers.

yetanotherloss 3y ago

There seem to be hard cuts in search returns at 5 and 10 years, it's been really difficult to find anything from before 2012 without incredibly specific searches. Lots and lots of link rot too so it's hard to say how much of that is google/bing/etc.

Faaak 3y ago

The folding@home client, for example, is written in C with a "does everything" library (called cbang if I recall correctly). The library only uses sockets with AF_INET and thus it doesn't work even with AAAA records..

nova77hn 3y ago

WSL2 famously doesn’t support ipv6 (because of NAT) which is mightily annoying.

ajsnigrutin 3y ago
Why is NAT a problem here? IPv6 supports full NAT (no matter that the basic idea of ipv6 is "no nat").
uxp8u61q 3y ago
The prerelease finally supports ipv6: https://github.com/microsoft/WSL/releases https://github.com/microsoft/WSL/releases

josephcsible 3y ago

Docker's support for IPv6 is really poor. Basics are still gated behind the "experimental" flag, and there are bugs that have been open for years preventing very common configurations from working.

mmis1000 3y ago
It don't even support dynamically assigned ipv6 address. And ipv6 prefix need to be hardcoded into config. And even worse , ipv6 address(not suffix) is bounded directly to the container at creation time. If your ipv6 prefix changed for whatever reason.(laptop is a thing since 20 years ago, you know) Best you can do is scrap the container and make a new one. I would say keep it experimental at current status is a good decision. It's simply not usable currently.

dementik 3y ago

Colima on mac is struggling with ipv6. Not sure what component is responsible, but I have been unable to connect ipv6 hosts from colima containers.