Unable to ping from Local-PC to router's interface

[Khan-qureshi]

Hi. I am Practicing a simple Lab in which I am using a FortiGate Firewall. The Topology is pasted Below;

I created a policy on firewall to allow ping from local-PC to e0/1 interface of router. I have configured FortiGate interfaces, done static routing on both firewall and on Router. I also created a policy on FortiGate to allow access but still I am unable to ping. What can be the reason??

[AEK]

Most probably the issue is caused by having two default gateways.

On the PC, remove the first default gateway (192.168.44.1) and try again.

In case you need that gateway, then you will have to add a route to 10.200.2.0/24 via 10.0.1.254.

[Khan-qureshi]

But these two gateways are on two different interfaces. gateway 192.168.44.1 is on vnmet8 (use for GUI access of eve-ng) and 10.0.1.254 is on vmnet8 (use to access fortigate firewall).

[AEK]

The issue is the same even if the two gateways are on different interfaces.

So since you need this default gateway, just add on your PC a specific route to your destination as suggested higher.

[dbu]

You are right , but your host might get confused with two default gateways with same destination 0.0.0.0/0. Better add a specific route as @AEK  advised

[AntonyChen]

i dont look the details on your schema, but in this cannot ping from your PC to your router at the end, most case is miss the routing, you should create a static route on the router to make it understand if it want to connect to the network 10.0.1.10/24 which gateway it must go, in this case it must go the the next hop is 10.200.2.1, interface  e0/1, and then on fortigate you must create a firewall policy to allow traffic (ping) from port2 to internal network -port3

Always like that in network design

[ssteo]

Might be cause by routing table in PC itself because have two default gateway configured.