Hello guys i receive this error when i make a ping via CLI from fortigate 40F to 188.8.131.52
In particular i write this command on CLI:
- execute ping-option source 10.2.62.97 (ip address for internal LAN)
- execute ping 184.108.40.206
after i receive this issues posted below
16:27:28 178 vd-INTERNET:0 received a packet(proto=1, 10.2.62.97:23->220.127.116.11:2048) tun_id=0.0.0.0 from local. type=8, code=0, id=23, seq=0. 16:27:28 178 allocate a new session-0003f14f, tun_id=0.0.0.0 16:27:28 178 in-, out-[a] 16:27:28 178 len=0 16:27:28 178 result: skb_flags-00000000, vid-0, ret-no-match, act-accept, flag-00000000 16:27:28 178 gnum-100004, check-ffffffbffc041c80 16:27:28 178 checked gnum-100004 policy-1, ret-no-match, act-drop 16:27:28 178 checked gnum-100004 policy-1, ret-no-match, act-drop 16:27:28 178 checked gnum-100004 policy-2, ret-no-match, act-drop 16:27:28 178 checked gnum-100004 policy-2, ret-no-match, act-drop
I understand that seems that there is no match in policy but why if i have a policy that permit every traffic to internet.
In the debug seems that the traffic do not recognise the inbound interface in-, out-[a] ?
Someone has already seen this strange behavior ?
Go to Solution.
Thank you for posting your query.
This is an expected behavior for the locally generated traffic using the ping option from the LAN interface.
Please refer to the below KB for your reference:-
- Have you found a solution? Then give your helper a "Kudos" and mark the solution
View solution in original post
The Fortinet Security Fabric brings together the concepts of convergence and consolidation to provide comprehensive cybersecurity protection for all users, devices, and applications and across all network edges.
Copyright 2023 Fortinet, Inc. All Rights Reserved.