#ipv6

19 posts · Last used 1d

Back to Timeline
Boosted by Kevin Karhan @kkarhan@jorts.horse
In reply to
@T_X@chaos.social · Mar 06, 2026
@tazgetroete@mastodon.social an das Radio Corax habe ich noch sehr gute Erinnerungen, hab' damals, 2009, mit johnyb unseren Start mit @ffhl@chaos.social dort vorgestellt. Das ganze wurde während des @ffwcw@social.freifunk.net in der @cbase@chaos.social damals aufgezeichnet: https://www.freie-radios.net/28134 Ging unter anderem um @batadv@social.freifunk.net und #IPv6. Weitere Interviews rund um #Freifunk von jenem WCW: https://www.freie-radios.net/portal/suche.php?such=true&fast=1&end_monat=03&end_jahr=2026&ssu=1&query=WCW-2009 Während die einen sich Gedanken um neue Möglichkeiten, Ansätze und Lösungen machen, möchte die AfD wie immer lieber im vorvorgestern bleiben...
2
0
2
Boosted by Kevin Karhan @kkarhan@jorts.horse
@aiyion@infosec.exchange · Apr 16, 2026
Der geneigte Google Nutzer hat jetzt im Schnitt in 50% der Fälle IPv6 Konnektivität. Der geneigte Freifunk Hannover Nutzer hat seit mindestens 2012 in 100% der Fälle IPv6 Verbindung. Wir gratulieren Google in dem Sinne recht herzlich :D https://www.google.com/intl/en/ipv6/statistics.html #ipv6 #google #freifunk @freifunkh
4
0
2
In reply to
@kkarhan@jorts.horse · 4d ago
@Arusekk@infosec.exchange I'll be able to go #IPv6 once it's mandatory. Sadly it ain't but in fact many applications mandate #IPv4 to this day…I unsarcastically want #IPv8 (minus the obvious bullshit!) The only reason IPv6 traffic is increasing is propably becaise #MNO|s and #MVNOs still do #CGNAT on #RFC1918 address spaces, thus bricking #VPN|s. This was literally the reason I had to setup #DualStack at some company!
0
0
0
Boosted by Kevin Karhan @kkarhan@jorts.horse
@Arusekk@infosec.exchange · 4d ago
Finally! IPv6 traffic coming into Google exceeded IPv4 traffic last month! https://www.google.com/intl/en/ipv6/statistics.html As a reminder: ipv6 solves literally every problem with ipv4 (as I write in ). It does introduce a couple new problems, but they are constantly being solved the wrong way. #ipv4 #ipv6 #ipv8
4
2
3
@labria@social.yeschenko.com · 4d ago

Ok, the ipv6 experiment failed yet again Anyone knows a tunnelbroker that:

  • has endpoints in DUB/LND
  • has ip blocks with a decent reputations (he.net ranges get bans/captchas all of the time) I’m even ready to pay some reasonable price :-/ #ipv6 #ireland
2
0
3
@oxy@social.bsdlab.au · 6d ago
rcloning some data around the interwebz and seeing all of the connections happen over #IPv6 makes me happy
0
0
0
@claudiom@bsd.network · Apr 20, 2026
#IPv8?! We're still trying to get everyone to agree to move over to #IPv6!! :flan_despair::flan_XD:#ietf #InternetProtocol https://www.ietf.org/archive/id/draft-thain-ipv8-00.html
0
0
0
@Larvitz@burningboard.net · Apr 03, 2026
Successful surgery on my BGP core for AS201379 done. Got a third edge-router online, reorganized local-preferences and optimizing packet flows for efficiency and cost. Monitoring with Grafana is perfectly fine. RIPE Atlas measurement looks amazing for central Europe 🙂 Great connectivity for my 2a06:9801:1c::/48 Looking Glass: https://lg.hofstede.it Peering information: https://hofstede.it/as201379.html #networking #bgp #ipv6 #freebsd #frr #ripe
8
0
2
@zooper@mstdn.kernel-panic.lol · Mar 27, 2026
I've been mentioning my little hobby project Netpulse a few times, so I wrote a blog post about it now. https://as215855.net/posts/building-netpulse #homelab #ipv6 #networking #bgp
4
0
0
@Larvitz__dup_34529@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

0
0
1
@Larvitz__dup_34529@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

0
0
0
@Larvitz__dup_34529@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

0
0
0
@Larvitz__dup_34529@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
0
0
2
In reply to
@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.
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
20
0
6
Boosted by Gay, loud and annoying ! :flag: :transdprk: @hj@shigusegubu.club
In reply to
@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:
105
3
40
@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
0
0
0

You've seen all posts