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

    TLS Error: Unroutable control packet received

    Scheduled Pinned Locked Moved OpenVPN
    3 Posts 2 Posters 5.6k 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
      MacUsers
      last edited by

      Dear all,

      Running OpenVPN on 6100 (v22.05) and the connection is stuck at the Authorizing stage with this error on the server side:

      Dec 4 22:23:27 	openvpn 	33226 	xx.xxx.xxx.137:5243 UDPv4 READ [755] from [AF_INET]xx.xxx.xxx.137:5243: P_CONTROL_V1 kid=0 [ ] pid=4195 DATA len=741
      Dec 4 22:23:27 	openvpn 	33226 	xx.xxx.xxx.137:5243 TLS Error: Unroutable control packet received from [AF_INET]xx.xxx.xxx.137:5243 (si=3 op=P_CONTROL_V1) 
      

      All of the google search on the error indicates a time sync issue between the server and client bit that doesn't seem to be the problem here.

      the client side (Tunnelblick) simply just reports:

      2022-12-04 22:35:37.698750 TLS Error: TLS key negotiation failed to occur within 60 seconds (check your network connectivity)
      2022-12-04 22:35:37.698900 TLS Error: TLS handshake failed`
      

      An identical setup runs on a Dell R220 works perfectly fine but not on 6100; Any idea what am I missing or need to look in.

      Any kind of the help would be much appreciate.

      -S

      GertjanG 1 Reply Last reply Reply Quote 0
      • GertjanG
        Gertjan @MacUsers
        last edited by

        You've said :

        @macusers said in TLS Error: Unroutable control packet received:

        Dec 4 22:23:27 ...... a time sync issue

        Then you say :

        the client side (Tunnelblick) simply just reports:
        2022-12-04 22:35:37.698750 TLS Error: TLS

        I say : compare the two time stamps. They are more then 12 minutes off.
        Get your "time" fixed.

        No "help me" PM's please. Use the forum, the community will thank you.
        Edit : and where are the logs ??

        M 1 Reply Last reply Reply Quote 0
        • M
          MacUsers @Gertjan
          last edited by

          @gertjan Thanks fo rthe reply.
          logs were not necessarily from the same session - I pasted the lines as reference to the error.

          BTW, after increasing the log-level to 7, it reveals that the error was coming from the outdated CRL but the error reporting was very generic and confusing. It started working since this morning.

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