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

    site to site not working loc to loc

    Scheduled Pinned Locked Moved OpenVPN
    11 Posts 2 Posters 1.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.
    • M
      mic.bummer
      last edited by mic.bummer

      Hello forum, the configuration of the site is not working for me :(

      Routes are created on two sites, from local networks the route goes to ovpn adress and then there is no route to the local network, what should I update in my configuration?

      alt text
      alt text

      hm..😿

      alt text
      alt text
      alt text
      alt text

      thanks for reply 😧

      V 1 Reply Last reply Reply Quote 0
      • V
        viragomann @mic.bummer
        last edited by

        @mic-bummer
        In the client specific override state a certain IP for the client in the "Tunnel network" box.
        Also enter the client site's networks into the "Remote Networks" field in the same way as you did in the server settings and empty the Advanced options box.

        M 1 Reply Last reply Reply Quote 0
        • M
          mic.bummer @viragomann
          last edited by mic.bummer

          @viragomann

          Yes, I tried adding networks, routes are added on two sites, but there is no access to the local network😧

          alt text
          alt text

          from pf site B (client/10.0.1.2/10.10.21.1) can ping pf site B (server/10.0.1.2/10.2.101.1) and network clients 10.2.101.0/24 but not from client network site (B) 10.10.21.0/24

          from pf site A (server) cant ping pf site B (client/10.0.1.2/10.10.21.1) and network clients 10.10.21.0/24

          M V 2 Replies Last reply Reply Quote 0
          • M
            mic.bummer @mic.bummer
            last edited by

            tracert

            alt text
            alt text

            1 Reply Last reply Reply Quote 0
            • V
              viragomann @mic.bummer
              last edited by

              @mic-bummer
              10.0.1.0/28 is not a usable client IP, this is the network address. Enter something like 10.0.1.11/28 instead.

              Also I suggested to remove the iroute commands and enter the networks into the "Remote Networks" field in the CSO as it's intended in the pfSense docs.

              M 1 Reply Last reply Reply Quote 0
              • M
                mic.bummer @viragomann
                last edited by mic.bummer

                @viragomann where can I change the client's address? It automatically gets 10.0.1.2....

                alt text

                changed the parameter, but no change

                V 1 Reply Last reply Reply Quote 0
                • V
                  viragomann @mic.bummer
                  last edited by

                  @mic-bummer
                  The "Remote Networks" box in the CSO is still empty. You have to enter all client site networks there, same as in the server settings.

                  Then ensure that the client gets the correct virtual IP.

                  M 1 Reply Last reply Reply Quote 0
                  • M
                    mic.bummer @viragomann
                    last edited by mic.bummer

                    @viragomann yeap, client take 10.0.1.2 same before..

                    in diag_routes correct routes are added

                    network clients also cannot access 😵

                    alt text

                    V 1 Reply Last reply Reply Quote 0
                    • V
                      viragomann @mic.bummer
                      last edited by

                      @mic-bummer said in site to site not working loc to loc:

                      yeap, client take 10.0.1.2 same before..

                      So this means, that the CSO is not applied.
                      Ensure that the common name in the clients certificate is equal to that you stated in the CSO.

                      If this is correct set the servers log level to 4 and reestablish the connection and look in the log after for hints on this.

                      M 2 Replies Last reply Reply Quote 1
                      • M
                        mic.bummer @viragomann
                        last edited by mic.bummer

                        @viragomann openvpn status is connected, hope what no problem with ovpn authorization and routes, all traffic on the firewall is allowed, this is a new installation of pfssense

                        but clients a/b of network cant see other client network b/a ..

                        1 Reply Last reply Reply Quote 0
                        • M
                          mic.bummer @viragomann
                          last edited by

                          @viragomann hi, your solution work!
                          thanks!

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