Fortigate Deployed can ping inside interface but not any VMs with internal IPs

Google Cloud Compute Infrastructure
,
1

I deployed a fortigate with and Internal subnet of 10.0.10.x/24 and I have an IP bound to the ouside interface that allows me access to the fortigate.

I also have an IP sec tunnel thats active between my home fortigate and the google cloud fortigate..

however when I import an VM from a ESXI image … google assigns it an internal IP on the 10.0.10.x range and I am unable to even ping the VM though the tunnel.

I suspect Google is spinning up an IP with a /32 so the VM gets no place with traffic as it can not get to the inside interface of the fortigate to forward the traffic though the VPN…

any ideas how to rectify this ?

1 Like
2

Some thing else to note. if I place the VM in the default subnet that google defaults to 10.206.0.x it gives me a subnet of 255.255.255.240.0. and all the machines inside that network can ping each other.