Netgate Discussion Forum
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Search
    • Register
    • Login

    Need Help Resolving VLAN Errors OUT (Interface Statistics) on a Hyper-v Virtualized pfSense

    Scheduled Pinned Locked Moved Virtualization
    3 Posts 2 Posters 607 Views
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • T
      Tueurdragon
      last edited by

      Hello everyone,

      I am turning to you for help with a persistent problem that I haven't been able to solve despite several days of research.

      Context:
      I have set up a virtualized pfSense on a Hyper-V host with the following specifications:

      Hyper-V Host:

      • CPU: AMD 3700X
      • RAM: 128 GB
      • Storage: 4 TB NVME in REFS
      • Network Card: X520-DA2 fiber at 10Gb

      pfSense VM:

      • pfSense Version: 2.7.2
      • VCPU: 8
      • RAM: 16 GB
      • Disk Space: 256 GB in ZFS

      Network Configuration on Hyperv:

      • WAN VSwitch
      • LAN VSwitch in trunk mode (VLAN 0-100)

      Problem:
      I am observing numerous output errors (Error OUT) on the VLAN of my pfSense in the interface Statistics section. These errors barely increase when my network is lightly used, but spike by several thousands in just a few seconds during bandwidth tests. However, I am not experiencing any throughput issues.

      Actions Taken:

      • Replaced GBICs and fiber cables.
      • Checked for errors on the switch (none detected).
        I* n the Hyper-V configuration, RSC is disabled for the VSwitch and network card.
      • On pfSense, Hardware TCP Segmentation Offloading and Hardware Large Receive Offloading are disabled.
      • On pfSense, the Firewall Maximum Table Entries setting is set to 2,000,000.

      Additional Observation:
      Even after a clean reinstallation of pfSense, the problem persists. It seems there is a buffer memory saturation during high network load. I should note that this issue occurs only on the VLAN interfaces, for example, I do not encounter this on the WAN interface.

      I am looking for suggestions or potential solutions. Any help or advice would be greatly appreciated.
      Thank you in advance!

      1 Reply Last reply Reply Quote 0
      • planedropP
        planedrop
        last edited by

        Is this a brand new setup or has it been fine for a while and just started having this issue? (maybe after an update, pfSense or otherwise like the host)

        Just double checking that, with TCP segmentation offloading things should work pretty well. I've never used pfSense on Hyper-V (despite having a lot of Hyper-V experience) so I may not be the best resource here but will see if I can come up with any issues.

        Is they Hyper-V host a Win Server OS or Windows 10/11?

        1 Reply Last reply Reply Quote 0
        • T
          Tueurdragon
          last edited by

          @planedrop said in Need Help Resolving VLAN Errors OUT (Interface Statistics) on a Hyper-v Virtualized pfSense:

          s this a brand new setup or has it been fine for a while and just started having this issue? (maybe after an update, pfSense or otherwise like the host)

          Just double checking that, with TCP segmentation offloading things should work pretty well. I've never used pfSense on Hyper-V (despite having a lot of Hyper-V experience) so I may not be the best resource here but will see if I can come up with any issues.

          Is they Hyper-V host a Win Server OS or Windows 10/11?

          Good morning,

          I actually did a clean install in 2.7.2 when the version was released.
          In version 2.6, I didn't seem to have this problem.

          Regarding Windows updates, there are so many and I do them regularly.

          Thank you very much for the feedback.
          It's a hyper-v on Windows Server 2022.

          I tried with a fresh installation of PFSENSE 2.6, but I have the same problem.

          1 Reply Last reply Reply Quote 0
          • First post
            Last post
          Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.