Mastodawn

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.

Show thread

goetz 1d ago

@hugo
#IPv6 in ESPHome works. Although not privacy perserving, (EUI64 lwIP dependency) but needs currently IPv4 for connectivity.

#IPv6only is a way to go.
I see no way to interact with the #lwIP maintainers due to closing of all channels of communication for bug reports and feature requests.

#dns #ipv6

Wolfgang Tremmel 1d ago

@nuintari #esphome supports #IPv6

goetz 1d ago

@nuintari
Most do dual stack but prefer v4 or need dual stack. #ESPHome #tasmota
I have only 4 devices which actually are v4 only. #Sonos #SMA and #SolarLog

#IoT #IPv6 #internetOfThings #internetOfShit

wifi_freak 1d ago

TIL: Wenn du #Wireguard nen #IPv6 only Tunnel bereitstellen lassen möchtest, scheinst du, zumindest auf #Android15, trotzdem ne lokale #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).

Show thread

Michael Richardson 1d ago

@sodiboo Technology has no volition, it can't be cool or not. It wasn't technology that was cool, it was always that the TransFurryHackers that were cool. That the moneysick were posing as cool people (and they convinced the moneysick poser media) is really just another part of their sickness.
The "500 channel universe" was never supposed to be owned/intermediated by these morons. That happened because: NAT44, Windows-too-unsafe-to-use, Incumbent-Telco-want-eyeballs-not-citizens. #ipv6 #homehosting
I keep looking for business models that would support #littlebrother community mesh networks. Best I have come up with is community backups.

Thomas Schäfer 2d ago

#ipv6 #bdbos #sccon25

#bambi

...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

#sccon25 #ipv6 #protokollstandard #ipv6 #expertenkonferenz2025 #sccon25 #ipv6 #digitalisierung #egovernment #digitalesouveränität | Bundesanstalt für den Digitalfunk (BDBOS)

Die BDBOS auf der #SCCON25: Großes Interesse am #IPv6 Programm Mit einem interaktiven Messestand auf der Smart Country Convention 2025 informierte die BDBOS über die Mehrwerte der IPv6-Migration und deren aktuellen Umsetzungsstand im Bund. Über 150 Besucherinnen und Besucher nutzten an den drei Messetagen die Gelegenheit, Fachgespräche am Stand zu führen und tiefergehende Einblicke in die praxisnahen Ansätze für den erfolgreichen Übergang zum #Protokollstandard #IPv6 zu erhalten. Neben den Bundesbehörden besuchten auch viele Vertreterinnen und Vertreter aus Bundesländern und Kommunen den Messestand, um insbesondere die Chancen und Möglichkeiten einer Erweiterung des IPv6-Programms auf die föderale Ebene auszuweiten. Ein gut besuchtes Angebot war der Workshop unter Anleitung erfahrener IPv6-Coaches. Anhand einer fiktiven Behörde – dem „Bundesamt für Muster und Beispiele“ (kurz BAMBI) – konnten die Teilnehmenden verschiedene Migrationsszenarien praxisnah erproben. Auf der SCCON25 hatte BAMBI seinen ersten öffentlichen Auftritt. Nun wird das Projekt durch die Community und die BDBOS weiter aufgebaut, um die spannenden Möglichkeiten einer fiktiven Behörde nutzbar zu machen. Auch abseits von Messen wie der SCCON findet ein reger Dialog zur Einführung des Protokollstandards IPv6 in der deutschen Verwaltung statt. Zur 2. IPv6-Expertenkonferenz (#expertenkonferenz2025) vom 8. bis 10. Dezember 2025 in Berlin sind Umsetzungsverantwortliche der IPv6-Migration in Behörden und Organisationen des Bundes und der Länder sowie Vertreterinnen und Vertreter von IT-Herstellern und -Dienstleistern mit IPv6-Bezug herzlich eingeladen. Informationen und Anmeldung unter: https://lnkd.in/d6UDzsuE #SCCON25 #IPv6 #Digitalisierung #EGovernment #DigitaleSouveränität Bild: BDBOS

T_X 2d ago

Just noticed that the Wikipedia article regarding "#IPv6 address" says "::/0 -> Default *unicast*" here: https://en.wikipedia.org/wiki/IPv6_address#Default_address_selection
Has anyone any source/RFC why it'd be unicast only? Mathmatically it'd be both #unicast and #multicast, wouldn't it?

That was actually a question I asked on the #IETF PIM mailing list in the past: https://mailarchive.ietf.org/arch/msg/pim/ULFLgUK2tBTGkFu6lv9jjknaMsk/
Without getting a definitive answer.

IPv6 address - Wikipedia

Shane Kerr 2d ago

I was surprised to discover ProtonMail only supports IPv4. There's a 10-year old request for this:

https://protonmail.uservoice.com/forums/284483-proton-mail/suggestions/8482300-ipv6-support

#ProtonMail #IPV6

IPv6 support

IPv6 is the new Internet. Gmail has provided the support.

The Voice of the Proton Community

Rachel 3d ago

New blog post! My adventures in IPv6 in the homelab

https://blog.transitory.social/posts/2025-10-25-adventures-in-ipv6/

It covers going from an IPv4 only to Mikrotik config, all the way to getting Kubernetes running in dual stack mode with pods and services assigned IPv6 addresses

(Note: I have enabled a cache middleware on the blog, so if that explodes someone give a shout and I'll disable it ;) )
#Homelab #Blog #IPv6 #Mikrotik #Kubernetes #Networking

Adventures in IPv6: IPv6 in the Homelab

Adventures in IPv6: IPv6 in the Homelab Motivation There were three major motivations for starting down this project I like networking, and IPv6 is shiny. I’m fine as long as I am constantly distracted. I had mild concerns about how IPv6 would impact connectivity with IPv6 only sites. This project actually ended up being a hard requirement for my edge node project. More on that later. Going down the stack The plan was to go from outside in, starting with the router where IPv6 reaches my network, then moving to subnetting along VLAN lines, and then finally the clients, the kubernetes cluster in particular. This project is not yet complete, there are a handful areas left to cover which I will discuss in the recap at the end of the article, but the key goals have been met.

Transitory Blog