Frequently we will see these unnamed sessions in connecting status
$ swanctl -l
(unnamed): #285, CONNECTING, IKEv1, fbc6957e747f9fca_i 10d93d1c3eba057e_r*
passive: ISAKMP_VENDOR MAIN_MODE
Could you please explain the reason and how to avoid it?
#1 Updated by Michael Hu about 1 year ago
Repost the cmd output. The interesting is that the connection to 10.224.162.248 is already established while another unamed one to the same 10.224.162.248 is still there.
conn-10_107_0_21-10_224_162_248: #436, ESTABLISHED, IKEv1, 9a4f5ccf0e4ff087_i 89fe51d8c176dd81_r* local '22.214.171.124' @ 10.107.0.21 remote '10.224.162.248' @ 10.224.162.248 AES_CBC-256/HMAC_SHA2_256_128/PRF_HMAC_SHA2_256/MODP_2048 established 3s ago, rekeying in 27449s (unnamed): #435, CONNECTING, IKEv1, fbbe88fb7c8cd653_i 1294e4a171421eca_r* local '%any' @ 10.107.0.21 remote '%any' @ 10.224.162.248 AES_CBC-256/HMAC_SHA2_256_128/PRF_HMAC_SHA2_256/MODP_2048 passive: ISAKMP_VENDOR MAIN_MODE