Navigation

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

    I get this during filter reload

    2.2 Snapshot Feedback and Problems - RETIRED
    6
    8
    1592
    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.
    • chpalmer
      chpalmer last edited by

      2.2-ALPHA (i386)
      built on Wed Mar 26 15:25:08 CDT 2014

      [ There were error(s) loading the rules: /tmp/rules.debug:106: macro  not defined - The line in question reads [106]: antispoof log for $ tracker 1000001570]

      [ There were error(s) loading the rules: /tmp/rules.debug:106: macro  not defined - The line in question reads [106]: antispoof log for $ tracker 1000001570]

      nano version.  On a Watchguard x550e.

      Triggering snowflakes one by one..

      1 Reply Last reply Reply Quote 0
      • E
        eri-- last edited by

        Its a known issue.

        It should be fixed actually.

        1 Reply Last reply Reply Quote 0
        • T
          TAtari last edited by

          I had the same issues and tracker rules errors so I modified the /etc/inc/filter.inc

          So until the alpha is rebuilt with the fixes my "fixed" version can be found:
          http://iis.tatari.se/pfSense/filter.inc

          Fixes:
            antispoof interface was not included
            the 'tracker' part has been removed/disabled from the rule generation

          Tested/based on the filter.inc in 2.2-ALPHA (amd64) built on Wed Mar 26 16:34:16 CDT 2014

          Understeer is when you hit the wall with your front end.
          Oversteer is when you hit the wall with your rearend.
          Horsepower is how hard you hit the wall.
          Torque is how far you move the wall.

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

            Does it need a new binary to work?

            1 Reply Last reply Reply Quote 0
            • P
              phil.davis last edited by

              Does it need a new binary to work?

              Yes, the "tracker" rule keyword feature is a pfSense addition to PF - the code for that is hidden from us in pfSense-tools repo.
              For whatever reason, there has been no snapshot built since 27 March. So I guess the whole 2.2 testing thing is on hold until somebody makes a new snapshot, and preferably also makes the build log appear at http://snapshots.pfsense.org/logs/pfSense_HEAD__FreeBSD_10/i386/build.log

              As the Greek philosopher Isosceles used to say, "There are 3 sides to every triangle."
              If I helped you, then help someone else - buy someone a gift from the INF catalog http://secure.inf.org/gifts/usd/

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

                Thought so.

                1 Reply Last reply Reply Quote 0
                • Forst
                  Forst last edited by

                  This happens with a rule that has an "In" queue set to a limiter.

                  [ There were error(s) loading the rules: /tmp/rules.debug:187: syntax error - The line in question reads [187]: pass in quick on $PUBLICWLAN inet from any to any tracker 1396706432 keep state dnpipe ( 1) label USER_RULE: Limit IPv4 traffic]

                  2.2-ALPHA (amd64)
                  built on Thu Apr 3 01:45:59 CDT 2014

                  1 Reply Last reply Reply Quote 0
                  • E
                    eri-- last edited by

                    This is separate issue.
                    Please give more details in another thread.

                    1 Reply Last reply Reply Quote 0
                    • First post
                      Last post