Navigation

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

    Problem: Access OpenVPN Clients from LAN?

    OpenVPN
    3
    5
    242
    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
      demux last edited by

      Hi,

      we have OpenVPN (TUN) up and running.  Clients can access the LAN without problems.
      But we need to access the Clients from our LAN.  This is not possible.  Not even a ping…
      Is there something that we are missing or doing wrong?  Or is it by design?
      What shall we do to let LAN devices access the OpenVPN clients?

      Thanks a lot!
      -demux

      1 Reply Last reply Reply Quote 0
      • Z
        zaiderr last edited by

        Hi,

        You probably have to push a route into the hosts in your lan saying , " TO JOIN THE CLIENT X you have to go through the gateway " which is an openvpn client too " " And then the OpenVPN Client should take the relay, and forward the packet to the distant client

        1 Reply Last reply Reply Quote 0
        • D
          demux last edited by

          This should be done by the router.  It knows where to route the packets that are not part of the LAN's subnet.  And this router is the pfsense box.
          It does this correctly in one direction (OpenVPN clients -> LAN), but not in the other (LAN -> OpenVPN clients).

          I can ping the router with both IP addresses:  It's own address and it's .1 address from OpenVPN's subnet.
          traceroute to an OpenVPN client shows that it goes to the router, but not any further.

          -demux

          1 Reply Last reply Reply Quote 0
          • jimp
            jimp Rebel Alliance Developer Netgate last edited by

            Don't forget that when attempting to reach clients, the clients must also allow it. For example, Windows firewall will block those incoming connections by default.

            The firewall will deliver the packets to those clients by default unless you are policy routing, blocking the traffic, or otherwise preventing the LAN hosts from reaching the OpenVPN clients.

            1 Reply Last reply Reply Quote 0
            • D
              demux last edited by

              Yes, it was the firewall.
              After installing Kaspersky there was "another" firewall manager above the Windows firewall.
              There I had to add the subnet and add the connection to "Local LAN".

              Thanks a lot!
              -demux

              1 Reply Last reply Reply Quote 0
              • First post
                Last post

              Products

              • Platform Overview
              • TNSR
              • pfSense Plus
              • Appliances

              Services

              • Training
              • Professional Services

              Support

              • Subscription Plans
              • Contact Support
              • Product Lifecycle
              • Documentation

              News

              • Media Coverage
              • Press
              • Events

              Resources

              • Blog
              • FAQ
              • Find a Partner
              • Resource Library
              • Security Information

              Company

              • About Us
              • Careers
              • Partners
              • Contact Us
              • Legal
              Our Mission

              We provide leading-edge network security at a fair price - regardless of organizational size or network sophistication. We believe that an open-source security model offers disruptive pricing along with the agility required to quickly address emerging threats.

              Subscribe to our Newsletter

              Product information, software announcements, and special offers. See our newsletter archive to sign up for future newsletters and to read past announcements.

              © 2021 Rubicon Communications, LLC | Privacy Policy