31
22.1 Legacy Series / Re: 22.1rc1 slow in Hyper-V
« on: February 02, 2022, 04:11:02 pm »
Yes, I my case its single hyper-v host that has opnsense vm acting as FW for that host (and other VMs). So WAN is ethernet card and LAN is virtual card connected to vSwitch.
WAN has public ip, LAN private, NAT between on opnsense. In case of iperf on opnsense (direct) it runs directly on WAN port as client. In case of iperf on Host (or other VMs) connected to vSwitch iperf communicate on LAN (vswitch) -> GW (opnsense NAT) -> WAN.
Someone in this post wrote, that he installed stock Freebsd and bootstrapped opnsense and issue was still there.
Based on commits that were rolledback, there has to be something in these 2 commits. Are any new settings involved in these commits?
WAN has public ip, LAN private, NAT between on opnsense. In case of iperf on opnsense (direct) it runs directly on WAN port as client. In case of iperf on Host (or other VMs) connected to vSwitch iperf communicate on LAN (vswitch) -> GW (opnsense NAT) -> WAN.
Someone in this post wrote, that he installed stock Freebsd and bootstrapped opnsense and issue was still there.
Based on commits that were rolledback, there has to be something in these 2 commits. Are any new settings involved in these commits?