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

    Disabling NAT outbound on DMZ only

    Scheduled Pinned Locked Moved NAT
    9 Posts 3 Posters 1.9k 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.
    • P
      pwyatt
      last edited by

      Is there a way to disable outbound NAT on DMZ interface only? I am strictly using this for gaming on my PS4 and Xbox One and don't want any NAT at all. As of now I cannot access the internet on this interface without the Outbound NAT being on automatic. Is there a manual rule I can create that will disable it?

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

        Outbound NAT is done on the outbound interfaces.

        If you set it to hybrid and make a rule that matches the DMZ source addresses and check Do not NAT it seems like it should work.

        I've never used that checkbox.

        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
        • K
          kpa
          last edited by

          Do you have routable public IP addresses on the DMZ?

          1 Reply Last reply Reply Quote 0
          • P
            pwyatt
            last edited by

            no

            1 Reply Last reply Reply Quote 0
            • K
              kpa
              last edited by

              Well in that case you are forced to do outbound NAT, there's no way around it.

              1 Reply Last reply Reply Quote 0
              • P
                pwyatt
                last edited by

                I was afraid that was the case. Thanks.

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

                  Sorry. I thought that went without saying.

                  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
                  • P
                    pwyatt
                    last edited by

                    More of a test than anything. I keep getting kicked out of on-line games on the PS4 and Xbox One, so I was testing to see if it's Comcast service causing it or if it's because I am behind a NAT. I set an outbound rule for all my xboxes and PS4 and got it down to NAT 2 but that didn't help much either.

                    1 Reply Last reply Reply Quote 0
                    • K
                      kpa
                      last edited by

                      You could bridge OPT1 to WAN and that would give you a non-NATed network with public IPs (assuming the WAN network is using routable public IPs) and you would still be able to filter the traffic with firewall rules.

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