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

    2 VPN in the same server but separate network

    Scheduled Pinned Locked Moved OpenVPN
    4 Posts 2 Posters 245 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.
    • S
      Stefano.Coccia
      last edited by

      Hi I have a Phisycal server where I create different Virtual Machine, I need create 2 sperate group and with 2 VPN, If I enter in VPN1 I see only the NET1 (192.168.1.xxx) VPN2 only NET2 (192.168.10.1) and NET1 can't see Net2 and Net2 Can't see Net1
      If I create 2 VPN is all ok but I can't isolate the Network If I scan I see alway the other Network.
      Must create a new Pfsense for the new network?

      V 1 Reply Last reply Reply Quote 0
      • V
        viragomann @Stefano.Coccia
        last edited by

        @Stefano-Coccia
        Just restrict access for each VPN accordingly.

        Do you have two VPN servers or just two clients?

        NET1 and NET2 are assigned to pfsense interfaces?

        If you are on the NET1 VM, can you access anything in NET2 and vice versa?

        1 Reply Last reply Reply Quote 0
        • S
          Stefano.Coccia
          last edited by

          Hi I have a server with hyperV (wan, lan1 and lan2) inside a VM with Pfsense, now I have Vpn (Wan to Lan), and I need create wan2 to lan2, but if I do in the same pfsense lan2 see lan1... and I donato want... or I create another Pfsense server or I don't understand how I can do...

          V 1 Reply Last reply Reply Quote 0
          • V
            viragomann @Stefano.Coccia
            last edited by

            @Stefano-Coccia
            I created an networks alias:
            cf232d43-b3ac-44d1-86f5-f2d45c837db7-grafik.png

            Then I use this in the firewall rules to allow internet access:
            b9b952ec-707f-4674-9296-b40cfedb19b0-grafik.png

            The alias includes all RFC 1918 (private) network ranges.
            Note that in the rule "invert. match" is checked. So the pass rule is only applied to traffic with other destinations then the alias.

            To allow access to internal services like DNS, you need to add additional rules then. E.g.
            74728306-3bf6-47bf-9450-6bb6b783013d-grafik.png

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