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

    BINAT OK over IPsec on 2.1?

    Scheduled Pinned Locked Moved NAT
    2 Posts 2 Posters 933 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.
    • T
      ttblum
      last edited by

      Hello,

      I understand that bidirecting NAT'ing is now supported over IPSec in 2.1?

      So, the procedure to solve a routing conflict for this would be:

      
      192.168.1.0/24 <=pfsense 2.1==>=binat==> 192.168.70.0/24 <====ipsec====><=remote endpoint=> 192.168.1.0/24
                                              (NAT'd local LAN)
      
      

      Configure IPSec tunnel as normal on the pfSense side, but in Phase2 under Local Network NAT/BINAT, select Type: 'LAN subnet' and fill in 192.168.70.0/24?

      Then, after the tunnel establishes, the remote LAN can access the local IPs as follows?

      192.168.70.1 -> 192.168.1.1
      192.168.70.2 -> 192.168.1.2
      192.168.70.3 -> 192.168.1.3
      etc.?

      1 Reply Last reply Reply Quote 0
      • jimpJ
        jimp Rebel Alliance Developer Netgate
        last edited by

        Yes, NAT+IPsec works fine on 2.1 and later.

        It's close to what you said: Select Type=LAN Subnet, and then in the NAT options directly under that choice, pick Network and then enter 192.168.70.0/24

        Firewall rules would still refer to 192.168.1.x (rules after NAT, as always)

        Remember: Upvote with the 👍 button for any user/post you find to be helpful, informative, or deserving of recognition!

        Need help fast? Netgate Global Support!

        Do not Chat/PM for help!

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