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

    Packetloss on pfsense firewall

    Scheduled Pinned Locked Moved General pfSense Questions
    32 Posts 5 Posters 5.8k 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.
    • 1
      1-21Giggawatts
      last edited by

      Yup - thats better

      em0: <Intel(R) PRO/1000 Network Connection 7.6.1-k> port 0xe000-0xe01f mem 0xd0700000-0xd071ffff,0xd0720000-0xd0723fff irq 16 at device 0.0 on pci1
      em0: Using an MSI interrupt
      em0: Ethernet address: 00:e0:67:05:24:40
      em0: netmap queues/slots: TX 1/1024, RX 1/1024
      pcib2: <ACPI PCI-PCI bridge> irq 17 at device 28.1 on pci0
      pcib2: [GIANT-LOCKED]
      pci2: <ACPI PCI bus> on pcib2
      em1: <Intel(R) PRO/1000 Network Connection 7.6.1-k> port 0xd000-0xd01f mem 0xd0600000-0xd061ffff,0xd0620000-0xd0623fff irq 17 at device 0.0 on pci2
      em1: Using an MSI interrupt
      em1: Ethernet address: 00:e0:67:05:24:41
      em1: netmap queues/slots: TX 1/1024, RX 1/1024
      pcib3: <ACPI PCI-PCI bridge> irq 18 at device 28.2 on pci0
      pcib3: [GIANT-LOCKED]
      pci3: <ACPI PCI bus> on pcib3
      em2: <Intel(R) PRO/1000 Network Connection 7.6.1-k> port 0xc000-0xc01f mem 0xd0500000-0xd051ffff,0xd0520000-0xd0523fff irq 18 at device 0.0 on pci3
      em2: Using an MSI interrupt
      em2: Ethernet address: 00:e0:67:05:24:42
      em2: netmap queues/slots: TX 1/1024, RX 1/1024
      pcib4: <ACPI PCI-PCI bridge> irq 19 at device 28.3 on pci0
      pcib4: [GIANT-LOCKED]
      pci4: <ACPI PCI bus> on pcib4
      em3: <Intel(R) PRO/1000 Network Connection 7.6.1-k> port 0xb000-0xb01f mem 0xd0400000-0xd041ffff,0xd0420000-0xd0423fff irq 19 at device 0.0 on pci4
      em3: Using an MSI interrupt
      em3: Ethernet address: 00:e0:67:05:24:43
      em3: netmap queues/slots: TX 1/1024, RX 1/1024

      Thank you for your informative help Gertjan - its appreciated!

      1 Reply Last reply Reply Quote 0
      • 1
        1-21Giggawatts
        last edited by

        And after a day - the issue is back... OK 2.4.4 it is then.

        1 Reply Last reply Reply Quote 0
        • P
          perlenbacher
          last edited by perlenbacher

          Before flattening your install, update your system after selecting the latest Dev branch in the GUI.
          It would only take 2 minutes.
          2.5.0a may suit you better...
          It is built on FreeBSD 12.1-STABLE

          1 Reply Last reply Reply Quote 0
          • 1
            1-21Giggawatts
            last edited by 1-21Giggawatts

            Good idea - i tried 2.5 last night but still having the same lockup / packetloss issues.

            I have found a website that has an archive of older version, will roll back and find out if its actually my hardware thats stuffed.

            1 Reply Last reply Reply Quote 0
            • 1
              1-21Giggawatts
              last edited by

              got 2.4.3 running again now - lets see how it goes

              1 Reply Last reply Reply Quote 0
              • 1
                1-21Giggawatts
                last edited by

                In order to install snort had to update to 2.4.4(3) hoping that isnt where the issues started ;-/

                1 Reply Last reply Reply Quote 0
                • 1
                  1-21Giggawatts
                  last edited by

                  Ok i have tried just about everything with this. I have come to the conclusion is most likely a hardware error. Still getting packetloss to the device on internal interface every few hours for around 5 seconds.

                  I have connected the switch directly to my Cisco switch rather than use the conduit cables in the wall to eliminate those - changed all cables. Changed the switchport in the Cisco switch - no errors on ports. Tested with all of the available interfaces in my device em0,1,2,3. When the error occurs I dont drop packets to any other devices connected on same vlan on the Cisco switch - its only the firewall. I am running a yanling n10 plus device, 4 nics and

                  I thought perhaps it could be a BSD issue - so i installed HP's ClearOS 7.6.0 to compare which runs on a linux kernel - but the problem is still there. I have installed Pfsense 2.4.3 2.4.4 and 2.4.5 - I also tried OPNsense 20.1 which runs on a more recent version of BSD too, nothing has fixed this problem yet.

                  I guess the only other issue is to change the internal IP just in case something on my network is trying trying to use that IP occasionally - although i would expect to see a macflap alert on my switch log if that were the case..

                  1 Reply Last reply Reply Quote 0
                  • 1
                    1-21Giggawatts
                    last edited by 1-21Giggawatts

                    Last throw of the dice - I decided to try IPFire - I still really wanted something that incorporated inline IPS and that I could use my snort VRT subscription with.

                    Downloaded v2.25 last night - installed and its still going strong. Got through my morning MS Teams meeting with 0 packetloss. Running a ping test to internal interface for around 8 hours so far and it hasnt dropped a beat. Fantastic!

                    The firewall is not as intuitive or as fully featured as pfsense - the GUI is fairly archaic looking - however it seems quick and most importantly for me - stable with my hardware!

                    A pity that Pfsense stopped working for me - perhaps I will try the next major release - but until then I will just stick with IPFire

                    1 Reply Last reply Reply Quote 0
                    • 1
                      1-21Giggawatts @jimp
                      last edited by

                      @jimp Looks like the issue may have been some BSD driver for my hardware - im assuming the <Intel(R) PRO/1000 Network Connection 7.6.1-k>?

                      1 Reply Last reply Reply Quote 0
                      • F
                        fezster
                        last edited by

                        Identical issue here! (And quite a few of us it seems).

                        See my thread here: https://forum.kitz.co.uk/index.php/topic,24600.60.html

                        Ive been running OPNSense 20.1 (FreeBSD 11.2) for almost a week without issue. No packet loss, no high ping etc.

                        I found this thread when searching for whether PfSense 2.4.4-p3 (also based on FreeBSD 11.2) would resolve the issue - did you ever try this?

                        1 Reply Last reply Reply Quote 0
                        • 1
                          1-21Giggawatts
                          last edited by

                          Yep I ran version 2.4.4(3) and 2.3.4 same problems - also tried version 20.1 OPNsense same issue. Ive been running IPFire 2.25 for over a week now with zero issues (other than suricata does not parse the snort VRT ruleset very well)

                          Perhaps when thewy release a new version of pfsense i will take a look but I just want a stable firewall with inline IPS capabilities - so IPFire is doing that for me now.

                          1 Reply Last reply Reply Quote 1
                          • F
                            fezster
                            last edited by

                            Resolved by putting unbound into DNS forward mode, instead of resolver.

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