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

    nat rules failing to apply

    Scheduled Pinned Locked Moved NAT
    4 Posts 2 Posters 565 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.
    • R
      rbflurry
      last edited by

      Recently I have been unable to create any new Port forwarding rules. This started after a reboot and alot of prexsiting rules failed to load. This is the error message I am getting for this rule in particular. all the errors look the same except the destination IP and port changes accordingly.

      There were error(s) loading the rules: /tmp/rules.debug:146: rule expands to no valid combination - The line in question reads [146]: no nat on vtnet1 proto tcp from vtnet1 to 192.168.47.90 port 80

      I am running 2.4.3-RELEASE-p1 (amd64). And can supply any additional information you may need I just dont know what else to include.

      1 Reply Last reply Reply Quote 0
      • jimpJ
        jimp Rebel Alliance Developer Netgate
        last edited by

        What is vtnet1? Does it have an IP address?

        Remember: Upvote with the 👍 button for any user/post you find to be helpful, informative, or deserving of recognition!

        Need help fast? Netgate Global Support!

        Do not Chat/PM for help!

        1 Reply Last reply Reply Quote 0
        • R
          rbflurry
          last edited by

          VTNET1 is my lan interface with an IP. it also has two virtual ip address 192.168.1.1 and 192.168.0.1

          0_1528151898868_7771f8e7-6d11-41ba-8b25-387b8953b5b5-image.png

          1 Reply Last reply Reply Quote 0
          • R
            rbflurry
            last edited by

            I realized the Nat policies that were failing was anything nating to my lan interface. Any other interface worked correctly.

            To fix this I went in and changed my lan interface from an /24 to a /23 and then back again. After refreshing the interface the Nat policy started working as expected.

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