I currently have two proxmox Metals in Scaleway Cloud. Yesterday I bought my second one but with the first one I didn't have any issue. So my setup in the first one is a pfsense firewall with a WAN and a LAN in 192.168.1.0/24. Now I introduced the second Metal and created another pfsense (I know it was not necessary but I did) and again WAN and LAN 192.168.2.0/24. I also have a feature called VPC where you connect the two metals in the same private network. I assign the metals to a private network and get both a Vlan id for both metals. Also I managed to connect the two metals by giving them IP addresses 10.10.10.2/24 and 10.10.10.3/24. Both metals can ping each other. My issue is that I cannot make the two LAN VMs ping each other. I know I can connect the two pfsense using VPN in their WAN but I don't want this in case that I can make it work directly internally. So what should I do, to make for example 192.168.1.5 VM in Metal 1 communicate with 192.168.2.2 VM in metal 2?
Make Two different Proxmox Lan's VMs to communicate with each other.
- Thread starter eveliou
- Start date
You need to setup a bridge interface on both Proxmox nodes that uses the new VPC VLAN interface as a port.
Then you can vNICs to the VM that both use the new bridge and they should be able to communicate via this interface.
Then you can vNICs to the VM that both use the new bridge and they should be able to communicate via this interface.
Add a new virtual network interface to each of your VMs that use vmbr2 as bridge device. Inside the VM you will then see a new network interface (probably ens19) that you can configure as you like (e.g. with IPs out of 10.10.10.0/24).
I believe that in the screenshot is what you mean, and also the netplan configuration in ubuntu. While attaching the new bridge, do i also have to add a vlan tag? Metal 1 VMs get the metal 1 vlan tag..metal 2 etc?
Attachments
As vmbr2 sits ontop a VLAN interface you do not need to specify a VLAN tag in the vNIC configuration.
