is-is is the superior IGP, watch this from the start to the end:
www.youtube.com/watch?v=jWdD...
Posts by Daryll Swer
Ha, I didn't know this information was archived online. Funnily enough it says the object disappeared into the "Lum (meaning mountain or hill) Swer" forest, didn't know that detail. I've been to that forest before, it's named after my clan's surname.
I think there was probably 3-5 more sightings.
In K8s I believe a custom CNI that permits seperate subnets per-Pod should in theory do the trick.
I am not K8s pro, but in Docker this is easily achieved: Use different subnets for Anycast/unicast, container is exposed to WAN on both subnets natively, no reverse proxy. As long as container app talks SIP/Other protocols, it should work. BGP handles routing with the leave switches.
Quick research suggests TPROXY is ossified and limited only to TCP/UDP. This leaves out all other standardised layer 3/4 protocols (including native IPSec in IPv6 without UDP encap hack).
Ideally there exists an implementation that allows stable Anycast addresses for end user access (seperate ephemeral unicast for Pod-to-pod and intra-cluster traffic).
What if my application is SIP server using native SIP (no UDP) or native SCTP? Ideally I'd like to avoid reverse proxy of any kind.
That's just just unicast, right? Or Anycast for global ingress + seperate unicast for pod-to-pod comms or pod-to-WAN comms.
Also cover BGP ECMP/Anycast of pods + seperate GUA addressing for unique unicast per node to eliminate the need for GENEVE or other host-to-host tunnelling. Would love to see a single blog post or blog post that covers this end-to-end.
This is the way.
Can you shoot me a text on Telegram? I think there's a way to solve it by NOT using popular CNIs, rather a custom implementation straight out of network engineering textbooks.
Let's discuss further in DMs. I'm not a K8s guy, but I'm keen to have truly NAT-less IPv6 everywhere.
Is it truly NAT-less IPv6 or there's DNAT66 happening on ingress? Or it's true BGP anycast + ECMP LB across the network infrastructure.
BGP-to-the-host is an industry standard design. And it's free to do it at zero cost with FRR and BGP unnumbered combined with correctly done IPv6 Architecture of underlay and overlay (VXLAN/EVPN may come into play depending on your situation).
If you're talking about macOS/Windows then ia_pd.
daemon.json isn't the modern way of using ROUTED mode in Docker:
docs.docker.com/engine/relea...
Docker Compose follows declarative config management and I would recommend it.
Sharing the container's namespace/veth broadcast domain with underlay layer 3 router isn't routing, that's basically bridging.
Routing implies no Layer 2 bs, pure layer 3 with routing protocols. If you want to build scalable networks with BGP/ECMP/Anycast, routing is the way.
Docker has not required the daemon.json params for a whole year now.
www.daryllswer.com/how-to-confi...
github.com/docker/docs/...
1. Stop using RAs/SLAAC in a production environment, use unnumbered eBGP-to-the-host design in your clos fabric.
2. Enable Routed IPv6 mode in Docker Compose.
3. The rest is history.
www.daryllswer.com/how-to-confi...
#IPv6 implementation by varying “experts” across the globe often leads to failures like this one:
www.reddit.com/r/ipv6/comme...
It's definitely better than legacy phpBB. If only their network code also had such a massive upgrade and came with SR-MPLS IPv6!
Ever wondered what it’s like to bring physical IP transit directly to your home over #MPLS? I pulled it off — twice — in India.
#BGP, #IXP, fibre runs, barter deals, and plenty of Layer 8 chaos. Blog post up now👇
www.daryllswer.com/how-to-bring...
#IPTransit #NetEng #IPTTTH #AS149794
You don't need scripts and you shouldn't be messing with that "enable_ipv6" flag at all on latest Docker versions.
I published a blog post to address this, later I'll link it on the open GitHub issue I created on Docker repo as well:
bsky.app/profile/dary...
Think native IPv6 in Docker is rocket science? 🚀 It’s not.
Set up routed IPv6 with Docker Compose—no NAT66, no bridging, just pure Layer 3 connectivity via routing.
Blog post up now👇
www.daryllswer.com/how-to-confi...
#IPv6 #Docker #Networking #Routing #Containers #DevOps #NetEng #BGP
Helped fix a network mess at a non-profit where “certified experts” left behind broken #IPv6, triple #NAT, and the wrong hardware. Might not have been incompetence—might’ve been intentional.
Full story + tech details on LinkedIn 👇
www.linkedin.com/posts/daryll...
#NetEng #CGNAT #NetworkEngineering
Always nice to see, how my work has positively helped both network business owners and network engineers across the world.
#IPv6 and #BGP FTW!
www.linkedin.com/posts/ekowny...
That isn't the correct way to do routed IPv6 in Docker. Some references here:
github.com/docker/docs/...
daemon.json should be empty.
Yet another post about #CGNAT - because the #internet still hasn’t learnt. It’s 2025, and we’re still patching #IPv4 with CGNAT instead of embracing #routing with #IPv6.
Shout out to @FastNetMon for sponsoring this article!
www.daryllswer.com/lets-talk-ab...
#NetEng #NetworkEngineering
Please read and circulate this explainer from @telegeography.bsky.social that debunks the recent sensationalist headlines stemming from the filing of a Chinese patent for a subsea cable cutter (cut and hold grapnel):
blog.telegeography.com/demystifying...
"AI" would suggest a human brain equivalent that's verified by a neurologist.
Do you mean, LLMs? I've found most aren't anti-LLM in our community, I use it myself. But it's absolutely trash at generating complex configurations.
Nice to see that my IPv6 Architecture guide has been helpful enough to inspire ISPs in the USA to adopt BCOP-690—especially with a static /48 prefix delegation for residential customers to boot!
#NetworkEngineering #NetEng #IPv6