Jump to content
  • Announcements

    • Как правильно добавить self-test и прочую отладку в тему   08/18/2016

      self-test и логи могут содержать непубличную информацию, потому их не стоит прикреплять к постам бездумно. Однако, слать селф-тесты в личку абсолютно неправильно, поскольку это усложняет координацию между разработчиками и отрывает диагностику от темы с проблемой. Потому следует делать так: Пишете пост или создаете тему с описанием проблемы. Сразу после этого в этой же теме создаете сообщение с приложенным self-test, логами и прочей отладкой. В это же сообщение добавляете ссылку на предыдущее, чтобы не приходилось искать описание. Скрываете сообщение с отладкой. Эта функция доступна всем юзерам. Выбираете в меню поста (спасибо @KorDen):

      После этого эти сообщения станут доступны только администрации, а все пользователи не будут иметь к ней доступ.
  • 3
Equalizer

исправлено
Что-то с пингом

Question

Всем добрый день!

Имеем Keenetic Giga II с 2.11.A.6.0-0 на борту, при пинге удаленного узла через cli или веб-интерфейс имеем следующее:

sending ICMP ECHO request to yandex.ru...
PING yandex.ru (77.88.55.66) 56 (84) bytes of data.
84 bytes from yandex.ru (77.88.55.66): icmp_req=1, ttl=54, time=24.27 ms.
84 bytes from yandex.ru (77.88.55.66): icmp_req=2, ttl=54, time=24.06 ms.
84 bytes from yandex.ru (77.88.55.66): icmp_req=3, ttl=54, time=24.07 ms.
"Destination unreachable" ICMP packet received from 127.0.0.1 (type = 3, code = 3).
84 bytes from yandex.ru (77.88.55.66): icmp_req=4, ttl=54, time=24.06 ms.
84 bytes from yandex.ru (77.88.55.66): icmp_req=5, ttl=54, time=24.08 ms.
—- yandex.ru ping statistics —-
5 packets transmitted, 5 packets received, 0% packet loss,
0 duplicate(s), time 4026.60 ms.
Round-trip min/avg/max = 24.06/24.10/24.27 ms.

При пинге через ssh:

~ # ping yandex.ru
PING yandex.ru (5.255.255.80): 56 data bytes
64 bytes from 5.255.255.80: seq=0 ttl=56 time=20.342 ms
64 bytes from 5.255.255.80: seq=1 ttl=56 time=20.097 ms
64 bytes from 5.255.255.80: seq=2 ttl=56 time=20.037 ms
64 bytes from 5.255.255.80: seq=3 ttl=56 time=20.397 ms
64 bytes from 5.255.255.80: seq=4 ttl=56 time=20.022 ms
64 bytes from 5.255.255.80: seq=5 ttl=56 time=19.983 ms
64 bytes from 5.255.255.80: seq=6 ttl=56 time=20.198 ms
64 bytes from 5.255.255.80: seq=7 ttl=56 time=20.132 ms
64 bytes from 5.255.255.80: seq=8 ttl=56 time=20.045 ms
64 bytes from 5.255.255.80: seq=9 ttl=56 time=20.473 ms
64 bytes from 5.255.255.80: seq=10 ttl=56 time=20.373 ms
^C
—- yandex.ru ping statistics —-
11 packets transmitted, 11 packets received, 0% packet loss
round-trip min/avg/max = 19.983/20.190/20.473 ms

Интересует эта строчка:

"Destination unreachable" ICMP packet received from 127.0.0.1 (type = 3, code = 3).

Что не так?

  • Thanks 1
  • Upvote 1

Share this post


Link to post
Share on other sites

24 answers to this question

  • 0
2 часа назад, Equalizer сказал:

 

"Destination unreachable" ICMP packet received from 127.0.0.1 (type = 3, code = 3).

Тот же роутер с такой же прошивкой, проблемы не заметил.

Share this post


Link to post
Share on other sites
  • 0
4 минуты назад, Kiborg_Man сказал:

Тот же роутер с такой же прошивкой, проблемы не заметил.

Набор компонентов заскринить можете?

Share this post


Link to post
Share on other sites
  • 0
4 минуты назад, Equalizer сказал:

Набор компонентов заскринить можете?

На скриншотах видны только установленные компоненты.

Скрытый текст


Screenshot at 2017-11-02 12:50:10.png

Screenshot at 2017-11-02 12:50:54.png

 

 

Edited by Kiborg_Man

Share this post


Link to post
Share on other sites
  • 0
2 часа назад, Equalizer сказал:

Всем добрый день!

Имеем Keenetic Giga II с 2.11.A.6.0-0 на борту, при пинге удаленного узла через cli или веб-интерфейс имеем следующее:

sending ICMP ECHO request to yandex.ru...
PING yandex.ru (77.88.55.66) 56 (84) bytes of data.
84 bytes from yandex.ru (77.88.55.66): icmp_req=1, ttl=54, time=24.27 ms.
84 bytes from yandex.ru (77.88.55.66): icmp_req=2, ttl=54, time=24.06 ms.
84 bytes from yandex.ru (77.88.55.66): icmp_req=3, ttl=54, time=24.07 ms.
"Destination unreachable" ICMP packet received from 127.0.0.1 (type = 3, code = 3).
84 bytes from yandex.ru (77.88.55.66): icmp_req=4, ttl=54, time=24.06 ms.
84 bytes from yandex.ru (77.88.55.66): icmp_req=5, ttl=54, time=24.08 ms.
—- yandex.ru ping statistics —-
5 packets transmitted, 5 packets received, 0% packet loss,
0 duplicate(s), time 4026.60 ms.
Round-trip min/avg/max = 24.06/24.10/24.27 ms.

При пинге через ssh:

~ # ping yandex.ru
PING yandex.ru (5.255.255.80): 56 data bytes
64 bytes from 5.255.255.80: seq=0 ttl=56 time=20.342 ms
64 bytes from 5.255.255.80: seq=1 ttl=56 time=20.097 ms
64 bytes from 5.255.255.80: seq=2 ttl=56 time=20.037 ms
64 bytes from 5.255.255.80: seq=3 ttl=56 time=20.397 ms
64 bytes from 5.255.255.80: seq=4 ttl=56 time=20.022 ms
64 bytes from 5.255.255.80: seq=5 ttl=56 time=19.983 ms
64 bytes from 5.255.255.80: seq=6 ttl=56 time=20.198 ms
64 bytes from 5.255.255.80: seq=7 ttl=56 time=20.132 ms
64 bytes from 5.255.255.80: seq=8 ttl=56 time=20.045 ms
64 bytes from 5.255.255.80: seq=9 ttl=56 time=20.473 ms
64 bytes from 5.255.255.80: seq=10 ttl=56 time=20.373 ms
^C
—- yandex.ru ping statistics —-
11 packets transmitted, 11 packets received, 0% packet loss
round-trip min/avg/max = 19.983/20.190/20.473 ms

Интересует эта строчка:

"Destination unreachable" ICMP packet received from 127.0.0.1 (type = 3, code = 3).

Что не так?

Giga 2  2.11.A.6.0-0 есть такое

sending ICMP ECHO request to yandex.ru...
PING yandex.ru (77.88.55.70) 0 (28) bytes of data.
28 bytes from yandex.ru (77.88.55.70): icmp_req=1, ttl=53
28 bytes from yandex.ru (77.88.55.70): icmp_req=2, ttl=53
"Destination unreachable" ICMP packet received from 127.0.0.1 (type = 3, code = 3).
28 bytes from yandex.ru (77.88.55.70): icmp_req=3, ttl=53
28 bytes from yandex.ru (77.88.55.70): icmp_req=4, ttl=53
28 bytes from yandex.ru (77.88.55.70): icmp_req=5, ttl=53
 
--- yandex.ru ping statistics ---
5 packets transmitted, 5 packets received, 0% packet loss,
0 duplicate(s), time 4009.73 ms.

Share this post


Link to post
Share on other sites
  • 0

Только что сам поймал ошибку Destination unreachable. Похоже ошибки проявляется иногда т.к. ранее я её не ловил.

Скрытый текст

 

sending ICMP ECHO request to yandex.ru...
PING yandex.ru (77.88.55.66) 56 (84) bytes of data.
84 bytes from yandex.ru (77.88.55.66): icmp_req=1, ttl=51, time=9.39 ms.
84 bytes from yandex.ru (77.88.55.66): icmp_req=2, ttl=51, time=8.84 ms.
84 bytes from yandex.ru (77.88.55.66): icmp_req=3, ttl=51, time=8.71 ms.
84 bytes from yandex.ru (77.88.55.66): icmp_req=4, ttl=51, time=8.47 ms.
84 bytes from yandex.ru (77.88.55.66): icmp_req=5, ttl=51, time=8.57 ms.
84 bytes from yandex.ru (77.88.55.66): icmp_req=6, ttl=51, time=9.44 ms.
84 bytes from yandex.ru (77.88.55.66): icmp_req=7, ttl=51, time=8.57 ms.
84 bytes from yandex.ru (77.88.55.66): icmp_req=8, ttl=51, time=8.79 ms.
84 bytes from yandex.ru (77.88.55.66): icmp_req=9, ttl=51, time=9.30 ms.
84 bytes from yandex.ru (77.88.55.66): icmp_req=10, ttl=51, time=8.76 ms.
84 bytes from yandex.ru (77.88.55.66): icmp_req=11, ttl=51, time=8.43 ms.
84 bytes from yandex.ru (77.88.55.66): icmp_req=12, ttl=51, time=8.53 ms.
"Destination unreachable" ICMP packet received from 156.34.178.238 (type = 3, code = 1).
84 bytes from yandex.ru (77.88.55.66): icmp_req=13, ttl=51, time=8.59 ms.
84 bytes from yandex.ru (77.88.55.66): icmp_req=14, ttl=51, time=8.52 ms.
84 bytes from yandex.ru (77.88.55.66): icmp_req=15, ttl=51, time=8.50 ms.
84 bytes from yandex.ru (77.88.55.66): icmp_req=16, ttl=51, time=8.69 ms.
84 bytes from yandex.ru (77.88.55.66): icmp_req=17, ttl=51, time=8.94 ms.
84 bytes from yandex.ru (77.88.55.66): icmp_req=18, ttl=51, time=9.43 ms.
84 bytes from yandex.ru (77.88.55.66): icmp_req=19, ttl=51, time=9.05 ms.
84 bytes from yandex.ru (77.88.55.66): icmp_req=20, ttl=51, time=8.69 ms.
84 bytes from yandex.ru (77.88.55.66): icmp_req=21, ttl=51, time=8.56 ms.
84 bytes from yandex.ru (77.88.55.66): icmp_req=22, ttl=51, time=8.78 ms.
84 bytes from yandex.ru (77.88.55.66): icmp_req=23, ttl=51, time=8.35 ms.
84 bytes from yandex.ru (77.88.55.66): icmp_req=24, ttl=51, time=8.67 ms.
84 bytes from yandex.ru (77.88.55.66): icmp_req=25, ttl=51, time=8.51 ms.
84 bytes from yandex.ru (77.88.55.66): icmp_req=26, ttl=51, time=10.47 ms.
84 bytes from yandex.ru (77.88.55.66): icmp_req=27, ttl=51, time=8.54 ms.
84 bytes from yandex.ru (77.88.55.66): icmp_req=28, ttl=51, time=9.53 ms.
84 bytes from yandex.ru (77.88.55.66): icmp_req=29, ttl=51, time=12.48 ms.
84 bytes from yandex.ru (77.88.55.66): icmp_req=30, ttl=51, time=8.57 ms.
 
--- yandex.ru ping statistics ---
30 packets transmitted, 30 packets received, 0% packet loss,
0 duplicate(s), time 29027.20 ms.
Round-trip min/avg/max = 8.35/8.95/12.48 ms.

 

 

  • Thanks 1

Share this post


Link to post
Share on other sites
  • 0
2 минуты назад, Kiborg_Man сказал:

Только что сам поймал ошибку Destination unreachable. Похоже ошибки проявляется иногда т.к. ранее я её не ловил.

  Скрыть содержимое

 

sending ICMP ECHO request to yandex.ru...
PING yandex.ru (77.88.55.66) 56 (84) bytes of data.
84 bytes from yandex.ru (77.88.55.66): icmp_req=1, ttl=51, time=9.39 ms.
84 bytes from yandex.ru (77.88.55.66): icmp_req=2, ttl=51, time=8.84 ms.
84 bytes from yandex.ru (77.88.55.66): icmp_req=3, ttl=51, time=8.71 ms.
84 bytes from yandex.ru (77.88.55.66): icmp_req=4, ttl=51, time=8.47 ms.
84 bytes from yandex.ru (77.88.55.66): icmp_req=5, ttl=51, time=8.57 ms.
84 bytes from yandex.ru (77.88.55.66): icmp_req=6, ttl=51, time=9.44 ms.
84 bytes from yandex.ru (77.88.55.66): icmp_req=7, ttl=51, time=8.57 ms.
84 bytes from yandex.ru (77.88.55.66): icmp_req=8, ttl=51, time=8.79 ms.
84 bytes from yandex.ru (77.88.55.66): icmp_req=9, ttl=51, time=9.30 ms.
84 bytes from yandex.ru (77.88.55.66): icmp_req=10, ttl=51, time=8.76 ms.
84 bytes from yandex.ru (77.88.55.66): icmp_req=11, ttl=51, time=8.43 ms.
84 bytes from yandex.ru (77.88.55.66): icmp_req=12, ttl=51, time=8.53 ms.
"Destination unreachable" ICMP packet received from 156.34.178.238 (type = 3, code = 1).
84 bytes from yandex.ru (77.88.55.66): icmp_req=13, ttl=51, time=8.59 ms.
84 bytes from yandex.ru (77.88.55.66): icmp_req=14, ttl=51, time=8.52 ms.
84 bytes from yandex.ru (77.88.55.66): icmp_req=15, ttl=51, time=8.50 ms.
84 bytes from yandex.ru (77.88.55.66): icmp_req=16, ttl=51, time=8.69 ms.
84 bytes from yandex.ru (77.88.55.66): icmp_req=17, ttl=51, time=8.94 ms.
84 bytes from yandex.ru (77.88.55.66): icmp_req=18, ttl=51, time=9.43 ms.
84 bytes from yandex.ru (77.88.55.66): icmp_req=19, ttl=51, time=9.05 ms.
84 bytes from yandex.ru (77.88.55.66): icmp_req=20, ttl=51, time=8.69 ms.
84 bytes from yandex.ru (77.88.55.66): icmp_req=21, ttl=51, time=8.56 ms.
84 bytes from yandex.ru (77.88.55.66): icmp_req=22, ttl=51, time=8.78 ms.
84 bytes from yandex.ru (77.88.55.66): icmp_req=23, ttl=51, time=8.35 ms.
84 bytes from yandex.ru (77.88.55.66): icmp_req=24, ttl=51, time=8.67 ms.
84 bytes from yandex.ru (77.88.55.66): icmp_req=25, ttl=51, time=8.51 ms.
84 bytes from yandex.ru (77.88.55.66): icmp_req=26, ttl=51, time=10.47 ms.
84 bytes from yandex.ru (77.88.55.66): icmp_req=27, ttl=51, time=8.54 ms.
84 bytes from yandex.ru (77.88.55.66): icmp_req=28, ttl=51, time=9.53 ms.
84 bytes from yandex.ru (77.88.55.66): icmp_req=29, ttl=51, time=12.48 ms.
84 bytes from yandex.ru (77.88.55.66): icmp_req=30, ttl=51, time=8.57 ms.
 
--- yandex.ru ping statistics ---
30 packets transmitted, 30 packets received, 0% packet loss,
0 duplicate(s), time 29027.20 ms.
Round-trip min/avg/max = 8.35/8.95/12.48 ms.

 

 

Тут иная ситуация, это ответ от маршрутизатора в интернете а не от кинетика как у тс

  • Thanks 1

Share this post


Link to post
Share on other sites
  • 0

@Equalizer

destination unreachable (3) — destination unreachable/destination port unreachable (адресат недосягаем).
 

127.0.0.1 - localhost

Edited by enpa

Share this post


Link to post
Share on other sites
  • 0
11 час назад, Equalizer сказал:

Имеем Keenetic Giga II с 2.11.A.6.0-0 на борту, при пинге удаленного узла через cli или веб-интерфейс имеем следующее:

sending ICMP ECHO request to yandex.ru...
PING yandex.ru (77.88.55.66) 56 (84) bytes of data.
....

"Destination unreachable" ICMP packet received from 127.0.0.1 (type = 3, code = 3).
...

5 packets transmitted, 5 packets received, 0% packet loss,
0 duplicate(s), time 4026.60 ms.
Round-trip min/avg/max = 24.06/24.10/24.27 ms.

KII проц такой же, на релизе 211А6 све нормально

Скрытый текст

(config)> tools ping yandex.ru
sending ICMP ECHO request to yandex.ru...
PING yandex.ru (5.255.255.5) 56 (84) bytes of data.
84 bytes from yandex.ru (5.255.255.5): icmp_req=1, ttl=56, time=17.96 ms.
84 bytes from yandex.ru (5.255.255.5): icmp_req=2, ttl=56, time=17.79 ms.
84 bytes from yandex.ru (5.255.255.5): icmp_req=3, ttl=56, time=17.88 ms.
84 bytes from yandex.ru (5.255.255.5): icmp_req=4, ttl=56, time=18.03 ms.
84 bytes from yandex.ru (5.255.255.5): icmp_req=5, ttl=56, time=18.80 ms.
84 bytes from yandex.ru (5.255.255.5): icmp_req=6, ttl=56, time=18.31 ms.
84 bytes from yandex.ru (5.255.255.5): icmp_req=7, ttl=56, time=17.68 ms.
84 bytes from yandex.ru (5.255.255.5): icmp_req=8, ttl=56, time=17.69 ms.
84 bytes from yandex.ru (5.255.255.5): icmp_req=9, ttl=56, time=18.01 ms.
84 bytes from yandex.ru (5.255.255.5): icmp_req=10, ttl=56, time=17.87 ms.
84 bytes from yandex.ru (5.255.255.5): icmp_req=11, ttl=56, time=17.80 ms.
84 bytes from yandex.ru (5.255.255.5): icmp_req=12, ttl=56, time=18.25 ms.
84 bytes from yandex.ru (5.255.255.5): icmp_req=13, ttl=56, time=17.78 ms.
84 bytes from yandex.ru (5.255.255.5): icmp_req=14, ttl=56, time=17.93 ms.
84 bytes from yandex.ru (5.255.255.5): icmp_req=15, ttl=56, time=17.79 ms.
84 bytes from yandex.ru (5.255.255.5): icmp_req=16, ttl=56, time=17.76 ms.
84 bytes from yandex.ru (5.255.255.5): icmp_req=17, ttl=56, time=18.66 ms.
84 bytes from yandex.ru (5.255.255.5): icmp_req=18, ttl=56, time=17.81 ms.
84 bytes from yandex.ru (5.255.255.5): icmp_req=19, ttl=56, time=18.24 ms.
84 bytes from yandex.ru (5.255.255.5): icmp_req=20, ttl=56, time=17.82 ms.
84 bytes from yandex.ru (5.255.255.5): icmp_req=21, ttl=56, time=17.88 ms.
84 bytes from yandex.ru (5.255.255.5): icmp_req=22, ttl=56, time=17.86 ms.
84 bytes from yandex.ru (5.255.255.5): icmp_req=23, ttl=56, time=18.17 ms.
84 bytes from yandex.ru (5.255.255.5): icmp_req=24, ttl=56, time=18.06 ms.
84 bytes from yandex.ru (5.255.255.5): icmp_req=25, ttl=56, time=17.90 ms.
84 bytes from yandex.ru (5.255.255.5): icmp_req=26, ttl=56, time=18.29 ms.
84 bytes from yandex.ru (5.255.255.5): icmp_req=27, ttl=56, time=17.74 ms.
84 bytes from yandex.ru (5.255.255.5): icmp_req=28, ttl=56, time=18.60 ms.
84 bytes from yandex.ru (5.255.255.5): icmp_req=29, ttl=56, time=17.74 ms.
--- yandex.ru ping statistics ---
29 packets transmitted, 29 packets received, 0% packet loss,
0 duplicate(s), time 28627.50 ms.
Round-trip min/avg/max = 17.68/18.00/18.80 ms.
(config)>

Судя всего если получаем 77.88.55.66 возможно включена фильтрация YANDEX поэтому и 127.0.0.1

Share this post


Link to post
Share on other sites
  • 0
8 часов назад, vasek00 сказал:

KII проц такой же, на релизе 211А6 све нормально

  Показать содержимое

(config)> tools ping yandex.ru
sending ICMP ECHO request to yandex.ru...
PING yandex.ru (5.255.255.5) 56 (84) bytes of data.
84 bytes from yandex.ru (5.255.255.5): icmp_req=1, ttl=56, time=17.96 ms.
84 bytes from yandex.ru (5.255.255.5): icmp_req=2, ttl=56, time=17.79 ms.
84 bytes from yandex.ru (5.255.255.5): icmp_req=3, ttl=56, time=17.88 ms.
84 bytes from yandex.ru (5.255.255.5): icmp_req=4, ttl=56, time=18.03 ms.
84 bytes from yandex.ru (5.255.255.5): icmp_req=5, ttl=56, time=18.80 ms.
84 bytes from yandex.ru (5.255.255.5): icmp_req=6, ttl=56, time=18.31 ms.
84 bytes from yandex.ru (5.255.255.5): icmp_req=7, ttl=56, time=17.68 ms.
84 bytes from yandex.ru (5.255.255.5): icmp_req=8, ttl=56, time=17.69 ms.
84 bytes from yandex.ru (5.255.255.5): icmp_req=9, ttl=56, time=18.01 ms.
84 bytes from yandex.ru (5.255.255.5): icmp_req=10, ttl=56, time=17.87 ms.
84 bytes from yandex.ru (5.255.255.5): icmp_req=11, ttl=56, time=17.80 ms.
84 bytes from yandex.ru (5.255.255.5): icmp_req=12, ttl=56, time=18.25 ms.
84 bytes from yandex.ru (5.255.255.5): icmp_req=13, ttl=56, time=17.78 ms.
84 bytes from yandex.ru (5.255.255.5): icmp_req=14, ttl=56, time=17.93 ms.
84 bytes from yandex.ru (5.255.255.5): icmp_req=15, ttl=56, time=17.79 ms.
84 bytes from yandex.ru (5.255.255.5): icmp_req=16, ttl=56, time=17.76 ms.
84 bytes from yandex.ru (5.255.255.5): icmp_req=17, ttl=56, time=18.66 ms.
84 bytes from yandex.ru (5.255.255.5): icmp_req=18, ttl=56, time=17.81 ms.
84 bytes from yandex.ru (5.255.255.5): icmp_req=19, ttl=56, time=18.24 ms.
84 bytes from yandex.ru (5.255.255.5): icmp_req=20, ttl=56, time=17.82 ms.
84 bytes from yandex.ru (5.255.255.5): icmp_req=21, ttl=56, time=17.88 ms.
84 bytes from yandex.ru (5.255.255.5): icmp_req=22, ttl=56, time=17.86 ms.
84 bytes from yandex.ru (5.255.255.5): icmp_req=23, ttl=56, time=18.17 ms.
84 bytes from yandex.ru (5.255.255.5): icmp_req=24, ttl=56, time=18.06 ms.
84 bytes from yandex.ru (5.255.255.5): icmp_req=25, ttl=56, time=17.90 ms.
84 bytes from yandex.ru (5.255.255.5): icmp_req=26, ttl=56, time=18.29 ms.
84 bytes from yandex.ru (5.255.255.5): icmp_req=27, ttl=56, time=17.74 ms.
84 bytes from yandex.ru (5.255.255.5): icmp_req=28, ttl=56, time=18.60 ms.
84 bytes from yandex.ru (5.255.255.5): icmp_req=29, ttl=56, time=17.74 ms.
--- yandex.ru ping statistics ---
29 packets transmitted, 29 packets received, 0% packet loss,
0 duplicate(s), time 28627.50 ms.
Round-trip min/avg/max = 17.68/18.00/18.80 ms.
(config)>

Судя всего если получаем 77.88.55.66 возможно включена фильтрация YANDEX поэтому и 127.0.0.1

От яндеса в роутере только dns-ы указаны ручками вместо провайдерских. Получается, что иногда яндекс заворачивает запрос на локалхост, но зачем? И почему этого не происходит через ssh?

Может быть дело все таки в стандартной утилите для пинга?

Вот пинг к гуглу:

(tools)> ping google.ru
sending ICMP ECHO request to google.ru...
PING google.ru (173.194.222.94) 56 (84) bytes of data.
84 bytes from google.ru (173.194.222.94): icmp_req=1, ttl=50, time=34.33 ms.
84 bytes from google.ru (173.194.222.94): icmp_req=2, ttl=50, time=32.82 ms.
"Destination unreachable" ICMP packet received from 127.0.0.1 (type = 3, code = 3).
"Destination unreachable" ICMP packet received from 127.0.0.1 (type = 3, code = 3).
84 bytes from google.ru (173.194.222.94): icmp_req=3, ttl=50, time=32.97 ms.
84 bytes from google.ru (173.194.222.94): icmp_req=4, ttl=50, time=32.81 ms.
84 bytes from google.ru (173.194.222.94): icmp_req=5, ttl=50, time=32.80 ms.
"Destination unreachable" ICMP packet received from 127.0.0.1 (type = 3, code = 3).
"Destination unreachable" ICMP packet received from 127.0.0.1 (type = 3, code = 3).
84 bytes from google.ru (173.194.222.94): icmp_req=6, ttl=50, time=32.83 ms.
84 bytes from google.ru (173.194.222.94): icmp_req=7, ttl=50, time=32.80 ms.
84 bytes from google.ru (173.194.222.94): icmp_req=8, ttl=50, time=32.81 ms.
"Destination unreachable" ICMP packet received from 127.0.0.1 (type = 3, code = 3).
84 bytes from google.ru (173.194.222.94): icmp_req=9, ttl=50, time=32.78 ms.
84 bytes from google.ru (173.194.222.94): icmp_req=10, ttl=50, time=32.85 ms.
84 bytes from google.ru (173.194.222.94): icmp_req=11, ttl=50, time=32.78 ms.
"Destination unreachable" ICMP packet received from 127.0.0.1 (type = 3, code = 3).
84 bytes from google.ru (173.194.222.94): icmp_req=12, ttl=50, time=32.77 ms.
84 bytes from google.ru (173.194.222.94): icmp_req=13, ttl=50, time=32.84 ms.
--- google.ru ping statistics ---
14 packets transmitted, 13 packets received, 7% packet loss,
0 duplicate(s), time 13038.03 ms.
Round-trip min/avg/max = 32.77/32.93/34.33 ms.

Edited by Equalizer
  • Thanks 1

Share this post


Link to post
Share on other sites
  • 0

И вот через ssh:


~ # ping google.ru
PING google.ru (173.194.222.94): 56 data bytes
64 bytes from 173.194.222.94: seq=0 ttl=50 time=36.917 ms
64 bytes from 173.194.222.94: seq=1 ttl=50 time=33.936 ms
64 bytes from 173.194.222.94: seq=2 ttl=50 time=32.664 ms
64 bytes from 173.194.222.94: seq=3 ttl=50 time=32.712 ms
64 bytes from 173.194.222.94: seq=4 ttl=50 time=32.649 ms
64 bytes from 173.194.222.94: seq=5 ttl=50 time=32.669 ms
64 bytes from 173.194.222.94: seq=6 ttl=50 time=32.784 ms
64 bytes from 173.194.222.94: seq=7 ttl=50 time=32.660 ms
64 bytes from 173.194.222.94: seq=8 ttl=50 time=32.676 ms
64 bytes from 173.194.222.94: seq=9 ttl=50 time=32.745 ms
64 bytes from 173.194.222.94: seq=10 ttl=50 time=32.640 ms
64 bytes from 173.194.222.94: seq=11 ttl=50 time=32.655 ms
64 bytes from 173.194.222.94: seq=12 ttl=50 time=32.660 ms
64 bytes from 173.194.222.94: seq=13 ttl=50 time=32.653 ms
^C
--- google.ru ping statistics ---
14 packets transmitted, 14 packets received, 0% packet loss
round-trip min/avg/max = 32.640/33.072/36.917 ms

Share this post


Link to post
Share on other sites
  • 0
2 часа назад, Equalizer сказал:

От яндеса в роутере только dns-ы указаны ручками вместо провайдерских. Получается, что иногда яндекс заворачивает запрос на локалхост, но зачем? И почему этого не происходит через ssh?

Может быть дело все таки в стандартной утилите для пинга?

Вот пинг к гуглу:

(tools)> ping google.ru
sending ICMP ECHO request to google.ru...
PING google.ru (173.194.222.94) 56 (84) bytes of data.
84 bytes from google.ru (173.194.222.94): icmp_req=1, ttl=50, time=34.33 ms.
84 bytes from google.ru (173.194.222.94): icmp_req=2, ttl=50, time=32.82 ms.
"Destination unreachable" ICMP packet received from 127.0.0.1 (type = 3, code = 3).
"Destination unreachable" ICMP packet received from 127.0.0.1 (type = 3, code = 3).
84 bytes from google.ru (173.194.222.94): icmp_req=3, ttl=50, time=32.97 ms.
84 bytes from google.ru (173.194.222.94): icmp_req=4, ttl=50, time=32.81 ms.
84 bytes from google.ru (173.194.222.94): icmp_req=5, ttl=50, time=32.80 ms.
"Destination unreachable" ICMP packet received from 127.0.0.1 (type = 3, code = 3).
"Destination unreachable" ICMP packet received from 127.0.0.1 (type = 3, code = 3).
84 bytes from google.ru (173.194.222.94): icmp_req=6, ttl=50, time=32.83 ms.
84 bytes from google.ru (173.194.222.94): icmp_req=7, ttl=50, time=32.80 ms.
84 bytes from google.ru (173.194.222.94): icmp_req=8, ttl=50, time=32.81 ms.
"Destination unreachable" ICMP packet received from 127.0.0.1 (type = 3, code = 3).
84 bytes from google.ru (173.194.222.94): icmp_req=9, ttl=50, time=32.78 ms.
84 bytes from google.ru (173.194.222.94): icmp_req=10, ttl=50, time=32.85 ms.
84 bytes from google.ru (173.194.222.94): icmp_req=11, ttl=50, time=32.78 ms.
"Destination unreachable" ICMP packet received from 127.0.0.1 (type = 3, code = 3).
84 bytes from google.ru (173.194.222.94): icmp_req=12, ttl=50, time=32.77 ms.
84 bytes from google.ru (173.194.222.94): icmp_req=13, ttl=50, time=32.84 ms.
--- google.ru ping statistics ---
14 packets transmitted, 13 packets received, 7% packet loss,
0 duplicate(s), time 13038.03 ms.
Round-trip min/avg/max = 32.77/32.93/34.33 ms.

А здесь еще интереснее, наряду с ответами о недоступности от локалхоста есть еще и удачные ответы от пингуемого сервера на один и тот же пинг. 

Edited by r13

Share this post


Link to post
Share on other sites
  • 0
21 час назад, Equalizer сказал:

Имеем Keenetic Giga II с 2.11.A.6.0-0 на борту, при пинге удаленного узла через cli или веб-интерфейс имеем следующее:

От яндеса в роутере только dns-ы указаны ручками вместо провайдерских. Получается, что иногда яндекс заворачивает запрос на локалхост, но зачем? И почему этого не происходит через ssh?

Может быть дело все таки в стандартной утилите для пинга?

Вот мы подошли к доп.информации что у вас в роутере нет провайдерских, а может попробовать с ними. Второе самое важное можно откатиться и выяснить связано ли с прошивкой или нет?

" DNS Proxy " это локальная служба запущенная на роутере, настройка своих серверов можно в двух местах в WEB - Интернет-Прочее или Интрнет на соединении, Для того чтоб что то понять нужна более полная картина ситуации в данном случае по настройкам и =>

Скрытый текст

~ # netstat -ntulp | grep ndnproxy

...

/tmp # cat ndnproxymain.conf
rpc_port = 54321
rpc_ttl = 30000
rpc_wait = 10000
timeout = 7000
bantime = 300000
proceed = 500
ban_threshold = 3
stat_file = /var/ndnproxymain.stat
stat_time = 10000
dns_server = хх.хх.хх.хх .
static_a = my.keenetic.net 78.47.125.180
set-profile-ip 127.0.0.1 0
set-profile-ip ::1 0
....
dns_tcp_port = 53
dns_udp_port = 53
/tmp #

ban_threshold = 3 -> Задать количество последовательных неудачных запросов для запрета DNS-сервера. По умолчанию используется значение 3.

ТУТ вопрос у вас один DNS или несколько серверов указано, попробовать пару если один

bantime = 300000 -> Установить время, в течение которого DNS-сервер не будет использоваться. По умолчанию используется значение 30000mc

proceed = 500 -> Задать интервал между параллельными запросами, которые отправляет DNS-прокси нескольким DNS-серверам. По умолчанию используется значение 500mc

/tmp # cat ndnproxymain.stat
# ndnproxy statistics file

Total incoming requests: 3
Proxy requests sent:     3
Cache hits ratio:        0.000 (0)
Memory usage:            0.98K of 0.00K

DNS Servers

                      Ip   Ban  R.Sent  A.Rcvd  Med.Resp  Avg.Resp  
            хх.хх.хх.хх    no       3       3       5ms       5ms 

/tmp #

 

Share this post


Link to post
Share on other sites
  • 0
6 минут назад, vasek00 сказал:

Вот мы подошли к доп.информации что у вас в роутере нет провайдерских, а может попробовать с ними. Второе самое важное можно откатиться и выяснить связано ли с прошивкой или нет?

" DNS Proxy " это локальная служба запущенная на роутере, настройка своих серверов можно в двух местах в WEB - Интернет-Прочее или Интрнет на соединении, Для того чтоб что то понять нужна более полная картина ситуации в данном случае по настройкам и =>

  Показать содержимое

~ # netstat -ntulp | grep ndnproxy

...

/tmp # cat ndnproxymain.conf
rpc_port = 54321
rpc_ttl = 30000
rpc_wait = 10000
timeout = 7000
bantime = 300000
proceed = 500
ban_threshold = 3
stat_file = /var/ndnproxymain.stat
stat_time = 10000
dns_server = хх.хх.хх.хх .
static_a = my.keenetic.net 78.47.125.180
set-profile-ip 127.0.0.1 0
set-profile-ip ::1 0
....
dns_tcp_port = 53
dns_udp_port = 53
/tmp #

ban_threshold = 3 -> Задать количество последовательных неудачных запросов для запрета DNS-сервера. По умолчанию используется значение 3.

ТУТ вопрос у вас один DNS или несколько серверов указано, попробовать пару если один

bantime = 300000 -> Установить время, в течение которого DNS-сервер не будет использоваться. По умолчанию используется значение 30000mc

proceed = 500 -> Задать интервал между параллельными запросами, которые отправляет DNS-прокси нескольким DNS-серверам. По умолчанию используется значение 500mc

/tmp # cat ndnproxymain.stat
# ndnproxy statistics file

Total incoming requests: 3
Proxy requests sent:     3
Cache hits ratio:        0.000 (0)
Memory usage:            0.98K of 0.00K

DNS Servers

                      Ip   Ban  R.Sent  A.Rcvd  Med.Resp  Avg.Resp  
            хх.хх.хх.хх    no       3       3       5ms       5ms 

/tmp #

 

Или исключить влияние dns и проверить пинги по ip

Share this post


Link to post
Share on other sites
  • 0
20 минут назад, vasek00 сказал:

Вот мы подошли к доп.информации что у вас в роутере нет провайдерских, а может попробовать с ними. Второе самое важное можно откатиться и выяснить связано ли с прошивкой или нет?

" DNS Proxy " это локальная служба запущенная на роутере, настройка своих серверов можно в двух местах в WEB - Интернет-Прочее или Интрнет на соединении, Для того чтоб что то понять нужна более полная картина ситуации в данном случае по настройкам и =>

  Показать содержимое

~ # netstat -ntulp | grep ndnproxy

...

/tmp # cat ndnproxymain.conf
rpc_port = 54321
rpc_ttl = 30000
rpc_wait = 10000
timeout = 7000
bantime = 300000
proceed = 500
ban_threshold = 3
stat_file = /var/ndnproxymain.stat
stat_time = 10000
dns_server = хх.хх.хх.хх .
static_a = my.keenetic.net 78.47.125.180
set-profile-ip 127.0.0.1 0
set-profile-ip ::1 0
....
dns_tcp_port = 53
dns_udp_port = 53
/tmp #

ban_threshold = 3 -> Задать количество последовательных неудачных запросов для запрета DNS-сервера. По умолчанию используется значение 3.

ТУТ вопрос у вас один DNS или несколько серверов указано, попробовать пару если один

bantime = 300000 -> Установить время, в течение которого DNS-сервер не будет использоваться. По умолчанию используется значение 30000mc

proceed = 500 -> Задать интервал между параллельными запросами, которые отправляет DNS-прокси нескольким DNS-серверам. По умолчанию используется значение 500mc

/tmp # cat ndnproxymain.stat
# ndnproxy statistics file

Total incoming requests: 3
Proxy requests sent:     3
Cache hits ratio:        0.000 (0)
Memory usage:            0.98K of 0.00K

DNS Servers

                      Ip   Ban  R.Sent  A.Rcvd  Med.Resp  Avg.Resp  
            хх.хх.хх.хх    no       3       3       5ms       5ms 

/tmp #

 

Вы слишком глубоко копнуть решили, уверен, проблема где-то на поверхности. Про предыдущие версии прошивки не скажу, ибо обновился с 2.11 4.0.1 (на ней не тестил), а до этого был релиз 2.06, там все норм было

Вот пинги по ip, как предложил r13:

sending ICMP ECHO request to 77.88.55.66...
PING 77.88.55.66 (77.88.55.66) 56 (84) bytes of data.
84 bytes from 77.88.55.66: icmp_req=1, ttl=56, time=24.19 ms.
84 bytes from 77.88.55.66: icmp_req=2, ttl=56, time=23.95 ms.
84 bytes from 77.88.55.66: icmp_req=3, ttl=56, time=23.91 ms.
"Destination unreachable" ICMP packet received from 127.0.0.1 (type = 3, code = 3).
"Destination unreachable" ICMP packet received from 127.0.0.1 (type = 3, code = 3).
"Destination unreachable" ICMP packet received from 127.0.0.1 (type = 3, code = 3).
84 bytes from 77.88.55.66: icmp_req=4, ttl=56, time=23.93 ms.
84 bytes from 77.88.55.66: icmp_req=5, ttl=56, time=23.92 ms.
 
--- 77.88.55.66 ping statistics ---
5 packets transmitted, 5 packets received, 0% packet loss,
0 duplicate(s), time 4026.18 ms.
Round-trip min/avg/max = 23.91/23.98/24.19 ms.
 
Как видим, днс не причем. Все же грешу на утилиту
Edited by Equalizer

Share this post


Link to post
Share on other sites
  • 0
20 минут назад, Equalizer сказал:

Вы слишком глубоко копнуть решили, уверен, проблема где-то на поверхности. Про предыдущие версии прошивки не скажу, ибо обновился с 2.11 4.0.1 (на ней не тестил), а до этого был релиз 2.06, там все норм было

Копнул глубоко, да нет поверхностно - вид подключения и где прописан 77.88.55.66 в каком месте, то что netstat это просто увидеть на каких интерфейсах весит DNS Proxу, что не спрашивать лишнего.

Цитата

Вы слишком глубоко копнуть решили, уверен, проблема где-то на поверхности

Вопросов нет.

Share this post


Link to post
Share on other sites
  • 0
47 минут назад, r13 сказал:

Или исключить влияние dns и проверить пинги по ip

Extra II на 211А6 на ней вообще нет WAN, маршрут на шлюз в лок.сети.

(config)> tools ping 77.88.55.66
sending ICMP ECHO request to 77.88.55.66...
PING 77.88.55.66 (77.88.55.66) 56 (84) bytes of data.
84 bytes from 77.88.55.66: icmp_req=1, ttl=58, time=17.11 ms.
84 bytes from 77.88.55.66: icmp_req=2, ttl=58, time=16.75 ms.
84 bytes from 77.88.55.66: icmp_req=3, ttl=58, time=16.75 ms.
84 bytes from 77.88.55.66: icmp_req=4, ttl=58, time=16.75 ms.
84 bytes from 77.88.55.66: icmp_req=5, ttl=58, time=16.74 ms.
84 bytes from 77.88.55.66: icmp_req=6, ttl=58, time=16.70 ms.
84 bytes from 77.88.55.66: icmp_req=7, ttl=58, time=16.72 ms.
84 bytes from 77.88.55.66: icmp_req=8, ttl=58, time=16.71 ms.
84 bytes from 77.88.55.66: icmp_req=9, ttl=58, time=16.63 ms.
84 bytes from 77.88.55.66: icmp_req=10, ttl=58, time=16.68 ms.
84 bytes from 77.88.55.66: icmp_req=11, ttl=58, time=16.67 ms.
84 bytes from 77.88.55.66: icmp_req=12, ttl=58, time=16.66 ms.
84 bytes from 77.88.55.66: icmp_req=13, ttl=58, time=16.64 ms.
84 bytes from 77.88.55.66: icmp_req=14, ttl=58, time=16.64 ms.
84 bytes from 77.88.55.66: icmp_req=15, ttl=58, time=17.09 ms.
84 bytes from 77.88.55.66: icmp_req=16, ttl=58, time=16.64 ms.
84 bytes from 77.88.55.66: icmp_req=17, ttl=58, time=16.64 ms.
--- 77.88.55.66 ping statistics ---
17 packets transmitted, 17 packets received, 0% packet loss,
0 duplicate(s), time 16787.49 ms.
Round-trip min/avg/max = 16.63/16.73/17.11 ms.
(config)> 

dns_server = 77.88.55.66 .
static_a = my.keenetic.net 78.47.125.180

Только обратите внимание на повтор

"Destination unreachable" ICMP packet received from 127.0.0.1 (type = 3, code = 3).
"Destination unreachable" ICMP packet received from 127.0.0.1 (type = 3, code = 3).
84 bytes from google.ru (173.194.222.94): icmp_req=3, ttl=50, time=32.97 ms.
84 bytes from google.ru (173.194.222.94): icmp_req=4, ttl=50, time=32.81 ms.
84 bytes from google.ru (173.194.222.94): icmp_req=5, ttl=50, time=32.80 ms.
"Destination unreachable" ICMP packet received from 127.0.0.1 (type = 3, code = 3).
"Destination unreachable" ICMP packet received from 127.0.0.1 (type = 3, code = 3).
84 bytes from google.ru (173.194.222.94): icmp_req=6, ttl=50, time=32.83 ms.
84 bytes from google.ru (173.194.222.94): icmp_req=7, ttl=50, time=32.80 ms.
84 bytes from google.ru (173.194.222.94): icmp_req=8, ttl=50, time=32.81 ms.
"Destination unreachable" ICMP packet received from 127.0.0.1 (type = 3, code = 3).
84 bytes from google.ru (173.194.222.94): icmp_req=9, ttl=50, time=32.78 ms.
84 bytes from google.ru (173.194.222.94): icmp_req=10, ttl=50, time=32.85 ms.
84 bytes from google.ru (173.194.222.94): icmp_req=11, ttl=50, time=32.78 ms.
"Destination unreachable" ICMP packet received from 127.0.0.1 (type = 3, code = 3)

через 3

Share this post


Link to post
Share on other sites
  • 0
Скрытый текст

Port Unreachable

Unlike the Network Unreachable and Host Unreachable messages which come from routers, the Port Unreachable message comes from a host. The primary implication for troubleshooting is that the frame was successfully routed across the communications infrastructure, the last router ARP’ed for the host, got the response, and sent the frame. Furthermore, the intended destination host was on-line and willing to accept the frame into its communications buffer. The frame was then processed by, say, TCP or, perhaps UDP, RIP, OSPF, or some other protocol. The protocol (TCP or UDP) tried to send the data up to the destination port number (TCP or UDP port) and the port process didn’t exist. The protocol handler then reports Destination Unreachable – Port Unreachable.

One of the most common Port Unreachable errors occurs when an SNMP (Simple Network Management Protocol) console is polling a number of devices on the network. The console has been configured with a list of IP addresses to poll for the acquisition of network management data. The assumption is that each of those managed devices has been configured with an SNMP agent program assigned to a particular port number. One standard SNMP port number is 161. If you see a Port 161 Unreachable then you could reasonably assume that a console was polling a device which didn’t have an SNMP agent configured into it.

If you try to setup a NetBIOS connection (port 513) with a server that doesn’t support NetBIOS (hence, no 513 processing entity) you get a Port Unreachable. Mounting a file volume to a server that doesn’t support NFS results in the same.

When troubleshooting a Port Unreachable error it is necessary to know what is supposed to be at the indicated (unreachable) port. This may be as simple as looking up RFC 1700 (the well known number list) or as complicated as interacting with a vendors development team to figure out the operation of some proprietary application program that is using special port numbers.

One odd error that might be associated with a Port Unreachable message is seen when an otherwise normally operating conversation is interrupted by a Port Unreachable message. When you inspect the conversation you observe that the unreachable port was working without a problem. Frames were going to and from the port number when, suddenly – Port Unreachable. This is indicative of an overload condition or process priority configuration problem in the reporting host. The process in question was swapped out of memory and was not able to swap back in quickly enough to avoid the unreachable indication.

The nice thing about a Port Unreachable message is that it confirms proper operation of the intervening communications infrastructure and the presence of the destination host processor.

Summary: Port Unreachable

The host and the communications infrastructure are working properly.

The ICMP Port Unreachable message originates from a host, not a router.

The indicated port process was either not running or was swapped out. SNMP (Port 161) is a common port to be missing.

Find out what the port is used for and why it wasn’t available.

https://www.savvius.com/networking-glossary/tcp_ip_overview/icmp/unreachable/

немножко тут:
https://wiki.dieg.info/icmp

кто-то, похоже, подыхает на лупбэке, пакет ловить нужно:
http://www.firewall.cx/networking-topics/protocols/icmp-protocol/153-icmp-destination-unreachable.html

так-то тема старая, а арпы еще жарит на ване? забейте.

Share this post


Link to post
Share on other sites
  • 0

Та же проблема.

100 bytes from yandex.ru (5.255.255.60): icmp_req=43, ttl=44, time=49.30 ms.
"Destination unreachable" ICMP packet received from 127.0.0.1 (type = 3, code = 3).
"Destination unreachable" ICMP packet received from 127.0.0.1 (type = 3, code = 3).
100 bytes from yandex.ru (5.255.255.60): icmp_req=44, ttl=44, time=53.89 ms.
100 bytes from yandex.ru (5.255.255.60): icmp_req=45, ttl=44, time=62.33 ms.
100 bytes from yandex.ru (5.255.255.60): icmp_req=46, ttl=44, time=39.81 ms.
"Destination unreachable" ICMP packet received from 127.0.0.1 (type = 3, code = 3).
"Destination unreachable" ICMP packet received from 127.0.0.1 (type = 3, code = 3).
"Destination unreachable" ICMP packet received from 127.0.0.1 (type = 3, code = 3).
"Destination unreachable" ICMP packet received from 127.0.0.1 (type = 3, code = 3).
"Destination unreachable" ICMP packet received from 127.0.0.1 (type = 3, code = 3).
100 bytes from yandex.ru (5.255.255.60): icmp_req=47, ttl=44, time=44.34 ms.
100 bytes from yandex.ru (5.255.255.60): icmp_req=48, ttl=44, time=49.04 ms.
100 bytes from yandex.ru (5.255.255.60): icmp_req=49, ttl=44, time=41.66 ms.
"Destination unreachable" ICMP packet received from 127.0.0.1 (type = 3, code = 3).
"Destination unreachable" ICMP packet received from 127.0.0.1 (type = 3, code = 3).
100 bytes from yandex.ru (5.255.255.60): icmp_req=50, ttl=44, time=62.21 ms.

--- yandex.ru ping statistics ---
50 packets transmitted, 50 packets received, 0% packet loss,
0 duplicate(s), time 49090.36 ms.
Round-trip min/avg/max = 36.85/54.47/116.90 ms.

Отваливаются, зацикливаются или заикаются онлайн радио.

Прошивка v2.10.C.0.0-0

Edited by WMac
Уточнение

Share this post


Link to post
Share on other sites
  • 0

Аналогично...

sending ICMP ECHO request to ya.ru...
PING ya.ru (87.250.250.242) 56 (84) bytes of data.
84 bytes from ya.ru (87.250.250.242): icmp_req=1, ttl=55, time=4.69 ms.
"Destination unreachable" ICMP packet received from 127.0.0.1 (type = 3, code = 3).
84 bytes from ya.ru (87.250.250.242): icmp_req=2, ttl=55, time=4.39 ms.
84 bytes from ya.ru (87.250.250.242): icmp_req=3, ttl=55, time=4.45 ms.
84 bytes from ya.ru (87.250.250.242): icmp_req=4, ttl=55, time=4.51 ms.
"Destination unreachable" ICMP packet received from 127.0.0.1 (type = 3, code = 3).
"Destination unreachable" ICMP packet received from 127.0.0.1 (type = 3, code = 3).
"Destination unreachable" ICMP packet received from 127.0.0.1 (type = 3, code = 3).
"Destination unreachable" ICMP packet received from 127.0.0.1 (type = 3, code = 3).
"Destination unreachable" ICMP packet received from 127.0.0.1 (type = 3, code = 3).
84 bytes from ya.ru (87.250.250.242): icmp_req=5, ttl=55, time=4.41 ms.
--- ya.ru ping statistics ---
5 packets transmitted, 5 packets received, 0% packet loss,
0 duplicate(s), time 4006.67 ms.
Round-trip min/avg/max = 4.39/4.49/4.69 ms.

2.10.C.0.0-0

Share this post


Link to post
Share on other sites
  • 0

У кого вылезает строчка "Destination unreachable" ICMP packet received from 127.0.0.1 (type = 3, code = 3), проверьте, включен ли компонент IntelliQoS, если да, то отключаем его в http://192.168.1.1/#home.ntce. Можно через консоль:

без выключения ntce (dpi), мы получаем

(config)> tools ping 8.8.8.8 count 100 size 80
sending ICMP ECHO request to 8.8.8.8...
PING 8.8.8.8 (8.8.8.8) 52 (80) bytes of data.
80 bytes from 8.8.8.8: icmp_req=1, ttl=56, time=3.00 ms.
80 bytes from 8.8.8.8: icmp_req=2, ttl=56, time=2.26 ms.
80 bytes from 8.8.8.8: icmp_req=3, ttl=56, time=2.34 ms.
"Destination unreachable" ICMP packet received from 127.0.0.1 (type = 3, code = 3).
"Destination unreachable" ICMP packet received from 127.0.0.1 (type = 3, code = 3).
"Destination unreachable" ICMP packet received from 127.0.0.1 (type = 3, code = 3).
80 bytes from 8.8.8.8: icmp_req=4, ttl=56, time=2.40 ms.
80 bytes from 8.8.8.8: icmp_req=5, ttl=56, time=2.31 ms.
80 bytes from 8.8.8.8: icmp_req=6, ttl=56, time=2.34 ms.
80 bytes from 8.8.8.8: icmp_req=7, ttl=56, time=2.35 ms.
--- 8.8.8.8 ping statistics ---
7 packets transmitted, 7 packets received, 0% packet loss,
0 duplicate(s), time 6206.39 ms.
Round-trip min/avg/max = 2.26/2.42/3.00 ms.
(config)>
 

с выключенным ntce (dpi), мы получаем

(config)> no service ntce
Ntce::Manager: Disabled.

(config)> tools ping 8.8.8.8 count 100 size 80
sending ICMP ECHO request to 8.8.8.8...
PING 8.8.8.8 (8.8.8.8) 52 (80) bytes of data.
80 bytes from 8.8.8.8: icmp_req=1, ttl=56, time=2.56 ms.
80 bytes from 8.8.8.8: icmp_req=2, ttl=56, time=2.33 ms.
80 bytes from 8.8.8.8: icmp_req=3, ttl=56, time=2.38 ms.
80 bytes from 8.8.8.8: icmp_req=4, ttl=56, time=2.74 ms.
80 bytes from 8.8.8.8: icmp_req=5, ttl=56, time=2.24 ms.
80 bytes from 8.8.8.8: icmp_req=6, ttl=56, time=2.35 ms.
80 bytes from 8.8.8.8: icmp_req=7, ttl=56, time=6.12 ms.
80 bytes from 8.8.8.8: icmp_req=8, ttl=56, time=2.30 ms.
80 bytes from 8.8.8.8: icmp_req=9, ttl=56, time=2.35 ms.
80 bytes from 8.8.8.8: icmp_req=10, ttl=56, time=2.43 ms.
80 bytes from 8.8.8.8: icmp_req=11, ttl=56, time=2.40 ms.
80 bytes from 8.8.8.8: icmp_req=12, ttl=56, time=2.28 ms.
80 bytes from 8.8.8.8: icmp_req=13, ttl=56, time=2.54 ms.
80 bytes from 8.8.8.8: icmp_req=14, ttl=56, time=2.42 ms.
80 bytes from 8.8.8.8: icmp_req=15, ttl=56, time=2.36 ms.
--- 8.8.8.8 ping statistics ---
15 packets transmitted, 15 packets received, 0% packet loss,
0 duplicate(s), time 14087.77 ms.
Round-trip min/avg/max = 2.24/2.65/6.12 ms.

p.s.: если не пользуетесь ntce (dpi).

Edited by enpa
  • Upvote 1

Share this post


Link to post
Share on other sites
  • 0
5 минут назад, enpa сказал:

У кого вылезает строчка "Destination unreachable" ICMP packet received from 127.0.0.1 (type = 3, code = 3), проверьте, включен ли компонент IntelliQoS, если да, то отключаем его в http://192.168.1.1/#home.ntce. Можно через консоль:

без выключения ntce (dpi), мы получаем

(config)> tools ping 8.8.8.8 count 100 size 80
sending ICMP ECHO request to 8.8.8.8...
PING 8.8.8.8 (8.8.8.8) 52 (80) bytes of data.
80 bytes from 8.8.8.8: icmp_req=1, ttl=56, time=3.00 ms.
80 bytes from 8.8.8.8: icmp_req=2, ttl=56, time=2.26 ms.
80 bytes from 8.8.8.8: icmp_req=3, ttl=56, time=2.34 ms.
"Destination unreachable" ICMP packet received from 127.0.0.1 (type = 3, code = 3).
"Destination unreachable" ICMP packet received from 127.0.0.1 (type = 3, code = 3).
"Destination unreachable" ICMP packet received from 127.0.0.1 (type = 3, code = 3).
80 bytes from 8.8.8.8: icmp_req=4, ttl=56, time=2.40 ms.
80 bytes from 8.8.8.8: icmp_req=5, ttl=56, time=2.31 ms.
80 bytes from 8.8.8.8: icmp_req=6, ttl=56, time=2.34 ms.
80 bytes from 8.8.8.8: icmp_req=7, ttl=56, time=2.35 ms.
--- 8.8.8.8 ping statistics ---
7 packets transmitted, 7 packets received, 0% packet loss,
0 duplicate(s), time 6206.39 ms.
Round-trip min/avg/max = 2.26/2.42/3.00 ms.
(config)>
 

с выключенным ntce (dpi), мы получаем

(config)> no service ntce
Ntce::Manager: Disabled.

(config)> tools ping 8.8.8.8 count 100 size 80
sending ICMP ECHO request to 8.8.8.8...
PING 8.8.8.8 (8.8.8.8) 52 (80) bytes of data.
80 bytes from 8.8.8.8: icmp_req=1, ttl=56, time=2.56 ms.
80 bytes from 8.8.8.8: icmp_req=2, ttl=56, time=2.33 ms.
80 bytes from 8.8.8.8: icmp_req=3, ttl=56, time=2.38 ms.
80 bytes from 8.8.8.8: icmp_req=4, ttl=56, time=2.74 ms.
80 bytes from 8.8.8.8: icmp_req=5, ttl=56, time=2.24 ms.
80 bytes from 8.8.8.8: icmp_req=6, ttl=56, time=2.35 ms.
80 bytes from 8.8.8.8: icmp_req=7, ttl=56, time=6.12 ms.
80 bytes from 8.8.8.8: icmp_req=8, ttl=56, time=2.30 ms.
80 bytes from 8.8.8.8: icmp_req=9, ttl=56, time=2.35 ms.
80 bytes from 8.8.8.8: icmp_req=10, ttl=56, time=2.43 ms.
80 bytes from 8.8.8.8: icmp_req=11, ttl=56, time=2.40 ms.
80 bytes from 8.8.8.8: icmp_req=12, ttl=56, time=2.28 ms.
80 bytes from 8.8.8.8: icmp_req=13, ttl=56, time=2.54 ms.
80 bytes from 8.8.8.8: icmp_req=14, ttl=56, time=2.42 ms.
80 bytes from 8.8.8.8: icmp_req=15, ttl=56, time=2.36 ms.
--- 8.8.8.8 ping statistics ---
15 packets transmitted, 15 packets received, 0% packet loss,
0 duplicate(s), time 14087.77 ms.
Round-trip min/avg/max = 2.24/2.65/6.12 ms.

 

Спасибо за рецепт, но это не панацея. IntelliQoS - вещь все таки нужная

Share this post


Link to post
Share on other sites
  • 0
2 часа назад, enpa сказал:

но это для тех, кто не пользуется ntce (dpi). 

Берем 211A808, компонент IntelliQoS установлен (с какого релиза не помню) но не используется, интернет PPPoE

Скрытый текст

(config)> tools ping 8.8.8.8 count 100 size 80
sending ICMP ECHO request to 8.8.8.8...
PING 8.8.8.8 (8.8.8.8) 52 (80) bytes of data.
80 bytes from 8.8.8.8: icmp_req=1, ttl=58, time=15.41 ms.
80 bytes from 8.8.8.8: icmp_req=2, ttl=58, time=15.26 ms.
80 bytes from 8.8.8.8: icmp_req=3, ttl=58, time=15.35 ms.
80 bytes from 8.8.8.8: icmp_req=4, ttl=58, time=15.24 ms.
80 bytes from 8.8.8.8: icmp_req=5, ttl=58, time=15.22 ms.
80 bytes from 8.8.8.8: icmp_req=6, ttl=58, time=15.23 ms.
80 bytes from 8.8.8.8: icmp_req=7, ttl=58, time=15.41 ms.
80 bytes from 8.8.8.8: icmp_req=8, ttl=58, time=15.25 ms.
80 bytes from 8.8.8.8: icmp_req=9, ttl=58, time=15.33 ms.
80 bytes from 8.8.8.8: icmp_req=10, ttl=58, time=15.23 ms.
80 bytes from 8.8.8.8: icmp_req=11, ttl=58, time=15.30 ms.
80 bytes from 8.8.8.8: icmp_req=12, ttl=58, time=15.27 ms.
80 bytes from 8.8.8.8: icmp_req=13, ttl=58, time=15.25 ms.
80 bytes from 8.8.8.8: icmp_req=14, ttl=58, time=15.25 ms.
80 bytes from 8.8.8.8: icmp_req=15, ttl=58, time=15.29 ms.
80 bytes from 8.8.8.8: icmp_req=16, ttl=58, time=15.24 ms.
80 bytes from 8.8.8.8: icmp_req=17, ttl=58, time=15.30 ms.
80 bytes from 8.8.8.8: icmp_req=18, ttl=58, time=15.23 ms.
80 bytes from 8.8.8.8: icmp_req=19, ttl=58, time=15.20 ms.
80 bytes from 8.8.8.8: icmp_req=20, ttl=58, time=15.31 ms.
80 bytes from 8.8.8.8: icmp_req=21, ttl=58, time=15.23 ms.
80 bytes from 8.8.8.8: icmp_req=22, ttl=58, time=15.25 ms.
"Destination unreachable" ICMP packet received from 127.0.0.1 (type = 3, code = 3).
80 bytes from 8.8.8.8: icmp_req=23, ttl=58, time=15.22 ms.
80 bytes from 8.8.8.8: icmp_req=24, ttl=58, time=15.25 ms.
80 bytes from 8.8.8.8: icmp_req=25, ttl=58, time=15.26 ms.
80 bytes from 8.8.8.8: icmp_req=26, ttl=58, time=15.21 ms.
80 bytes from 8.8.8.8: icmp_req=27, ttl=58, time=15.32 ms.
80 bytes from 8.8.8.8: icmp_req=28, ttl=58, time=15.27 ms.
80 bytes from 8.8.8.8: icmp_req=29, ttl=58, time=15.29 ms.
80 bytes from 8.8.8.8: icmp_req=30, ttl=58, time=15.22 ms.
80 bytes from 8.8.8.8: icmp_req=31, ttl=58, time=15.18 ms.
"Destination unreachable" ICMP packet received from 127.0.0.1 (type = 3, code = 3).
80 bytes from 8.8.8.8: icmp_req=32, ttl=58, time=15.24 ms.
80 bytes from 8.8.8.8: icmp_req=33, ttl=58, time=15.40 ms.
80 bytes from 8.8.8.8: icmp_req=34, ttl=58, time=15.28 ms.
80 bytes from 8.8.8.8: icmp_req=35, ttl=58, time=15.35 ms.
80 bytes from 8.8.8.8: icmp_req=36, ttl=58, time=15.32 ms.
80 bytes from 8.8.8.8: icmp_req=37, ttl=58, time=15.38 ms.
80 bytes from 8.8.8.8: icmp_req=38, ttl=58, time=15.19 ms.
80 bytes from 8.8.8.8: icmp_req=39, ttl=58, time=15.26 ms.
80 bytes from 8.8.8.8: icmp_req=40, ttl=58, time=15.22 ms.
80 bytes from 8.8.8.8: icmp_req=41, ttl=58, time=15.26 ms.
80 bytes from 8.8.8.8: icmp_req=42, ttl=58, time=15.23 ms.
80 bytes from 8.8.8.8: icmp_req=43, ttl=58, time=15.25 ms.
80 bytes from 8.8.8.8: icmp_req=44, ttl=58, time=15.29 ms.
80 bytes from 8.8.8.8: icmp_req=45, ttl=58, time=15.24 ms.
80 bytes from 8.8.8.8: icmp_req=46, ttl=58, time=15.37 ms.
80 bytes from 8.8.8.8: icmp_req=47, ttl=58, time=15.25 ms.
80 bytes from 8.8.8.8: icmp_req=48, ttl=58, time=15.28 ms.
80 bytes from 8.8.8.8: icmp_req=49, ttl=58, time=15.72 ms.
80 bytes from 8.8.8.8: icmp_req=50, ttl=58, time=15.36 ms.
80 bytes from 8.8.8.8: icmp_req=51, ttl=58, time=15.27 ms.
80 bytes from 8.8.8.8: icmp_req=52, ttl=58, time=15.36 ms.
80 bytes from 8.8.8.8: icmp_req=53, ttl=58, time=15.22 ms.
80 bytes from 8.8.8.8: icmp_req=54, ttl=58, time=15.29 ms.
80 bytes from 8.8.8.8: icmp_req=55, ttl=58, time=15.29 ms.
80 bytes from 8.8.8.8: icmp_req=56, ttl=58, time=15.23 ms.
80 bytes from 8.8.8.8: icmp_req=57, ttl=58, time=15.23 ms.
80 bytes from 8.8.8.8: icmp_req=58, ttl=58, time=15.36 ms.
80 bytes from 8.8.8.8: icmp_req=59, ttl=58, time=15.24 ms.
80 bytes from 8.8.8.8: icmp_req=60, ttl=58, time=15.26 ms.
80 bytes from 8.8.8.8: icmp_req=61, ttl=58, time=15.28 ms.
80 bytes from 8.8.8.8: icmp_req=62, ttl=58, time=15.21 ms.
80 bytes from 8.8.8.8: icmp_req=63, ttl=58, time=15.22 ms.
80 bytes from 8.8.8.8: icmp_req=64, ttl=58, time=15.23 ms.
80 bytes from 8.8.8.8: icmp_req=65, ttl=58, time=15.22 ms.
80 bytes from 8.8.8.8: icmp_req=66, ttl=58, time=15.30 ms.
80 bytes from 8.8.8.8: icmp_req=67, ttl=58, time=15.26 ms.
80 bytes from 8.8.8.8: icmp_req=68, ttl=58, time=15.20 ms.
80 bytes from 8.8.8.8: icmp_req=69, ttl=58, time=15.23 ms.
80 bytes from 8.8.8.8: icmp_req=70, ttl=58, time=15.35 ms.
80 bytes from 8.8.8.8: icmp_req=71, ttl=58, time=15.21 ms.
80 bytes from 8.8.8.8: icmp_req=72, ttl=58, time=15.32 ms.
80 bytes from 8.8.8.8: icmp_req=73, ttl=58, time=15.25 ms.
80 bytes from 8.8.8.8: icmp_req=74, ttl=58, time=15.19 ms.
80 bytes from 8.8.8.8: icmp_req=75, ttl=58, time=15.23 ms.
80 bytes from 8.8.8.8: icmp_req=76, ttl=58, time=15.24 ms.
80 bytes from 8.8.8.8: icmp_req=77, ttl=58, time=15.63 ms.
80 bytes from 8.8.8.8: icmp_req=78, ttl=58, time=15.21 ms.
80 bytes from 8.8.8.8: icmp_req=79, ttl=58, time=15.32 ms.
80 bytes from 8.8.8.8: icmp_req=80, ttl=58, time=15.23 ms.
80 bytes from 8.8.8.8: icmp_req=81, ttl=58, time=15.29 ms.
80 bytes from 8.8.8.8: icmp_req=82, ttl=58, time=15.22 ms.
80 bytes from 8.8.8.8: icmp_req=83, ttl=58, time=15.27 ms.
80 bytes from 8.8.8.8: icmp_req=84, ttl=58, time=15.22 ms.
"Destination unreachable" ICMP packet received from 127.0.0.1 (type = 3, code = 3).
80 bytes from 8.8.8.8: icmp_req=85, ttl=58, time=15.23 ms.
80 bytes from 8.8.8.8: icmp_req=86, ttl=58, time=15.29 ms.
80 bytes from 8.8.8.8: icmp_req=87, ttl=58, time=15.22 ms.
80 bytes from 8.8.8.8: icmp_req=88, ttl=58, time=15.44 ms.
80 bytes from 8.8.8.8: icmp_req=89, ttl=58, time=15.24 ms.
80 bytes from 8.8.8.8: icmp_req=90, ttl=58, time=15.35 ms.
80 bytes from 8.8.8.8: icmp_req=91, ttl=58, time=15.23 ms.
80 bytes from 8.8.8.8: icmp_req=92, ttl=58, time=15.21 ms.
80 bytes from 8.8.8.8: icmp_req=93, ttl=58, time=15.21 ms.
80 bytes from 8.8.8.8: icmp_req=94, ttl=58, time=15.31 ms.
80 bytes from 8.8.8.8: icmp_req=95, ttl=58, time=15.20 ms.
80 bytes from 8.8.8.8: icmp_req=96, ttl=58, time=15.29 ms.
80 bytes from 8.8.8.8: icmp_req=97, ttl=58, time=15.24 ms.
80 bytes from 8.8.8.8: icmp_req=98, ttl=58, time=15.24 ms.
80 bytes from 8.8.8.8: icmp_req=99, ttl=58, time=15.21 ms.
80 bytes from 8.8.8.8: icmp_req=100, ttl=58, time=15.32 ms.
--- 8.8.8.8 ping statistics ---
100 packets transmitted, 100 packets received, 0% packet loss,
0 duplicate(s), time 99083.41 ms.
Round-trip min/avg/max = 15.18/15.27/15.72 ms.
(config)>

На всякий случай

(config)> no service ntce
Ntce::Manager: Disabled.
(config)>

Скрытый текст

(config)> tools ping 8.8.8.8 count 100 size 80
sending ICMP ECHO request to 8.8.8.8...
PING 8.8.8.8 (8.8.8.8) 52 (80) bytes of data.
80 bytes from 8.8.8.8: icmp_req=1, ttl=58, time=15.35 ms.
80 bytes from 8.8.8.8: icmp_req=2, ttl=58, time=15.20 ms.
80 bytes from 8.8.8.8: icmp_req=3, ttl=58, time=15.28 ms.
80 bytes from 8.8.8.8: icmp_req=4, ttl=58, time=15.26 ms.
80 bytes from 8.8.8.8: icmp_req=5, ttl=58, time=15.32 ms.
80 bytes from 8.8.8.8: icmp_req=6, ttl=58, time=15.23 ms.
80 bytes from 8.8.8.8: icmp_req=7, ttl=58, time=15.30 ms.
80 bytes from 8.8.8.8: icmp_req=8, ttl=58, time=15.26 ms.
80 bytes from 8.8.8.8: icmp_req=9, ttl=58, time=15.26 ms.
80 bytes from 8.8.8.8: icmp_req=10, ttl=58, time=15.26 ms.
80 bytes from 8.8.8.8: icmp_req=11, ttl=58, time=15.21 ms.
80 bytes from 8.8.8.8: icmp_req=12, ttl=58, time=15.23 ms.
80 bytes from 8.8.8.8: icmp_req=13, ttl=58, time=15.23 ms.
80 bytes from 8.8.8.8: icmp_req=14, ttl=58, time=15.26 ms.
80 bytes from 8.8.8.8: icmp_req=15, ttl=58, time=15.52 ms.
80 bytes from 8.8.8.8: icmp_req=16, ttl=58, time=15.24 ms.
80 bytes from 8.8.8.8: icmp_req=17, ttl=58, time=15.23 ms.
80 bytes from 8.8.8.8: icmp_req=18, ttl=58, time=15.21 ms.
80 bytes from 8.8.8.8: icmp_req=19, ttl=58, time=15.24 ms.
80 bytes from 8.8.8.8: icmp_req=20, ttl=58, time=15.23 ms.
80 bytes from 8.8.8.8: icmp_req=21, ttl=58, time=15.22 ms.
80 bytes from 8.8.8.8: icmp_req=22, ttl=58, time=15.22 ms.
80 bytes from 8.8.8.8: icmp_req=23, ttl=58, time=15.23 ms.
80 bytes from 8.8.8.8: icmp_req=24, ttl=58, time=15.91 ms.
80 bytes from 8.8.8.8: icmp_req=25, ttl=58, time=15.68 ms.
80 bytes from 8.8.8.8: icmp_req=26, ttl=58, time=15.20 ms.
80 bytes from 8.8.8.8: icmp_req=27, ttl=58, time=15.23 ms.
80 bytes from 8.8.8.8: icmp_req=28, ttl=58, time=15.22 ms.
80 bytes from 8.8.8.8: icmp_req=29, ttl=58, time=15.21 ms.
80 bytes from 8.8.8.8: icmp_req=30, ttl=58, time=15.22 ms.
80 bytes from 8.8.8.8: icmp_req=31, ttl=58, time=15.22 ms.
80 bytes from 8.8.8.8: icmp_req=32, ttl=58, time=15.19 ms.
80 bytes from 8.8.8.8: icmp_req=33, ttl=58, time=15.20 ms.
80 bytes from 8.8.8.8: icmp_req=34, ttl=58, time=15.22 ms.
80 bytes from 8.8.8.8: icmp_req=35, ttl=58, time=15.20 ms.
80 bytes from 8.8.8.8: icmp_req=36, ttl=58, time=15.22 ms.
80 bytes from 8.8.8.8: icmp_req=37, ttl=58, time=15.50 ms.
80 bytes from 8.8.8.8: icmp_req=38, ttl=58, time=15.67 ms.
80 bytes from 8.8.8.8: icmp_req=39, ttl=58, time=15.21 ms.
80 bytes from 8.8.8.8: icmp_req=40, ttl=58, time=15.24 ms.
80 bytes from 8.8.8.8: icmp_req=41, ttl=58, time=15.21 ms.
80 bytes from 8.8.8.8: icmp_req=42, ttl=58, time=15.20 ms.
80 bytes from 8.8.8.8: icmp_req=43, ttl=58, time=15.24 ms.
"Destination unreachable" ICMP packet received from 127.0.0.1 (type = 3, code = 3).
"Destination unreachable" ICMP packet received from 127.0.0.1 (type = 3, code = 3).
80 bytes from 8.8.8.8: icmp_req=44, ttl=58, time=15.23 ms.
80 bytes from 8.8.8.8: icmp_req=45, ttl=58, time=15.22 ms.
80 bytes from 8.8.8.8: icmp_req=46, ttl=58, time=15.19 ms.
80 bytes from 8.8.8.8: icmp_req=47, ttl=58, time=15.26 ms.
80 bytes from 8.8.8.8: icmp_req=48, ttl=58, time=15.22 ms.
80 bytes from 8.8.8.8: icmp_req=49, ttl=58, time=15.26 ms.
80 bytes from 8.8.8.8: icmp_req=50, ttl=58, time=15.25 ms.
80 bytes from 8.8.8.8: icmp_req=51, ttl=58, time=15.25 ms.
80 bytes from 8.8.8.8: icmp_req=52, ttl=58, time=15.21 ms.
80 bytes from 8.8.8.8: icmp_req=53, ttl=58, time=15.22 ms.
80 bytes from 8.8.8.8: icmp_req=54, ttl=58, time=15.28 ms.
80 bytes from 8.8.8.8: icmp_req=55, ttl=58, time=15.23 ms.
80 bytes from 8.8.8.8: icmp_req=56, ttl=58, time=15.21 ms.
80 bytes from 8.8.8.8: icmp_req=57, ttl=58, time=15.31 ms.
80 bytes from 8.8.8.8: icmp_req=58, ttl=58, time=15.22 ms.
80 bytes from 8.8.8.8: icmp_req=59, ttl=58, time=15.25 ms.
80 bytes from 8.8.8.8: icmp_req=60, ttl=58, time=15.20 ms.
80 bytes from 8.8.8.8: icmp_req=61, ttl=58, time=15.25 ms.
80 bytes from 8.8.8.8: icmp_req=62, ttl=58, time=15.30 ms.
80 bytes from 8.8.8.8: icmp_req=63, ttl=58, time=15.19 ms.
80 bytes from 8.8.8.8: icmp_req=64, ttl=58, time=15.24 ms.
80 bytes from 8.8.8.8: icmp_req=65, ttl=58, time=15.25 ms.
80 bytes from 8.8.8.8: icmp_req=66, ttl=58, time=15.24 ms.
80 bytes from 8.8.8.8: icmp_req=67, ttl=58, time=15.39 ms.
80 bytes from 8.8.8.8: icmp_req=68, ttl=58, time=15.30 ms.
80 bytes from 8.8.8.8: icmp_req=69, ttl=58, time=15.22 ms.
80 bytes from 8.8.8.8: icmp_req=70, ttl=58, time=15.22 ms.
80 bytes from 8.8.8.8: icmp_req=71, ttl=58, time=15.25 ms.
80 bytes from 8.8.8.8: icmp_req=72, ttl=58, time=15.23 ms.
80 bytes from 8.8.8.8: icmp_req=73, ttl=58, time=15.25 ms.
80 bytes from 8.8.8.8: icmp_req=74, ttl=58, time=15.42 ms.
80 bytes from 8.8.8.8: icmp_req=75, ttl=58, time=15.21 ms.
80 bytes from 8.8.8.8: icmp_req=76, ttl=58, time=15.20 ms.
80 bytes from 8.8.8.8: icmp_req=77, ttl=58, time=15.24 ms.
80 bytes from 8.8.8.8: icmp_req=78, ttl=58, time=15.26 ms.
80 bytes from 8.8.8.8: icmp_req=79, ttl=58, time=15.31 ms.
80 bytes from 8.8.8.8: icmp_req=80, ttl=58, time=15.28 ms.
80 bytes from 8.8.8.8: icmp_req=81, ttl=58, time=15.23 ms.
80 bytes from 8.8.8.8: icmp_req=82, ttl=58, time=15.25 ms.
80 bytes from 8.8.8.8: icmp_req=83, ttl=58, time=15.26 ms.
80 bytes from 8.8.8.8: icmp_req=84, ttl=58, time=15.27 ms.
80 bytes from 8.8.8.8: icmp_req=85, ttl=58, time=15.23 ms.
80 bytes from 8.8.8.8: icmp_req=86, ttl=58, time=15.22 ms.
80 bytes from 8.8.8.8: icmp_req=87, ttl=58, time=15.23 ms.
80 bytes from 8.8.8.8: icmp_req=88, ttl=58, time=15.27 ms.
80 bytes from 8.8.8.8: icmp_req=89, ttl=58, time=15.24 ms.
80 bytes from 8.8.8.8: icmp_req=90, ttl=58, time=15.25 ms.
80 bytes from 8.8.8.8: icmp_req=91, ttl=58, time=15.23 ms.
80 bytes from 8.8.8.8: icmp_req=92, ttl=58, time=15.24 ms.
80 bytes from 8.8.8.8: icmp_req=93, ttl=58, time=15.28 ms.
80 bytes from 8.8.8.8: icmp_req=94, ttl=58, time=15.25 ms.
80 bytes from 8.8.8.8: icmp_req=95, ttl=58, time=15.26 ms.
80 bytes from 8.8.8.8: icmp_req=96, ttl=58, time=15.29 ms.
80 bytes from 8.8.8.8: icmp_req=97, ttl=58, time=15.21 ms.
80 bytes from 8.8.8.8: icmp_req=98, ttl=58, time=15.23 ms.
80 bytes from 8.8.8.8: icmp_req=99, ttl=58, time=15.24 ms.
"Destination unreachable" ICMP packet received from 127.0.0.1 (type = 3, code = 3).
"Destination unreachable" ICMP packet received from 127.0.0.1 (type = 3, code = 3).
80 bytes from 8.8.8.8: icmp_req=100, ttl=58, time=15.22 ms.
--- 8.8.8.8 ping statistics ---
100 packets transmitted, 100 packets received, 0% packet loss,
0 duplicate(s), time 99084.63 ms.
Round-trip min/avg/max = 15.19/15.26/15.91 ms.
(config)>

Обращаю внимание на следующие :

100 packets transmitted, 100 packets received, 0% packet loss,

Edited by vasek00
  • Thanks 1

Share this post


Link to post
Share on other sites
  • 0

Исправлено в версии 2.12.A.4.0-5. Пинг реагировал на нерелевантные ICMP-пакеты, что могло сказываться, в том числе, на работе функции ping-check.

  • Thanks 1
  • Upvote 2

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now


  • Recently Browsing   0 members

    No registered users viewing this page.

×