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

    NAT all traffic from alias except a single port/IP

    Scheduled Pinned Locked Moved NAT
    23 Posts 4 Posters 3.5k 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.
    • L
      lastb0isct
      last edited by

      Yes, the 192.168.1.62 machine is fine with routing directly through the WAN interface.  Have to clear states to get it to behave that way though since it holds on to the OPT1TOPIA interface until states have been refreshed.

      EDIT: I do also notice that it helps restarting the 192.168.1.62 machine when making those changes or else it stays in a funky state.  Upon rebooting it behaves at it should through the WAN_DHCP interface.

      1 Reply Last reply Reply Quote 0
      • L
        lastb0isct
        last edited by

        I was able to figure this out!  Attached are the rules. I figured out that it was traffic on port 563 that was needed and did a bi-directional rule.

        Is there any easier way to do bi-directional rules than how i did it here?

        ![Usenet success.PNG](/public/imported_attachments/1/Usenet success.PNG)
        ![Usenet success.PNG_thumb](/public/imported_attachments/1/Usenet success.PNG_thumb)

        1 Reply Last reply Reply Quote 0
        • DerelictD
          Derelict LAYER 8 Netgate
          last edited by

          The first rule with the source port 563 is probably doing nothing.

          There is no such thing as a bi-directional rule on an interface tab.  They only match traffic being received by that interface.

          The firewall state is created which automatically allows return traffic for that connection.

          Chattanooga, Tennessee, USA
          A comprehensive network diagram is worth 10,000 words and 15 conference calls.
          DO NOT set a source address/port in a port forward or firewall rule unless you KNOW you need it!
          Do Not Chat For Help! NO_WAN_EGRESS(TM)

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