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

Error TLS

Scheduled Pinned Locked Moved OpenVPN
8 Posts 3 Posters 883 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
    shubakas
    last edited by Sep 26, 2018, 3:15 PM

    Hello,

    I have a 192.168.26.1 modem router with a 192.168.26.10 dmz connected to the pfsense WAN in 192.168.26.10
    I have 2 separate network LAN1 (192.168.27.0) and LAN2 (192.168.28.0)

    I configured openvpn on pfsense as shown on this tutorial to connect to LAN1
    everything went well
    I downloaded the installation package via Client Export
    on the client computer I installed the package and replaced the local ip with the public ip
    but I get an error:
    TLS key negociation failed
    TLS handshake failed

    I have rules that are created automatically in the firewall

    I do not understand what blocks, do you have an idea please?

    thanks

    1 Reply Last reply Reply Quote 0
    • R
      Rico LAYER 8 Rebel Alliance
      last edited by Sep 26, 2018, 5:38 PM

      What is your pfSense showing in the OpenVPN Server Log? Any notice for the OpenVPN Client connection?
      When your pfSense is not directly connected to the Internet, maybe you need to forward the OpenVPN Ports from your Edge Router 192.168.26.1 to pfSense WAN 192.168.26.10 ?

      -Rico

      1 Reply Last reply Reply Quote 0
      • S
        shubakas
        last edited by Sep 26, 2018, 6:27 PM

        @rico said in Error TLS:

        What is your pfSense showing in the OpenVPN Server Log? Any notice for the OpenVPN Client connection?
        When your pfSense is not directly connected to the Internet, maybe you need to forward the OpenVPN Ports from your Edge Router 192.168.26.1 to pfSense WAN 192.168.26.10 ?

        No nothing to the log
        I don't think then the WAN is configured like a DMZ on the router

        1 Reply Last reply Reply Quote 0
        • V
          viragomann
          last edited by Sep 26, 2018, 6:54 PM

          The mentioned error is typical for a client not reaching the server.

          Use Packet capture from the Diagnostic menu to investigate if the vpn packets arrive on the WAN interface to get sure.
          Maybe they are blocked by the ISP or anywhere else.

          1 Reply Last reply Reply Quote 0
          • S
            shubakas
            last edited by Sep 26, 2018, 7:45 PM

            Nothing in packet capture 😯

            1 Reply Last reply Reply Quote 0
            • V
              viragomann
              last edited by Sep 26, 2018, 7:57 PM

              To check if the DMZ works on the router try to access your public address on other common ports like 80 or 443 while capturing on WAN.

              1 Reply Last reply Reply Quote 0
              • S
                shubakas
                last edited by Sep 26, 2018, 8:22 PM

                I try but nothing in packet capture
                the dmz don't working i think
                i try to configure the modem like a bridge

                1 Reply Last reply Reply Quote 0
                • S
                  shubakas
                  last edited by Sep 29, 2018, 7:50 AM

                  Thank you very much, I configured the modem bridge and pfsense PPPoE and all is ok !!!
                  Thanks

                  1 Reply Last reply Reply Quote 0
                  8 out of 8
                  • First post
                    8/8
                    Last post
                  Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.
                    This community forum collects and processes your personal information.
                    consent.not_received