You said "Disabling SR-IOV on those VMs dropped their throughput to similar rates as I was seeing on the pfSense VM host." Something is going on that is not SR-IOV related. I have a Hyper-V host running 2016 w/ an Intel I350-T4 and it can easily hit 125 MB/s going from vLAN to LAN without SR-IOV or VMQ. I can also max out my 250/40 internet without issue. My motherboard doesn't support SR-IOV so it's not an option here. However from my understanding SR-IOV and VMQ were designed for 10 gbps or higher links. When you say you are disabling VMQ do you mean in the VM properties page, or in the actual host OS via powershell?

Glad it's working for you.

Does anyone have a way to resole it? Please help.

pf only filters at layer 3, it still works the same way on a bridge. I've setup filtering bridges like that in the past a number of times and it has worked fine. There's no way to debug at the command line I'm aware of. You can pcap on the various interfaces to see what's happening there. Steve

You can't use subnets contained inside your VPC subnet anywhere but the VPC itself. Use something outside of that for the other side of the VPN. Sorry. That's just the way AWS works, as you can see from that error message.

So, I think I found the source of my issue: my DNS setting. I had shut off and uninstalled SquidGuard, Squid and Snort (in that order) and still had no luck. As soon as I changed my DNS settings to Google (for example), I no longer have any latency issues. Put back Squid and Snort and still no latency. So, it looks like something with OpenDNS is causing my problem. Off to try another DNS to see if it's still running ok.

Amigos, a solução para o meu problema foi aumentar as entradas máximas da tabela do firewall no campo: System / Advanced / Firewall e NAT Mudei o valor padrão de 400000 para 800000, mas o valor fica a critério de cada um de acordo a sua necessidade.

teşekkür ederim ilginiz için