#ipv6

10 posts · Last used 7d

Back to Timeline
@Larvitz@burningboard.net · Mar 09, 2026
Our Mastodon instance "burningboard.net" now internally **ONLY** uses the Internet Protocol in Version 6. I did successfully migrate away from any RFC1918 addresses in any of the internal infrastructure connections. Nginx -> Mastodon: IPv6 Mastodon -> PostgreSQL: IPv6 Mastodon -> Opensearch: IPv6 Mastodon -> Sidekiq: IPv6 Mastodon -> Loki: IPv6 Sidekiq -> PostgreSQL: IPv6 Prometheus -> Mastodon: IPv6 All using globally routed unique addresses and proper routing and packet filtering from "pf" (FreeBSD). Outbound connections to legacy hosts (for example for Federation) uses NAT64 over Tayga. Inbound the Nginx is the only component, that supports IPv4 on NAT on a best-effort approach. But I refuse to put a lot of work into this. We have 2026 and it's a dying, smelly protocol, that I don't even monitor anymore. If someone looks at the Firewall rules.. Yes, we do run a (private) Factorio Server on our Mastodon system :factorio: #mastodon #mastoadmin #ipv6 #networking #freebsd @tux@burningboard.net
View on burningboard.net
0
0
1
@Larvitz@burningboard.net · Feb 26, 2026
I just published a new guide on evolving a single BGP router into a multi-homed, two-PoP network using FreeBSD, FRR, and PF. - Native peering on Vultr + 3 GRE transits - Tying it together with iBGP - Why stateful firewalls break asymmetric transit (and how to fix it) All for ~€18/mo. Read it here: https://blog.hofstede.it/running-your-own-as-going-multi-homed-with-ibgp-and-three-transits/ #FreeBSD #BGP #IPv6 #Networking #Sysadmin #FRR #Homelab
View on burningboard.net
0
0
0
@Larvitz@burningboard.net · Feb 25, 2026
Got my AS201379 (2a06:9801:1c::/48) well connected to European networks. RIPE Atlas measurements are pretty satisfying now 🙂 My website (hofstede.it / blog.hofstede.it) is reachable in <10ms from most of Europe via my own address space. - 4 Upstream providers - Two BGP routers - Stable for > 48hrs and reasonable ingress and egress paths 🙂 Very, VERY pleased with the result! Next stop: Own NAT64 setup 🙂 Big thanks to @UnderEu@mas.to , @tschaefer@ipv6.social and @Hypopheralcus@det.social for giving me the Atlas credits for Measurements! Highly appreciated! #ipv6 #networking #it #ripe #bgp
View on burningboard.net
0
0
0
@Larvitz@burningboard.net · Feb 23, 2026
Any chance that someone might have a leftover RIPE ATLAS credits? I currently do some experiments with the IPv6 routing of my AS201379 and being able to do measurements on Atlas would be sooooo helpful right now. #fedihelp #ripe #ripencc #ripeatlas #ipv6 #networking
View on burningboard.net
0
0
2
Thread context 4 posts in path
Root @tux@burningboard.net Open
@tux@burningboard.net
@AlienJay@burningboard.net Beides mit der Priorität auf IPv6.
Ancestor 2 @AlienJay@burningboard.net Open
@AlienJay@burningboard.net
@tux@burningboard.net Wie hast du Dynamic DNS für IPv6 gelöst? Gibt es da schon was? Denn die Adresse ja den Präfix und deinen Rechner im lokalen Netz.
Parent @tux@burningboard.net Open
@tux@burningboard.net
@AlienJay@burningboard.net Ich glaube, da liegt ein Missverständnis vor 🤔 Der vServer verbindet sich von außen via IPv6 auf meine Fritzbox und bekommt hier im LAN eine IPv4-Adresse, die ich ansprechen
Current reply
@AlienJay@burningboard.net · Feb 23, 2026
@tux@burningboard.net OK, ich dachte du machst Geräte in deinem lokalen Netz direkt per #IPv6 von außen erreichbar. Denn nach meinem Verständnis wird das ja auch immer als einer der Vorteile von IPv6 angepriesen. Kein NAT, kein Portforwarding. Direktes Routing.
View full thread on burningboard.net
0
0
0
@ruawhitepaw@chitter.xyz · Jan 31, 2026
TIL that Github does not have IPv6. Which is pretty ridiculous for anytime in the last decade, but in 2026, for a site that big and important? Better go to Codeberg... #Github #IPv6
View on chitter.xyz
20
0
6
Thread context 2 posts in path
Parent @jana@social.jsteuernagel.de Open
on social.jsteuernagel.de
Open ancestor post
Current reply
Boosted by Gay, loud and annoying ! :flag: :transdprk: @hj@shigusegubu.club
@jana@social.jsteuernagel.de · Jan 23, 2026
Remember when in December I had a bit of a debug session why I couldn't reach my monitoring server via #IPv6 from a DTAG internet line? Well, this later motivated @domi@donotsta.re to dig a bit deeper and it ended up with @q3k@social.hackerspace.pl sending some emails to EPIX, DTAG and Lumen about it, as it was obviously a bigger issue of an entire /32 IPv6 prefix from Lumen not being accepted by DTAG. The issue ended up being escalated multiple times and it seemed to take them quite a while to figure out what was wrong. But as of today (or recently, today is when I got note of it), it works! DTAG now accepts the 2a0d:eb00::/32 prefix, which they previously rejected due to, supposedly, an incorrectly documented Lumen AS-SET in the RIPE DB. This is certainly not the escalation I expected after I connect to my server back then :neobot_giggle:
View full thread on social.jsteuernagel.de
20
0
12
@hn50@social.lansky.name · Jan 13, 2026
0
0
0
@hn50@social.lansky.name · Jan 08, 2026
0
0
0
@hn50@social.lansky.name · Jan 02, 2026
IPv6 just turned 30 and still hasn't taken over the world Link: https://www.theregister.com/2025/12/31/ipv6_at_30/ Discussion: https://news.ycombinator.com/item?id=46465327 #ipv6
View on social.lansky.name
0
0
0

You've seen all posts