Cannot define table negate_networks error with pfSense 2.4.3

  • Since upgrading from 2.4.2_1 to 2.4.3 I've begun seeing this error about every other day or so.

    /tmp/rules.debug:26: cannot define table negate_networks: Cannot allocate memory - The line in question reads [26]: table <negate_networks>
    Followed by a list of some subnets on the firewall…

    pfSense already had 1GB of RAM and never more than 50% in use. I threw another 1GB at it and the message is still happening, with 23% memory in use. Is this a known issue in 2.4.3, or can I tweak a tunable to address this?

  • LAYER 8 Global Moderator

    What is this netgate_networks table?

    Did you use hosts vs network and put some huge network in there that expanded out to host entries? Post a screenshot of your alias settings.

  • Rebel Alliance Developer Netgate

    Most likely, your other tables (like bogons) are taking up space first and that one happens to fail loading afterward.

    You can increase the Firewall Maximum Table Entries limit under System > Advanced, Firewall & NAT tab.

    It defaults to 200,000 but the IPV6 bogon list recent increased past a point where that amount is insufficient to hold it all during a reload. We are increasing the default to 400,000.

Log in to reply