Skip to main content
AhmedWahba
New Member
February 22, 2025
Question

unable to ping from FortiGate VM throw Port2 and Port3

  • February 22, 2025
  • 3 replies
  • 2361 views

unable to ping from FortiGate VM throw Port2 and Port3 to any connected device throw these two ports and also we enable Ping under each interface instead of can ping and hear Arp throw port1 when connect it throw any device.

Can any one help me ?

3 replies

dingjerry_FTNT
Staff
Staff
February 22, 2025

Hi @AhmedWahba ,

 

Your description is really unclear.

 

Can you elaborate on the issue?  Something like, what IP did you try to Ping?  Did you capture sniffer packets?  What does the routing table look like on FGT?  Did you specify the Ping source IP?  And so on.

dingjerry_FTNT
Staff
Staff
February 22, 2025

Hi @AhmedWahba ,

 

You'd better provide details of all the steps.

AhmedWahba
New Member
March 1, 2025

my Forti VM has 3 ports started from port0 to port2 on GNS3

and FYI on real Forti VM it has ports from port1 to port3 my problem

is i'm unable to ping from forti to Cisco router

 

Capture.PNG

 

AEK
SuperUser
SuperUser
February 22, 2025

First of all, go to device inventory (dashboard) and make sure the devices are connected to the right ports. If not, correct the interface/VLAN assignment from VMware and try again.

AEK
jipsy
New Member
March 1, 2025

It seems like you can't ping devices on Port2 and Port3 of your FortiGate VM, even though ping is enabled. Since Port1 works fine, check these:

  1. Ensure Port2/Port3 IPs and subnets are correct.

  2. Verify firewall policies allow ICMP traffic.

  3. Check routing tables for proper routes.

  4. Confirm ARP entries for connected devices.

  5. Ensure ports are up and error-free.

If the issue persists, review logs or contact Fortinet support.

dingjerry_FTNT
Staff
Staff
March 1, 2025

Hi @jipsy ,

 

"If the issue persists, review logs or contact Fortinet support."

 

Buddy, he is using GNS3. Can't get support from Fortinet.

jipsy
New Member
March 1, 2025

Contacting support is the last resort before that, do look into the logs