For more information regarding the security incident at F5, the actions we are taking to address it, and our ongoing efforts to protect our customers, click here.

Forum Discussion

Alessiom_265101's avatar
Alessiom_265101
Icon for Nimbostratus rankNimbostratus
May 23, 2016
Solved

F5 Ipsec VPN and ERROR: none message must be encrypted.

Greetings Folks.   Recently have been tasked to configure an IPSEC vpn between my company and another company's network. Managed to get all the configuration parameters and followed the followin...
BIG-IP
devops
ipsec
racoon
security
TMOS
vpn
  • zeiss_63263's avatar
    zeiss_63263
    Sep 13, 2017

    One reason for the message is covered in K35087734.

     

    The log is not due to the specific misconfiguration mentioned in K35087734, but because racoon (the IPsec daemon) is at the encrypted stage of negotiating an SA, but unexpectedly receives an unencrypted ISAKMP message from the peer.

     

Arnaud_Lemaire's avatar
Arnaud_Lemaire
Icon for Employee rankEmployee
Jun 02, 2016

hello, not much experience but from googled that error message : That means the peer is trying to send you data without encrypting it, or it's sending data on a connection that you no longer considers valid.

 

and :

 

Just want to add that this can also mean the shared secret does not match. I just ran into this error recently. The remote end (Checkpoint) revealed in the logs that it could be a shared secret mismatch. Sure enough it was off on one character. The pfsense side was initiating the connection.