Kind reminder that there is this neat tool: Yggdrasil Network.

https://yggdrasil-network.github.io/

#IPv6

#ItsAlwaysDNS Finally learning IPv6, a thing I tried to avoid for the longest time. All my servers are reachable via IPv6, I know how to do that, but now I am learning to set up IPv6 in my home(lab) network and wrapping my head around concepts like ULAs (Unique Local Addresses, that don't route to/from the internet), prefixes I get from my ISP and how all of that translates to DNS entries on my BIND9. Mistakes will be made.

1/4

#SelfHost #Homelab #IPv6 #DNS

For once it seems that having a VDSL connection with Deutsche Telekom is worth it, as their IPv6 setup delegates a /56 to my home. This means I get 255 /64 to play with :)

2/4

#SelfHost #Homelab #IPv6 #DNS

Enough for today, which I will remember as my personal IPv6 day :) Time for a cuppa and a Madeleine. Uffa.

4/4

#SelfHost #Homelab #Ipv6 #DNS

OK. Step 1 done. My homelab machines get ULAs and I have added AAAA records to my DNS. So this already works :) Ping and ssh via IPv6 with hostname resolution via my own DNS server. Now to add reverse lookup.

Unfinished brain dump at https://codeberg.org/jwildeboer/gists/src/branch/main/2025/20250827BasicIPv6Unfinished.md

Corrections and enhancements welcome! I'm a noob wrt IPv6 ...

3/4

#SelfHost #Homelab #IPv6 #DNS

Alt...

cat /var/named/forward.homelab.jhw $TTL 3600 @ IN SOA inf01.homelab.jhw. root.homelab.jhw. ( 2025082705 ;Serial 3600 ;Refresh 1800 ;Retry 604800 ;Expire 86400 ;Minimum TTL ) @ IN NS inf01.homelab.jhw. @ IN A 192.168.1.10 inf01 IN A 192.168.1.10 inf01 IN AAAA fdda:a4da:69a5:0:2783:8c26:b2f1:a6f7 hl01 IN A 192.168.1.11 hl01 IN AAAA fdda:a4da:69a5:0:6e4b:90ff:fe75:3a73 hl02 IN A 192.168.1.12 hl02 IN AAAA fdda:a4da:69a5:0:6e4b:90ff:fe21:c3f5 hl03 IN A 192.168.1.13 hl03 IN AAAA fdda:a4da:69a5:0:6e4b:90ff:fe21:ca06 ca IN CNAME inf01.homelab.jhw.

Alt...

% ping6 -c 2 hl01.homelab.jhw PING6(56=40+8+8 bytes) fdda:a4da:69a5:0:1c38:385f:940:d721 --> fdda:a4da:69a5:0:6e4b:90ff:fe75:3a73 16 bytes from fdda:a4da:69a5:0:6e4b:90ff:fe75:3a73, icmp_seq=0 hlim=255 time=16.264 ms 16 bytes from fdda:a4da:69a5:0:6e4b:90ff:fe75:3a73, icmp_seq=1 hlim=255 time=9.203 ms --- hl01.homelab.jhw ping6 statistics --- 2 packets transmitted, 2 packets received, 0.0% packet loss round-trip min/avg/max/std-dev = 9.203/12.733/16.264/3.531 ms % ssh -6 [email protected] Web console: https://hl01.homelab.jhw:9090/ or https://192.168.1.11:9090/ Last login: Wed Aug 27 21:20:42 2025 from 217.237.90.172 root@hl01:~# who root pts/0 2025-08-27 21:29 (fdda:a4da:69a5:0:1c38:385f:940:d721) root@hl01:~#

AWS Client VPN now supports connectivity to IPv6 resources
Posted on: Aug 26, 2025
https://aws.amazon.com/about-aws/whats-new/2025/08/aws-client-vpn-connectivity-ipv6-resources/

#aws #ipv6

@jwildeboer @luisfcorreia

Dynamic Prefix is a major hassle for connectivity and especially for the homelabers.
There are numerous RFC to work around the broken ISPs like the one you mentioned.
Currently there is an active discussion in the IETF WG how to solve this problem.
What I learned in this regard, only use ULA as a last resort, as this is not an RFC1918 equivalent.

Please tag your posts with #IPv6.

@jwildeboer
Most of it is quite easy.

The shitty part of #IPv6 is basically:
* dynamic readdressing caused by dynamic prefix rotation
* upstream source filtering esp. when dual homed and you don't have a flat internal network
* cellular source filtering sometimes to a single /128 and a specific TTL
* Docker and dynamically getting addresses, esp. on notebooks when you don't fully control upstream network (neigh proxy, prefix delegation, ...)
* multi homing with multiple ISPs (without peering)

I wonder how many of you does really have to, or, need to, configure NAT64 routing. Any special scenario you guys have stumbled upon that wanna share with the rest of the class ?

https://bsdrp.net/documentation/examples/nat64

#ipv6 #ipv6 #bsd #freebsd

Alt...

#ipv6 #ipv6 #bsd #freebsd

@snep If only there was a way for everyone to get all ports! Gosh, too bad we as humanity haven't come up with a solution to this. (#IPv6 👀)

I am now a RIPE NCC Certified IPv6 Security Expert.
I am happy that I passed the exam despite technical difficulties with the exam platform.

@ripencc #IPv6

Alt...

You can see a kind of digital pin badge. It is silver around the edge and purple on the inside. It bears the text "RIPE NCC Certified Professionals IPv6 Security Expert".

Alt...

A certificate with a purple pattern. The text "RIPE NCC Certified Professionals" is at the top left. "Marek Küthe has completed the RIPE NCC Certified Professionals requirements and is recognised as an IPv6 Security Expert" is in the middle. "Issued on: 25 AUG 2025" "Expires on: 25 AUG 2028" is at the bottom left. "Issued by RIPE NCC" "Verify: https://www.credly.com/go/5hEun2tP" is at the bottom right.

ooh this'd be a fun thing to implement as a public DNS server dynamically returning TXT for reverse lookups and AAAA for forwards

https://github.com/lstn/ip6words

#IPv6 #DNS

https://blog.apnic.net/2025/08/25/the-ipv6-divide/

#ipv6 #blog #apnic
#notbyGeoffHuston

Was ich gar nicht wußte: Bei #Vodafone bekommt man mittlerweile einfach so ein /64, ohne das irgendwo beantragen zu müssen.
Und es funktioniert noch dazu, kein Gehampel mit #tunnelbroker mehr, der #Mikrotik macht das sauber inklusive Sonderlocken wie "ignoriere die Nameserver, die Vodafone Dir aufs Auge drücken möchte, nimm den #pihole!"

#ipv6 wie es sein soll. Na gut, größer als /64 bekomme ich als Privatkunde wohl nicht, d.h, #Vlans im Heimnetz gehen dann eben nicht, jedenfalls nicht mit v6.
Irgendwas ist ja immer, für jetzt bin ich zufrieden.

In general, I like netcup. The FediMeteo VPS rocks and they're quite reliable but....their IPv6 implementation is such a mess! Hetzner allows you to route, so each vnet jail can have its own IPv6 address. On netcup, I have never been able to achieve such a result.

#ipv6 #Networking

Does anyone have experience with #proxmox #sdn and #IPv6 ?

It works fine as long as there's only an IPV4 range configured, but when I add an IPv6 ULA it breaks. Starting a CT leads to

```
DEBUG utils - ../src/lxc/utils.c:run_buffer:560 - Script exec /usr/share/lxc/hooks/lxc-pve-prestart-hook 103 lxc pre-start produced output: org.freedesktop.DBus.Error.ServiceUnknown: The name uk.org.thekelleys.dnsmasq.local was not provided by any .service files
```

The forums have no clue.

Anyone using OVHCloud with IPv6?
I have a server at Netcup.de and it seems, there's a nasty routing issue from OVH to the German Nuremberg Datacenter of NetCup.

Could someone try reaching out to 2a0a:4cc0:c1:2f90::2 from an OVH network? (Ping, SSH, Traceroute ..)

#networking #ovh #netcup #fedihelp #routing #ipv6 @OVHcloud @netcup

@goetz nothing... Not even after nagging for 8 years. Not willing to add #ipv6 knowledge leads to these horrible routing layouts

@nico
They don't even have an #IPv6 prefix allocated to their AS?
What a shame!

Real life #legacy Internet routing - this is so broken. Snapshot taken from a provider who did not deploy #IPv6 at all. I personally find it very shameful.

$ host -t AAAA isitfridayyet.net
isitfridayyet.net has no AAAA record

#ipv6

Predict when GitHub will deploy IPv6.

https://www.metaculus.com/questions/37128/when-will-github-deploy-ipv6/

Current community prediction is Sep 2030.

#IPv6 #github

@apalrd https://community.ui.com/releases/UniFi-Network-Application-9-4-17/e5af0578-a091-4644-8205-2b912034b756

Significant progress on the current protocol, on this release (still in RC, as of this moment).

#IPv6 #Ubiquiti #UniFi

Someone should tell Newfold they need to modernize. https://www.theregister.com/2025/08/20/ietf_dnsop_3901bis_ipv4_ipv6/ #IPv6

#ipv6 #dns

https://www.theregister.com/2025/08/20/ietf_dnsop_3901bis_ipv4_ipv6/

https://datatracker.ietf.org/doc/draft-ietf-dnsop-3901bis/04/

by @tfiebig

There are dozens of server mirrors of my distro of choice in my country, half of them compliant with actual Internet standards a.k.a. #IPv6 enabled & the ISP I have @ home (AS18881), despite being one of the biggest if not the biggest company around and providing #IPv6 connectivity for decades... due to "internal politics", they won't peer with ANYONE in this stack. The result? To reach the server literally next door, the connection goes to Disney and back

https://ipv6.reddit.com/r/InternetBrasil/comments/1imwrbj/apenas_mais_um_dia_de_pacote_fazendo_batevolta

[...]

Ah klar die #Telekom. Das erklärt, warum in Deutschland nichts voran geht ​​ #IPv6

@UnderEu @nivex @forwardingplane

Interesting that #OVH gets also an A, as there whole management interfaces are not #IPv6 enabled and no roadmap.

@forwardingplane Interesting that Linode has a lower grade than DigitalOcean. Linode's #IPv6 is enabled by default, whereas with DO you still have to opt-in at VM creation time and I'm told it's quite difficult to retroactively do this.

@mrblubber … das Problem habe ich auch (nicht mit meinem Gerät, da Telekom, aber mit den anderen in der Familie): #IPv6 über Glasfaser, mobil bei #Vodafone nur #IPv4 - wenn da jemand eine Lösung hat - gerne her damit!

#NoNAT Saturday
Interesting findings:

https://geschaeftskunden.telekom.de/ is #IPv4only
Same with https://www.telekom.de/

#Telekomfail no #IPv6

To extend this to other German ISPs

Main website reachable over #IPv6

#Vodafone OK
#1und1 OK
#DeutscheGlasfaser OK
#Netcologne OK

#Telekom NOK
#o2 NOK
#Easybell NOK
#WOBCOM NOK
#DeutscheGiganetz NOK

🙂

#IPv6 #HurricaneElectric

Alt...

Badge in Hurricane Electric IPv6 Certification page, informing that I am now certified as "Sage"

#NoNAT Saturday

Looking for a new computer on the modern internet?

It is either #Framework , #Apple, #Microsoft or #Google

The usual suspects and mini-pc manufacturers are all not available via #IPv6

@UnderEu they provide it mostly on #IPv6 payment is not possible #IPv6only

#IPv6 and #musicstreaming I checked #Deezer #soundcloud #qobuz as alternatives to #spotify for their ability to work on the modern internet. Non of those 3 are capable off. I opened an issue / feature request with all of them. Please chime in if you are a current user or would like to switch but cannot due to this constrain.

#rosenheim #ipv6

#eduroam by komro

(in der City)

👍👍👎(some MTU issues)