Navigation

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

    IPSec DNAT not working

    NAT
    2
    8
    63
    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
      Matt_Sharpe last edited by

      We had a prior setup on an NSX edge for a customer where they would attempt to RDP to an IP address which was listed on the remote IPsec site. It would then DNAT on RDP to an IP address on an isolated interface (isolated network is NOT on the IPsec)

      This previously was setup to DNAT on 'any' interface. However it doesn't appear PFsense offer an 'any' on DNAT rules.

      Wondering how we can re-create the same NAT rule but having no luck so far...

      V 1 Reply Last reply Reply Quote 0
      • V
        viragomann @Matt_Sharpe last edited by

        @matt_sharpe
        Not clear, what you want to achieve here.
        Maybe you can provide a drawing, which shows details, from where you want to access which device.

        M 1 Reply Last reply Reply Quote 0
        • M
          Matt_Sharpe @viragomann last edited by

          @viragomann so if we imagine a simple 2 site connection via an IPsec VPN.

          Site 1 = 172.16.100.0/24
          Site 2 = 172.16.200.0/24

          Site 2 has an isolated network which we want to be able to provide RDP access to. However, we don't want this on IPsec VPN, so we're aiming to create a NAT rule which NATs an IP address on the 172.16.200.0/24 which directs to the isolated network.

          The connection should look like this:

          172.16.100.1 > IPsec tunnel > 172.16.200.253 (NATs to) 172.16.210.253

          We achieved this on another firewall using a DNAT on 'any' interface' However no luck on PFsense as of yet.

          V 1 Reply Last reply Reply Quote 0
          • V
            viragomann @Matt_Sharpe last edited by

            @matt_sharpe said in IPSec DNAT not working:

            However, we don't want this on IPsec VPN

            NAT has to happen in IPSec. There is no way around.

            172.16.100.1 > IPsec tunnel > 172.16.200.253 (NATs to) 172.16.210.253

            You can do this in the IPSec phase 2, however:
            At site 2 add an additional p 2, at
            local network select Address and enter 172.16.210.253
            NAT/BINAT translation select Address and enter 172.16.200.253
            Remote Network select Network and enter 172.16.100.0/24

            M 1 Reply Last reply Reply Quote 1
            • M
              Matt_Sharpe @viragomann last edited by

              @viragomann Done this in our lab but no luck (generic FW rules allowing all traffic)

              I assume no P2 tweaks needed on Site 1 for this....

              M V 2 Replies Last reply Reply Quote 0
              • M
                Matt_Sharpe @Matt_Sharpe last edited by

                @matt_sharpe Got it working, needed the Phase 1 setting "Split Connections" and an IPsec tunnel restart. Thanks @viragomann !

                1 Reply Last reply Reply Quote 0
                • V
                  viragomann @Matt_Sharpe last edited by

                  @matt_sharpe
                  If it's a pfSense it should work with that so far.

                  But since both phase to have the same local network, you probably have to move the BINAT p2 to the top.

                  M 1 Reply Last reply Reply Quote 0
                  • M
                    Matt_Sharpe @viragomann last edited by

                    @viragomann This resolution does work. However the P2 tunnel (only created on the target site) is disconnecting after short periods. Even with a keep alive enabled and an IP to ping...

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