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

    IPSec narrowing down

    Scheduled Pinned Locked Moved IPsec
    1 Posts 1 Posters 48 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.
    • D
      DBug
      last edited by

      I added an IPSec between two pfSense instances. from 10.0.0.0/24 to 10.12.0.0/16
      If I go to the IPSec status and bring the connection P1 & P2 up the connection is established and I am able to access from 10.0.0.0/24 to any place in 10.12.0.0/16
      however, if I let the connection be established automatically because 10.0.0.2 tried to connect to 10.12.2.3, the tunnel is created from 10.0.0.0/24 to 10.12.2.0/24 and I cannot access the whole range on 10.12.0.0/16

      Also, If I manually connect P1 & P2 from the IPSec status page and then 10.0.0.2 tries to connect to 10.12.2.3, a new connection appears in the IPSec status page from 10.0.0.0/24 to 10.12.2.0/24

      I have checked and double checked all P1 & P2 settings and they are all the same.

      When I created 3 phase 2 settings 10.0.0.0/24 to 10.12.2.0/24, 10.12.3.0/24, 10.12.4.0/22 (which are all the networks I am currently intrested in) things appear to work normally and even if I manually connect there is no 2nd line created when 10.0.0.2 tried to connect to 10.12.2.3

      Any ideas?

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