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

    [SOLVED] inbound traffic with NAT/BINAT translation via IPsec

    Scheduled Pinned Locked Moved IPsec
    3 Posts 2 Posters 4.3k 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.
    • Q
      qsthensel
      last edited by qsthensel

      Hi,
      we are using pfsense 2.4.4
      our LAN subnet is 192.168.1.0/24
      we have setup an IPsec IKEv1 Tunnel to a partner which need to use NAT/BINAT translation using 192.168.101.2 as the NAT Address.
      Now the partner wants to access a Service within our LAN on the IP 192.168.1.26 over this IPsec Tunnel.
      How do I realize such a traffic flow?
      Do I just need to setup a Port Forward NAT on the IPsec interface giving the NAT IP 192.168.101.2 as destination address and the local LAN IP 192.168.1.26 as the Redirect IP?
      And then for sure setup firewall rules on the IPsec interface with the desired LAN IP as the destination?

      We have already set up a few IPsec tunnels with NAT/BINAT translation but always accessing services on the remote side an not accessing services on my LAN side.

      I do not find something about this in the docs.

      Thank you and best regards!

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

        Have you tried to do what you have described? It sounds like the correct thing to do, but I do not think I have ever seen it done - or don't remember. Note that you can only do one such forward on each port. Just like inbound connections to a single WAN address.

        Also, you cannot forward from arbitrary source addresses over IPsec because you do not get reply-to. The source address (the destination for reply traffic) has to be something interesting to IPsec - as in a remote network in the Phase 2 entry.

        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 2
        • Q
          qsthensel
          last edited by

          I tried it exactly as I guessed (and derelict too) and it worked.

          Thank you for your help!

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