![]() ![]() ![]() Vlan10 to Vlan10 commiunication (or any VlanX to VlanX) runs MUCH faster than VlanX to VlanY communication because that traffic is 'virtually' on the same network and does NOT need to traverse your router in order to properly make it from Vlan10 host A to Vlan10 host B. This happens when you have communication within your various VLANS rather than between VLANs.īasically, I'm willing to put a whopping $0.25 that you're running into this issue. What I think is happening is, when you're getting higher than 1GB when your network traffic does not need to traverse a 1Gb link between your PFSense router and your Proxmox systems. Is your PFSense router a separate device that has 1Gb links to your network infrastructure somewhere in the mix? I'm going to make a guess as to your router config here. ![]() However still traffic going via the bridge is only limited to 1 Gbits/sec.ġ0.0.20.1 is the pfSense IP on vtnet2 which is on vmbr0 with all the other containers and VM. I can see pfSense showing 10Gbase-T on all connected interfaces, which is expected. These are exposed to pfSense in this order, hence vmbr0 is coming up as vtnet2 in pfSense. vmbr0: The Proxmox bridge shared with all other containers and VMs (vtnet2) vmbr2: A Proxmox bridge dedicated to pfSense where the only other connection on the bridge is another physical ethernet interface connected directly to the DSL modem (1GbE) (vtnet1) vmbr1: A Proxmox bridge dedicated to pfSense where the only other connection on the bridge is a physical ethernet interface connected to my switch (physical interface connection is 1 GbE only) (vtnet0) The pfSense has 3 ethernet interfaces in total: a simple virtio ethernet interface on vmbr0, which is the bridge that connects all of the VMs and LXCs. The Docker-VM is configured similarly to pfSense, i.e. ![]() Iperf3: interrupt - the client has terminatedĪs you can see this has no trouble reaching >1 Gbits/sec speed. ![]()
0 Comments
Leave a Reply. |