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

NATing behind IPSec Vti Tunnel

Scheduled Pinned Locked Moved NAT
6 Posts 2 Posters 454 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
    trademark27
    last edited by trademark27 Oct 2, 2019, 1:10 AM Oct 2, 2019, 1:07 AM

    I've managed to setup an IPSEC (vti) tunnel between PFsense running on AWS and my Cisco router at home. Reason for this, is to have access to a public IP since my stupid ISP has resorted to NATing its customers. So basically i want to point to public IP on pfsense in the cloud, and be able to reach my local services at home. However, i'm stuck on the NAT part. If i use my phone to connect to the ipsec vpn, i can access my local network, but outside of the vpn, no luck. Doing a TCPDUMP on the local server shows tracffic hitting it but port still shows blocked. See screenshots

    port-check.png pftop.png host.png fw-nat.png image url)
    ipsec2.png ipsec.png

    1 Reply Last reply Reply Quote 0
    • D
      Derelict LAYER 8 Netgate
      last edited by Oct 2, 2019, 3:00 AM

      So Your home is behind NAT now so you cannot connect directly.

      You want to:

      1. Connect via IKEv2 using your phone into an AWS IPsec
      2. From there, go across a VTI to your home network

      ?

      Where does the NAT come in?

      Probably need a better explanation of exactly what you want to do and what is not working. Be descriptive and let us know what subnets are in what part of the network.

      A diagram would be great.

      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 0
      • T
        trademark27
        last edited by Oct 2, 2019, 6:14 PM

        I'm already able to connect to VPN using phone and access my home network. But that's not the goal. I want to access my home network without having to connect to VPN. Hence the NAT from outside public to host behind tunnel.

        Phone > Public IP of pfsense > VPN Tunnel > Home Network > NVR
        iphone > 55.55.55.55 > 10.2.0.0/30 > 172.10.15.0/24 > 172.10.15.20:554

        I want to access 55.55.55.55:554 from internet

        1 Reply Last reply Reply Quote 0
        • D
          Derelict LAYER 8 Netgate
          last edited by Derelict Oct 2, 2019, 6:34 PM Oct 2, 2019, 6:32 PM

          I still don't know what you are representing with that diagram.

          But if you want to connect to a WAN from an arbitrary internet address and hit a port forward to something across an IPsec VTI, you cannot do that with IPsec.

          You can do it with OpenVPN, though.

          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 0
          • T
            trademark27
            last edited by trademark27 Oct 2, 2019, 6:37 PM Oct 2, 2019, 6:34 PM

            i also have openvpn up, can you explain how to do this?
            what about if i do a L2TP over Ipsec? or gre ?

            1 Reply Last reply Reply Quote 0
            • D
              Derelict LAYER 8 Netgate
              last edited by Oct 2, 2019, 6:38 PM

              https://forum.netgate.com/post/489029

              The diagram is down below. There are two. That was written against the one with the blue symbols. The version of pfSense there is old but the principles haven't changed.

              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 0
              1 out of 6
              • First post
                1/6
                Last post
              Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.
                This community forum collects and processes your personal information.
                consent.not_received