Slow WAN speed on upgrade 2.6.0

berbec

@je7ebel said in Slow WAN speed on upgrade 2.6.0:

Same problem here, hyper-v pfsense upgraded to 2.6.0.
im rolling back to previous version.

Any solution to this issue?

And another. Hyper-V running on Server 2019. 1gbps WAN on 2.5.2. Upgraded to 2.6.0 and get 5mbps WAN. I rolled back (read: full reinstalled) to 2.5.2 and everything is fine again.

DD

We have same problems as I wrote here. And I found other people that have same problem too. I think that problem is in FreeBSD 12.3. I tried OPNsense 22.1 which is based on FreeBSD 13 and everything is working ok on it.

DD

So, I found solution. When I disabled Enabled virtual machine queue in Hardware acceleration on all of VM network adapter, then everything is working ok.

berbec

@dd this did not work for me, but it's possible I did it wrong. I attempted to do that, as well as recreate all adapters with SR-IOV, to no effect. Did you make any other changes?

DD

@berbec No, nothing more changed. When I enable this setting, WAN speed is going down immediatelly, then when I disable, everything is ok.

GrimmSh0t

@DD - no change for me! (Disabled / Uncheck - Enable virtual machine queue, then rebooted host.)

Setup:
Windows Server 2022
HyperV

Worked on 2.5.2

In one of the other threads I read youtube plays fine. I can also play youtube at 4k, strange....
Another strange one (I work from home) - Teams is working just fine and FUBO TV seems nice and happy

berbec

@grimmsh0t 4k YouTube worked fine for me as well. I rolled back to 2.5.2

Bob.Dig

@grimmsh0t said in Slow WAN speed on upgrade 2.6.0:

@DD - no change for me! (Disabled / Uncheck - Enable virtual machine queue, then rebooted host.)

Same here, I disabled it in every VM, in the real NIC also and even rebooted, makes no difference at all.

GrimmSh0t

@DD / @Bob-Dig - Thanks for the reply, if I had more time I would start troubleshooting but only have about 3 hours before the family gets home. Guess I'll roll back the VM before they get home, thank goodness for backups. On the positive guess I get to test my DR :)

Not to get off topic: I use Windows Backup for my VM's and while the VM was on I restored the backup, it worked perfect :) ! Took about 2 minutes 48GB. Back to 2.5.2 :(

lifeasben

I'm having the same issue on Windows Server 2019 (1809, 17763.2366). I tried the tip to uncheck "Enable virtual machine queue" on both WAN and LAN ports, but this didn't help at all.
Since I wanted the ZFS storage, I had started with a clean install, so just stopped the 2.6.0 machine and started 2.5.2 back up.
Only an hour of time lost, so not a big deal, but would love to hear of a sure fix!

RMH 0

I put this in another thread which may help here too

@rmh-0 said in After Upgrade inter (V)LAN communication is very slow on Hyper-V, for others WAN Speed is affected:

A bit of digging and it looks like 2 issues to me.

One in Hyper-V which I have now got resolved, fix below (well for me anyhow)
One in pfsense that is missreporting throughput (I can live with that till a fix comes)

For Hyper-V I found this article on RSC https://www.doitfixit.com/blog/2020/01/15/slow-network-speed-with-hyper-v-virtual-machines-on-windows-server-server-2019/
Once I disabled RSC on all virtual switches my speed was back to normal. No restart needed, just go on to Hyper-V host, open powershell and input commands to disable RSC on each virtual switch.

These are commands I used

Get-VMSwitch -Name LAN | Select-Object RSC
Checks status, if true run next command LAN is my vswitch name

Set-VMSwitch -Name LAN -EnableSoftwareRsc $false
This disables RSC, re run first command to confirm it is disabled

If your vSwitch has a space in the name add "" around the name
Get-VMSwitch -Name "WAN #1" | Select-Object RSC

After applying speed is back to normal but pfsense seems to top out showing throughput at 60mb, even though I was getting over 500mb.

Anyhow, hope it helps thers on Hyper-V (this is a 2019 instance of Hyper-V)

Dominixise

@rmh-0

I can confirm this method you list works on my server with hyper-v pfsense vm :)

Thanks thanks

Dom

mxkied2

Thank you @rmh-0

I can can also confirm this fixed the speed issues for me as well,

Only thing to note was that the command to check if RSC was enabled for me needed to include the wildcards

Get-VMSwitch -Name LAN | Select-Object RSC

needed to be

Get-VMSwitch -Name LAN | Select-Object asteriskshereRSCasteriskshere

otherwise I got no results. Just wanted to mention it.

Forum posting is removing the asterisks place asterisks before and after RSC in the get command

berbec

@mxkied2 the wildcards seem to have been eaten by markup. Is it an asterisk before and after RSC?

mxkied2

@berbec Yes, before and after

GrimmSh0t

@dominixise - I can confirm this works for me at least...Thanks for the post. Will do some more testing but for now running 2.6 with normal speeds.

RMH 0

@mxkied2 Sorry, I did not notice posting messed up the commands ran. I should have posted a screen shot of when I ran it. :(

mxkied2

@rmh-0

No worries at all, it did the same thing to me as you can see from the edits above. HUGE THANK YOU for finding a fix and posting it!

GrimmSh0t

@rmh-0

Here you go :

berbec

@grimmsh0t I just did this on my machine:

PS C:\Users\Administrator> Get-VMSwitch -Name * | Select-Object *RSC*

SoftwareRscEnabled
------------------
              True
             False
              True
              True
              True

PS C:\Users\Administrator> Set-VMSwitch -Name * -EnableSoftwareRsc $false
Set-VMSwitch : Failed while modifying virtual Ethernet switch connection settings.
At line:1 char:1
+ Set-VMSwitch -Name * -EnableSoftwareRsc $false
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : NotSpecified: (:) [Set-VMSwitch], VirtualizationException
    + FullyQualifiedErrorId : OperationFailed,Microsoft.HyperV.PowerShell.Commands.SetVMSwitch

PS C:\Users\Administrator> Get-VMSwitch -Name * | Select-Object *RSC*

SoftwareRscEnabled
------------------
             False
             False
             False
             False
             False

Despite the error, it looks like using an * as the -Name option works. EDIT Error looks safe to ignore.

So that leaves us with one command to disable RSC and one commands to check the setting, assuming you don't have any vSwitches that need RSC:

Check: Get-VMSwitch -Name * | Select-Object *RSC*

Disable: Set-VMSwitch -Name * -EnableSoftwareRsc $false

I will upgrade to 2.6.0 tonight and report if this fixes the issue.

EDIT: I figured out why I was getting an error. I have a Private vSwitch, and that one can't have RSC enabled. The error would not have occured for normal vSwitches attached to ports on a Ethernet card.