From d47d5a2bed8739f3598d997f5b3caed4fbb6d0cb Mon Sep 17 00:00:00 2001 From: Pim van Pelt Date: Sun, 15 Feb 2026 14:10:14 +0100 Subject: [PATCH] typo fix --- content/articles/2025-07-12-vpp-evpn-1.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/articles/2025-07-12-vpp-evpn-1.md b/content/articles/2025-07-12-vpp-evpn-1.md index 87edd6f..96b494e 100644 --- a/content/articles/2025-07-12-vpp-evpn-1.md +++ b/content/articles/2025-07-12-vpp-evpn-1.md @@ -101,7 +101,7 @@ configuration: {{< image width="6em" float="left" src="/assets/shared/brain.png" alt="brain" >}} For the controlplane parts, [[FRRouting](https://frrouting.org/)] has a working implementation for -L2 (MAC-VRF) and L3 (IP-VRF). My favorite, [[Bird](https://birg.nic.cz/)], is slowly catching up, and +L2 (MAC-VRF) and L3 (IP-VRF). My favorite, [[Bird](https://bird.nic.cz/)], is slowly catching up, and has a few of these controlplane parts already working (mostly MAC-VRF). Commercial vendors like Arista, Nokia, Juniper, Cisco are ready to go. If we want VPP to inter-operate, we may need to make a few changes.