I have had a few issues over the years with Peplink IPSEC VPNs, sometimes working, sometimes not - particularly in complex aggressive/dynamic instances where there is no clear reason for the IPSEC tunnel not to establish properly (and with peplinks lack of actual diagnostics for VPN logs…)
Until i came across this; Peplink sends IKEv2 IDs as RFC822/email ID type and not FQDN.
So in an ISO cisco instance - setting as follows seems to fix VPN intermittency/failing to establish for no good known reason.
crypto ikev2 profile BEDSFRPEP-IKEV2-PROFILE
match identity remote email vpn@peplink
identity local email vpn@cisco
If you’re using another vendor maybe specifically setting email type instead of FQDN will also improve things.
Thought id post, incase it helps anyone else.
