Navigation

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

    Second OpenVPN Server

    OpenVPN
    2
    2
    579
    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
      sreece last edited by

      Hello,

      I currently use an OpenVPN server that utilizes udp/1194. This VPN connection works perfectly, including cn matching and LDAP group membership. I've decided to create a second VPN for users that need to connect from a device not owned by our company, and therefore not controlled by our security apps. This VPN uses udp/1195.

      I'm finding that I am unable to complete the connection on the 1195 configuration, even though it is an exact copy (with the exception of the port) of the working 1194 config. The error I'm seeing is:

      Fri Apr 08 14:44:45 2016 TLS Error: TLS key negotiation failed to occur within 60 seconds (check your network connectivity)
      Fri Apr 08 14:44:45 2016 TLS Error: TLS handshake failed
      Fri Apr 08 14:44:45 2016 SIGUSR1[soft,tls-error] received, process restarting

      I can see the packets reaching the firewall on the WAN interface, but nothing is sent back. Logging the ACL shows that the traffic is passed. This is leading me to believe I'm running into a certificate issue, but I'm utilizing the same user certificates (InternalVPNCA) that work on 1194. Any ideas what I might be doing wrong?

      1 Reply Last reply Reply Quote 0
      • D
        divsys last edited by

        I've decided to create a second VPN for users that need to connect from a device not owned by our company, and therefore not controlled by our security apps. This VPN uses udp/1195

        There are a couple of places this can be problematic certificate wise.
        I would suggest that the 2nd OpenVPN server needs it's own certificate.
        As long as the new Cert. is created using the same CA used for the first server, you should be OK with your current setup.
        You may need to enable "Allow Duplicate-cn" if you're trying to connect to both servers using the same client (that may or may not sense in your setup).

        You might want to go so far as to create a new CA as well as a new server Cert for the second instance.
        If you do, you'll need dedicated client certs for the 2nd server.
        In many scenarios, that's a good thing (if only for enforcing separation of who's connecting and from where).

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

        Products

        • Platform Overview
        • TNSR
        • pfSense
        • Appliances

        Services

        • Training
        • Professional Services

        Support

        • Subscription Plans
        • Contact Support
        • Product Lifecycle
        • Documentation

        News

        • Media Coverage
        • Press
        • Events

        Resources

        • Blog
        • FAQ
        • Find a Partner
        • Resource Library
        • Security Information

        Company

        • About Us
        • Careers
        • Partners
        • Contact Us
        • Legal
        Our Mission

        We provide leading-edge network security at a fair price - regardless of organizational size or network sophistication. We believe that an open-source security model offers disruptive pricing along with the agility required to quickly address emerging threats.

        Subscribe to our Newsletter

        Product information, software announcements, and special offers. See our newsletter archive to sign up for future newsletters and to read past announcements.

        © 2021 Rubicon Communications, LLC | Privacy Policy