Hi JBelinha. the problem was that the segments that we were passing through the VPN tunnel were not the same. here the detail is that on both sides there have to be exactly the same segments that are allowed to pass. For example, if on one side of the tunnel you are passing segments 10.0.0.0/24, 172.16.0.0/24 and 192.168.10.0/24 on the other side, the same segments must be configured. The failure originates from the segments of both sites not coinciding in the renegotiation process. Sorry for the redundancy but that was the solution. check the segments of both firewalls. I hope this solution helps you. Greetings. ... View more

Hello. I have the same problem. check the logs and the following is displayed:   2 de mayo 22:59:51   Negociación VPN no Meraki/cliente msg: <remote-peer-2|224> cerrando CHILD_SA net-2-2{766} con SPI cca577a3 (entrante) (0 bytes) f114c4b8 (saliente) (0 bytes) y TS 10.1.44.0/24 === 10.99 .24.0/25 2 de mayo 22:58:23   Negociación VPN no Meraki/cliente msg: <remote-peer-2|224> cerrando CHILD_SA net-2-3{765} con SPI c7cfc2c2(entrante) (709463 bytes) f114c3ff(saliente) (648993 bytes) y TS 10.3.44.0/24 === 10.99 .24.0/25   There are 2 WANs. when it goes down I have to turn VPN mode off and on. I need to know how to solve this problem. The firewall at the other end is a Fortinet. Greetings. ... View more