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

    Error loading rules

    General pfSense Questions
    firewall rules configuration
    1
    3
    721
    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
      jbeez
      last edited by jbeez

      All my fault, tried a small edit to filter.inc, didnt work, restored filter.inc but ever since I’m getting an error loading one of the rules in /tmp/debug.rules despite replacing original filter.inc file. Its a rule for a 169 network and it has a tracker number listed in there. I’m thinking something got out of sync with that tracker? I’m not even sure how to check that.

      fw php-fpm[19282]: /rc.filter_configure_sync: New alert found: There were error(s) loading the rules: /tmp/rules.debug:257: syntax error - The line in question reads [257]: block in  quick from 169.254.0.0/16 to any tracker 1000000101 label "Block IPv4 link-local"
      

      What I've tried so far, in order:
      Restored original filter.inc
      Reverted configuration change to a revision from last night(made this change this morning).
      Rebooted.

      Please help! This is very puzzling.

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

        @jbeez said in Error loading rules:

        169.254.0.0/16

        This may be a red herring... when I check the /tmp/debug.rules it looks like that rule and everyone after it shows the same, I'm guessing system.log only shows the first error because it stops at that point

        pfctl -f /tmp/rules.debug
        /tmp/rules.debug:254: syntax error
        /tmp/rules.debug:...: syntax error
        /tmp/rules.debug:549: syntax error
        pfctl: Syntax error in config file: pf rules not loaded
        

        the line directly above this is anchor "ipsec/*"

        J 1 Reply Last reply Reply Quote 0
        • J
          jbeez @jbeez
          last edited by

          @jbeez fixed... definitely user error. I was restoring a filter.inc from a prior version. Restored the proper one and its good to go.

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