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

    Using OpenVPN with my local network

    Scheduled Pinned Locked Moved OpenVPN
    1 Posts 1 Posters 609 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.
    • T
      tcsteve
      last edited by

      Hello,

      I'm using a Windows 7 laptop for all of this.

      We have a pfSense box in our office, and another one at the data center.  When I'm in the office, I can connect to the local pfSense box at 192.168.1.1.  I set up OpenVPN at the data center so that I can administer the remote pfSense box from the office also.

      In the OpenVPN Server set up page, I configured the tunnel network as 10.10.1.0/24.  On the LAN interface for that pfSense box, I set it up as 192.168.10.0/24, but I left the IPv4 Local Network box blank in the OpenVPN Server config.

      I can connect and log in to the remote pfSense box, but when I do the local pfSense box at 192.168.1.1 is unreachable, I assume our entire office LAN is unreachable (by IP) when I have the VPN connected.

      How can I set that up so that I can connect to the remote pfSense box by VPN (and, hopefully, access its LAN also) while still being able to access the office LAN?

      edit: after disconnecting the VPN, I still cannot access the local pfSense box at 192.168.1.1.

      In case it's relevant, the remote pfSense used to have the LAN configured at 192.168.1.0/24, but I changed that to 192.168.10.0/24 once I realized I couldn't connect to the local LAN while the VPN is connected.  I believe I made all of the necessary changes when I changed the remote LAN.

      I just noticed that the dashboard for the remote box showed the LAN interface status as "No Carrier".  I changed the LAN config back to 192.168.1.0/24, and the status changed to "autoselect".  The LAN currently is not connected to anything, so "autoselect" makes sense because it's not plugged in.  I'm not sure if the "No Carrier" message indicates that there's a problem using the other IP range.

      Never mind, I just switched back to 192.168.10.0/24 and it stayed at "autoselect".

      Thanks

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