netlab 26.04: EXOS, BGP Prefix Origination, More Static Routes

netlab release 26.04 is out. Here are the highlights:

• Extreme Networks EXOS is supported as a Vagrant box or containerlab node with OSPF, VLAN, and VRRP configuration (by Seb d’Argoeuves).
• The new bgp.advertise node attribute allows you to advertise networks in the IP routing table into BGP. It’s supported on most platforms.
• The bgp.originate attribute is now dual-stack and VRF-aware, allowing you to originate IPv4 and IPv6 prefixes into per-VRF BGP instances.
• New platforms with static route support: FortiOS (by Aleksey Popov), Nexus OS, Nokia SR OS, Nokia SR Linux. OpenBSD got discard static routes.

Public Videos: Docker 101

While according to the GIFEE True Believers™, Docker is dead and Kubernetes rules the world, people who want to have a bit of life might be perfectly happy running “obsolete” stuff like Docker on their laptops or Linux VMs.

If you happen to be one of the latter, you might like the Introduction to Docker webinar I put together a few years ago. It’s now public; you can watch it with an ipSpace.net account.

Looking for more binge-watching materials? You’ll find them here.

Interoperability of EVPN/VXLAN with IPv6 Next Hops

FRRouting release 10.6 promised “BGP IPv6 VTEP support,” claiming “it enables EVPN deployments using IPv6 tunnel endpoints while maintaining full backward compatibility with IPv4 VTEPs.” Of course, I had to try it out, and since we already have EVPN over IPv6 running on Arista EOS (since netlab release 26.01), I decided to set up a simple lab with an Arista cEOS device running release 4.35.2F and the latest FRRouting container.

I was not exactly surprised when it did not work. While Arista accepted FRRouting EVPN routes, the FRRouting BGP daemon rejected routes sent by Arista EOS:

Worth Reading: Shameless Guesses, Not Hallucinations

In a recent article, Scott Alexander made an interesting point: What AI produces are not hallucinations but shameless guesses (also known as bullshit) because the training process rewards the correct answers but does not penalize the incorrect ones. After all, having an AI model say, “I don’t know that” is not good for business, is it?

On a tangential note, calling those blunders hallucinations was a marketing masterstroke. Not being a native English speaker, I might be missing some nuances, but I feel like hallucinations might be something you’re not responsible for (some of the time), whereas we all know who’s responsible for bullshit and shameless guesses – and responsibility is something the AI companies are clearly trying to stay as far away from as possible.

On another tangential note, if you’re not following Scott Alexander’s blog substack, you’re missing out.