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

    Port Forwarding: Remote Client via IPSEC VPN - Port Forward to Pfsense LAN IP

    Scheduled Pinned Locked Moved NAT
    4 Posts 2 Posters 1.0k 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.
    • R
      rayone
      last edited by

      Hello, I am having a IPSEC Port Forwarding Issue, any help appreciated!!

      • Normal: Interal LAN A IP - port forward to WAN - Works fine as you would expect

      • IPSEC Issue: Remote Client IP through IPSEC VPN - port forward to LAN A - doesn't work

      Image explains the issue:

      fail.png
      fail.png_thumb

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

        I don't get it. 10.0.0.0/16 does not collide with 10.17.0.0/24.

        But what you are doing should work, I guess.

        Depends on what the rest of the firewall rules on that interface are, the IPsec traffic selectors, any policy routing in place, etc.

        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
        • R
          rayone
          last edited by

          Yes, sorry I meant to put 10.0.0.0/8.

          In theory it should work, its good to hear that someone else agrees. Here are some further details:

          Firewall Rules
          Are allow all on all interfaces for testing

          IP Traffic Selectors (see image).
          Only NAT is not configured, I don't need this right?

          Policy Routing
          I have not done anything with routing policy. What would I need to do?

          Thanks,
          Ray

          ipsecHQ.png
          ipsecHQ.png_thumb

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

            Well that doesn't work because 172.16.0.0/24 is not in the traffic selector. Port forwards translate the destination address, not the source address.

            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
            • First post
              Last post
            Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.