Why is there 100% packet loss


#1
ping -c 2 google.com
PING google.com (216.58.193.142) 56(84) bytes of data.

--- google.com ping statistics ---
2 packets transmitted, 0 received, 100% packet loss, time 1026ms

traceroute google.com
traceroute to google.com (216.58.193.142), 30 hops max, 60 byte packets
 1  dslrouter.netgear.com (192.168.254.254)  0.650 ms  0.899 ms  1.100 ms
 2  * * *
 3  * * *
 4  * * *

#2

A firewall blocking ICMP packets, perhaps? What happens when you try to browse to http://216.58.193.142 ?


#3

It goes to the Google site.


#4

Yep, it does for me too, but I also get replies to my pings. Seems like a firewall blocking ICMP to me, possibly on that local Netgear box or the very machine you're pinging from. Can you ping other sites, say yahoo.com?


#5

Same with yahoo and other sites.

I found this, but not sure if it's a good idea?
I was looking at the very bottom response.


#6

I have UFW set to the default Public profile and it works for me, so it seems the default rule set allows ICMP echo requests and replies. Unless you have changed the firewall rules I would guess the culprit is elsewhere. You could test it by turning the firewall off for a few seconds, pinging google again, and if still fails you'll know for sure.


#7

It fails whether firewall is ON or OFF.

I have not added any firewall rules.


#8

OK, so I'll guess your router (192.168.254.254) has a firewall function that's blocking incoming ICMP. With your firewall on, can you ping 192.168.254.254 or other machines on your LAN?


#9

Why is there no packet loss with this? Unless it means that the pings are getting to my Internet Provider.

ping 192.168.254.254
PING 192.168.254.254 (192.168.254.254) 56(84) bytes of data.
64 bytes from 192.168.254.254: icmp_seq=1 ttl=64 time=0.613 ms
64 bytes from 192.168.254.254: icmp_seq=2 ttl=64 time=0.650 ms
64 bytes from 192.168.254.254: icmp_seq=3 ttl=64 time=0.735 ms
64 bytes from 192.168.254.254: icmp_seq=4 ttl=64 time=0.696 ms
64 bytes from 192.168.254.254: icmp_seq=5 ttl=64 time=0.732 ms
64 bytes from 192.168.254.254: icmp_seq=6 ttl=64 time=0.753 ms
64 bytes from 192.168.254.254: icmp_seq=7 ttl=64 time=0.763 ms
64 bytes from 192.168.254.254: icmp_seq=8 ttl=64 time=0.748 ms
64 bytes from 192.168.254.254: icmp_seq=9 ttl=64 time=0.802 ms
64 bytes from 192.168.254.254: icmp_seq=10 ttl=64 time=0.758 ms
64 bytes from 192.168.254.254: icmp_seq=11 ttl=64 time=0.713 ms
^C
--- 192.168.254.254 ping statistics ---
11 packets transmitted, 11 received, 0% packet loss, time 10232ms
rtt min/avg/max/mdev = 0.613/0.723/0.802/0.062 ms


#10

I believe you're just pinging the internal interface of the router that connects you to the internet (because it was the first hop in your traceroute to google), which means your echo requests (and 192.168.254.254's replies) are never leaving your local LAN. It's when you try to ping something outside of your LAN that something goes wrong, and my guess is that that router is the culprit. It may have a built in firewall that's stomping on icmp. If you can get the model number from it, one might google it. Or you could just type http://192.168.254.254 into a web browser and see what you get.


#11

I tried it. user and pw are both admin. :slight_smile:

The connection was reset

The connection to the server was reset while the page was loading.

The site could be temporarily unavailable or too busy. Try again in a few moments.
If you are unable to load any pages, check your computer’s network connection.
If your computer or network is protected by a firewall or proxy, make sure that Firefox is permitted to access the Web. 

model number. D2200D


#12

I downloaded the manual.

But if I can not get past this, I think I am outta luck.

Set General Firewall Settings

To set general firewall settings:

  1. Launch an Internet browser from a computer or wireless device that is connected to the
    network.
  2. Type http:/192.168.254.254.
    A login window opens.
  3. Enter the user name and password

#13

Well, if that device is controlled by your ISP you might be locked out of it. If you're really motivated about this you could call them and ask why you can't ping or traceroute past your router and see what they say.


#14

I found the solution.

You gave me clues that really helped.

I did a factory reset of the router by pressing a recessed button in the back of the router for 20 seconds.

Results:

  1. Pings now work
  2. Thunderbird can now get mail :slight_smile:

#15

Um, a bold move! Not quite what I would have suggested as you have blown away whatever configuration was previously there. You should be able to get into it now and make sure you still have some kind of firewall in place.


#16

Which security setting would you recommend?


#17

Well I'm a bit uncomfortable dishing out firewall advice as I'm not an expert. I didn't know we were going to wind up here! But that said, I would start with typical/medium, do your ping and Thunderbird tests, and then modify from there if needed. I would NOT leave it at Low or None even if that breaks ping and Thunderbird.