From 337fbe4cced2ebeeef6e257de005f58e9290e88d Mon Sep 17 00:00:00 2001 From: Christopher Tauchen Date: Tue, 19 May 2026 16:14:51 +0100 Subject: [PATCH] Remove broken link --- calico-cloud/networking/configuring/mtu.mdx | 2 +- .../version-22-2/networking/configuring/mtu.mdx | 2 +- calico-enterprise/networking/configuring/mtu.mdx | 2 +- .../version-3.20-2/networking/configuring/mtu.mdx | 2 +- .../version-3.21-2/networking/configuring/mtu.mdx | 2 +- .../version-3.22-2/networking/configuring/mtu.mdx | 2 +- .../version-3.23-1/networking/configuring/mtu.mdx | 2 +- calico/networking/configuring/mtu.mdx | 2 +- .../version-3.29/networking/configuring/mtu.mdx | 2 +- .../version-3.30/networking/configuring/mtu.mdx | 2 +- .../version-3.31/networking/configuring/mtu.mdx | 2 +- .../version-3.32/networking/configuring/mtu.mdx | 2 +- 12 files changed, 12 insertions(+), 12 deletions(-) diff --git a/calico-cloud/networking/configuring/mtu.mdx b/calico-cloud/networking/configuring/mtu.mdx index 884a4a4f0d..7d5303e3da 100644 --- a/calico-cloud/networking/configuring/mtu.mdx +++ b/calico-cloud/networking/configuring/mtu.mdx @@ -60,7 +60,7 @@ The following table lists common MTU sizes for $[prodname] environments. Because **Recommended MTU for overlay networking** -The extra overlay header used in IP in IP, VXLAN and WireGuard protocols, reduces the minimum MTU by the size of the header. (IP in IP uses a 20-byte header, IPv4 VXLAN uses a 50-byte header, IPv6 VXLAN uses a 70-byte header, IPv4 WireGuard uses a [60-byte header](https://lists.zx2c4.com/pipermail/wireguard/2017-December/002201.html) and IPv6 WireGuard uses an 80-byte header). +The extra overlay header used in IP in IP, VXLAN and WireGuard protocols, reduces the minimum MTU by the size of the header. (IP in IP uses a 20-byte header, IPv4 VXLAN uses a 50-byte header, IPv6 VXLAN uses a 70-byte header, IPv4 WireGuard uses a 60-byte header and IPv6 WireGuard uses an 80-byte header). When using AKS, the underlying network has an [MTU of 1400](https://docs.microsoft.com/en-us/azure/virtual-network/virtual-network-tcpip-performance-tuning#azure-and-vm-mtu), even though the network interface will have an MTU of 1500. WireGuard sets the Don't Fragment (DF) bit on its packets, and so the MTU for WireGuard on AKS needs to be set to 60 bytes below (or 80 bytes for IPv6) the 1400 MTU of the underlying network to avoid dropped packets. diff --git a/calico-cloud_versioned_docs/version-22-2/networking/configuring/mtu.mdx b/calico-cloud_versioned_docs/version-22-2/networking/configuring/mtu.mdx index 884a4a4f0d..7d5303e3da 100644 --- a/calico-cloud_versioned_docs/version-22-2/networking/configuring/mtu.mdx +++ b/calico-cloud_versioned_docs/version-22-2/networking/configuring/mtu.mdx @@ -60,7 +60,7 @@ The following table lists common MTU sizes for $[prodname] environments. Because **Recommended MTU for overlay networking** -The extra overlay header used in IP in IP, VXLAN and WireGuard protocols, reduces the minimum MTU by the size of the header. (IP in IP uses a 20-byte header, IPv4 VXLAN uses a 50-byte header, IPv6 VXLAN uses a 70-byte header, IPv4 WireGuard uses a [60-byte header](https://lists.zx2c4.com/pipermail/wireguard/2017-December/002201.html) and IPv6 WireGuard uses an 80-byte header). +The extra overlay header used in IP in IP, VXLAN and WireGuard protocols, reduces the minimum MTU by the size of the header. (IP in IP uses a 20-byte header, IPv4 VXLAN uses a 50-byte header, IPv6 VXLAN uses a 70-byte header, IPv4 WireGuard uses a 60-byte header and IPv6 WireGuard uses an 80-byte header). When using AKS, the underlying network has an [MTU of 1400](https://docs.microsoft.com/en-us/azure/virtual-network/virtual-network-tcpip-performance-tuning#azure-and-vm-mtu), even though the network interface will have an MTU of 1500. WireGuard sets the Don't Fragment (DF) bit on its packets, and so the MTU for WireGuard on AKS needs to be set to 60 bytes below (or 80 bytes for IPv6) the 1400 MTU of the underlying network to avoid dropped packets. diff --git a/calico-enterprise/networking/configuring/mtu.mdx b/calico-enterprise/networking/configuring/mtu.mdx index d284ed2c7d..ab660d3891 100644 --- a/calico-enterprise/networking/configuring/mtu.mdx +++ b/calico-enterprise/networking/configuring/mtu.mdx @@ -60,7 +60,7 @@ The following table lists common MTU sizes for $[prodname] environments. Because **Recommended MTU for overlay networking** -The extra overlay header used in IP in IP, VXLAN and WireGuard protocols, reduces the minimum MTU by the size of the header. (IP in IP uses a 20-byte header, IPv4 VXLAN uses a 50-byte header, IPv6 VXLAN uses a 70-byte header, IPv4 WireGuard uses a [60-byte header](https://lists.zx2c4.com/pipermail/wireguard/2017-December/002201.html) and IPv6 WireGuard uses an 80-byte header). +The extra overlay header used in IP in IP, VXLAN and WireGuard protocols, reduces the minimum MTU by the size of the header. (IP in IP uses a 20-byte header, IPv4 VXLAN uses a 50-byte header, IPv6 VXLAN uses a 70-byte header, IPv4 WireGuard uses a 60-byte header and IPv6 WireGuard uses an 80-byte header). When using AKS, the underlying network has an [MTU of 1400](https://docs.microsoft.com/en-us/azure/virtual-network/virtual-network-tcpip-performance-tuning#azure-and-vm-mtu), even though the network interface will have an MTU of 1500. WireGuard sets the Don't Fragment (DF) bit on its packets, and so the MTU for WireGuard on AKS needs to be set to 60 bytes below (or 80 bytes for IPv6) the 1400 MTU of the underlying network to avoid dropped packets. diff --git a/calico-enterprise_versioned_docs/version-3.20-2/networking/configuring/mtu.mdx b/calico-enterprise_versioned_docs/version-3.20-2/networking/configuring/mtu.mdx index a46090b002..e9d5975aa0 100644 --- a/calico-enterprise_versioned_docs/version-3.20-2/networking/configuring/mtu.mdx +++ b/calico-enterprise_versioned_docs/version-3.20-2/networking/configuring/mtu.mdx @@ -60,7 +60,7 @@ The following table lists common MTU sizes for $[prodname] environments. Because **Recommended MTU for overlay networking** -The extra overlay header used in IP in IP, VXLAN and WireGuard protocols, reduces the minimum MTU by the size of the header. (IP in IP uses a 20-byte header, IPv4 VXLAN uses a 50-byte header, IPv6 VXLAN uses a 70-byte header, IPv4 WireGuard uses a [60-byte header](https://lists.zx2c4.com/pipermail/wireguard/2017-December/002201.html) and IPv6 WireGuard uses an 80-byte header). +The extra overlay header used in IP in IP, VXLAN and WireGuard protocols, reduces the minimum MTU by the size of the header. (IP in IP uses a 20-byte header, IPv4 VXLAN uses a 50-byte header, IPv6 VXLAN uses a 70-byte header, IPv4 WireGuard uses a 60-byte header and IPv6 WireGuard uses an 80-byte header). When using AKS, the underlying network has an [MTU of 1400](https://docs.microsoft.com/en-us/azure/virtual-network/virtual-network-tcpip-performance-tuning#azure-and-vm-mtu), even though the network interface will have an MTU of 1500. WireGuard sets the Don't Fragment (DF) bit on its packets, and so the MTU for WireGuard on AKS needs to be set to 60 bytes below (or 80 bytes for IPv6) the 1400 MTU of the underlying network to avoid dropped packets. diff --git a/calico-enterprise_versioned_docs/version-3.21-2/networking/configuring/mtu.mdx b/calico-enterprise_versioned_docs/version-3.21-2/networking/configuring/mtu.mdx index a46090b002..e9d5975aa0 100644 --- a/calico-enterprise_versioned_docs/version-3.21-2/networking/configuring/mtu.mdx +++ b/calico-enterprise_versioned_docs/version-3.21-2/networking/configuring/mtu.mdx @@ -60,7 +60,7 @@ The following table lists common MTU sizes for $[prodname] environments. Because **Recommended MTU for overlay networking** -The extra overlay header used in IP in IP, VXLAN and WireGuard protocols, reduces the minimum MTU by the size of the header. (IP in IP uses a 20-byte header, IPv4 VXLAN uses a 50-byte header, IPv6 VXLAN uses a 70-byte header, IPv4 WireGuard uses a [60-byte header](https://lists.zx2c4.com/pipermail/wireguard/2017-December/002201.html) and IPv6 WireGuard uses an 80-byte header). +The extra overlay header used in IP in IP, VXLAN and WireGuard protocols, reduces the minimum MTU by the size of the header. (IP in IP uses a 20-byte header, IPv4 VXLAN uses a 50-byte header, IPv6 VXLAN uses a 70-byte header, IPv4 WireGuard uses a 60-byte header and IPv6 WireGuard uses an 80-byte header). When using AKS, the underlying network has an [MTU of 1400](https://docs.microsoft.com/en-us/azure/virtual-network/virtual-network-tcpip-performance-tuning#azure-and-vm-mtu), even though the network interface will have an MTU of 1500. WireGuard sets the Don't Fragment (DF) bit on its packets, and so the MTU for WireGuard on AKS needs to be set to 60 bytes below (or 80 bytes for IPv6) the 1400 MTU of the underlying network to avoid dropped packets. diff --git a/calico-enterprise_versioned_docs/version-3.22-2/networking/configuring/mtu.mdx b/calico-enterprise_versioned_docs/version-3.22-2/networking/configuring/mtu.mdx index d284ed2c7d..ab660d3891 100644 --- a/calico-enterprise_versioned_docs/version-3.22-2/networking/configuring/mtu.mdx +++ b/calico-enterprise_versioned_docs/version-3.22-2/networking/configuring/mtu.mdx @@ -60,7 +60,7 @@ The following table lists common MTU sizes for $[prodname] environments. Because **Recommended MTU for overlay networking** -The extra overlay header used in IP in IP, VXLAN and WireGuard protocols, reduces the minimum MTU by the size of the header. (IP in IP uses a 20-byte header, IPv4 VXLAN uses a 50-byte header, IPv6 VXLAN uses a 70-byte header, IPv4 WireGuard uses a [60-byte header](https://lists.zx2c4.com/pipermail/wireguard/2017-December/002201.html) and IPv6 WireGuard uses an 80-byte header). +The extra overlay header used in IP in IP, VXLAN and WireGuard protocols, reduces the minimum MTU by the size of the header. (IP in IP uses a 20-byte header, IPv4 VXLAN uses a 50-byte header, IPv6 VXLAN uses a 70-byte header, IPv4 WireGuard uses a 60-byte header and IPv6 WireGuard uses an 80-byte header). When using AKS, the underlying network has an [MTU of 1400](https://docs.microsoft.com/en-us/azure/virtual-network/virtual-network-tcpip-performance-tuning#azure-and-vm-mtu), even though the network interface will have an MTU of 1500. WireGuard sets the Don't Fragment (DF) bit on its packets, and so the MTU for WireGuard on AKS needs to be set to 60 bytes below (or 80 bytes for IPv6) the 1400 MTU of the underlying network to avoid dropped packets. diff --git a/calico-enterprise_versioned_docs/version-3.23-1/networking/configuring/mtu.mdx b/calico-enterprise_versioned_docs/version-3.23-1/networking/configuring/mtu.mdx index d284ed2c7d..ab660d3891 100644 --- a/calico-enterprise_versioned_docs/version-3.23-1/networking/configuring/mtu.mdx +++ b/calico-enterprise_versioned_docs/version-3.23-1/networking/configuring/mtu.mdx @@ -60,7 +60,7 @@ The following table lists common MTU sizes for $[prodname] environments. Because **Recommended MTU for overlay networking** -The extra overlay header used in IP in IP, VXLAN and WireGuard protocols, reduces the minimum MTU by the size of the header. (IP in IP uses a 20-byte header, IPv4 VXLAN uses a 50-byte header, IPv6 VXLAN uses a 70-byte header, IPv4 WireGuard uses a [60-byte header](https://lists.zx2c4.com/pipermail/wireguard/2017-December/002201.html) and IPv6 WireGuard uses an 80-byte header). +The extra overlay header used in IP in IP, VXLAN and WireGuard protocols, reduces the minimum MTU by the size of the header. (IP in IP uses a 20-byte header, IPv4 VXLAN uses a 50-byte header, IPv6 VXLAN uses a 70-byte header, IPv4 WireGuard uses a 60-byte header and IPv6 WireGuard uses an 80-byte header). When using AKS, the underlying network has an [MTU of 1400](https://docs.microsoft.com/en-us/azure/virtual-network/virtual-network-tcpip-performance-tuning#azure-and-vm-mtu), even though the network interface will have an MTU of 1500. WireGuard sets the Don't Fragment (DF) bit on its packets, and so the MTU for WireGuard on AKS needs to be set to 60 bytes below (or 80 bytes for IPv6) the 1400 MTU of the underlying network to avoid dropped packets. diff --git a/calico/networking/configuring/mtu.mdx b/calico/networking/configuring/mtu.mdx index 3d5959ede0..0b2d6a30fc 100644 --- a/calico/networking/configuring/mtu.mdx +++ b/calico/networking/configuring/mtu.mdx @@ -59,7 +59,7 @@ The following table lists common MTU sizes for $[prodname] environments. Because **Recommended MTU for overlay networking** -The extra overlay header used in IP in IP, VXLAN and WireGuard protocols, reduces the minimum MTU by the size of the header. (IP in IP uses a 20-byte header, IPv4 VXLAN uses a 50-byte header, IPv6 VXLAN uses a 70-byte header, IPv4 WireGuard uses a [60-byte header](https://lists.zx2c4.com/pipermail/wireguard/2017-December/002201.html) and IPv6 WireGuard uses an 80-byte header). +The extra overlay header used in IP in IP, VXLAN and WireGuard protocols, reduces the minimum MTU by the size of the header. (IP in IP uses a 20-byte header, IPv4 VXLAN uses a 50-byte header, IPv6 VXLAN uses a 70-byte header, IPv4 WireGuard uses a 60-byte header and IPv6 WireGuard uses an 80-byte header). When using AKS, the underlying network has an [MTU of 1400](https://docs.microsoft.com/en-us/azure/virtual-network/virtual-network-tcpip-performance-tuning#azure-and-vm-mtu), even though the network interface will have an MTU of 1500. WireGuard sets the Don't Fragment (DF) bit on its packets, and so the MTU for WireGuard on AKS needs to be set to 60 bytes below (or 80 bytes for IPv6) the 1400 MTU of the underlying network to avoid dropped packets. diff --git a/calico_versioned_docs/version-3.29/networking/configuring/mtu.mdx b/calico_versioned_docs/version-3.29/networking/configuring/mtu.mdx index de2d452853..0e9499a05a 100644 --- a/calico_versioned_docs/version-3.29/networking/configuring/mtu.mdx +++ b/calico_versioned_docs/version-3.29/networking/configuring/mtu.mdx @@ -59,7 +59,7 @@ The following table lists common MTU sizes for $[prodname] environments. Because **Recommended MTU for overlay networking** -The extra overlay header used in IP in IP, VXLAN and WireGuard protocols, reduces the minimum MTU by the size of the header. (IP in IP uses a 20-byte header, IPv4 VXLAN uses a 50-byte header, IPv6 VXLAN uses a 70-byte header, IPv4 WireGuard uses a [60-byte header](https://lists.zx2c4.com/pipermail/wireguard/2017-December/002201.html) and IPv6 WireGuard uses an 80-byte header). +The extra overlay header used in IP in IP, VXLAN and WireGuard protocols, reduces the minimum MTU by the size of the header. (IP in IP uses a 20-byte header, IPv4 VXLAN uses a 50-byte header, IPv6 VXLAN uses a 70-byte header, IPv4 WireGuard uses a 60-byte header and IPv6 WireGuard uses an 80-byte header). When using AKS, the underlying network has an [MTU of 1400](https://docs.microsoft.com/en-us/azure/virtual-network/virtual-network-tcpip-performance-tuning#azure-and-vm-mtu), even though the network interface will have an MTU of 1500. WireGuard sets the Don't Fragment (DF) bit on its packets, and so the MTU for WireGuard on AKS needs to be set to 60 bytes below (or 80 bytes for IPv6) the 1400 MTU of the underlying network to avoid dropped packets. diff --git a/calico_versioned_docs/version-3.30/networking/configuring/mtu.mdx b/calico_versioned_docs/version-3.30/networking/configuring/mtu.mdx index de2d452853..0e9499a05a 100644 --- a/calico_versioned_docs/version-3.30/networking/configuring/mtu.mdx +++ b/calico_versioned_docs/version-3.30/networking/configuring/mtu.mdx @@ -59,7 +59,7 @@ The following table lists common MTU sizes for $[prodname] environments. Because **Recommended MTU for overlay networking** -The extra overlay header used in IP in IP, VXLAN and WireGuard protocols, reduces the minimum MTU by the size of the header. (IP in IP uses a 20-byte header, IPv4 VXLAN uses a 50-byte header, IPv6 VXLAN uses a 70-byte header, IPv4 WireGuard uses a [60-byte header](https://lists.zx2c4.com/pipermail/wireguard/2017-December/002201.html) and IPv6 WireGuard uses an 80-byte header). +The extra overlay header used in IP in IP, VXLAN and WireGuard protocols, reduces the minimum MTU by the size of the header. (IP in IP uses a 20-byte header, IPv4 VXLAN uses a 50-byte header, IPv6 VXLAN uses a 70-byte header, IPv4 WireGuard uses a 60-byte header and IPv6 WireGuard uses an 80-byte header). When using AKS, the underlying network has an [MTU of 1400](https://docs.microsoft.com/en-us/azure/virtual-network/virtual-network-tcpip-performance-tuning#azure-and-vm-mtu), even though the network interface will have an MTU of 1500. WireGuard sets the Don't Fragment (DF) bit on its packets, and so the MTU for WireGuard on AKS needs to be set to 60 bytes below (or 80 bytes for IPv6) the 1400 MTU of the underlying network to avoid dropped packets. diff --git a/calico_versioned_docs/version-3.31/networking/configuring/mtu.mdx b/calico_versioned_docs/version-3.31/networking/configuring/mtu.mdx index de2d452853..0e9499a05a 100644 --- a/calico_versioned_docs/version-3.31/networking/configuring/mtu.mdx +++ b/calico_versioned_docs/version-3.31/networking/configuring/mtu.mdx @@ -59,7 +59,7 @@ The following table lists common MTU sizes for $[prodname] environments. Because **Recommended MTU for overlay networking** -The extra overlay header used in IP in IP, VXLAN and WireGuard protocols, reduces the minimum MTU by the size of the header. (IP in IP uses a 20-byte header, IPv4 VXLAN uses a 50-byte header, IPv6 VXLAN uses a 70-byte header, IPv4 WireGuard uses a [60-byte header](https://lists.zx2c4.com/pipermail/wireguard/2017-December/002201.html) and IPv6 WireGuard uses an 80-byte header). +The extra overlay header used in IP in IP, VXLAN and WireGuard protocols, reduces the minimum MTU by the size of the header. (IP in IP uses a 20-byte header, IPv4 VXLAN uses a 50-byte header, IPv6 VXLAN uses a 70-byte header, IPv4 WireGuard uses a 60-byte header and IPv6 WireGuard uses an 80-byte header). When using AKS, the underlying network has an [MTU of 1400](https://docs.microsoft.com/en-us/azure/virtual-network/virtual-network-tcpip-performance-tuning#azure-and-vm-mtu), even though the network interface will have an MTU of 1500. WireGuard sets the Don't Fragment (DF) bit on its packets, and so the MTU for WireGuard on AKS needs to be set to 60 bytes below (or 80 bytes for IPv6) the 1400 MTU of the underlying network to avoid dropped packets. diff --git a/calico_versioned_docs/version-3.32/networking/configuring/mtu.mdx b/calico_versioned_docs/version-3.32/networking/configuring/mtu.mdx index 3d5959ede0..0b2d6a30fc 100644 --- a/calico_versioned_docs/version-3.32/networking/configuring/mtu.mdx +++ b/calico_versioned_docs/version-3.32/networking/configuring/mtu.mdx @@ -59,7 +59,7 @@ The following table lists common MTU sizes for $[prodname] environments. Because **Recommended MTU for overlay networking** -The extra overlay header used in IP in IP, VXLAN and WireGuard protocols, reduces the minimum MTU by the size of the header. (IP in IP uses a 20-byte header, IPv4 VXLAN uses a 50-byte header, IPv6 VXLAN uses a 70-byte header, IPv4 WireGuard uses a [60-byte header](https://lists.zx2c4.com/pipermail/wireguard/2017-December/002201.html) and IPv6 WireGuard uses an 80-byte header). +The extra overlay header used in IP in IP, VXLAN and WireGuard protocols, reduces the minimum MTU by the size of the header. (IP in IP uses a 20-byte header, IPv4 VXLAN uses a 50-byte header, IPv6 VXLAN uses a 70-byte header, IPv4 WireGuard uses a 60-byte header and IPv6 WireGuard uses an 80-byte header). When using AKS, the underlying network has an [MTU of 1400](https://docs.microsoft.com/en-us/azure/virtual-network/virtual-network-tcpip-performance-tuning#azure-and-vm-mtu), even though the network interface will have an MTU of 1500. WireGuard sets the Don't Fragment (DF) bit on its packets, and so the MTU for WireGuard on AKS needs to be set to 60 bytes below (or 80 bytes for IPv6) the 1400 MTU of the underlying network to avoid dropped packets.