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

    2 VPN servers, no connection A-to-B while B-to-A is connected

    Scheduled Pinned Locked Moved OpenVPN
    2 Posts 1 Posters 1.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.
    • M
      martta
      last edited by

      I don't know what search terms would get an answer to this so I decided to post a question after looking through all the FAQs.

      Situation:
      I have two locations that both have an OpenVPN server for remote client connections. Both servers function well except for two anomalies:

      1. if someone at site A uses a client to connect to site B, nobody from site B can connect to site A, and vice versa. It is still possible to connect from any other location, just not from either site.

      2. if someone from site A connects to site B, nobody else from site A can connect to site B.

      Both systems are running pfsense (2.0.2-RELEASE (i386) pretty much with default settings. The only thing that I can think of is the outbound NAT which is set to Manual and the port setting for LAN-to-WAN that is set to static port. When I was running a VPN server only in one of the sites, multiple clients could connect even from the same location concurrently. So introducing a pfsense system at both endpoints is doing something to this. As far as I know, this is not a limitation in OpenVPN.

      My intention is to create a site-to-site setup between the two locations in the future to overcome this issue, but I would need to find out what is causing this issue right now.

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

        The problem was what I was suspecting. I had to create a rule that did not use a static port for destinations with port 1194. I then moved it in front of the rest of the LAN to WAN NAT settings.

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