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

    Port Forward and translated traffic on LAN not going through IPSec

    IPsec
    1
    1
    427
    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
      trimmings
      last edited by

      Hi all.

      I have a device in a DMZ (192.168.240.x) network that I have port forwarded to the LAN interface of my pfsense router.  The thing works great in the local network (172.16.A.xyz/24) but will not open on the Ipsec remote network (172.16.B.xyz/24) - I have allowed all Ipsec interface traffic and all other traffic is happily operating from network A to B.

      –---------
      EDIT: fixed the below by reworking the ipsec routes (it didn't like routing to a /16 172 subnet) and some tweaks
      Also in a problem along the same vein perhaps I have a network through a gateway that I route to (10.3.xyz.xyz/16) - from the local networking everything seems to be working fine, however it won't seem to function over the Ipsec vpn at the remote site.

      Am I missing something in translating networks through the Ipsec interface? In previous routers I used (snapgears) creating a source translation on the outgoing traffic interface was sufficient, but that doesn't seem to be the case here or I'm doing something wrong.

      Thanks in advance - if there is any more info, config required let me know...

      1 Reply Last reply Reply Quote 0
      • First post
        Last post