Interested in an easy to use one-click for users #Wireguard setup?
We are maintaining an #IPv6 enabled and up-to-date version of #wg-access-server.
Want new features or contribute?
Go here:
https://github.com/freifunkMUC/wg-access-server
Our own VPN servers are also running this server.
What do you guys do with your left-over (public) IPv4 addresses? And no, that’s meant for real :)
github is still ipv4-only
And another #HowIPv6HelpedMeThisWeek (from another week) related to this toot, I have a BIND nameserver in my homelab with 112 views (for shenanigans reasons), and I can't expose that construct to the internet without either #IPv6, or some truly hideous port-based NAT hijinks (which, ugh, no thank you).
(And worse: I actually have two of them now. 
)
https://mspsocial.net/@jima/114354031715285418
Wie wäre es, ihr kümmert euch mal um den #IPv6|-Rollout auf social.bund.de? Ja, ihr müsstet dafür entweder Fa. T-Systems etwas bearbeiten oder den Hoster wechseln. Aber es lohnt sich, weil euch dann endlich die Grundfunktionen der genutzten Dienstleistung zur VErfügung stehen würden! @Bundesregierung
The slime also evolves, apparently. Today https://nxdomain.no/~peter/wankstortion/20250416_jevkisca@teksavvy.com_me@pmg-pub-smtp1.teksavvy.com.txt (https://nxdomain.no/~peter/wankstortion/20250416_jevkisca@teksavvy.com_me@pmg-pub-smtp1.teksavvy.com_original_base64.txt) inboxed, as far as I can recall the first #wankstortion message received here over #IPv6 (and likely inboxed for that reason, bypassing the IPv4 only #spamd).
See "The Despicable, No Good, Blackmail Campaign Targeting ... Imaginary Friends?" https://nxdomain.no/~peter/despicable_no_good_blackmail.html and links therein for some background #cybercrime #scams #sextortion #bitcon #bitcoin #cryptotulips #cryptocurrency #extortion #teksavvy
@plord12
Thank you for sharing.
What I missed was that #IPv6 allows for route aggregation and greater visibility.
As with #IPv6 prefixes I can now tell you the top 10-20 ASes apart without looking up things.
The Subnetting is also more consistent.
@u3acommunities.org
What #IPv6 also would solve, besides address scarcity, would be those weird feuds where companies that fail in their not policy compliant grab of address space seek out to destroy the RIR system using gaslighting
yesterdays talk to @u3acommunities.org on #ipv4 and #ipv6 went well I believe. Although if I do it again I need to improve the flow a bit.
As usual the followup can be found at https://u3acommunities.org/interest-groups/computing/
Seitenladefehler: http://www.fh-kiel.de/
ich sollte meine Messungen auch öfter mal anschauen
https://atlas.ripe.net/measurements/37917240/results
Leider hat ripe-atlas da keine Benachrichtigungsfunktion.
New Blog Post: IPv6 Support in Public Docker Registries in 2025
https://blog.miyuru.lk/ipv6-docker-registries-2025/
Let me know any other docker registries , that I have missed. I will check and update the post.
The case of multiple devices each with its own Wireguard tunnel would be way simpler by using #IPv6 . This can be done with an ULA prefix, so no "real" IPv6 is needed. Each machine gets a /128 and a static route back to /48, so monitoring and remote management don't have to be limited to a single host.
This would be way simpler than containers or VNETs. And there would be no risk of conflicting with any existing networks (or rather for ULA: it would be greatly limited).
Noob-level #SelfHosting #IPv6 question:
My home computers are connected through a router and, although they're clearly using NAT through said router for IPv4, they appear to all have outside IPv6 addresses. Are those addresses directly accessible from outside? When adding AAAA records to my outside DNS zones, should they point to my router's address, or the target machine's?
Nice! @tailscale finally updated their infrastructure to support IPv6-only OIDC endpoints (after I complained)
