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

    Setup of OpenVPN

    Scheduled Pinned Locked Moved OpenVPN
    4 Posts 4 Posters 2.2k 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.
    • P
      punkme112
      last edited by

      All,

      I have been running pfsense for almost a year now and I love it.  Now, I am just getting into using the OpenVPN on here.  I am using 2.0.  I ran through the server setup wizard and have all my certs created, and it is running with no issues.  I then can connect to this fine from my client PC and authenticate with no issues. However, I get my tunnel IP and dns servers, but I do not get my gateway IP.  I am also unable to connect to any of my LAN devices on my home network.  This may have been posted somewhere else on here, but I just wanted to try and get some input since I am still a noob at this.  Any help would be appreciated.  If any settings are needed to be seen, I can upload them as needed.

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

        1. Enter the network address of your LAN under "Local Network". This will allow access to your LAN when using split tunneling.

        2. If you want your gateway to show, and force all traffic thru the tunnel, check "Redirect Gateway".

        1 Reply Last reply Reply Quote 0
        • N
          Nachtfalke
          last edited by

          3. if you like to route to further subnets than your "Local Netzwork" (point 1. of the post above) than enter this in OpenVPN Server custom options:

          push "route 192.168.100.0 255.255.255.0";
          
          1 Reply Last reply Reply Quote 0
          • D
            dlogan
            last edited by

            I had the same problem.  With the OpenVPN client, if you're using Windows 7 or Windows Vista, you need to run the client as Administrator – not meaning an account with administrative rights, but either right-click, run as administrator, or edit the properties of the shortcut to run the client as admin.  It needs this to create a route on your Windows PC.  Running as administrator solved the problem for me.

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