So this is an expected behavior and not an issue with the FortiGate. That is because when one pings 8.8.8.8, automatically public WAN IP is used as source and hence the pings will be successful. If one wonders, why it works when source option is not chosen? When tested from public IP, that is sourcing the WAN IP and pinging a public IP should work. Generating traffic form a host should work and the packets can be traced to see the route. Testing from the firewall itself is not ideal, at least not from a private IP as source. Here basically its being told to firewall to generate a ping with a private IP as source out through a wan port hence it'll be dropped as no private IP address will be routed. Local traffic does not match a IPv4 firewall policy. For the traffic going through the firewall it will hit the firewall policy and get NATed but not for the local traffic generated from the FortiGate. To confirm if a hosts in the LAN network is able to reach the public servers (reach internet), it is recommended to test it from one of the host itself and not from the firewall. This is an expected behavior as the ping's that are local traffic generated from FortiGate and are also from a private IP 10.254.8.65. # execute ping-options source 10.254.8.65ĥ packets transmitted, 0 packets received, 100% packet loss You should contact and complain to your ISP Support.ĭoing the above maintenance acts to your router should be doneįirst, in case Support will ask about them.This article describes about the issue where users are unable to ping public servers (for testing) using ping-option source from LAN interface.Ĭonsider the following network, where the LAN facing interface with IP address 10.254.8.65 is trying to reach public servers. Means that the interruption in service lasted about 4 seconds. In one such case ping had 4 consequent such errors, which Google DNS site itself, so it's clearly with the ISP and There is very little chance that the problem was with the In these cases we can see that the lost packetsĬrossed over to the router and died there, coming back with Occurrence where the problem is clearly the ISP timing out on In these logs you have packet loss, so it's a quite ordinary For good measure, check if a newer driver exists for your network adapter.Īpart from the first and somewhat puzzling log, your new logs.If the problem persists, check if you can find a firmware update.Were sent, which explains why these errors did not cause any lost My understanding is that if the router became unavailable, no pings type the following in the command window then press Enter: ping -i 200 8.8.8.8 Unknown Host: This response indicates that the IP address or website you are pinging is not found on the network or Internet. The router then drops out from time to time for a short instant. Request Timed Out: This ping response can indicate the remote device is offline. The IP address 192.168.1.1 surely relates to your router that is the The interesting message in your first log is : Link to a PasteBin of the log when connected to Wi-Fi. Link to a PasteBin of the log when connected to router with wire, which again is connected to the modem with wire. Link to a PasteBin containing the log when connected to modem with wire. Reply from 192.168.1.1: Destination net unreachable. Some lines from the test: Reply from 8.8.8.8: bytes=32 time=10ms TTL=57 Packets: Sent = 10674, Received = 10674, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 9ms, Maximum = 15ms, Average = 9ms Ping results through the wired connection are: Ping statistics for 8.8.8.8: The three cases did not happen consecutively. After pinging for 3 hours, I was able to log zero packet loss and very low latency.Īfter scrolling through the log I found 3 cases of the message 'Reply from : destination net unreachable'. I have performed a ping test while being directly connected to the modem through ethernet. I am using Windows 10 and having issues with my Wi-Fi dropping out sporadically, sometimes up to 10 times during an hour.

Ping 8.8 8.8 request timed out