#ripe90 #ipv6 #ipv6only

https://mailman.ripe.net/archives/list/ipv6-wg@ripe.net/thread/KVHVWALNG2YA5CN7ULSVXOOZVHQML5WG/

Nice! @tailscale finally updated their infrastructure to support IPv6-only OIDC endpoints (after I complained)

#WhatsMissing: A tool to check if #TorBridges are still available/online/reachable that one can use either #standalone (with #TorBrowser and/or #Tor Expert Bundle) or on @tails_live / @tails / #Tails.

• Cuz I do run into issues and kinda want to sort #Bridges by availability so I don't waste time on a #TorBridge that is down and also thin-out the list of bridges that ain't online anymore.

Whilst I do acknowledge that @torproject do disrecommend having a huge list of Tor Bridges on hand, I do regularly need them for contacts who are behind a #GreatFirewall and can't #SSH-Tunnel out of it.

• Sadly #BridgeDB doesn't offer good #filtering options so one can't just query types effectively like "I need #webtunnel on #IPv4" or "I can only use Ports 80 & 443 on #IPv6" which may work.

Espechally being able to filter for #IPv4only and not just #IPv6only is something I miss, alongside the filter for #PluggableTransports type as @guardianproject #Orbot seems to only handle #obfs4 and not webtunnel or #meek at all...

• I'm pretty certain that merely pinging a bridge at it's port isn't working as a shure-fire way to check for it's availability.

I just set up a backup Internet connection on a customer's firewall, and since their applications require IPv4 while the connection is #IPv6only, I set up a CLAT on the backup router since the ISP does 464XLAT.

The only drawback is that the usable MTU for IPv4 has been reduced by 40 bytes, but for a backup link that only has an #IPv6 prefix, I think that's a fair tradeoff.

Are you a GitHub user, or wanting to be a GitHub user, but have issues because of IPv6? Upvote and join the discussion.

Feature Request: Provide a centralized resource and GitHub Public Roadmap tracking of IPv6-support for GitHub Services

https://github.com/orgs/community/discussions/151477

Dear followers,

Please:
Test devices and services in your area for #ipv6only (with DNS64 or without) and write to the manufacturers/operators if it doesn't work!

Sometimes you're successful, often not.

But the more people do it, the higher the chances of success!

Liebe Follower,

eine kleine Bitte:
Tested in eurer Umgebung Geräte und Services auf #ipv6only (mit DNS64 oder auch ohne) und schreibt die Hersteller/Betreiber an, wenn es nicht geht!

Manchmal hat man Erfolg dabei, oft auch nicht.
Aber je mehr es tun, desto höher sind die Erfolgschancen!

#CLAT support on Linux is making progress thanks to @mary

https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/merge_requests/2107

@mbpaz I mean, we don't have to do classful subnetting anymore, so a /22 is an option. Plus, it's still a good practice to have multiple, smaller subnets than one big subnet, if all nodes don't have an actual need to reach other nodes w/o routing.

But this advice also applies to #IPv6, so might as well go all-in and relegate old equipment to stay in the Legacy IP /24 network, and add all the new stuff to a new dual-stack or #IPv6only network.

If you're into the #IPv6 and #ipv6only thing, be sure to check out https://conferences.computer.org/sc-wpub/pdfs/SC-W2024-6oZmigAQfgJ1GhPL0yE3pS/555400a785/555400a785.pdf, we did some pretty sweet stuff at #SC24 using RFC8925 and DNS trickery :)

Completely forgot to put something here earlier the year, my bad!