Recent content by cwathan

Ugh... Layer 8 issue. The guest images in question are very particular in how they map their intra-vm interfaces to the host. I had given them IPs in the wrong subnet for the interface to VLAN mapping without realizing it. Not enough sleep this week. Thank you for your time Dunuin!

I currently have some guests setup like that and they are not able to communicate with the VLAN gateway on the directly connected physical interface. Yes, the directly connected gateway interface *IS* set as a trunk port and worked when I had this same workstation deployed with ESXi at the...

It's really quite basic. I don't recall having this issues with basic trunking in the past. But, it's been a while since I've used anything besides SDN. . . . auto lo iface lo inet loopback iface enp4s0f2np2 inet manual mtu 9000 iface eno1 inet manual auto vmbr0 iface vmbr0 inet...

Good day, I recently setup a lab workstation with proxmox 8.2 and no bridge other than vmbr0 is listed when creating a network interface during VM creation or when adding a vNIC to an existing VM. I used custom names for Linux VLANs as well as a vmbr0.X nomenclature in which X is the VLAN...

The vmbr interfaces and switch interfaces are 9100. The zone and EVPN are 9050. I had gone from having the VM interfaces match the EVPN MTU to making them 8900 and there has been no improvement. IPsec encryption is not enabled. On the same host they SHOULD be going through the EVPN as that...

I apologize for bringing an old thread back to life but, this seems relevant to the issue I'm seeing. I am using an EVPN between multiple VMs both on same host and across hosts. Communications between VMs on the same host see about a 20-25% throughput loss in comparison to host to host...

An update to everyone, after some additional digging I discovered that if you install the strongswan packet for VXLAN IPsec encryption, it automatically takes effect. I had installed the packet with the intent to configure and utilize after validating VXLAN worked without. What this resulted...

For VXLAN, do I need to enable VXLAN on the physical switch for traffic that is passing through between Proxmox nodes? I've been working under the presumption that it was not necessary for pass through traffic so long as MTU settings were correct. I know that you need to configure VXLAN on the...

So, the solution would be to disable "vlan-aware" on all Vnets? I've tried that without success. Do I need to restart nodes or frr after this change? Or, did you mean I should not use OVS with SDN/frr? I'm beginning to think restarting from scratch and seeing what happens might be worthwhile.

spirit, I apologize tit took me a while to get back to you on this. Attached is the information you requested.

FW is disabled on grid, host and VM level and traffic is still not passing. I statically assigned ARP and traffic still does not pass.

I created a VXLAN zone and created a VNET within that zone. I assigned the VNICs to the VXLAN VNET (selecting just the VXLAN zone isn't permitted in the GUI). Traffic is still not passing. I ended up having to use the standard vmbr bridge interface and add a VLAN to that bridge. There...

My understanding of your SDN deployment is that the VNETs are the VXLANs within an EVPN. Is that incorrect? I've statically assigned the ARP entries and traffic still is not passing through. I've created an independent VXLAN that is not under the EVPN and attempted the same. It still is not...

spirit, no traffic needs to leave the VNET because it is a cross-connect between the two router VMs for optimal routing. The traffic will only ever go between the two VMs and nowhere else. The VMs have physical interfaces shared to them that connect to independent providers. The VMs also have...

spirit, this is for a PtP connection between two virtual routers. A /31 conserves IP space and has been the generally accepted norm for IPv4 Point to Point (PtP) links for many years. So, in a day and age when you have to purchase IPv4 space second hand at exhorbinate rates ($40-$65/IP) it is...