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

Memory error reloading pfB_Top_v6 (SOLVED)

pfBlockerNG
2
5
2.2k
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.
  • J
    jsbsmd
    last edited by Oct 26, 2016, 6:55 PM Oct 26, 2016, 12:58 PM

    running

    2.3.2-RELEASE-p1 (i386)
    built on Tue Sep 27 12:13:32 CDT 2016
    FreeBSD 10.3-RELEASE-p9

    AMD Athlon™ 64 X2 Dual Core Processor 3800+
    2 CPUs: 1 package(s) x 2 core(s)

    Not sure why I would get memory error when free memory is showing 50% of 1gb

    error message:

    There were error(s) loading the rules: /tmp/rules.debug:26: cannot define table pfB_Top_v6: Cannot allocate memory - The line in question reads [26]: table <pfB_Top_v6> persist file "/var/db/aliastables/pfB_Top_v6.txt" @ 2016-10-26 08:52:05

    1 Reply Last reply Reply Quote 0
    • J
      jsbsmd
      last edited by Oct 26, 2016, 1:46 PM

      Just some more FYI,

      If I do not chose any of the geoip top20 ipv6 countries, I do not get the error message.

      1 Reply Last reply Reply Quote 0
      • R
        RonpfS
        last edited by Oct 26, 2016, 6:33 PM

        You need to raise Firewall Maximum Table Entries in System / Advanced / Firewall & NAT.

        2.4.5-RELEASE-p1 (amd64)
        Intel Core2 Quad CPU Q8400 @ 2.66GHz 8GB
        Backup 0.5_5, Bandwidthd 0.7.4_4, Cron 0.3.7_5, pfBlockerNG-devel 3.0.0_16, Status_Traffic_Totals 2.3.1_1, System_Patches 1.2_5

        1 Reply Last reply Reply Quote 1
        • J
          jsbsmd
          last edited by Oct 26, 2016, 6:53 PM

          Thanks Ron,

          Worked fine. you would like it should spit out an error message like "maximum entries reached" and not a memory error ::)

          1 Reply Last reply Reply Quote 0
          • R
            RonpfS
            last edited by Oct 26, 2016, 8:31 PM

            It's not pfBlockerNG that generate the error, it's the reload process.

            Default settings in pfSense can not handle huge alias table like GeoIP IPv6 tables.

            2.4.5-RELEASE-p1 (amd64)
            Intel Core2 Quad CPU Q8400 @ 2.66GHz 8GB
            Backup 0.5_5, Bandwidthd 0.7.4_4, Cron 0.3.7_5, pfBlockerNG-devel 3.0.0_16, Status_Traffic_Totals 2.3.1_1, System_Patches 1.2_5

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