It’s criminal. #DigitalOcean makes each droplet spun up #IPv4 only by default. You have to specifically make sure the #IPv6 checkbox is selected, or you’re stuck with v4 without a bunch of annoying steps to get v6 working later. Infuriating.

I really don’t understand why v6 isn’t on by default. Terrible. End rant.

#rosenheim #ipv6

#eduroam by komro

(in der City)

Hello to our friends in Singapore !

We’re happy to announce that we just opened up a new POP in Sin1, SG to come even closer to you! What does it mean?! IP-Space in Singapore including GEO objects & lower latencies in your area

Thanks to Route64 and @gyptazy !

#Homelab/#Networking question: I just realise that 'setting a static #IPv6 address' on a (#Linux) server is not as simple as it'd be with #IPv4 - one of the reasons being, realising, that the address prefix changes when my router restarts (i.e. due to any configuration changes).

When that network address prefix changes, obviously, any 'static' IPv6 address I'd like to set for my server would just be rendered invalid, since the network address portion/prefix is no longer applicable.

On my #TP-Link router, under IPv6 LAN settings, I saw an option to configure the Address Prefix - however, this field is currently prefilled with the network address prefix my servers/client devices are currently using/assigned to, and it is immutable (not configurable). To make it configurable, I could set a different setting on the same page called Prefix Delegation to Disable instead of its default, Enable.

My idea is to disable it, set an address prefix, and save/apply it - my expectation is, after the router restarts, all IPv6 addresses on my network will have that prefix, and it'll never change unless I explicitly do so (again, on the router). Is my idea right? or am I getting it tooootally wrong (which is possible bcos IPv6 is something else)?

Finland tends to be a bit different. This includes @UpCloud. If you slap #OpenBSD on a VM: IPv4 and IPv6 are two different NICs. Works great if you are aware of this - if they ever get a wiki I pinky swear I'll write it down on some relevant page.

Adding a poll because it is all the rage in Helsinki.

Oh please!!!!

I wanted to add a smoke-test/integration test for my Ansible FreeBSD connection plugin against a test-server and the GitHub Actions don't support outgoing IPv6 in 2025?! WTF!

Tempted to move my remaining stuff off of GitHub and migrate my CI/CD to @Codeberg Woodpecker

I refuse to use IPv4 for that, just because of GitHub.

@gyptazy Auch mal ein Setup, was ich bisher noch nie in der Praxis getestet habe :-) Aber funktioniert einwandfrei.

Host: IPv6-only
Jails: IPv6-only (via ULA Adressen und NAT66)

Das ganze als VNet mit ipv6_forward und NAT über pf.

Für sowas liebe ich FreeBSD ja einfach

I really want to create my own simple router with FreeBSD for NIDS use. However, that's a future wish that I want to do later. My current target is to create a simulation with multiple jails that act as clients and routers. With IPv6 addressing, I want to connect them and pass the traffic between different networks. My current problem is how to do packet forwarding(?) like a normal router does. But I want to do it FreeBSD style. Any hints or help are appreciated

My current knowledge: I am familiar with basic jail, the epair mechanism, and a small bit of pf configurations.

Tried to configure a OpenDNS filtering service on my Fritzbox modem with an ISP which offers IPv6. Don't even bother.

OpenDNS won't let you register a IPv6 subnet. The modem prefers IPv6 DNS servers (because there's often no CGNAT). So the Fritzbox selects the ISP's IPv6 DNS server over the IPv4 OpenDNS server, meaning no filtering occurs.

OpenDNS does allow access to the resolver via IPv6, but this does not work if you have an account with filtering preferences.

To be clear, this issue is with OpenDNS. Not Fritzbox. Not the IPv6 protocol.

Thanks to @s3phy again for helping me understand another area where IPv6 is broken in Linux desktop networking configuration tools: connecting to a SSH server to create a SOCKS proxy using the NetworkManager SSH plugin. That thing only checks if the gateway address is a valid IPv4 address

I reported the issue here: https://github.com/danfruehauf/NetworkManager-ssh/issues/130

Did you notice? The registration was temporary open today and we welcome all new users!

While we still have a plenty of free resources, we might switch from an open registration model to a recommendation / mentor model where already present users can invite new users.

This is not yet fix but a possibility to avoid misusage and abuse where our primary goal is still to provide resources for people interested into BSD based systems. Maybe also closer integrations with BSD communities like the BSD Cafe (@stefano) could be an approach.

#freevps #free #education #ipv6 #hosting #bhyve #proxmox #freebsd #netbsd #openbsd #runbsd #boxybsd @gyptazy

#IPv6 bizarro world, courtesy of whmyip [dot] com. Just me or IPv6=IPv4 for everyone.

Made a high level, basic "get your #IPv6 address plan started" app and posted to github. It's somewhat complimentary to ipv6utils (also on GitHub and Mac homebrew). It is pretty basic, more of a bootstrap than anything - because the first step is usually the hardest. https://github.com/buraglio/ipv6planner

So mein Mastodon Server ist nun auch endlich über #IPv6 erreichbar... Dauert alles etwas, wenn man sich etwas dusselig anstellt...