Hi,
I have the below network in VMware Workstation.
The PC VM can ping all the Fortigate VM interface but nothing beyond that, and can't reach internet, this is the issue.
PS C:\Users\Administrator> ipconfig /all
Ethernet adapter Ethernet0:
IPv4 Address. . . . . . . . . . . : 192.168.30.199(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.30.3
DNS Servers . . . . . . . . . . . : 192.168.30.3
PS C:\Users\Administrator> ping 192.168.25.11
Pinging 192.168.25.11 with 32 bytes of data:
Reply from 192.168.25.11: bytes=32 time<1ms TTL=255
Reply from 192.168.25.11: bytes=32 time<1ms TTL=255
PS C:\Users\Administrator> ping 192.168.25.6
Pinging 192.168.25.6 with 32 bytes of data:
Request timed out.
Request timed out.
Fortigate Static Route
Fortigate is acting as a DNS forwarder.
The PC VM when pinging google.com seems to resolve the IP, just no response.
S C:\Users\Administrator> ping www.google.com
Pinging www.google.com [209.85.202.147] with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Ping statistics for 209.85.202.147:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss)
Unsure what is missing, any thoughts ?
So is the 192.188.30.x/24 using Host Only or NAT? I assume it is Host Only.
Just remember whether NAT or Host-Only the .1 is the host machine's IP and .2 is the gateway. So 192.188.30.1 belongs to the host machine while 192.188.30.2 should be the gateway address if the Fortigate/vyOS VMs IP addresses are manually configured. Other than that it might be something within Fortigate settings (i.e. outside of VMware scope).
Thanks,
This was due to no route present in VyOS to the .30 network behind Fortigate which is why IP was resolved just jo ping replies..