If you dont get a response best to open an issuein github
local-0 { id = auth = pubkey certs = cert-1.crt } remote-0 { id = %any auth = pubkey eap_id = %any } remote_addrs = %any encap = no dpd_delay = 10 s dpd_timeout = 60 s pools = defaultv4 remote-1 { auth = eap-mschapv2 }
The stability is very similar since both the old and the new GUI use swanctl.conf as its base.[...]Yes. It could be that old dialog is more prone to automatic migration issues to swanctl.conf format having been carried out. The new dialog follows swanctl.conf syntax more closely so such hiccups are less likely to occur.Nevertheless, old one will be fixed as it's clearly a regression.