- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Intermediate Packet Drops in traffic.
We have deployed Fortigate 3501F & It is connected to cisco Catalyst C9300-24T switch.
We are using 1G-SFP-RJ45 module on firewall side.
While trying to ping from the host that is behind the switch, we are facing intermediate packet drops. The destination host is behind the firewall.
Kindly suggest on this.
- Labels:
-
FortiGate

Created on ‎06-24-2022 01:00 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hello,
Thank you for using the Community, further information would be useful to this topic. Can you please provide the following information for:
- Which version is running on the FortiGate?
- Verify that ping service are allowed on the concerned ports as follows:
- show system interface portX
- Can you confirm that you have configured a firewall policy and enable the ping? (hostSW to hostFGT)?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
1. FortiOS 6.4.6 Build 6135
2. Checked,Ping is allowed & traffic is going through the firewall not to the firewall itself.
3. Yes, Policy has been already configured.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hello,
I don't quite understand what do you mean by "traffic is going through the firewall not to the firewall itself". Can you please elaborate this for me?
But it would be great if you could share the packet capture and trace flow.
- Check the routing table, and verify that the subnets of the hosts are in the table.
- get router info routing-table all
- Use sniffer trace when running a constant ping from hostSW to hostFGT as follows:
- diag sniffer packet portX 'addr hostSW' 4 0 L
- Use debug flow, to help us understand if the ping is received, routed or blocked by FortiGate as follows:
- diag debug enable
- diag debug flow filter clear
- diag debug flow filter addr <hostSW>
- diag debug flow trace start 100
