Proxmox create VXLAN using its native SDN Rumi, January 12, 2024 Prerequisite: You need to have an Installed Proxmox and Configure a Clustered setup. The first step in any installation is to make sure your hosts are updated. By default, Proxmox hosts will reach out to the enterprise repository, so I need to configure the pve-no-subscription repository. To enable that, I added it to /etc/apt/sources.list like the image below. Add the pve-no-subscription repository After adding the repository, I run an apt update and upgrade to install the latest patches and make sure the new repository works. # apt update && apt upgrade -y Now I can install the needed dependencies on each host. Important note here, the next few steps are run on EVERY node in the cluster. # apt install libpve-network-perl ifupdown2 Configure Software Defined Networking in Proxmox After updating the hosts and installing the dependencies the last step to enable software defined networking is to add a line to the interface configuration. I added the line below to the /etc/network/interfaces file on every host. source /etc/network/interfaces.d/* Example /etc/network/interfaces file with additional line Once added, you should automatically see the software defined network menu in your datacenter view. Adding VXLANs to the Lab Network Configuring a software defined network in Proxmox consists of three steps for each network. I need to configure a Zone, a Vnet, and if I want to assign an IP range, a Subnet for each VXLAN. Adding a VXLAN zone To add a VXLAN zone, you select that zone type in the Proxmox SDN interface. According to Proxmox SDN documentation, when adding a VXLAN, you need to set the MTU to a slightly lower value than the standard 1500. A VXLANs is a simulated layer 2 network on top of the existing network. So the extra 50 bytes allows for the VXLAN header added to each packet. You also need to configure an ID and peer IP address list. Example VXLAN zone configuration DMZ and LAN VXLAN zones added to Lab Network Adding Vnets and Subnets Once you configure a VXLAN zone, the next step is to add the associated Vnets and Subnets to each zone. In my lab, each zone will have a single Vnet and Subnet. Here is an example configuration of the LANnet and LAN subnet. LANnet Vnet configuration Vnet configuration overview for Lab Network Example subnet configuration Apply to Configure Software Defined Networking in Proxmox Lab The last step is to go back to the SDN overview and apply the configuration. I hit apply and then Proxmox configures the DMZ and LAN VXLANs on each host in the cluster. Data center overview after software defined network configuration That’s all there is to it, my lab network is ready for virtual machines. Next up, I create a virtual firewall running pfsense and configure the WAN, LAN, and DMZ interfaces. Src: Configure Software Defined Networking in Proxmox Related Administrations Collected Articles Proxmox ProxmoxProxmox SDNSDNVXLAN
Migrate hosting sites from one VestaCP to another VestaCP November 12, 2017 Lately, I was trying to migrate vesta hosted sites from one server to another. This trick might help to those who- Either tried to update IP (after tried with so many vesta forum links!) and failed or Have installed on a physical computer and need to move out sites on… Read More
Hiding Apache and PHP Server Signature March 20, 2017March 26, 2017 Revealing web server signature with server/PHP version info can be a security risk as you are essentially telling attackers known vulnerabilities of your system. Thus it is recommended you disable all web server signatures as part of server hardening process. Disable Apache Web Server Signature Disabling Apache web server signature… Read More
Allow Ping on PFSense WAN interface September 9, 2022 This article shows you how to allow ##ping## on the WAN side of your pfSense firewall. By default, ping to WAN address is disabled on pfSense for security reason. However, you may want to allow ping for different reasons, here is how: # Login to pfSense # Open Firewall >… Read More