snac.void.my is a Fediverse instance that uses the ActivityPub protocol. In other words, users at this host can communicate with people that use software like Mastodon, Pleroma, Friendica, etc. all around the world.
This server runs the snac software and there is no automatic sign-up process.
We've created a large number of transition technologies for migrating from IPv4 to #IPv6 , but we still have to migrate the people. To that end I have a small proposal to help folk get used to the new way of doing things:
IPv4 addresses are 32-bit numbers, the most common representation being the dotted quad. There is, however, nothing stopping you from expressing that number in hexidecimal as in IPv6. So, if I want to ping my router's IPv4 address, this is a valid command: ping 0xac1f0301
Once you get used to seeing all your addresses in hex, expanding your mind out to more digits becomes a much easier exercise.
Still using 1.1.1.1 or 8.8.8.8 for #DNS?
Switch to more privacy friendly #EU based DNS Servers today.
#IPv4 185.150.99.255 / 5.1.66.255
#IPv6 2001:678:e68:f000:: / 2001:678:ed0:f000::
#DoH: https://doh.ffmuc.net/dns-query
#DoT/#DoQ: dot.ffmuc.net / doq.ffmuc.net Port 853
Donations to keep the service running: https://spende.ffmuc.net
TIL: Wenn du #Wireguard nen #IPv6 only Tunnel bereitstellen lassen möchtest, scheinst du, zumindest auf #Android15, trotzdem ne #IPv4 Adresse konfigurieren zu müssen weil sonst Android keinen IPv4 Traffic mehr raus lässt (auch wenn nur ::/0 in den Tunnel gerouted werden soll).
@Golemde ich hatte eurem Consent Team vor 4 Wochen schon geschrieben. Aber leider keine Rückmeldung erhalten.
golem.de ist per #IPv6 nur sehr eingeschränkt nutzbar, da das Consent Management kein #IPv6 kann.
Das durch das AWS Hosting auch noch richtig Geld kostet, es nur per IPv4 zu betreiben.
Würdet Ihr das Bitte fixen?
...fiktiven Behörde – dem „Bundesamt für Muster und Beispiele“ (kurz BAMBI)...
Ein Bambi 🤗
https://de.linkedin.com/posts/bdbos_sccon25-ipv6-protokollstandard-activity-7387353105413095424-Ncb1
finished landing the fix for this FreeBSD bug: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=289198
this is quite fun. in one sense, it's a fairly serious bug: inet_net_pton() is completely broken for IPv6; it simply doesn't work and returns garbage output. but this bug has been present since 2006, when this function was first imported into libc, and no one noticed until August of this year when the PR was filed.
what i conclude this from is that literally no one uses these functions, and they should probably have never been imported in the first place. but, well, we can't remove them without breaking ABI compatibility, so now they're here forever, like an obnoxious uninvited party guest.
I also added some small rules for #Backblaze to #Delegacy #RPZ: https://codeberg.org/IPv6-Monostack/delegacy-rpz/pulls/69
@miyuru Do you want to add them to IPv6-dns-server as well?
The first such system I encountered was https://tgif.network/ , a #hamradio DMR network. Users would log in to the website and their hotspots would be shown based on whether they were connected from the same IPv4 address. They've moved away from this mechanism as all hotspots are now credential authenticated as well. Unfortunately, even with this change, the underlying software does not have any #IPv6 support.
The most recent encounter is https://adsb.fi/
> These endpoints are accessible for people contributing to adsb.fi by hosting a receiver. Your feeder IP address is automatically given access.
src: https://github.com/adsbfi/opendata/blob/main/README.md
adsb.fi is fronted by Cloudflare, so they could enable #IPv6 relatively easily, but they would have to revamp their feeder authentication.
I'm still running into websites that grant access based on your IPv4 address, presuming some other authenticated device coming from the same network. This image clearly has not clicked with the admins of these systems yet.
(image source https://chrisgrundemann.com/index.php/2011/nat444-cgn-lsn-breaks/ )
ChatGPT was released a mere two years ago and people will not shut up about it.
But I'm the weird one because I won't stop talking about #IPv6.
with IPv6 deployment reaching 80%+ in many places, we can probably remove IPv4 support from FreeBSD 17.0.
i'm sure this won't cause any issues for users because people constantly say that FreeBSD users are super evolved and up-to-date with the latest technologies, unlike those awful Linux users.
I didn't have the script under version control, but by virtue of my having migrated it across machines I had enough breadcrumbs to re-create some of the version history. If you'd like to see what I've been working on: https://git.home.nivex.net/nivex/jool-clat
I got down a rabbit hole this evening of tweaking my Jool CLAT script. More parameter checks, support for the internal bridge I use for my VMs, and a proper wait loop for SLAAC to finish when determining the CLAT v6 address. It leverages jq to parse iproute2 JSON output to make things easier.