hey folks:

did you know that you can make the experience for users on mobile data networks faster by making sure your instance is accessible over IPv6?

This is because in a lot of mobile data networks nowadays, IPv4 connectivity is provided via CGN device (Carrier Grade NAT) and IPv6 is provided natively which means that IPv4 is going to be slower.

If your instance's web front end doesn't have IPv6 connectivity, what's the blocker?


a lot of y'all are on server providers that provide IPv6 connectivity and it can be as simple as adding a AAAA record in DNS and making sure your front end web server is listening on IPv6 (which it probably is doing already)

If your provider provides IPv6 connectivity and you need help configuring it, hit me up

I'll be glad to help

If you are using masto.host, that's something you need to take up with the folks that run masto.host

If you are using Linode, IPv6 connectivity is configured on your server by default

Hetzner Cloud nodes also come with IPv6 connectivity enabled by default

If you are using DigitalOcean, make sure IPv6 is enabled on your server first


same with Vultr, you need to enable it if you don't already have it enabled

if you are using some sort of load balanced setup with floating IPs that doesn't support IPv6...well you are on your own on that one

*grumbles about DigitalOcean and Vultr not enabling IPv6 by default*

@packetcat sobs in “needs a VPN to host animal crossing despite the ISP’s root servers supporting IPv6”

@packetcat ARIN has been giving the "IPv6: No Longer Optional" presentation since 2010 (possibly longer). Makes me wonder how these companies missed the memo.

@packetcat Packet.net also has ipv6 setup by default for their boxes

OVH has some seriously goofy ipv6

Scaleway's can change if you ever shutdown a host through their UI (i never quite sorted how to make an ipv6 stable over there)

EC2 doesn't have it by default

@kemonine indeed, thankfully most people on the fediverse seem to have moved away from using Scaleway for hosting their instances because of...unreliability issues

(and I heard they recently increased their prices, which is hilarious to me)

and OVH's IPv6 setup is...ugh..frustrating but it does work after its configured and the prefix is stable to the server

enabling IPv6 on EC2, I'm gonna charge people my hourly rate to get that sorted lol

@packetcat LOL

I moved off Scaleway once they pulled their arm server offerings

That was a death sentence for a TON of my self-hosting and an OSS project I ran for a couple years.

And the ec2 arm offerings are, uh, ec2 priced?

One trick I've found that helps with ipv6 support but isn't the best : CloudFlare proxies for web services. If you've got a goofy provider like Scaleway or OVH or EC2 and don't want to fight with their brands of stupid CloudFlare can easily kick the can down the road

@packetcat The issue with madto host is OVH's capabilities and how the load balancing (or failover) has been implemented.Last I asked about it, if we were to use ipv6, hugo would need to tell us every time we need to update our dns records.

@ishara ahh I figured it was a issue with the LB system


@packetcat My suspicion is that the root cause is around floating IP addresses. My usual strategy when doing cloud hosting is to reserve a floating IP, put that floating IP in my DNS, and pin that floating IP each time I need to change my underlying VM. I've not found a single provider that supports floating IPv6 addresses, including Openstack.

Sign in to participate in the conversation
Ten Forward

The social network of the future: No ads, no corporate surveillance, ethical design, and decentralization! Own your data with Mastodon!