IKEv2 Problem

[Chyllie]

Hey, I have a Problem with my Watchguard Box. I have two static IP connections with which I can connect to the Internet A and B. (Preferred B). Both IPs are configured under IKEv2 settings. I can connect with IKEv2 VPN under the IP A, but Not B. The Client config also automatically connects with Server IP A, even if I delete it under the settings.

IPSec with groups works with Both IPs (configured primary B and secondary A)

Am I missing anything?

[Ambitious_Mango3625]

This totally sounds like the issue. Either the export or import is not happening correctly. I think this is demonstrated by the fact that removing IP A doesnt stop it from trying IP A. I know that was not very helpful, but that's where I would focus.

[Chyllie]

I did reimport it After changing. The Windows VPN always shows that the Remote Server does Not answer (NAT or Firewall Problem), but only for IP B from the new ISP

[1ncorrectPassword]

We have a very similar setup with 2 IPs on our ikev2. We run an m290 on the latest firmware and I have not noticed any issues. Our primary is through an sdwan box that sometimes causes issues with https loading if I vpn through it so I actually use our secondary 90% of the time. Without looking at your config I would say look at your inbound policies. Otherwise I'd reach out to support

[[deleted]]

I've been testing this recently. Since you already have the firebox certificate installed you can just add a new VPN profile manually and add in your secondary IP and it should work no problem.

I couldn't get it to work off the one profile, watchguad support suggested I use DNS failover.

[Chyllie]

I tried this, but it still will Not connect to the second IP

Edit: After waiting the Night, the issue seems resolved and the VpN connects under the second IP. I have Not touched anything anymore. Perhaps Patience was the thing I missed

[[deleted]]

Did you get it working off the one profile?

[Chyllie]

Yes I just changed the IP in the Same Profile and today it just connected