Support Forum
The Forums are a place to find answers on a range of Fortinet products from peers and product experts.
New Contributor

Could not ping from an internal private IP to a destination in the Internet

Hello community,


I have a weird situation where I could not ping from the internal private IP address to a host in the Internet. The issue is described as follows.


The FW (200E) has an vlan, let say vlan 200 and IP range is The logical interface on the FW for this network is


When I assigned a PC to this VLAN, it has the IP From this PC I can ping the Internet as normal.


However, If on the FW, I choose ping-option source, I can ping the WAN interface but could not ping the Internet. The weird situation is that both and are on the same VLAN, affected by the same policy, but 200.1 could not ping the Internet while 200.2 could.


Can anyone give some advice?


Thank you so much.



Esteemed Contributor III

Try "diag debug flow" to see why.


"Kernel panic: Aiee, killing interrupt handler!"
Ede"Kernel panic: Aiee, killing interrupt handler!"
New Contributor

Hi Ede,


Thank you for your advice.


I ran the debug and execute ping with 01 repeat and got the result below. It does not provide much of information to consider.


 id=20085 trace_id=131 func=print_pkt_detail line=5347 msg="vd-root received a packet(proto=1,> from local. type=8, code=0, id=23046, seq=0." id=20085 trace_id=131 func=init_ip_session_common line=5506 msg="allocate a new session-1ffebb0f"


The IP is assigned on an logical interface. Have you got any further suggestion?


Thank you.


Esteemed Contributor III

What is your rule and if you have SNAT? I bet if you diag sniffer packet on the outside interface, your going out NOT-SNAT




diag sniffer packet wan1 "icmp and host"


Ken Felix




PCNSE NSE StrongSwan
Top Kudoed Authors