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

    Outbound NAT Doesn't Work [FIXED]

    Scheduled Pinned Locked Moved NAT
    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.
    • O
      oliverjrose99
      last edited by

      Hi

      Im trying to setup a virtual network with pfSense and im having trouble getting Outbound NAT to work. I currently have pfSense on VMware with a WAN interface of 192.168.0.100 and a LAN interface of 10.1.1.1. For NAT I have automatic mode set and a mapping on the WAN interface with source 10.1.1.0/24 and address 192.168.0.100.

      I have a gateway on WAN as 192.168.0.100. From a virtual machine I can ping 10.1.1.1 and 192.168.0.100 but nothing else.

      What am I doing wrong?

      Thanks

      –EDIT--

      I fixed the problem. I didn't select the upstream gateway on the WAN interface. Thanks to Derelict for pointing out the gatway ip error

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

        You have your gateway set to itself.  It should be the next-hop to get off the 192.168.0.0 network.

        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
        • O
          oliverjrose99
          last edited by

          @Derelict:

          You have your gateway set to itself.  It should be the next-hop to get off the 192.168.0.0 network.

          I changed the gateway to 192.168.0.1 which is the physical routers gateway. I still cant access the internet.

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

            The thread is marked as fixed.  What's the deal? You mean the physical router's LAN interface address, not gateway, right?

            You're going to have to go through the basic troubleshooting steps and tell us what's actually not working.  "can't access the internet" could be anything.

            https://doc.pfsense.org/index.php/Connectivity_Troubleshooting

            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.