#ipv6

Klaus Frank @agowa338@chaos.social · 4d ago

Note to self: Just don't touch #ipsec. It's shit all way round and always breaks. Just use something else. Why? Every time I want an encrypted tunnel between two public IPs I think like "oh yea, using IPSec here would be easy and straight forward". And then it never fucking works reliably. And if it does work it stops to work the next time you try to apply the exact same config. And it fails with shit like this... What have I done wrong?!? Why work sometimes?? #networking #strongswan #ipv6

3

1

0

Larvitz

@Larvitz@burningboard.net · 5d ago

https://netzluege.netlify.app #humor #networking #ipv6 #verschwörung #netzwerk

0

1

0

Nivex 🐧 📻 @nivex@tenforward.social · Aug 05, 2026

Silly mozilla: [ERROR crashreporter::glean::uploader] failed to send glean ping: process failed (exit status exit status: 7) with stderr: curl: (7) Failed to connect to incoming.telemetry.mozilla.org port 443 after 2 ms: Could not connect to server I guess the ultimate way to avoid being tracked is to go #IPv6-only.

0

3

0

Will Brien @willb@infosec.exchange · Aug 04, 2026

true then, true now, but not today #sysadmin #lazy #ipv6 #nope #pass #busy

0

adminForge

@adminforge@kanoa.de · Aug 04, 2026

🎉 Neues Design für ipwho.de Die IP-Lookup-Seite aus der adminForge-Familie hat ein frisches, modernes Design bekommen mit eigenem violetten 🟣 Look. ✅ IPv4 & IPv6 auf einen Blick 🖥️ Weiterhin 100% curl-freundlich, kein API-Key nötig 🚫 Kein Tracking, keine Werbung, keine Cookies 👉 https://ipwho.de #adminForge #OpenSource #SelfHosted #IPv6 #Linux

41

0

31

0

Jaap de Vos @jaap@mastodon.bsd.cafe · Jul 13, 2026

A new article at the RIPE blog explains the current state of running IPv4 services over IPv6-only networks. The three pieces are RFC 8950 (IPv6 next-hops for IPv4 prefixes), a draft about IPv6 next-hops for IPv4 routes, and a draft for solving the IPv4 gateway problem that systems running IPv4 services in these types of networks typically have. It’s cool to see this gateway thing in such an informed piece, I’ve been wondering about that bit for a while. You might have seen different service providers solving this in different ways, with a /32 on either a regular interface or a loopback, and a strange default route pointing to just an interface (with no destination IP), or a destination IP in a prefix that the given machine doesn’t know about. Linux seems to support a couple of different ways to go about this (of course), and FreeBSD and OpenBSD each support a single, different solution AFAIK. I don’t believe illumos even has a way to solve this problem at the moment, but I might have that one wrong. Anyway, do have a look at the article: https://labs.ripe.net/author/remco-van-mook/a-farewell-to-arps-ipv4-service-on-ipv6-only-networks/ #IPv6 #IPv6mostly #fuckdualstack #networking

12

2

6

0

Larvitz

@Larvitz@burningboard.net · Jul 30, 2026

AS201379, part 5: joined EVIX (an IXP whose fabric is VXLAN tunnels, so no port and no new machine), got IPv4 onto an IPv6-only network, and cleaned up four routers' worth of config drift. Fourteen BGP sessions, all FreeBSD, all still fitting on one Grafana screen. https://blog.hofstede.it/running-your-own-as-an-ixp-over-vxlan-ipv4-on-the-overlay-and-a-config-spring-clean/ #FreeBSD #BGP #IPv6 #Networking

4

1

5

0

Larvitz

@Larvitz@burningboard.net · Jul 30, 2026

I really don’t need any more peers for my AS201379! (Okay, maybe a few more...) Started back in December 2025, and now this "little" infrastructure is running: 14 individual eBGP sessions 3 Internet Exchanges Multiple transit providers 110+ direct peers All 100% IPv6 (2a06:9801:1c::/48) because legacy IP belongs in the last century. Powered entirely by FreeBSD

4 routers on 15.1-RELEASE running FRR and PF. #BGP #IPv6 #FreeBSD #Routing #Networking #sysadmin

17

4

8

0

Erik Nygren

@nygren@hachyderm.io · Jul 28, 2026

Following some discussions during #IETF last week (in the hallway and on various mailing lists), the awesome #IPvFoo extension now shows in Mozilla #FireFox if connections used H1, H2, or H3, not just IPv4-vs-IPv6! This is helpful for seeing how that angle of Happy Eyeballs works. (It would work in the Chrome version as well but the interface for getting at this info is broken and always returns H1.) Note that if the connection starts with H2 but then switches to H3 for later objects on the hostname (eg, if you have an Alt-Svc record) then it will show H3 rather than H2. https://addons.mozilla.org/en-US/firefox/addon/ipvfoo/ #QUIC #HTTP2 #HTTP3 #IPv6 #HappyEyeballs

17

3

12

0

Martin Pugh @pugmiester@bsd.network · Jul 23, 2026

Picked up a little light reading material to hopefully help me get a better handle on IPv6. I still consider myself an absolute novice. I have working IPv6 at home but I confess I really don't understand all the "nerd knobs" that make it work. Plus, this might even give me enough of an understanding to start making a case for it at $dayjob. Right now, I don't understand it well enough for that. #ipv6

0

1

0

Andrew @ausfestivus@aus.social · Jul 22, 2026

I heard you like IPv6. Well, so does Windows. #ipv6

0

3

0

Limping @limping@mastodon.ml · Jan 28, 2026

Replying to on mastodon.ml

Прогрессивная штука #OpenWRT, без сомнения. Но одно расстраивает. Отключение #IPv6 - даже в 2026 году там пользователи себе прописывают прямо в uci-defaults Такое ретроградство, конечно, не от хорошей жизни. Я раньше тоже отключал, но теперь... NTC.party заставляет задуматься, и вообще. Вижу, как много ресурсов на кинетике пашут именно через IPv6.

3

1

2

0

Richard "RichiH" Hartmann @RichiH@chaos.social · Jul 21, 2026

Hey #GitHub, it's roughly half a year until #FOSDEM. As a reminder, I will disable the #NAT64-based #IPv4 fallback on the default network next year. The default network will be #IPv6-only. I do note that @Codeberg@social.anoxinon.de does support IPv6.

161

6

94

1

Richard "RichiH" Hartmann @RichiH@chaos.social · Jul 21, 2026

Hey @Gina@fosstodon.org et.al, it's roughly half a year until #FOSDEM. As a reminder, I will disable the #NAT64-based #IPv4 fallback on the default network. The default network will be #IPv6-only #Fosstodon is still IPV4-only, so that will be impacted.

1

2

0

ivan @baudrate115200@infosec.exchange · Jul 21, 2026

First #ipv6 related issue, and it's honestly not what I expected. #roku, do better. Enable IPv6.

0

ivan @baudrate115200@infosec.exchange · Jul 21, 2026

NAT64 on #ipv6 is working!

0

linuxwebzine @linuxwebzine@mstdn.ro · Jul 21, 2026

📡🌐 NetworkManager 1.58 a fost lansat: Suport extins pentru Wi-Fi 6 GHz, integrare CLAT și protocoale GENEVENetworkManager, daemonul standard folosit de majoritatea distribuțiilor Linux pentru gestionarea conexiunilor de rețea, a primit o nouă actualizare majoră: NetworkManager 1.58. Această versiune aduce îmbunătățiri substanțiale atât pentru utilizatorii de desktop-uri moderne, cât și pentru administratorii de sistem care gestionează infrastructuri complexe de rețea.Iată cele mai importante noutăți și caracteristici introduse în NetworkManager 1.58:🔹 Suport nativ optimizat pentru banda Wi-Fi de 6 GHzOdată cu adopția pe scară largă a standardelor Wi-Fi 6E și Wi-Fi 7, gestionarea frecvenței de 6 GHz a devenit esențială.NetworkManager 1.58 rafinează scanarea și conectarea la rețelele de 6 GHz, asigurând o tranziție mult mai lină între benzile de 2.4 GHz, 5 GHz și 6 GHz (band steering).S-a îmbunătățit stabilitatea conexiunilor pe chipset-urile wireless de ultimă generație, eliminând deconectările aleatorii la comutarea punctelor de acces (AP-uri).🔹 Suport nativ pentru CLAT (Customer-side Translator)Tranziția globală către IPv6 continuă, iar tehnologia 464XLAT joacă un rol crucial în furnizarea accesului la servicii vechi IPv4 peste infrastructuri pur IPv6.NetworkManager adaugă suport direct pentru CLAT, permițând dispozitivelor Linux să traducă transparent traficul IPv4 local într-un format IPv6 înainte de a trimite pachetele prin rețeaua furnizorului de internet (ISP).Această funcționalitate este extrem de utilă pentru rețelele mobile (LTE/5G) sau ISP-urile care folosesc conexiuni IPv6-only.🔹 Integrarea protocolului GENEVE (Generic Network Virtualization Encapsulation)Pentru mediile de virtualizare, centrele de date și infrastructurile cloud (cum ar fi OpenStack sau Kubernetes):NetworkManager 1.58 adaugă suport nativ pentru crearea și gestionarea interfețelor GENEVE.Protocolul GENEVE este un standard de încapsulare flexibil, conceput să înlocuiască protocoale mai vechi precum VXLAN sau NVGRE, oferind performanțe superioare în rețelele virtualizate create software (Software-Defined Networking - SDN).🔹 Alte optimizări și îmbunătățiriGestionare mai bună a fișierelor de configurare: Instrumentul de linie de comandă nmcli primește opțiuni noi de filtrare și raportare a erorilor de rețea.Performanță VPN: S-a optimizat modul în care sunt gestionate rutele de rețea la activarea și dezactivarea rapidă a conexiunilor VPN (precum WireGuard sau OpenVPN).Această lansare consolidează NetworkManager ca o soluție completă, capabilă să gestioneze atât conexiunile wireless rapide de zi cu zi, cât și tehnologiile avansate de rețea enterprise.#OpenSource #NetworkManager #NetworkManager158 #WiFi6GHz #IPv6 #Networking #Linux #SysAdmin #TechNews #Linuxiac

0

Eduardo Collado 🚲🇪🇺 @ecollado@mastodon.social · Jul 17, 2026

A Farewell to ARPs: IPv6 resolved gateways #ipv6 #ipv4 https://youtube.com/watch?v=AjAPXyXcxGo&si=yhRzBJ0FmTWpSPLR

2

0

2

0

Thomas Schäfer @tschaefer@ipv6.social · Jul 20, 2026

https://blog.apnic.net/2026/07/20/ipv6-address-planning-from-bit-conservation-to-elegant-alignment/ #ipv6 #blog #apnic

2

0

2

0

muddle 🥣 @muddle@infosec.exchange · Jul 20, 2026

Anyone out there an expert on #IPv6? I'm thinking of setting up a home lab type thing with various different kinds of servers in a sort of ad-hoc network (plug stuff into whatever ports are available, but make sure that each machine is reachable to every other machine). I know IPv4 and have a reasonable idea about how IPv6 works. It seems I could do like IPv4 with static subnet assignments and routing rules but I'm wondering to what extent this sort of ad-hoc network could self-organise, so to speak. If that's even possible. I think that it should be possible to authenticate Routing Advertisement packets by using a pre-shared key and IPSEC (of which I know pretty much nothing, but I assume it has to be able to do this) so that any box that does routing can recognise peer routers and trust that their routing info is authentic, as opposed to just random nodes that pump out fake RA packets. I can totally do the IPv4-style networking where I hand-craft all the subnets and routing tables (and having an STP-style algorithm to determine reachability), but I'm just wondering if there's a way to implement a generic "trusted router" black box for such nets? As in, just a way of signalling that the RA packets from these machines are most likely legitimate?

0

About This Hashtag

#ipv6

Related