<?xml version="1.0" encoding="utf-8"?><?xml-stylesheet type="text/xsl" href="/feed.xsl"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Evpn · Darren Qu</title><link>https://darrenqu.net/tags/evpn/</link><description>Technical writing on network engineering: campus and WAN, hybrid cloud interconnect, automation and observability, and the data center fabrics — InfiniBand, RoCE, Spectrum-X — underneath GPU clusters.</description><generator>Hugo</generator><language>en-US</language><managingEditor>Darren Qu</managingEditor><webMaster>Darren Qu</webMaster><copyright>2026 Darren Qu</copyright><atom:link href="https://darrenqu.net/tags/evpn/index.xml" rel="self" type="application/rss+xml"/><lastBuildDate>Wed, 16 Sep 2026 00:00:00 +0000</lastBuildDate><item><title>EVPN Multihoming Across Vendors, Part 2: Verifying the Forwarding Plane</title><link>https://darrenqu.net/ai-networking/evpn-multihoming-across-vendors-part-2/</link><pubDate>Wed, 16 Sep 2026 00:00:00 +0000</pubDate><guid isPermaLink="true">https://darrenqu.net/ai-networking/evpn-multihoming-across-vendors-part-2/</guid><category>AI Networking</category><category>evpn</category><description>The control plane agrees on the Designated Forwarder and the host still receives every broadcast twice. Multi-point captures, a same-vendor control group, and a packet capture that was quietly lying.</description></item><item><title>EVPN Multihoming Across Vendors, Part 1: From Configuration to Control Plane Alignment</title><link>https://darrenqu.net/ai-networking/evpn-multihoming-across-vendors-part-1/</link><pubDate>Wed, 16 Sep 2026 00:00:00 +0000</pubDate><guid isPermaLink="true">https://darrenqu.net/ai-networking/evpn-multihoming-across-vendors-part-1/</guid><category>AI Networking</category><category>evpn</category><description>Four leaves, two vendors, one Ethernet Segment. Five configuration differences between Cumulus and Arista stand between the RFC and a working all-active bond — four get solved here, and none of them are in the RFC.</description></item></channel></rss>