Finding good content in the swamp of AI slop is hard, and whenever I find a blog post worth reading, I’d like to know when the author publishes the next one.
For stupid reasons (like a day having only 24 hours, and me having a life), I can’t periodically scan all websites I find interesting, but fortunately, I don’t have to. Two well-known mechanisms work reliably: email updates and RSS feeds.
A library of Calico tools and skills — delivered through the Calico MCP Server
Anyone who has operated Kubernetes networking at scale knows the shape of a bad day. A request that should succeed is quietly failing. The application team swears nothing changed. Somewhere across a stack of tiers, selectors, and policies, some written last week and some inherited from an engineer who left two years ago, a rule is denying the traffic. Finding it means reading YAML, cross-referencing flow logs, and reconstructing the policy evaluation order in your head. For a genuinely knotty case, that work can stretch across days and pull in more than one team before anyone gets to the bottom of it.
I think that day is about to get a lot shorter. Today we’re introducing Mylo, an expert for Calico that works inside the AI tools your teams already use. Ask Mylo why a pod can’t reach a service, and it traces the path, points to the exact policy and rule doing the blocking, and explains why in plain language, in about the time it took you to read this paragraph. Mylo Continue reading
The beauty of SR-MPLS is that it’s a drop-in replacement for the traditional (LDP- or RSVP-based) MPLS control plane. For example, you could replace LDP with SR-MPLS in a network using MPLS to implement a BGP-free transport core, and it just keeps working.
This scenario was the first “fun” scenario in the ITNOG10 Segment Routing workshop. The core network uses the same topology as in the previous examples; I added two hosts and BGP routing.
Simplest possible network using a BGP-free core
The vrnetlab project and its containerlab fork implement a wonderful idea: let’s package virtual machines (primarily network devices that cannot be containerized) as containers to use reliable orchestration tools like containerlab to provision network topologies.
That approach might have a few drawbacks (depending on how the container images are built), but the obvious elephant in the room is: how do you make the virtual network plumbing work?
The goal of this guide is to explain how to configure TorBox to use a […]
The post How to Set TorBox wlan1 as WAN on RPi 3B first appeared on Brezular's Blog.
I’ve noticed something in the last few weeks that might drive me crazy. I’m sure you noticed it too. There are people talking about things and they’re ready to join your community. Just click on this notification to learn more!
Earlier this year I talked about how everything seems to be geared to disrupt our attention. At that time, I thought it would get better by just ignoring the notifications and removing them from my devices to reduce it to the minimum. I think the providers read my post because they found even more ways to get to me. I think they have it out for me.
Attention is a resource like money or oil or the amount of hydrogen atoms in the sun. It has a finite limit and we only have so much to work with. Every disruption causes us to switch contexts and try to manage it. As I mentioned, I went about removing as much of that distraction as I could. Because having my focus be on a task and not on a cute popup banner is important for work and the other things that I do.
Thankfully, the social media apps found a Continue reading
After
enabling IPv6 on the Ethernet0 interface, we can configure BGP peering. Instead of statically defining a peer IP address and AS number, the
BGP neighbor is defined at the interface level. This tells BGP to expect a neighbor
and initialize the BGP peering over Ethernet0. Because our intent is to transport IPv4 traffic
over the IPv6 network, we activate both the IPv4 and IPv6 address families. We
also configure the peer as an external BGP (eBGP) neighbor by using a command remote-as external. This tells BGP that the peer must use an AS
number different from the local AS number.
Because the network uses IPv6 as the
transport for IPv4 traffic, IPv4 Network Layer Reachability Information (NLRI) exchanged
through BGP use IPv6 next-hop addresses. BGP therefore needs the Extended Next
Hop Encoding capability to support IPv4 routes with IPv6 next hops. In this
configuration, the capability is explicitly enabled with the capability extended-nexthop
command.
In FRRouting, the v6only option controls which IP version is used for interface-based BGP Unnumbered peering. Without v6only, FRR uses the interface's IPv6 link-local address for peering only when no suitable IPv4 address is configured on the interface. With v6only, FRR skips Continue reading
I sure wish Tony Mattke had started publishing his Git-related blog posts in 2017 when I was still struggling with the basics. In his latest Going Pro article he covers:
Absolutely worth every second you’ll spend reading the article!