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

    rule error There were error(s) loading the rules: /tmp/rules.debug

    Scheduled Pinned Locked Moved General pfSense Questions
    4 Posts 2 Posters 1.0k 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.
    • Y
      yuu
      last edited by

      hi
      I am configuring vpn with pfsense.
      I'm pretty new to pfsense at the moment but just saw these flagging up from today.

      There were error(s) loading the rules: /tmp/rules.debug:68: macro 'WIREGUARD__NETWORK' not defined - The line in question reads [68]: nat on $WAN inet from $WAN__NETWORK to $WIREGUARD__NETWORK -> 172.16.40.1/32 port 1024:65535

      Any idea what this is about?

      stephenw10S 1 Reply Last reply Reply Quote 0
      • stephenw10S
        stephenw10 Netgate Administrator @yuu
        last edited by

        WIREGUARD__NETWORK is an internal alias used to contain all the subnets assigned to the WIREGUARD interface. So if that is not defined it implies there is no WIREGUARD interface any longer but at one time there was because the alias still exists in a rule.

        Were you using WireGuard and now removed it?

        Do you have Outbound NAT set to automatic still? That should update itself to interface changes. If you have set it to manual though you may need to update it.

        Steve

        Y 1 Reply Last reply Reply Quote 0
        • Y
          yuu @stephenw10
          last edited by yuu

          @stephenw10 KakaoTalk_20240630_094648435.png

          Thank you for answer.
          Is there anything in these settings that needs to be erased or updated?

          1 Reply Last reply Reply Quote 0
          • stephenw10S
            stephenw10 Netgate Administrator
            last edited by

            Do you have a wireguard connection still? A wireguard interface?

            If not you should remove (or disable) those rules with that alias in them.

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