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

    OpenSSL hardware crypto engine functionality is not available

    Scheduled Pinned Locked Moved OpenVPN
    4 Posts 2 Posters 2.3k 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.
    • B
      bchan
      last edited by bchan

      I just upgraded to CE 2.7.1. When I looked at the log of OpenVPN I found the captioned message.
      In the System/Advanced/Misc setting, I have "Cryptographic Hardware" set to "AES-NI CPU based acceleration". This worked perfectly in the past.
      I am using these ciphers:
      AES-128-GCM
      AES-128-CBC

      Am I missing something in the setting in CE 2.71?
      How can I turn on hardware acceleration again?

      Thanks in advance for any advice and insights.

      tinfoilmattT 1 Reply Last reply Reply Quote 0
      • tinfoilmattT
        tinfoilmatt @bchan
        last edited by

        @bchan reboot.

        B 1 Reply Last reply Reply Quote 0
        • B
          bchan @tinfoilmatt
          last edited by bchan

          @cyberconsultants The upgrade already triggered a reboot and I have not changed any setting. Why another reboot will solve the problem?

          On the other hand, I read somewhere that CPU AES-NI is considered "kernal" now in openssl. Perhaps that is the reason why it is not longer needed in OPENVPN configuration.
          I have measured both the upload and download speed and noticed no degradation even with the warning message.

          tinfoilmattT 1 Reply Last reply Reply Quote 0
          • tinfoilmattT
            tinfoilmatt @bchan
            last edited by

            @bchan you could review kernel initialization by running...

            sysctl -a
            

            ...if you want to review what might not have 'come up' properly. a subsequent reboot could then affirm or disaffirm any findings.

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