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

    PFSense IPSec with phase 2 remote subnet overlaps local subnet.

    IPsec
    2
    4
    1.5k
    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.
    • F
      Fenx42
      last edited by

      I'm trying to integrate my pfSense into a larger network via IPSec VPN. The network is a hub and spoke configuration. My router is one of the spokes and the remote site (hub) is a Fortinet Fortigate, therefore I have to use IPSec. The attached image is an oversimplified representation of the network since there are a lot of sites and multiple subnets per site. The problem is I'm trying to avoid creating a lot of phase 2's. In other firewalls I've used, you can use a supernet (example a /16) in the phase 2 for the remote network. This will in this example send 10.0.anything.anything up the IPSec and let the hub router handle the routing between sites. But since the local LAN falls within that /16, the PFSense is actually sending local traffic to the IPSec, rather than it recognizing that that subnet belongs to a local interface. Is there a way to handle this using IPSec without building a bunch of phase 2's that do not overlap with the local subnets?

      Thanks in advance :)0_1535476340038_ipsec supernet.png

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

        The firewall should bypass the LAN network there, but it will only work if 10.0.5.0/24 is on LAN, not an OPT or secondary interface. LAN must be the second defined interface. In Status > Interfaces the internal name will be lan. As in LAN Interface (lan, igb1.223)

        You must also not uncheck Enable bypass for LAN interface IP in the advanced IPsec settings. That must be enabled.

        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 1
        • F
          Fenx42
          last edited by

          This post is deleted!
          1 Reply Last reply Reply Quote 0
          • F
            Fenx42
            last edited by Fenx42

            Ahh.. Got it. But I have 7 interfaces LAN I have to apply this to, not just one. In the pfSense website, I found Bug 5826 that describes the problem I'm having. https://redmine.pfsense.org/issues/5826 . I'll do some research to see if I get into the strongSwan config if I might be able to do this for multiple interfaces manually.

            Thanks again for the help. I never noticed the Auto-exclude LAN address feature in IPSec.

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