#IPV6

2026-02-15

RE: hachyderm.io/@zrail/1160537724

So I think I solved... half(?) the problem. It dawned on me that I can use any machine on a given network to announce an #ipv6 prefix and as long as it has the router lifetime set to 0 no clients will try to use it as a gateway.

Thus, I'm announcing a /64 slice of the /48 I leased from a tiny lxc running on my N100 "critical stuff" machine.

I think for DNS I'm going to just put these addresses in public DNS. The whole point is that they're static and one fewer moving piece is nice. This doesn't solve the "but what if internet is down" problem but I don't think that's super realistic.

Oh one other thing worth mentioning: this /64 is not routed. From the outside it'll hit the blackhole route on my router VPS.

@homelab #selfhosting

2026-02-15

Fellow Homelabbers, has anyone of you any experience running an IPv6 only Matrix / Synapse Server and could tell me if there any noticeable limitations apart from homeservers not beeing reachable via IPv6 in 2026?
@homelab @homelab_de #homelab #matrix #synapse #ipv6 #selfhosting

2026-02-15

Geschaut, welche Dienste der Uni kein #IPv6 haben und die Antwort ist belastend

Beni HB9HNTbeni@wirebug.ch
2026-02-15
So, what do you do if you want to avoid learning and implementing #ipv6 at all costs? The only answer IPv4 nostalgics can come up with: NAT everything, everywhere! In this instance, use NAT64 inbound rather than outbound as intended. Hope this organisation is not typical for Europe's strive for digital independence....

https://docs.stackit.cloud/products/network/core-networking/public-ip-address/how-tos/setup-ipv6-reachability/

(Originally posted by @tschaefer@ipv6.social)
Joseph A di Paolantoniojadp
2026-02-15

Interesting fix. @czds and I have been having trouble adding two new Eve Thread/Matter Energy Plugs to our Apple Home, even the Eve app. We tried the various “fixes” in Eve and Apple and various third-party support/discussion forums. Nada. Until we stumbled upon one suggestion. Enable IPv6 in your local router. We didn’t even configure IPv6, just enabled it. Now to find the time to replace the WeMo switches

sensor analytics ecosystem

2026-02-14

@soaproot @apz @Mastodon As I understand it, only supports for AWS and not for @hetzner, which is the provider for mastodon.social. Hopefully it will be added soon, as this would improve for many people.

Erik Nygren :verified:nygren@hachyderm.io
2026-02-14

I'm amused that as useful as it is, #Claude Opus 4.5 proposes bogus #IPv6 addresses containing characters outside of /[0-9a-f]/

Yet another example of it being a useful tool for experts who know what they are doing and can review its output.

2026-02-14

Question for my #ipv6 #homelab peeps. Is it actively bad practice to have multiple instances of radvd announcing the same prefix with ra lifetime set to 0?

I.e. they're not gateway devices, I just want them to respond to NS packets.

Anderson SilvaUnderEu@mas.to
2026-02-14

@cloudflare Could you help your customer #Shopify to fix their connectivity by not disabling #IPv6 on websites they host?

2026-02-14

@zrail

Yes. After doing it once one always has the lurking suspicion that one day one will come up against the LAN of someone else who has had the very same idea — whose birthday, or lucky numbers, or CRC16, or whatever just happen to make the same octets in the network part.

Then there are things like having an ISP that uses various parts of 10.0/8 for its internal infrastructure. Even my own ISP uses 192.168.100.0/24 for its own purposes on customer-premises equipment.

@mdavis
#RFC1918 #IPv6 #IPv4 #SiteLocalAddresses #PrivateUseAddresses #LANs #NetworkAdministration

2026-02-14

@mdavis I picked a /24 in 10.0.0.0/8 that I figured would be unique enough, and so far it has been. I'm much more on the #ipv6 train these days though.

2026-02-14

I'm starting to wonder, if Amazon continues to buy up as much of the IPv4 address space as they can, will AWS eventually become the only network---not the only IaaS platform, the only *network*---that can practically absorb IPv4 Internet growth of any kind? #IPv6

2026-02-13

@armbian Got the key issue sorted but the #IPv6 mirror situation is still pretty awful.

2026-02-13
Running a single user or small user instance in the #Fediverse? A relay instance can help you to find more interesting content and to broadcast to other instances!

https://fedi-relay.gyptazy.com is a tech related relay instance that connects over 100 instances, focussing on things like #FreeBSD, #BGP, #IPv6, #Proxmox, #Homelab, #Linux and many other things! You can easily add a really when using #snac / #snac2, #mastodon, #pleroma and many other ones!

#community #activitypub #socialmedia #fedi #fediwall #relay #opensource #tech #federated #social
Overview of the fedi-relay gyptazy instance for the Fediverse
2026-02-13

It has been 5000 days since World #IPv6 Launch.

2026-02-13

RE: ipv6.social/@tschaefer/1160394

Jeder der sein Wissen oder Vorurteile über #IPv6 erweitern möchte sei dieser Podcast Folge ans Herz gelegt.

weberblog.net/ipv6/

2026-02-13

@ufm фронтенд ще дуже сирий, по трохи звітую виявлені проблеми, згодом планую засісти за їх вирішення особисто. як мінімум, є проблеми з сирим #IPv6 і портами в ID

кому цікаво - рекомендую поки юзати бекенд (через командний рядок rad) фронтенд поставив виключно для візуалізації і розуміння того що там в біса робиться

2026-02-13

@apz This is partly because mastodon.social, @Mastodon's own instance, is IPv4-only. I thought you might want to support this call to action: mastodon.social/@rickvanrooije. Anything you can do to help, whether it's boosting the message, upvoting the GitHub issues, or putting your own spin on it, is greatly appreciated.

Client Info

Server: https://mastodon.social
Version: 2025.07
Repository: https://github.com/cyevgeniy/lmst