meta data for this page
  •  

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision		Previous revision
vm:proxmox:sdn [2024/04/23 19:40] – niziakvm:proxmox:sdn [2024/12/20 20:55] (current) – niziak
Line 10: Line 10:
       * **Simple** a simple bridge on single Proxmox node - no communication across the cluster.       * **Simple** a simple bridge on single Proxmox node - no communication across the cluster.
         * usage: user friendly zone names instead of ''vmbrX'' interfaces. But still needs to specify VLAN tag for VLANs.         * usage: user friendly zone names instead of ''vmbrX'' interfaces. But still needs to specify VLAN tag for VLANs.
 +        * DHCP server and IPAM possible for zone
 +        * Outbound NAT to internet provided locally by each node
       * **VLAN**        * **VLAN** 
         * like above but with VLAN tag assigned         * like above but with VLAN tag assigned
-      * **QinQ** +      * **QinQ** - 802.1Q tunnelling / stacked VLANs / 802.1ad 
-      * **VXLAN** +        * first VLAN tag in L2 frame is a provider / service vlan  
-      * **EVPN**+        * 2nd VLAN tag in L2 frame is customer tag 
 +      * **VxLAN** RFC 7348 (tech preview)  
 +        * encapsulate L2 frames in L3 UDP packets. 
 +        * L3 networks solves lots of forwarding/routing problems of L2 networks. No STP nor VLANs needed. 
 +        * well known protocols like OSPF, EIGRP can be used for L3. 
 +        * VNI tag is 24 bit (16 777 215 VxLANs) 
 +        * one VxLAN is a group of Virtual Tunnels. VTEPs (Virtual Tunnel Endpoint) acts like switch 
 +      * **EVPN** (tech preview)
   * **VNets** - lower    * **VNets** - lower 
 +
 +[[https://pve.proxmox.com/wiki/Software-Defined_Network]]
 +
 +[[https://pve.proxmox.com/wiki/Setup_Simple_Zone_With_SNAT_and_DHCP]]
 +