From eac0159766ee490209ad160c3eb9ec0fafb6f6a9 Mon Sep 17 00:00:00 2001
From: nage1234 <88926279+nage1234@users.noreply.github.com>
Date: Fri, 28 Jun 2024 17:03:43 +0530
Subject: [PATCH] Revert "docs: update vxlan-overlay.md (#3121)"

This reverts commit 5378832832746117dd0bc908d64ef3f34a9c0609.
---
 docs/docs-content/clusters/edge/networking/vxlan-overlay.md | 4 ----
 1 file changed, 4 deletions(-)

diff --git a/docs/docs-content/clusters/edge/networking/vxlan-overlay.md b/docs/docs-content/clusters/edge/networking/vxlan-overlay.md
index 821cc5a1e1..c815e61cf0 100644
--- a/docs/docs-content/clusters/edge/networking/vxlan-overlay.md
+++ b/docs/docs-content/clusters/edge/networking/vxlan-overlay.md
@@ -58,10 +58,6 @@ server. The region experiences a bad weather event that causes a sustained outag
 - At least one Edge host registered with your Palette account.
 - Your cluster profile must have K3s or RKE2 as its Kubernetes distribution.
 - All Edge hosts must be on the same Layer-2 network.
-- Broadcast messages must be allowed between all Edge hosts participating in the cluster.
-  - For Virtual Machine (VM) Edge hosts in VMware, this means features such as promiscuous mode must be enabled to allow
-    broadcasts between hosts.
-  - Switches cannot implement features that block broadcast between ports where Edge hosts are connected.
 - If you are launching your Edge hosts in virtual machine environments and you are using either Cilium or Flannel as
   your container network interface (CNI), ensure that you add the following commands in the **user-data** file at the
   boot stage. Replace `INTERFACE_NAME` with the name of the network interface on your Edge host.