Okedokey
Well-Known Member
For the purposes of future reference,
Applies to Hyper-V 2019 and pfsense 2.6.0 only.
Those experiencing mysterious network slow downs since updating pfsense 2.5.2 to 2.6.0 (only on MS Hyper-V) one must disable Receive Segment Coalescing (RSC) on the virtual switches, where vSwitchName is your pfsense virtual machines' adaptor names (wan and lan) :
Check the RSC status:
Get-VMSwitch -Name vSwitchName | Select-Object *RSC*
Disable RSC (to fix network problem with pfsense):
Set-VMSwitch -Name vSwitchName -EnableSoftwareRsc $false
Enable RSC (to set back to default):
Set-VMSwitch -Name vSwitchName -EnableSoftwareRsc $True
My upload speed post-update was capped at 200kB/s and instantly returned to normal throughput once RSC was disabled (can be done on the fly). Check SR-IOV settings upon completion just to be sure. The only downside of this workaround is a slightly higher CPU utilisation, which for most workloads on the community branch is not an issue imho.
Applies to Hyper-V 2019 and pfsense 2.6.0 only.
Those experiencing mysterious network slow downs since updating pfsense 2.5.2 to 2.6.0 (only on MS Hyper-V) one must disable Receive Segment Coalescing (RSC) on the virtual switches, where vSwitchName is your pfsense virtual machines' adaptor names (wan and lan) :
Check the RSC status:
Get-VMSwitch -Name vSwitchName | Select-Object *RSC*
Disable RSC (to fix network problem with pfsense):
Set-VMSwitch -Name vSwitchName -EnableSoftwareRsc $false
Enable RSC (to set back to default):
Set-VMSwitch -Name vSwitchName -EnableSoftwareRsc $True
My upload speed post-update was capped at 200kB/s and instantly returned to normal throughput once RSC was disabled (can be done on the fly). Check SR-IOV settings upon completion just to be sure. The only downside of this workaround is a slightly higher CPU utilisation, which for most workloads on the community branch is not an issue imho.
Last edited: