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

    Site access over IPSec

    Scheduled Pinned Locked Moved Routing and Multi WAN
    7 Posts 3 Posters 644 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.
    • A
      abracadabras
      last edited by

      Hello! Help please, there's something I can't understand. The problem is this. There are two offices "A" and "B" Each office has pfsense installed. IPSec is configured between offices (mode: Tunnel IPV4). A website has been deployed in office "B". I'm trying to access this site in office "B" via an external IP through office "A". NAT and Firewall are configured. Packages do not reach office "B".

      Client --> Office A <----- IPSec -----> Office B ------> Site

      P 1 Reply Last reply Reply Quote 0
      • P
        Pra2in @abracadabras
        last edited by

        @abracadabras .. EXTERNAL IP ? Virtual IP ? why do you want to access via External IP when you can just use Private IP of SiteB via IPSEC Tunnel ?

        A 1 Reply Last reply Reply Quote 0
        • A
          abracadabras @Pra2in
          last edited by

          @Pra2in Sorry for not explaining. In office "A" there was a site behind NAT, which I moved to office "B". But access is needed through the public IP WAN port of office “A”.

          V 1 Reply Last reply Reply Quote 0
          • V
            viragomann @abracadabras
            last edited by

            @abracadabras
            IPSec is not really ideal to handle this traffic.

            Is it a policy based or a routed IPSec?

            In case of policy, it would only work if you route all upstream traffic from B to A. This means at A phase 2 local network = 0.0.0.0/0, at B remote network = 0.0.0.0.0/0.

            Or in case of routed IPSec, you need at least to masquerade the forwarded traffic at A on the outgoing interface, as far as I know.

            Both solutions might have undesired side-effects. However, you can do this well with OpenVPN though.

            A 1 Reply Last reply Reply Quote 0
            • A
              abracadabras @viragomann
              last edited by

              @viragomannThanks for the answer. This is policy based IPSec. I'll look for other options then.

              V 1 Reply Last reply Reply Quote 0
              • V
                viragomann @abracadabras
                last edited by

                @abracadabras
                If masquerading is acceptable you could also forward the traffic over WAN.
                However, at B you would only see the IP of A.

                A 1 Reply Last reply Reply Quote 0
                • A
                  abracadabras @viragomann
                  last edited by

                  @viragomann Thank you very much, I'll try this option.

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