<?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 Support Tools</title><link>https://support.tools/tags/vxlan/</link><description>Recent content in VXLAN on Support Tools</description><generator>Hugo</generator><language>en-US</language><lastBuildDate>Sun, 25 Oct 2026 09:00:00 -0500</lastBuildDate><atom:link href="https://support.tools/tags/vxlan/index.xml" rel="self" type="application/rss+xml"/><item><title>Cilium MTU Black Hole: How a Linux Bridge and KubeVirt VMs Silently Broke VXLAN and Kept Longhorn Degraded</title><link>https://support.tools/cilium-mtu-linux-bridge-kubevirt-vxlan-blackhole-longhorn-degraded/</link><pubDate>Sun, 25 Oct 2026 09:00:00 -0500</pubDate><guid>https://support.tools/cilium-mtu-linux-bridge-kubevirt-vxlan-blackhole-longhorn-degraded/</guid><description>&lt;p&gt;For about ten hours, roughly 45 Longhorn volumes on one of our production RKE2 clusters sat in a degraded state. Replicas flapped to &lt;code&gt;ERR&lt;/code&gt;, rebuilds started and failed, and the Longhorn event stream logged more than 1,400 replica errors, nearly 800 of them in a single hour on one node. Small API calls worked. DNS worked. Health checks were green. Only bulk traffic between certain pairs of nodes was disappearing, and which pairs changed over the course of the day.&lt;/p&gt;&#10;&lt;p&gt;The cause turned out to be three ordinary behaviors stacked on top of each other. A Linux bridge takes the MTU of its smallest port. KubeVirt VMs attach 1500-byte veths to that bridge. And Cilium, with no MTU configured, does not just read the device MTU at startup: it follows it while running. Pods keep the MTU they were created with. So every time a VM moved onto or off a node, that node&amp;rsquo;s tunnel MTU changed underneath pods that still believed the old value, and their large VXLAN packets went into a black hole with no error anywhere.&lt;/p&gt;&#10;&lt;p&gt;This post walks through the mechanism, a reproducible demonstration of the bridge behavior, the commands that prove it on a live cluster, the fix (pin the MTU, flatten the underlay), and the planned full-cluster outage it took to apply that fix safely.&lt;/p&gt;</description></item><item><title>Networking</title><link>https://support.tools/training/networking/</link><pubDate>Fri, 25 Oct 2024 00:00:00 +0000</pubDate><guid>https://support.tools/training/networking/</guid><description>&lt;p&gt;Welcome to our comprehensive networking training section. Here you&amp;rsquo;ll find detailed guides and tutorials covering everything from basic networking concepts to advanced topics in modern cloud-native networking.&lt;/p&gt;&#10;&lt;h2 id="core-networking-concepts"&gt;Core Networking Concepts&lt;/h2&gt;&#10;&lt;ul&gt;&#10;&lt;li&gt;&lt;a href="https://support.tools/training/networking/networking-101/"&gt;Networking 101&lt;/a&gt;: TCP/IP, subnets, and fundamental concepts&lt;/li&gt;&#10;&lt;li&gt;&lt;a href="https://support.tools/training/networking/vxlan/"&gt;Understanding VXLAN&lt;/a&gt;: Deep dive into Virtual Extensible LAN&lt;/li&gt;&#10;&lt;li&gt;&lt;a href="https://support.tools/training/networking/security/"&gt;Network Security Fundamentals&lt;/a&gt;: Firewalls, encryption, and security best practices&lt;/li&gt;&#10;&lt;/ul&gt;&#10;&lt;h2 id="container-and-cloud-networking"&gt;Container and Cloud Networking&lt;/h2&gt;&#10;&lt;ul&gt;&#10;&lt;li&gt;&lt;a href="https://support.tools/training/networking/kubernetes-vxlan/"&gt;Kubernetes VXLAN Networking&lt;/a&gt;: How Kubernetes uses VXLAN for overlay networks&lt;/li&gt;&#10;&lt;li&gt;&lt;a href="https://support.tools/training/networking/cni/"&gt;Container Network Interface (CNI)&lt;/a&gt;: Understanding Kubernetes networking plugins&lt;/li&gt;&#10;&lt;li&gt;&lt;a href="https://support.tools/training/networking/service-mesh/"&gt;Service Mesh Architecture&lt;/a&gt;: Modern microservices networking&lt;/li&gt;&#10;&lt;/ul&gt;&#10;&lt;h2 id="advanced-topics"&gt;Advanced Topics&lt;/h2&gt;&#10;&lt;ul&gt;&#10;&lt;li&gt;Network Troubleshooting: Tools and techniques for debugging network issues&lt;/li&gt;&#10;&lt;li&gt;Network Performance: Optimization and monitoring&lt;/li&gt;&#10;&lt;li&gt;Software-Defined Networking: Modern approaches to network management&lt;/li&gt;&#10;&lt;/ul&gt;&#10;&lt;h2 id="hands-on-labs"&gt;Hands-on Labs&lt;/h2&gt;&#10;&lt;ul&gt;&#10;&lt;li&gt;Setting up a VXLAN Network&lt;/li&gt;&#10;&lt;li&gt;&lt;a href="https://support.tools/training/networking/cni-lab/"&gt;Kubernetes CNI Implementation&lt;/a&gt;&lt;/li&gt;&#10;&lt;li&gt;Network Monitoring Lab&lt;/li&gt;&#10;&lt;/ul&gt;&#10;&lt;p&gt;Each section includes practical examples, diagrams, and real-world scenarios to help you understand and implement networking concepts effectively.&lt;/p&gt;</description></item><item><title>How Kubernetes Uses VXLAN for Overlay Networking</title><link>https://support.tools/training/networking/kubernetes-vxlan/</link><pubDate>Thu, 24 Oct 2024 00:00:00 +0000</pubDate><guid>https://support.tools/training/networking/kubernetes-vxlan/</guid><description>&lt;h1 id="how-kubernetes-uses-vxlan-for-overlay-networking"&gt;How Kubernetes Uses VXLAN for Overlay Networking&lt;/h1&gt;&#10;&lt;p&gt;Kubernetes needs to create a &lt;strong&gt;virtual network&lt;/strong&gt; that connects pods across multiple nodes seamlessly. Since these pods reside in isolated networks, &lt;strong&gt;overlay networks&lt;/strong&gt;—like those implemented with &lt;strong&gt;VXLAN&lt;/strong&gt;—allow them to communicate over a physical Layer 3 infrastructure.&lt;/p&gt;&#10;&lt;p&gt;In this post, we explore &lt;strong&gt;how Kubernetes uses VXLAN&lt;/strong&gt; to build an overlay network, enabling communication between pods across nodes.&lt;/p&gt;&#10;&lt;hr&gt;&#10;&lt;h2 id="1-what-is-an-overlay-network"&gt;1. What is an Overlay Network?&lt;/h2&gt;&#10;&lt;p&gt;In Kubernetes, an &lt;strong&gt;overlay network&lt;/strong&gt; abstracts the physical network, allowing &lt;strong&gt;pods on different nodes&lt;/strong&gt; to communicate as if they were on the &lt;strong&gt;same Layer 2 network&lt;/strong&gt;. VXLAN is one of the most popular protocols for building this overlay.&lt;/p&gt;</description></item><item><title>Understanding VXLAN</title><link>https://support.tools/training/networking/vxlan/</link><pubDate>Thu, 24 Oct 2024 00:00:00 +0000</pubDate><guid>https://support.tools/training/networking/vxlan/</guid><description>&lt;h1 id="understanding-vxlan-virtual-extensible-lan"&gt;Understanding VXLAN: Virtual Extensible LAN&lt;/h1&gt;&#10;&lt;p&gt;Virtual Extensible LAN (VXLAN) is a network virtualization technology that helps extend Layer 2 networks over Layer 3 infrastructure. It’s a key enabler in modern data centers, especially in cloud environments, providing scalable overlay networks for virtual machines and containers.&lt;/p&gt;&#10;&lt;hr&gt;&#10;&lt;h2 id="1-what-is-vxlan"&gt;1. What is VXLAN?&lt;/h2&gt;&#10;&lt;p&gt;VXLAN is a &lt;strong&gt;network overlay protocol&lt;/strong&gt; that allows you to create a virtual Layer 2 network over a physical Layer 3 network. It encapsulates Ethernet frames in UDP packets, enabling the deployment of virtual networks across large, distributed environments.&lt;/p&gt;</description></item></channel></rss>