Thomas Schäfer
goetzIt seems to me, they need more testers.
still without the recent version of tayga
@nSonic kannst Du genaueres sagen? Welche Dienste? Nutze #Azure / MS in einem #IPv6mostly setup und sehe keine Probs.
#Android hat IPv6only addressing.
#Android hat IPv6only addressing.
@tschaefer
The best statement of every Jen presentation:
"You are not operating IPv6 until you turn IPv4 off"
Anderson Silva#NetworkManager will now include #CLAT capabilities: https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/merge_requests/2107 is now merged, functionality will be available on a future release.
Thanks to everyone involved 🙂
RE: https://ipv6.social/@tschaefer/115793614357898922
I have seen #39c3 provides #ipv6 #ipv6mostly #ipv6only
Please try it with windows 11 preview version, if you can!
These instructions should help.
"On the wireless network we are experimenting with ipv6-mostly, this means that if your wireless client supports it it will only have a IPv6 Address and access to IPv4 hosts will automaticly be routed trough our NAT64 gateways."
https://events.ccc.de/congress/2025/infos/network.html
#ipv6mostly #39c3 #ipv6 #ipv6only
👍👍👍
#464XLAT and #NAT64 on #Mikrotik routers.
https://forum.mikrotik.com/t/nat64-and-464xlat-on-ros-how-to/267046
Please have this out of the box available?
@[email protected] @mikrotik
NAT64 and 464XLAT on ROS how-to
Here is a working NAT64 solution for homelab folks wanting to experiment with IPv6-only, or their provider only offers IPv6 with IPv4 over CG-NAT. Full 464XLAT operation is achieved when the client devices include a CLAT, such as Apple devices. This solution does require the ISP provide an IPv4 address, so it won’t work if the provider is IPv6-only and doesn’t provide NAT64 in their network, Ive read that some do. My network is a fairly typical dual-stack setup where my ISP offers CG-NATed IPv4...
Das WLAN des Hotels/der Konferenz kann's nicht. ☹️
Wer #IPv6mostly hier ausprobieren möchte, einfach in meine Nähe stellen 🤗
@apalrd Have you been facing issues with #WiFiCalling while running #IPv6mostly in #OPNsense ?
I can't figure out exactly why it breaks in my home network, since there are no misconfigured rules nor anything related - if I disable DHCP option 108 and assign old addresses to each client, it works; when passing through #tayga #nat64, it stops entirely.
All this because the carrier's servers are stuck in the last millenium, of course they are: https://www.netify.ai/resources/mobile-gateways/country/br
