#IPv6only
Network Load Balancer now supports IPv6
Network Load Balancers now support IPv6. You can create an IPv6 Network Load Balancer in the Exoscale Portal or with the Exoscale CLI. An IPv6 Network Load Balancer gets a public IPv6 address and distributes TCP and UDP traffic across the instances in your Instance Pools, just like an IPv4 Network Load Balancer. Why use it Lower cost: Elastic IPv6 addresses are free, so you only pay the load balancer fee. An IPv6 Network Load Balancer costs EUR/CHF/USD 0.02083 per hour, about 40% less than the IPv4 version. Check the pricing page for details. Reach IPv6 users directly: Serve users on IPv6-only and IPv6-first networks, natively and without translation layers. Go fully IPv6: Your instances already get a free public IPv6 address. Now the load balancer in front of them can be IPv6 too. Nothing to give up: Same health checks, load balancing strategies and 200 service limit as an IPv4 Network Load Balancer. Before you start The target Instance Pool must have IPv6 enabled (dual-stack). Instance Pools are IPv4 only by default, so set public IP assignment to dual-stack. Instances without an IPv6 address won’t receive traffic.
changelog.exoscale.com
October 8, 2026 at 10:40 AM
https://test-ipv6.com/index.html.en_US

This should be always a 10/10.
If you haven't that, go bother your ISP, your IT guys, whoever needs a little slap in the back of the head.

And yes. Mobile providers deserve multiple pokes, preferably all in the same spot so they notice.

#ipv6 #ipv6only […]
Original post on hachyderm.io
hachyderm.io
August 18, 2026 at 6:27 PM
Still tying BGP Router IDs to IPv4?

That model is outdated.

In IPv6-native architectures, it’s time for logic-driven, structured IDs.

We break down how at Swer Networks:
www.swernetworks.com/blog/bgp-rou...

#IPv6 #BGP #IPv6Only #NetworkArchitecture #NetworkEngineering #NetEng #NetDesign
BGP Router ID Structuring in IPv6 Native Networks – Swer Networks
How to design and structure BGP Router IDs in IPv6-native networks.
www.swernetworks.com
June 4, 2026 at 7:15 PM
A few of us want to promote use of pref64 for IPv6-only. We wrote a draft to help. Eyeballs and input from practitioners would be useful . Let’s exercise this new momentum on non-x-sites.

https://datatracker.ietf.org/doc/html/draft-buraglio-deprecate7050

#ipv6 #ipv6only
November 20, 2024 at 4:37 PM
Yep! Not only do I have #ipv6only single stack hosts/systems, I have #ipv6 only single stacked entire VLANs.
November 25, 2024 at 10:14 PM
#cable4 hat #ipv4 anscheinend noch nicht eingerichtet. Bis aufs weitere hier also (unfreiwillig) #ipv6only!
#ipv6
June 29, 2026 at 6:43 AM
Multinode k3s with #Cilium #IPv6only in native routing mode. I need to put the configs up on my blog or somewhere.
February 23, 2025 at 6:28 AM
On dirait qu'il y a une panne chez Free Mobile, l'IPv6 fonctionne mais pas l'IPv4.
C'est ça l'Internet du futur ? Y'a plein de sites qui ne marchent pas 😅
#ipv6only
July 8, 2025 at 7:01 AM
First time setting up #rook and #ceph. First challenge: figure out why my OSDs aren't talking.

As I should have suspected, it was a matter of setting `ipFamily: IPv6` in my #ipv6only #kubernetes cluster. Heh
March 4, 2025 at 5:28 AM
@doachs I keep a small K8s cluster with an #ipv6only flat network (ie non overlay), with #nat64 elsewhere to translate legacy ingress traffic. It's supremely beneficial for my sanity to debug containers using only one IP protocol, without NAT or other distortions getting in my way.
November 26, 2024 at 9:28 PM
Es gibt sie noch die stillen Helden! Neuer TV von #Hisense - angeschlossen und der zieht sich einfach direkt ne IPv6-Addresse die auch im IPv6-only-Betrieb funktioniert!!!! Es gibt Hoffnung für den Planeten 😂👍🏻 #IPv4IstTot #IPv6Only #SmartTV #TheFutureIsNow
March 3, 2025 at 11:12 AM