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

    NAT through IPSEC VPN help please

    Scheduled Pinned Locked Moved NAT
    3 Posts 2 Posters 1.7k 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.
    • P
      pbl
      last edited by

      I've really done quite a bit of research and brute force combinations trying to get this to work. I guess I just simply don't know what I'm doing.

      A vendor has asked me to establish a full time IPSEC VPN with them to allow them access to their robot for software maintenance. I've managed establish the Phase 1 Phase 2 link. That part works.

      We need to connect them to me, and what I've been given is as follows:

      • Vendor encryption domain: 65.67.163.160/27 (they'll be connecting from several IP's to get to one asset)
      • Our encryption domain: 172.16.16.194/32 (I'm assuming that this is their alias for the next item)
      • The robot end point that they are reaching: 192.168.80.14 (this is on our LAN)

      Can anyone please tell me how I can get their multiple sources to connect to our robot, via the encryption domain, which is a different IP than our LAN address? I'm assuming that the flow is Vendor Encryption domain –> Our encryption domain --> Our LAN address.

      1 Reply Last reply Reply Quote 0
      • P
        podilarius
        last edited by

        I would start with making sure nat traversal is on. If they are using the same encryption credentials, then you might have to allow multiple connections. Also, if you have not done this already, go to Firewall -> Rules -> IPSEC and create an allow for the asset. Like source -> any, source ports -> any, destination -> asset, destination port -> any.

        1 Reply Last reply Reply Quote 0
        • P
          pbl
          last edited by

          Thanks for your assistance. A rule allowing all IPSEC traffic is in place. Should I be creating a 1:1 NAT?

          Would a 1:1 with external of 65.67.163.160, and internal of 172.16.16.194, and a destination of 192.168.80.14 work in this case?

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