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

    Ipsec - Routing site to multisite

    Scheduled Pinned Locked Moved IPsec
    6 Posts 3 Posters 2.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.
    • C
      Clouseau
      last edited by

      Setup:
      Site 1        <==IPSEC==>  Site 2         <==IPSEC==>  Site 3
      192.168.1.0/24               192.168.2.0/24                 192.168.3.0/24

      How can I access Site 3 from Site 1 ?
      Ipsec tunnels works from Site 1 to Site 2 and from Site 2 to Site 3. I need to get traffic through all of this.
      I have allowed any to any rules on all LAN interfaces. I have done routes to all of these subnets.

      Sendind data from Site 1 to Site 3 I can see that traffic comes to Site 2 from ipsec tunnel BUT does not go to tunnel to Site 3.

      All tunnels done by pfSense 2.0.2.

      Do I have to do ipsec tunnels directly between all the other sites (if I would have more than 2 sites)?
      Like this:
      Site 1 <==IPSEC==> Site 2
      Site 1 <==IPSEC==> Site 3
      Site 2 <==IPSEC==> Site 3
      etc..

      –--------------------------------------------------------------
      Multible Alix 2D13, APU1,APU2,APU3 - pfSense 2.4.x 64bit
      Multible Vmware vSphere - pfSense 2.4.x 64bit

      pfSense - FreeNAS - OwnCloud

      1 Reply Last reply Reply Quote 0
      • M
        Metu69salemi
        last edited by

        Have you allowed any any also in ipsec interfaces?
        you could also add more p2's on ipsec.

        And i prefer to have every site connected to every site, cause then you don't have problem with spokes if hub dies.

        1 Reply Last reply Reply Quote 0
        • C
          Clouseau
          last edited by

          @Metu69salemi:

          Have you allowed any any also in ipsec interfaces?
          you could also add more p2's on ipsec.

          And i prefer to have every site connected to every site, cause then you don't have problem with spokes if hub dies.

          Yes I have but adding more p2 to access Site 3 via Site 2 does not work. But it makes all sense that I have to make ipsec from every site to every site. Just wondering is it possible if needed to do so? You might have a situation where Site X is not availabe to access no other manner than via Site Y.

          –--------------------------------------------------------------
          Multible Alix 2D13, APU1,APU2,APU3 - pfSense 2.4.x 64bit
          Multible Vmware vSphere - pfSense 2.4.x 64bit

          pfSense - FreeNAS - OwnCloud

          1 Reply Last reply Reply Quote 0
          • M
            Metu69salemi
            last edited by

            I mean that if you have linked site1–site2--site3, and site2 goes down. site1 and site3 can't discuss each other.

            1 Reply Last reply Reply Quote 0
            • C
              Clouseau
              last edited by

              @Metu69salemi:

              I mean that if you have linked site1–site2--site3, and site2 goes down. site1 and site3 can't discuss each other.

              Yes, that's true.

              –--------------------------------------------------------------
              Multible Alix 2D13, APU1,APU2,APU3 - pfSense 2.4.x 64bit
              Multible Vmware vSphere - pfSense 2.4.x 64bit

              pfSense - FreeNAS - OwnCloud

              1 Reply Last reply Reply Quote 0
              • C
                craigduff
                last edited by

                I can explain how to do it, as i am have done it. But wouldnt it just be easier to establish another IPsec tunnel to Site 3 from Site 1?

                Kind Regards,
                Craig

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