Troubleshooting Tip: IPsec site-to-site tunnel between FortiGate and Barracuda firewall not getting established due to 'malformed message'
| Description | This article describes how to fix an IPsec tunnel problem due to a malformed AUTH message between a Barracuda firewall and a FortiGate. |
| Scope | IPsec, FortiGate, Barracuda firewall. |
| Solution | In the following IPsec site-to-site tunnel setup, FortiGate is the IKE initiator while the Barracuda firewall is the responder.
IPSec tunnel Name: CRR-T2. IKE version: IKEv2. Take debugs on the FortiGate firewall using the following commands:
diagnose vpn ike log-filter clear diagnose vpn ike log-filter name <Phase1 name> diagnose debug app ike -1
Notes: diagnose vpn ike log-filter name <Phase1 name> can be replaced by diagnose vpn ike log-filter dst-addr4 69.75.89.129.
Starting from v7.4.1, the 'diagnose vpn ike log-filter' command has been changed to 'diagnose vpn ike log filter', and the 'diagnose vpn ike log-filter dst-addr4' command has been changed to 'diagnose vpn ike log filter rem-addr4'.
7EB1FB50C80A427A360B04BAAB6C5C AD125DD4548D047A38FE4ABCB57B7FFCCCA2C660FF89C2373F82E9324A04655 Solution: Change the following settings in the IPsec configuration in Barracuda.
|



