Пинг Ubuntu приводит к 100% потере пакетов
Я использую Ubuntu 15.10 и могу успешно пропинговать localhost, gateway (192.168.1.1) и 8.8.8.8, но я не могу пропинговать любое другое имя хоста / IP-адрес (за пределами моей сети). Это приводит к 100% потере пакетов. Что интересно, когда я пингую имя хоста, оно преобразуется в IP-адрес, но пинг не проходит, и я могу пинговать любой хост / IP с виртуальной машины (debian) внутри коробки Ubuntu.
xxxx@xxxx:~$ ping -c 4 microsoft.com PING microsoft.com (104.40.211.35) 56(84) bytes of data. --- microsoft.com ping statistics --- 4 packets transmitted, 0 received, 100% packet loss, time 3022ms Я пробовал и других хостов. Microsoft является примером. Пришлось переустанавливать traceroute только тогда все заработало. Я переустановил iputils-ping, но у меня все еще остается та же проблема.
1 ответ
Начиная с Вас, где способный для проверки с помощью ping-запросов 8.8.8.8 , который является ясно не в собственной сети дома, я предполагаю, что Вы только протестировали с microsoft.com , который на самом деле блокирует icmp эхо-запросы, как уже указано в комментариях ниже Вашего вопроса.
, Чтобы видеть, можно ли проверить с помощью ping-запросов вне Вас, мог бы использовать в качестве примера google.com или как Вы сделали сервер DNS Google ( 8.8.8.8 ). Можно также использовать traceroute команда для наблюдения, где она зависает, при попытке проверить с помощью ping-запросов определенный хост. Так traceroute 8.8.8.8 владеет некоторым выводом как это (взятый с моей стороны, может отличаться для Вашей стороны):
michael@NEXUS-ONE:~$ traceroute 8.8.8.8 traceroute to 8.8.8.8 (8.8.8.8), 64 hops max 1 192.168.0.1 16,803ms 2,651ms 2,073ms 2 10.152.192.1 8,918ms 9,518ms 9,236ms 3 81.210.131.221 11,155ms 9,955ms 9,957ms 4 84.116.196.158 20,015ms 18,580ms 21,355ms 5 84.116.196.162 19,940ms 19,956ms 19,999ms 6 84.116.133.97 21,078ms 35,584ms 23,217ms 7 213.46.177.42 18,859ms 21,082ms 20,002ms 8 216.239.59.72 30,190ms 22,493ms 17,215ms 9 216.239.57.194 20,009ms 18,788ms 30,898ms 10 66.249.95.39 22,115ms 26,881ms 23,907ms 11 216.239.49.234 24,900ms 27,041ms 25,895ms 12 216.239.51.209 26,067ms 31,986ms 23,893ms 13 * * * 14 8.8.8.8 28,034ms 23,544ms 43,217ms , Как Вы видите, эти три звезды на транзитном участке № 13 могут указать на проблему (медленное время отклика и т.д.), если это происходит на последнем транзитном участке, но показ IP, это главным образом означает хост, Вы пытаетесь достигнуть мудрого ping, не отвечает на запросы PING.
100% Packet loss when pinging my external IP [closed]
This question was closed because it is not about an official Ubuntu flavor. It is not currently accepting answers.
This is not about an official Ubuntu flavor. Questions about other Linux distributions can be asked on Unix & Linux, those about Windows on Super User, those about Apple products on Ask Different and generic programming questions on Stack Overflow.
There’s a ddns domain pointing to my external ip & I am able to ping it from an off site computer. However, when I ping my external ip from my local computer, all of the packets fail & I end up with 100% packet loss. Ping from offsite computer:
PING something.mydomain.com (xx.xxx.xx.xxx) 56(84) bytes of data. 64 bytes from xx.xxx.xx.xxx: icmp_seq=1 ttl=42 time=16.8 ms 64 bytes from xx.xxx.xx.xxx: icmp_seq=2 ttl=42 time=23.5 ms 64 bytes from xx.xxx.xx.xxx: icmp_seq=3 ttl=42 time=25.1 ms 64 bytes from xx.xxx.xx.xxx: icmp_seq=4 ttl=42 time=16.6 ms 64 bytes from xx.xxx.xx.xxx: icmp_seq=5 ttl=42 time=18.9 ms 64 bytes from xx.xxx.xx.xxx: icmp_seq=6 ttl=42 time=17.2 ms 64 bytes from xx.xxx.xx.xxx: icmp_seq=7 ttl=42 time=18.9 ms 64 bytes from xx.xxx.xx.xxx: icmp_seq=8 ttl=42 time=17.3 ms --- something.mydomain.com ping statistics --- 8 packets transmitted, 8 received, 0% packet loss, time 1404ms rtt min/avg/max/mdev = 16.636/19.326/25.111/3.024 ms Remote PING completed. PING something.mydomain.com (xx.xxx.xx.xxx) 56(84) bytes of data. ^C --- something.mydomain.com ping statistics --- 77 packets transmitted, 0 received, 100% packet loss, time 77813ms (PII has been obscured) I’m kinda new to ubuntu & am not sure what other information would be helpful in this case so please ask!
Thread: 100% packet loss
First Cup of Ubuntu 
100% packet loss
A month or two ago I bought a crappy laptop to host a small Ubuntu Server on. The idea was to learn how to go about using it a Linux distro. Anyway, I’ve been using it as a development environment to work on a few projects.
Today however something has changed and I’m not sure what. Externally users can still access my server via IP/domain but no data is posted to it, it just results in 100% packet loss. I tried to ping the site externally and the same thing happens.
I’m not sure what I’ve done that has caused this and have no idea where to start.
Would really appreciate it if anyone can help shed some light on this so I can get back to work!
Re: 100% packet loss
Can’t really help from the info provided.
http://blog.jdpfu.com/2013/03/01/lin. 101-networking
We need more concrete data. Do everything ON the laptop/server.
First Cup of Ubuntu
Re: 100% packet loss
This should be more useful info to troubleshoot the issue:
dmesg |grep eth5 [ 16.255963] alx 0000:02:00.0 eth0: NIC Link Up: 1 Gbps Full
sudo lshw -C network PCI (sysfs)
ifconfig -a eth0 Link encap:Ethernet HWaddr 08:9e:01:e0:3b:49 inet addr:192.168.0.5 Bcast:192.168.0.255 Mask:255.255.255.0 inet6 addr: fe80::a9e:1ff:fee0:3b49/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:7753 errors:0 dropped:0 overruns:0 frame:0 TX packets:4771 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:5852352 (5.8 MB) TX bytes:1452735 (1.4 MB) Interrupt:36
lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING MTU:65536 Metric:1 RX packets:56 errors:0 dropped:0 overruns:0 frame:0 TX packets:56 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:4410 (4.4 KB) TX bytes:4410 (4.4 KB)
wlan0 Link encap:Ethernet HWaddr 70:18:8b:1b:e5:bb BROADCAST MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
more /etc/resolv.conf # Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8) # DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN nameserver 194.168.4.100 nameserver 194.168.8.100
route Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface default 192.168.0.1 0.0.0.0 UG 100 0 0 eth0 192.168.0.0 * 255.255.255.0 U 0 0 0 eth0
Re: 100% packet loss
Great. Can you ping .
* the router by IP
* the nameservers by IP
* any websites by IP
* any websites by DNS name?
Where this fails will tell us where the failure lies. The issue could be a bad port, bad cable, bad settings.
BTW, wrapping the output of commands in «code» tags would be helpful (Adv Reply has a button). It would keep things aligned and much easier to read, which means more eyes will review the data for issues.
I don’t see anything blatantly wrong so far.
First Cup of Ubuntu
Re: 100% packet loss
Here’s the result of my pinging
PING 192.168.0.1 (192.168.0.1) 56(84) bytes of data. 64 bytes from 192.168.0.1: icmp_req=1 ttl=64 time=0.771 ms 64 bytes from 192.168.0.1: icmp_req=2 ttl=64 time=0.674 ms 64 bytes from 192.168.0.1: icmp_req=3 ttl=64 time=0.691 ms
PING 8.8.8.8 (8.8.8.8) 56(84) bytes of data. 64 bytes from 8.8.8.8: icmp_req=1 ttl=47 time=25.6 ms 64 bytes from 8.8.8.8: icmp_req=2 ttl=47 time=24.3 ms 64 bytes from 8.8.8.8: icmp_req=3 ttl=47 time=22.0 ms
PING google.com (62.253.3.84) 56(84) bytes of data. 64 bytes from host-62-253-8-84.not-set-yet.virginmedia.net (62.253.3.84): icmp_req=1 ttl=59 time=11.3 ms 64 bytes from host-62-253-8-84.not-set-yet.virginmedia.net (62.253.3.84): icmp_req=2 ttl=59 time=12.8 ms 64 bytes from host-62-253-8-84.not-set-yet.virginmedia.net (62.253.3.84): icmp_req=3 ttl=59 time=11.6 ms
Not entirely sure what you meant about pinging name servers (apologies, I should understand that terminology by now). If it’s to do with the domain, GoDaddy is the registrar and I haven’t set any name servers there, they’re the default ones. If this is what you meant here is me pinging those two name servers:
PING 216.69.185.3 (216.69.185.3) 56(84) bytes of data. 64 bytes from 216.69.185.3: icmp_req=1 ttl=52 time=37.1 ms 64 bytes from 216.69.185.3: icmp_req=2 ttl=52 time=33.7 ms 64 bytes from 216.69.185.3: icmp_req=3 ttl=52 time=36.9 ms
PING 208.109.255.3 (208.109.255.3) 56(84) bytes of data. 64 bytes from 208.109.255.3: icmp_req=1 ttl=52 time=39.3 ms 64 bytes from 208.109.255.3: icmp_req=2 ttl=52 time=36.5 ms 64 bytes from 208.109.255.3: icmp_req=3 ttl=52 time=35.8 ms
PS: In this reply I added code tags and also updated the last reply with code tags (thanks for heads up)
Ubuntu ping results in 100% packet loss
I use ubuntu 15.10 and I can ping localhost, gateway (192.168.1.1) and 8.8.8.8 successfully, but I can’t ping any other hostname/IP address(outside my network that is). It results in 100% packet loss. What’s interesting is when I ping a hostname, its resolved into IP address but the ping doesn’t go through and I can ping any host/IP from the VM (debian) inside the Ubuntu box.
xxxx@xxxx:~$ ping -c 4 microsoft.com PING microsoft.com (104.40.211.35) 56(84) bytes of data. --- microsoft.com ping statistics --- 4 packets transmitted, 0 received, 100% packet loss, time 3022ms I’ve tried other hosts as well. Microsoft is an example. I had to reinstall traceroute only then it worked. I reinstalled the iputils-ping but I still have the same problem.
1 Answer 1
Since you where able to ping 8.8.8.8 which is clearly not within your own network at home I assume you only tested with microsoft.com which is in fact blocking icmp echo requests, as already stated in the comments below your question.
To see if you can ping outside you could use as example google.com or as you did the google-dns-server ( 8.8.8.8 ). You can as well use traceroute command to see where it hangs if you try to ping a certain host. So a traceroute 8.8.8.8 wields some output like this (taken from my side, may be different for your side):
michael@NEXUS-ONE:~$ traceroute 8.8.8.8 traceroute to 8.8.8.8 (8.8.8.8), 64 hops max 1 192.168.0.1 16,803ms 2,651ms 2,073ms 2 10.152.192.1 8,918ms 9,518ms 9,236ms 3 81.210.131.221 11,155ms 9,955ms 9,957ms 4 84.116.196.158 20,015ms 18,580ms 21,355ms 5 84.116.196.162 19,940ms 19,956ms 19,999ms 6 84.116.133.97 21,078ms 35,584ms 23,217ms 7 213.46.177.42 18,859ms 21,082ms 20,002ms 8 216.239.59.72 30,190ms 22,493ms 17,215ms 9 216.239.57.194 20,009ms 18,788ms 30,898ms 10 66.249.95.39 22,115ms 26,881ms 23,907ms 11 216.239.49.234 24,900ms 27,041ms 25,895ms 12 216.239.51.209 26,067ms 31,986ms 23,893ms 13 * * * 14 8.8.8.8 28,034ms 23,544ms 43,217ms As you can see the three stars on hop #13 may indicate a problem (slow response times etc.) if that happens on the last hop, but showing an IP it mostly means the host you try to reach ping wise doesn’t respond to PING requests.