<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>VXLAN on Tristan Germain</title><link>https://tristangermain.com/tags/vxlan/</link><description>Recent content in VXLAN on Tristan Germain</description><generator>Hugo -- gohugo.io</generator><language>en-us</language><copyright>© Tristan Germain</copyright><lastBuildDate>Mon, 10 Aug 2026 15:52:46 +0200</lastBuildDate><atom:link href="https://tristangermain.com/tags/vxlan/index.xml" rel="self" type="application/rss+xml"/><item><title>Network multi-tenancy - 4. Distributed multi-tenancy</title><link>https://tristangermain.com/posts/evpn/4-distributed-multi-tenancy/</link><pubDate>Mon, 10 Aug 2026 15:52:46 +0200</pubDate><guid>https://tristangermain.com/posts/evpn/4-distributed-multi-tenancy/</guid><description>Fourth post of a series on a deep, software-engineer-oriented exploration of how a modern datacenter network provides multi-tenancy, starting from the physical topology and progressively explaining the protocols and mechanisms that make the system work. It is strongly advised to read the intro first if not familiar with concepts such as clos topology and network multi-tenancy.
This one explains how servers belonging to the same tenant can be attached to different leaf switches in a clos topology and still being able to communicate among each other through the same L2 broadcast domain.</description></item><item><title>Network multi-tenancy - 3. Leaf local tenants isolation</title><link>https://tristangermain.com/posts/evpn/3-local-tenants-isolation/</link><pubDate>Sun, 09 Aug 2026 19:18:22 +0200</pubDate><guid>https://tristangermain.com/posts/evpn/3-local-tenants-isolation/</guid><description>Third post of a series on a deep, software-engineer-oriented exploration of how a modern datacenter network provides multi-tenancy, starting from the physical topology and progressively explaining the protocols and mechanisms that make the system work. It is strongly advised to read the intro first if not familiar with concepts such as clos topology and network multi-tenancy.
This one explains how leaf switches manage local isolation between attached servers that belongs to different tenants.</description></item><item><title>Network multi-tenancy - 2. Leaf reachability</title><link>https://tristangermain.com/posts/evpn/2-leaf-reachability/</link><pubDate>Fri, 07 Aug 2026 10:31:01 +0200</pubDate><guid>https://tristangermain.com/posts/evpn/2-leaf-reachability/</guid><description>Second post of a series on a deep, software-engineer-oriented exploration of how a modern datacenter network provides multi-tenancy, starting from the physical topology and progressively explaining the protocols and mechanisms that make the system work. It is strongly advised to read the intro first if not familiar with concepts such as clos topology and network multi-tenancy.
This one explains how switches connected to the servers and external networks communicate among each other.</description></item><item><title>Network multi-tenancy - 1. Intro</title><link>https://tristangermain.com/posts/evpn/1-intro/</link><pubDate>Sat, 01 Aug 2026 21:12:37 +0200</pubDate><guid>https://tristangermain.com/posts/evpn/1-intro/</guid><description>This is the first post of a series on a deep, software-engineer-oriented exploration of how a modern datacenter network provides multi-tenancy, starting from the physical topology and progressively explaining the protocols and mechanisms that make the system work.
I had to train myself on the subject for unStack, a start-up I co-founded. I read many informative books like Cloud Native Data Center Networking by Dinesh G. Dutt. But, as these topics interest a restricted number of people, mostly composed of network engineers, deep technical books assume a way of reasoning about the technology which is quite different from software engineer&amp;rsquo;s mental model.</description></item></channel></rss>