OVH Object Storage S3 now support IPv6.

https://public-cloud.status-ovhcloud.com/incidents/2w0vng621k8s

No need to force since, they using same endpoints.

#OVH #IPv6 #S3 #objectstorage

Did some coding on SixSpotting over the last couple days. It's all backend changes, not the least of which is moving from Postgres to SQLite since it's such a tiny little app. Nothing should be user visible, but if I did goof something please let me know.

https://game.flyingpenguintech.org/

#ipv6

A Farewell to ARPs: IPv4 Service on IPv6-Only Networks

https://labs.ripe.net/author/remco-van-mook/a-farewell-to-arps-ipv4-service-on-ipv6-only-networks/

#IPv4 #IPv6 #ARP

A new article at the RIPE blog explains the current state of running IPv4 services over IPv6-only networks.

The three pieces are RFC 8950 (IPv6 next-hops for IPv4 prefixes), a draft about IPv6 next-hops for IPv4 routes, and a draft for solving the IPv4 gateway problem that systems running IPv4 services in these kind of networks typically have.

It’s cool to see this gateway thing in such an informed piece, I’ve been wondering about that bit for a while. You might have seen different service providers solving this in different ways, with a /32 on either a regular interface or a loopback, and a strange default route pointing to just an interface (with no destination IP), or a destination IP in a prefix that the given machine doesn’t know about.
Linux seems to support a couple of different ways to go about this (of course), and FreeBSD and OpenBSD each support a single, different solution AFAIK. I don’t believe illumos even has a way to solve this problem at the moment, but I might have that one wrong.

Anyway, do have a look at the article:
https://labs.ripe.net/author/remco-van-mook/a-farewell-to-arps-ipv4-service-on-ipv6-only-networks/

#IPv6 #IPv6mostly #fuckdualstack #networking

"A Farewell to ARPs: IPv4 Service on IPv6-Only Networks": https://labs.ripe.net/author/remco-van-mook/a-farewell-to-arps-ipv4-service-on-ipv6-only-networks/

i really like this idea. it defines 192.0.0.11 as a special value for IPv4 default gateway meaning "use the IPv6 gateway" (as in IPv4-over-IPv6 routing), for routed networks that assign /32s to each client.

it's backward compatible with existing hosts as long as the router replies to ARPs for 192.0.0.11. but if the host supports this proposed standard, no ARP is required at all.

it doesn't let you do anything you can't do today, but it makes things neater and simpler.

#ipv6

Watching the premier of the Python documentary ( https://www.youtube.com/watch?v=GfH4QL4VqJ0 ). Reminded how the Python 2 -> 3 transition has a lot of parallels to the IPv4 -> #IPv6 transition.

AWS Client VPN now supports connectivity to IPv6 resources
Posted on: Aug 26, 2025
https://aws.amazon.com/about-aws/whats-new/2025/08/aws-client-vpn-connectivity-ipv6-resources/

#aws #ipv6

One slightly weird thing I had is that inbound #ipv6 traffic on both SSH and HTTPS was returning a "connection reset by peer" for a while. It seems to be working now, but if some IPv6 folks can check https://cablespaghetti.dev loads properly over v6 for them now, it would put my mind at rest.

#aws
#ipv6
#ripe88

https://ripe88.ripe.net/wp-content/uploads/submissions/Architect-IPv6-networks-on-AWS-RIPE88-5-16-2024.pdf