Navigation

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

    Error when using port aliases in NAT in Beta3

    NAT
    3
    6
    2666
    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.
    • M
      msamblanet last edited by

      Just upgraded from Beta2 to Beta3 and imported my old config (clean install, import old config backup)

      If I add the following single port NAT using an alias I get the error below - if I use the port # instead of the alias it works…Not a huge deal but was slightly confusing when I brought up my old config  ???

      If I can do anything further to help you troubleshoot, just let me know...

      Rule:
      WAN to Interface Address, UDP, From Teamspeak (alias for 8767), NAT to 10.11.12.16, Localport Teamspeak

      ERROR:

      php: : There were error(s) loading the rules: no IP address found for 10.11.12.16:* /tmp/rules.debug:117: could not parse host specification pfctl: Syntax error in config file: pf rules not loaded - The line in question reads* :

      Line from rules.debug when failing:
      
      rdr on rl0 proto udp from any to 68.100.12.254 port 8767:20000 -> 10.11.12.16:*
      
      Line from working rules.debug:
      
      rdr on rl0 proto udp from any to 68.100.12.254 port { 8767 } -> 10.11.12.16 port 8767
      
      1 Reply Last reply Reply Quote 0
      • S
        sullrich last edited by

        Is :20000  really the range you want or is it an error somehow?

        Also is reflection turned on in system -> advanced?  If so, please try turning it off and see if the problem persists.

        1 Reply Last reply Reply Quote 0
        • M
          msamblanet last edited by

          Nope - just trying to NAT a single port.

          Will try turning off the reflection tongiht.

          1 Reply Last reply Reply Quote 0
          • M
            msamblanet last edited by

            Actually had a second just now and turned off reflection (I didn't actually need/want it anyways) - same error however…

            BTW - is there anyplace in the GUI I can view on a full screen the notices and generated rules?  If not would be a nice future feature :)

            1 Reply Last reply Reply Quote 0
            • H
              hoba last edited by

              diagnsotics>edit file, open "/tmp/rules.debug"

              1 Reply Last reply Reply Quote 0
              • M
                msamblanet last edited by

                :-[ Well, I feel stupid now - entirely forgot about the view file feature - Thanks for pointing it out :-[

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