Navigation

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

    OpenVPN access to a single machine

    OpenVPN
    3
    4
    170
    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
      Parth last edited by

      Hi,

      I want to give my team remote access over VPN to a single NAS file server we have on premises. However, when configuring my VPN server when I enter 192.168.15.200/32 (the local IP address of my NAS server) as the CIDR range for the "IPv4 local network", the server provides access to the entire 192.168.15.0/24 subnet instead of just the 1 machine I would like it to.

      I do not know if I am not configuring my pfSense firewall incorrectly or if this is a bug. Maybe this use case is supposed to be handled using firewall rules instead of in the VPN server configuration. However, I'm a noob; so, any help on how to do this will be greatly appreciated.

      1 Reply Last reply Reply Quote 0
      • Rico
        Rico LAYER 8 Rebel Alliance last edited by

        You need to craft your Firewall Rules in the OpenVPN Tab.

        -Rico

        2x Netgate XG-7100 | 11x Netgate SG-5100 | 6x Netgate SG-3100 | 2x Netgate SG-1100

        1 Reply Last reply Reply Quote 0
        • KOM
          KOM last edited by

          You can define your OpenVPN users in such a way that they get the same IP address every time, and then use that IP address in a firewall rule on the OpenVPN tab to allow or block access to whatever you want. That way you can allow full access to employees through the VPN, but external contractors can only get to specific addresses that you allow.

          1 Reply Last reply Reply Quote 0
          • P
            Parth last edited by

            Sorry, it was an idiotic error on my part. I was using the wrong .ovpn file. Problem solved!

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