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

    As soon as start copying file pfsense port goes down with "no buffer available"

    Scheduled Pinned Locked Moved Virtualization
    14 Posts 5 Posters 2.2k 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.
    • V
      viragomann
      last edited by

      Try to increase nmbclusters / MBUF:
      https://doc.pfsense.org/index.php/Tuning_and_Troubleshooting_Network_Cards

      1 Reply Last reply Reply Quote 0
      • Z
        zambhoni
        last edited by

        Thank you for your suggestion, but I increased the MBUF size as suggested and still as soon as I copy file from a network on one interface to a server on another interface the firewall stops allowing packets (I can still connect to the gateway IP to access pfSense admin console) and I need to restart the pfSense server.

        here is what the MBUF usage looks like when this happens (see attachment)

        To resolve this problem I have to reboot pfSense.

        I will add that this does not happen always. Sometimes I can copy files fine and sometimes it happens every time.

        Help!

        pfSense_stats.png
        pfSense_stats.png_thumb

        1 Reply Last reply Reply Quote 0
        • D
          doktornotor Banned
          last edited by

          @zambhoni:

          We have pfsense 2.2-release on hyper-v with two Realtek PCIe GBE Family adapters.

          Hmmm, really? Was not aware they've added PCI pass-through to Hyper-V. I frankly don't see that option anywhere. (And SR-IOV needs to by supported by the NIC.)

          1 Reply Last reply Reply Quote 0
          • Z
            zambhoni
            last edited by

            @doktornotor:

            Hmmm, really? Was not aware they've added PCI pass-through to Hyper-V. I frankly don't see that option anywhere. (And SR-IOV needs to by supported by the NIC.)

            Yes it is supported in Hyper-V on Windows Server 2012 R2 (see below) and it works quite well, except the problem we are experiencing as described in this thread.

            sr-iov.png_thumb
            sr-iov.png

            1 Reply Last reply Reply Quote 0
            • Z
              zambhoni
              last edited by

              After posting the screen shot my last reply I noticed SR-IOV was NOT enabled on the virtual switch the pfSense was using (!!) I will try to re-created the switches and enable it and will re-test. I will advise of the results

              1 Reply Last reply Reply Quote 0
              • Z
                zambhoni
                last edited by

                No, didnt make a difference. As soon as I copy large file the pfSense stops routing

                1 Reply Last reply Reply Quote 0
                • D
                  doktornotor Banned
                  last edited by

                  SR-IOV is not exactly PCI pass-through. Plus, passing crappy HW through does not make it any less crappy. Realtek -> junk.

                  1 Reply Last reply Reply Quote 0
                  • Z
                    zambhoni
                    last edited by

                    I agree its junk but it should still work. Does it mean anyone who purchased Realtek cards and tried using them for pfSense is not able to copy large files? The cards work flawlessly with the base OS. How do I troubleshoot this? When in pfSense log can I see what is the error when the interface stops routing. THere must be some clue.

                    1 Reply Last reply Reply Quote 0
                    • Z
                      zambhoni
                      last edited by

                      I am still struggling with this. Anyone else with Realtek PCIe cards and Hyper-V on 2012 R2 experiencing this?

                      1 Reply Last reply Reply Quote 0
                      • H
                        Harvy66
                        last edited by

                        Have you tried another guest OS to performance test the network with?

                        If I spent more than a few hours trying to debug a hardware issue, I'd just purchase better hardware. I've had too many headaches with RealTek, Broadcom, and any other popular trash network hardware. I only use Intel now, cheap enough and well supported. i210 in my desktop and i350 in my pfsense. Wife has an integrated Intel nic, but if her next motherboard does not, then I'm purchasing an i210 for her also.

                        1 Reply Last reply Reply Quote 0
                        • C
                          cmb
                          last edited by

                          Put some real NICs in there. Running a server OS on something with NICs that are low quality for desktop purposes much less more than that isn't likely to end well, especially where doing things like that with Hyper-V.

                          1 Reply Last reply Reply Quote 0
                          • Z
                            zambhoni
                            last edited by

                            Any decent (tried in Hyper-V) recommendations?

                            1 Reply Last reply Reply Quote 0
                            • C
                              cmb
                              last edited by

                              Intel gigabit cards probably your best bet. Easy to find, inexpensive (especially if you want to go the ebay route for used), and reliable.

                              We sell two different options that'll work great with Windows too.
                              https://store.pfsense.org/accessories/

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