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

    Problem with creating Routable network with Do-Not-NAT with the external router

    Scheduled Pinned Locked Moved Routing and Multi WAN
    2 Posts 2 Posters 449 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.
    • K Offline
      Koval88
      last edited by

      Hello,

      I'm trying to create a routable on the pfsense with external router for servers on the OP2 Interface without NAT'ting.
      This is a virtual environment running on the ESXI Server. I have two routers, one VyOS that will be a core router for multiple pfSense routers.
      Please check the attachment for the brief diagram what I am trying to accomplish.
      In this example I have only one pfSense that I am trying to get working and acting as a router while still using NAT for the LAN interface.

      The VyOS would have a route from source network 192.168.101.0/24 to Next-Hop 100.100.129.1. I do not want to use Virtual IP and do 1:1 NAT but instead trying to accomplish Outbound NAT with Do-Not NAT option enabled in with Outbound NAT mode.

      I have tried creating a separate gateway for the OP2 Network  and creating static routing to the VyOS Network from the new Gateway.

      I still want the LAN network to pass through the firewall rules to the OP2 network internally.

      I must be missing some logic how the Outbound NAT works and how to accomplish that with the pfsense.
      Please let me know the steps to take and what do I need to make this happen and what am I missing logically and configuration-wise to get this working.

      Thank you!

      Edit:
      The router to the right of the diagram is pfSense not VyOS. A typo on a visio.
      Project_Network.jpg
      Project_Network.jpg_thumb

      1 Reply Last reply Reply Quote 0
      • johnpozJ Offline
        johnpoz LAYER 8 Global Moderator
        last edited by

        100.100.. why would you this.. Is your router doing address translation across its interfaces when addresses are identical on two different interfaces?

        So 10.129 is that suppose to represent your public address?

        So your routing 192.168.101 it itself the router on the left?  The route on that router on the left to get to 192.168.101 would be to pfsense wan IP 100.100.129.10

        So you setup your router on the left to nat this 192.168.101 network?  If not not going to work.  What would be the point of natting your 192.168.105 network to your 100.100.129 network??  And then to nat it again??

        An intelligent man is sometimes forced to be drunk to spend time with his fools
        If you get confused: Listen to the Music Play
        Please don't Chat/PM me for help, unless mod related
        SG-4860 25.07.1 | Lab VMs 2.8, 25.07.1

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