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

    Issues after update to 2.4.3

    Scheduled Pinned Locked Moved Problems Installing or Upgrading pfSense Software
    8 Posts 5 Posters 1.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.
    • Z
      zarje
      last edited by

      This morning I updated from 2.4.2 to 2.4.3 and after rebooting I am now unable to access  the web admin page. I've tried rebooting the firewall a couple of times but this hasn't helped. I am able to use the USB console cable to connect to the console but I'm not sure what I need to do to be able to get into the web admin GUI again?

      Whats also strange is that although my internet is working I can't RDP into my servers on another VLAN.

      So to start with, how do I get into the web admin GUI again?

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

        I managed to gain access by temporarily disabling pf and this is what I was presented with in the GUI (see attached)

        What is the issue here? Cannot allocate memory, what does this mean?

        error.jpg
        error.jpg_thumb

        1 Reply Last reply Reply Quote 0
        • KOMK
          KOM
          last edited by

          IT means you have the same problem that a lot of others are having with this upgrade.  This is like the fourth or fifth post about this exact same issue that I've read.

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

            I increased my "Firewall Maximum Table Entrie" from 200000 to 400000 and that seemed to do the trick.

            1 Reply Last reply Reply Quote 0
            • J
              Juve
              last edited by

              The issue is present with 2.4.2p1 also.
              Increasing the maximum table size resolve the issue.

              1 Reply Last reply Reply Quote 0
              • DerelictD
                Derelict LAYER 8 Netgate
                last edited by

                Yeah I believe the coincidence with 2.4.3 is just that - a coincidence. The bogonsv6 file simply seems to have grown to a point it is tickling the 200000 default, though I have no historical size data of that table.

                Using things like pfBlockerNG will only increase your chances of exceeding that allocation limit.

                Chattanooga, Tennessee, USA
                A comprehensive network diagram is worth 10,000 words and 15 conference calls.
                DO NOT set a source address/port in a port forward or firewall rule unless you KNOW you need it!
                Do Not Chat For Help! NO_WAN_EGRESS(TM)

                1 Reply Last reply Reply Quote 0
                • J
                  Juve
                  last edited by

                  Bogonsv6 reached 95K entries last week.

                  Only people with "serious" setup encountered this behaviour because they already have a lot of alias/tables configured.
                  I think it should be safe to increase the default value to something bigger.

                  1 Reply Last reply Reply Quote 0
                  • S
                    ssilvi501
                    last edited by

                    Hello

                    Access the console and use option 11 and retry access in the GUI

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