Hi
I ran into the exact same issue today...
Bob is right you could add an additionnal address but still, it requires one public ip address per subnet you need to route into the tunnel.
Did someone have a chance to find out a solution here?
Cheers
Marc
FYI I tried to use another additionnal address but you can't route an ipsec vpn through a specific ip. You get to choose which interface, not the ip.
Only option I found to connect 2 private networks to my GCP network is setting up 2 vpn using 1 SA each... It doubles the price for the private connection to your GCP projects!
M
I think you've got your thought process backwards. On the Ipsec connection on the UTM you are not specifying any IP but the Google Cloud Gateway
On the Google Cloud VPN Ipsec setting, you're specifying what IP it's connecting to
Only the google cloud vpn cares about what IP it's connecting to, remote peer address. In this case, another external IP of yours....which is on your WAN interface anyway
ok, I just tried that but unfortunately that's not working!
Log viewer in GCP shows that packets are coming into the UTM on the additional address but they are routed back to the primary address of the interface when going out of the UTM to GCP...
Looks like the original poster has this working, perhaps he can comment. Unless he refers to to WAN connections as two physical WAN ports, in which case the only option is what you suggested, multiple VPN's using multiple SA's..all using your main external WAN IP
I currently only have one ipsec connection to GCP