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

    How to visit client from server side?

    OpenVPN
    3
    7
    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.
    • J
      jeffwji
      last edited by

      Hi all,

      Recently I'm encountering a problem when connect two offices together via vpn. I'm able to access site B(OpenVpn Server) from site A(OpenVpn Client)  following by this introduction: https://doc.pfsense.org/index.php/Routing_internet_traffic_through_a_site-to-site_OpenVPN-connection_in_PfSense_2.1  but reverse is failed. What I'm missing?

      Your help will be very appreciated.

      Thanks

      Jeff

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

        • A firewall rule at clients OpenVPN interface to permit access.

        • If the client isn't the default gateway in its network, an appropriate route at the hosts you want to reach or a NAT rule at the client.

        • Consider that windows firewall like some other software firewalls block access from remote networks by default.

        1 Reply Last reply Reply Quote 0
        • J
          jeffwji
          last edited by

          Thank you Viragomann, I don't think it's about client end, as if I trace the package, it was stuck at server side, the server can't route it to client properly.

          Jeff

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

            Are you attempting access from a server-side network for which the client has a route? Meaning the server side network the client can access?

            viragomann listed all the things it's likely to be.

            If you can connect in one direction but not the other it's probably firewall rules, not routes.

            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 0
            • J
              jeffwji
              last edited by

              Yes Derelict, The firewall rules mentions by the link above all have been applied but still doesn't work, do you mean they are probably not enough?

              Jeff

              1 Reply Last reply Reply Quote 0
              • J
                jeffwji
                last edited by

                Weird! it works now! I did a bunch of tests, not sure which one triggered…but however it is working...

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

                  Amazing.

                  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 0
                  • First post
                    Last post
                  Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.