
T22:22:14 charon 15 destroying duplicate IKE_SA for peer 'RemoteSite', received INITIAL_CONTACT T22:22:14 charon 15 IKE_SA con2 established between MySite.RemoteSite I already changed the "Connection method" to respond only. The Lifetimes/Timeouts match on each side. On my Site the Tunnel seems to be up, looking at the tcpdump the remote side seems to reconnect? My tunnel to a remite Site (Cisco i think) is unstable. the state reset function is a bug and should be triggered when jumping back to the primary interface the state reset just happens by design on the 1st failover If i kill the ESTABLISHED connection in the "States Dump" GUI then it will start to connect via the active/correct gateway. HOWEVER: If i switch back on the Gateway the Active Gateway switches back to the main one again, BUT the TCP States does not get killed. It also seems to do a TCP States Reset since my SSH Tunnel/Access dies. When i produce the active Gateway failure, the Gateway swichting jumps in, the OpenVPN Tunnel times out and the takeover is fine. On top of that i run a OpenVPN Client Connection (TCP)


Sticky Connections ( Use sticky connections => not ticked) Kill States ( Disable State Killing on Gateway Failure => not ticked) Gateway switching (Allow default gateway switching => enabled) We are using MultiWAN with 2 Uplinks with:
