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

    Running 2 OpenVPN Client (each on a separate VLAN)

    Scheduled Pinned Locked Moved OpenVPN
    3 Posts 2 Posters 697 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.
    • J Offline
      jtjwatkins
      last edited by

      I am fairly new to pfsense (please go easy on me), I've looked at a number of post on here and have not come up with a solutions to my issue.

      My Question is this: Is it possible to run 2 separate OpenVPN clients on one installation of pfSense? If so, how would I go about setting up?

      I am looking to run 2 simultaneous OpenVPN clients (each running on their own VLAN):

      1. Static IP address for streaming services
      2. Normal shared IP for everything else

      The issue I'm running into is that I can only get one connection going but not the other. I've verified that my configs are correct for each client running by themselves, but once I add the second client it never connects. It doesn't matter what order I add them.

      1 Reply Last reply Reply Quote 0
      • V Offline
        viragomann
        last edited by

        That should be possible though. However, you have to care, that each client connects through the WAN gateway.

        So in the client settings of each check "Don't pull routes" to avoid that the server sets the default route. Now you have to control VPN traffic by firewall rules (policy routing) and each client should connect well.

        1 Reply Last reply Reply Quote 0
        • J Offline
          jtjwatkins
          last edited by

          @viragomann:

          That should be possible though. However, you have to care, that each client connects through the WAN gateway.

          So in the client settings of each check "Don't pull routes" to avoid that the server sets the default route. Now you have to control VPN traffic by firewall rules (policy routing) and each client should connect well.

          Thanks Viragomann!!!

          That worked.

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