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

    Unknown error, pfsense freeze

    Scheduled Pinned Locked Moved General pfSense Questions
    11 Posts 2 Posters 1.3k 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.
    • G
      g0rbe
      last edited by g0rbe

      Hi!

      Setup:

      • 2.4.4-RELEASE-p2
      • AMD Ryzen 5 2400G
      • No VM
      • RAM: 8gb
      • WAN: PPPoE (Realtek on motherboard)
      • LAN: DHCP (Intel)
      • Act as VPN client
      • No Vm

      There are about 60 computer on the LAN, some of those configured with static ip (remain from the previous config, use PfSense for a week)

      Problem:
      PfSense freezes in about every hour, sometimes the console work, ping WAN work. LAN totally gone, no WebGUI, can;t get IP.
      There are only 2 error in the logs:

      • arp: x.x.x.x moved from <a> to <b> on <interface>
      • dnsmasq / unbound: failed to send packet: No buffer space available

      I have tried (from here):

      • tuning intel interface
      • change interface to an usb ethernet (to test the faulty NIC):
      • No Traffic shaper
      1 Reply Last reply Reply Quote 0
      • stephenw10S
        stephenw10 Netgate Administrator
        last edited by

        @g0rbe said in Unknown error, pfsense freeze:

        arp: x.x.x.x moved from <a> to <b> on <interface>

        Are those the same MACs each time? What IP address is it?

        The send buffer error implies something lower level though like a bad cable, bad NIC, bad switch etc. But it could also be unable to find whatever it's trying to send to. I would expect to see route or host error in that case though.

        When it freezes are you able to ping out from the LAN at the console? What error do you see if not?

        Steve

        G 1 Reply Last reply Reply Quote 1
        • G
          g0rbe @stephenw10
          last edited by

          @stephenw10 said in Unknown error, pfsense freeze:

          Are those the same MACs each time? What IP address is it?

          Not the same MAC, its 10.10.1.164, inside the DHCP pool. Probably this is the problem?

          When it freezes are you able to ping out from the LAN at the console? What error do you see if not?

          No, it is also throw the No buffer space available error.

          After switching from unbound to dnsmasq, the uptime is now more than 5 hours, i can't get this unbound.

          Thanks for the answer :)

          1 Reply Last reply Reply Quote 0
          • stephenw10S
            stephenw10 Netgate Administrator
            last edited by

            But is it one IP address just moving from MAC A to MAC B and then back from B to A?

            If that's an Apple MAC then it's probably the Bonjour proxy enabled on something, often an Apple TV box:
            https://docs.netgate.com/pfsense/en/latest/monitoring/arp-moved-log-messages.html
            That's annoying but not a real problem.

            When it freezes what do you have to do to get back connectivity? Reboot? Disconnect and reconnect the LAN cable?
            Resave the interface?

            Steve

            Steve

            G 1 Reply Last reply Reply Quote 1
            • G
              g0rbe @stephenw10
              last edited by

              @stephenw10 said in Unknown error, pfsense freeze:

              But is it one IP address just moving from MAC A to MAC B and then back from B to A?

              If that's an Apple MAC then it's probably the Bonjour proxy enabled on something, often an Apple TV box:
              https://docs.netgate.com/pfsense/en/latest/monitoring/arp-moved-log-messages.html
              That's annoying but not a real problem.

              One ip moving, it an Andriod on a Raspberry Pi

              When it freezes what do you have to do to get back connectivity? Reboot? Disconnect and reconnect the LAN cable?
              Resave the interface?

              Only the reset button solve the problem, if i trying to reboot from the console, its hang.

              1 Reply Last reply Reply Quote 0
              • stephenw10S
                stephenw10 Netgate Administrator
                last edited by

                Hmm, does it hang with an error there? Like some process that will not close?

                Maybe try running at the console before trying to reboot: top -aSH

                Check for any processes using waaaay more CPU time than they should.

                The moving IP address is probably just noise. You can disable logging that if required. It would not stop pfSense like that.

                Steve

                G 1 Reply Last reply Reply Quote 1
                • G
                  g0rbe @stephenw10
                  last edited by

                  @stephenw10

                  "Syncing disks...." was the problematic process, now its work.

                  Anyway, i checked the cpu history in Status > Monitoring, and i found nothing.

                  1 Reply Last reply Reply Quote 0
                  • stephenw10S
                    stephenw10 Netgate Administrator
                    last edited by

                    Hmm, that's expected during shutdown, though obviously it shoudn't hang.

                    Normally I'd say the Intel NIC is going to be the better by far but I suggest you switch the NIC assignments and see if the problem follows the hardware or remains on the LAN.

                    Steve

                    G 1 Reply Last reply Reply Quote 1
                    • G
                      g0rbe @stephenw10
                      last edited by

                      @stephenw10
                      Thanks for your help!

                      It remains on the LAN, i changed the Intel NIC to a temporary usb to ethernet interface, but failed. the lan went down (but with better uptime)

                      1 Reply Last reply Reply Quote 0
                      • stephenw10S
                        stephenw10 Netgate Administrator
                        last edited by

                        There is a change it just failed because it's a USB NIC, they tend to do that unfortunately.

                        I would still recommend switching the NIC assignments as a further test.

                        Steve

                        G 1 Reply Last reply Reply Quote 1
                        • G
                          g0rbe @stephenw10
                          last edited by

                          @stephenw10
                          I will do that, thanks for your help :)

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