Jump to content
Как правильно добавить self-test и прочую отладку в тему
Где взять тестовые сборки
Официальное хранилище ПО в виде файлов
  • 0

Потеря соединения c медиасервером при влюченном igmp-proxy

Александр Рыжов

Asked by Александр Рыжов,

 Share

Question

Александр Рыжов Honored Flooder

Александр Рыжов

Posted
Posted (edited)

У меня после перезагрузки Ultra II (а перегружается она до-о-олго) плееры WD TV Live сообщают об отсутствии сети. Передёргивание сетевого кабеля плеера решает проблему.

Возможно, дело во внешнем свитче Ultra II: свитч остаётся включенным во время перезагрузки роутера, а клиенты за это время не дожидаются ответа от DHCP-службы кинетика.

Готов предоставить информацию для диагностики проблемы, если это будет необходимо.

Edited by Guest

7 answers to this question

Recommended Posts

  • 0
ndm Honored Flooder

ndm

Posted
Posted

Порты свича выключаются в загрузчике, auto-negotiation тоже перестартует. есть некоторая задержка между моментом поднятия линка и началом ответа DHCP-сервера, может маленький таймаут у плеееров. Можно ли узнать, на что конкретно жалуется плеер, в нем есть диагностика?

  • 0
McMCC Honored Flooder

McMCC

Posted
Posted

Возможно, дело во внешнем свитче Ultra II: свитч остаётся включенным во время перезагрузки роутера, а клиенты за это время не дожидаются ответа от DHCP-службы кинетика.

Вообще-то обыденная штатная ситуация, не касающаяся конкретно Ultra или свитчей, довольно часто бывает, что отваливается линк и не приходят ответы на DHCP запросы, поэтому на всех нормальных устройствах DHCP клиенты посылают запросы в сеть с некой периодичностью, пока не получат ответ. Тут скорее всего надо обращаться к производителю медиаплеера, почему он не учел эту ситуацию, это в принципе не нормально...

  • 0
Александр Рыжов Honored Flooder

Александр Рыжов

Posted
  • Author
Posted
Можно ли узнать, на что конкретно жалуется плеер, в нем есть диагностика?
Не могу воспроизвести: после трёх перезагрузок на прошивке ku_rd_nightly_2.06.A.4.0-4-75-1425621.bin проблемы не наблюдаю. Если повторится, то попытаюсь приложить больше информации.
  • 0
Александр Рыжов Honored Flooder

Александр Рыжов

Posted
  • Author
Posted (edited)

Что это за сообщения в логе и может ли это быть связано с тем, что сетевые плееры отваливаются от медиасервера на NAS'е строго раз в полчаса?

I [Oct 24 12:00:24] nimproxy: add mfc entry for 239.2.0.252.
I [Oct 24 12:00:24] nimproxy: joined group 239.2.0.252 succesfully.
I [Oct 24 12:00:24] nimproxy: add client 10.9.69.102 to group 239.2.0.252.
I [Oct 24 12:00:25] nimproxy: add client 10.9.69.105 to group 239.2.0.252.
I [Oct 24 12:00:26] nimproxy: add client 10.9.69.109 to group 239.2.0.252.
…
I [Oct 24 12:02:24] nimproxy: mfc entry:
                   239.2.0.252:0x00000002:joined:0.0.0.0:312978 expired.
I [Oct 24 12:02:24] nimproxy: leaved group 239.2.0.252 succesfully.
…
I [Oct 24 12:03:07] nimproxy: add mfc entry for 239.2.0.252.
I [Oct 24 12:03:07] nimproxy: joined group 239.2.0.252 succesfully.
I [Oct 24 12:03:07] nimproxy: add client 10.9.69.109 to group 239.2.0.252.
I [Oct 24 12:03:08] nimproxy: add client 10.9.69.105 to group 239.2.0.252.
I [Oct 24 12:03:20] nimproxy: add client 10.9.69.102 to group 239.2.0.252.
I [Oct 24 12:05:42] nimproxy: mfc entry:
                   239.2.0.252:0x00000002:joined:0.0.0.0:313175 expired.
I [Oct 24 12:05:42] nimproxy: leaved group 239.2.0.252 succesfully.
I [Oct 24 12:06:06] nimproxy: add mfc entry for 239.2.0.252.
I [Oct 24 12:06:06] nimproxy: joined group 239.2.0.252 succesfully.
I [Oct 24 12:06:06] nimproxy: add client 10.9.69.105 to group 239.2.0.252.
I [Oct 24 12:06:38] nimproxy: add client 10.9.69.102 to group 239.2.0.252.
I [Oct 24 12:06:39] nimproxy: add client 10.9.69.109 to group 239.2.0.252.
I [Oct 24 12:08:55] nimproxy: mfc entry:
                   239.2.0.252:0x00000002:joined:0.0.0.0:313368 expired.
I [Oct 24 12:08:55] nimproxy: leaved group 239.2.0.252 succesfully.
I [Oct 24 12:09:56] nimproxy: add mfc entry for 239.2.0.252.
I [Oct 24 12:09:56] nimproxy: joined group 239.2.0.252 succesfully.
I [Oct 24 12:09:56] nimproxy: add client 10.9.69.102 to group 239.2.0.252.
I [Oct 24 12:09:56] nimproxy: add client 10.9.69.105 to group 239.2.0.252.
I [Oct 24 12:09:57] nimproxy: add client 10.9.69.109 to group 239.2.0.252.
I [Oct 24 12:13:15] nimproxy: mfc entry:
                   239.2.0.252:0x00000002:joined:0.0.0.0:313628 expired.
I [Oct 24 12:13:15] nimproxy: leaved group 239.2.0.252 succesfully.
I [Oct 24 12:14:15] nimproxy: add mfc entry for 239.2.0.252.
I [Oct 24 12:14:15] nimproxy: joined group 239.2.0.252 succesfully.
I [Oct 24 12:14:15] nimproxy: add client 10.9.69.105 to group 239.2.0.252.
I [Oct 24 12:15:16] nimproxy: add client 10.9.69.109 to group 239.2.0.252.
I [Oct 24 12:15:16] nimproxy: add client 10.9.69.102 to group 239.2.0.252.
I [Oct 24 12:17:45] nimproxy: mfc entry:
                   239.2.0.252:0x00000002:joined:0.0.0.0:313898 expired.
I [Oct 24 12:17:45] nimproxy: leaved group 239.2.0.252 succesfully.
…
I [Oct 24 12:19:28] nimproxy: add mfc entry for 239.2.0.252.
I [Oct 24 12:19:28] nimproxy: joined group 239.2.0.252 succesfully.
I [Oct 24 12:19:28] nimproxy: add client 10.9.69.105 to group 239.2.0.252.
I [Oct 24 12:19:28] nimproxy: add client 10.9.69.109 to group 239.2.0.252.
I [Oct 24 12:19:39] nimproxy: add client 10.9.69.102 to group 239.2.0.252.
I [Oct 24 12:24:05] nimproxy: mfc entry:
                   239.2.0.252:0x00000002:joined:0.0.0.0:314278 expired.
I [Oct 24 12:24:05] nimproxy: leaved group 239.2.0.252 succesfully.
I [Oct 24 12:25:14] nimproxy: add mfc entry for 239.2.0.252.
I [Oct 24 12:25:14] nimproxy: joined group 239.2.0.252 succesfully.
I [Oct 24 12:25:14] nimproxy: add client 10.9.69.109 to group 239.2.0.252.
I [Oct 24 12:25:15] nimproxy: add client 10.9.69.105 to group 239.2.0.252.
I [Oct 24 12:25:55] nimproxy: add client 10.9.69.102 to group 239.2.0.252.
…
I [Oct 24 12:31:25] nimproxy: mfc entry:
                   239.2.0.252:0x00000002:joined:0.0.0.0:314718 expired.
I [Oct 24 12:31:25] nimproxy: leaved group 239.2.0.252 succesfully.
I [Oct 24 12:32:25] nimproxy: add mfc entry for 239.2.0.252.
I [Oct 24 12:32:25] nimproxy: joined group 239.2.0.252 succesfully.
I [Oct 24 12:32:25] nimproxy: add client 10.9.69.109 to group 239.2.0.252.
I [Oct 24 12:32:26] nimproxy: add client 10.9.69.105 to group 239.2.0.252.
I [Oct 24 12:32:26] nimproxy: add client 10.9.69.102 to group 239.2.0.252.
…
I [Oct 24 12:33:35] nimproxy: mfc entry:
                   239.2.0.252:0x00000002:joined:0.0.0.0:314848 expired.
I [Oct 24 12:33:35] nimproxy: leaved group 239.2.0.252 succesfully.
…
I [Oct 24 12:33:40] nimproxy: add mfc entry for 239.2.0.252.
I [Oct 24 12:33:40] nimproxy: joined group 239.2.0.252 succesfully.
I [Oct 24 12:33:40] nimproxy: add client 10.9.69.102 to group 239.2.0.252.
I [Oct 24 12:33:42] nimproxy: add client 10.9.69.105 to group 239.2.0.252.
I [Oct 24 12:34:35] nimproxy: mfc entry:
                   239.2.0.252:0x00000002:joined:0.0.0.0:314908 expired.
I [Oct 24 12:34:35] nimproxy: leaved group 239.2.0.252 succesfully.
I [Oct 24 12:35:35] nimproxy: add mfc entry for 239.2.0.252.
I [Oct 24 12:35:35] nimproxy: joined group 239.2.0.252 succesfully.
I [Oct 24 12:35:35] nimproxy: add client 10.9.69.105 to group 239.2.0.252.
I [Oct 24 12:36:36] nimproxy: add client 10.9.69.109 to group 239.2.0.252.
I [Oct 24 12:36:39] nimproxy: add client 10.9.69.102 to group 239.2.0.252.
…
I [Oct 24 12:40:05] nimproxy: mfc entry:
                   239.2.0.252:0x00000002:joined:0.0.0.0:315238 expired.
I [Oct 24 12:40:05] nimproxy: leaved group 239.2.0.252 succesfully.
I [Oct 24 12:40:54] nimproxy: add mfc entry for 239.2.0.252.
I [Oct 24 12:40:54] nimproxy: joined group 239.2.0.252 succesfully.
I [Oct 24 12:40:54] nimproxy: add client 10.9.69.102 to group 239.2.0.252.
I [Oct 24 12:40:56] nimproxy: add client 10.9.69.109 to group 239.2.0.252.
I [Oct 24 12:41:56] nimproxy: add client 10.9.69.105 to group 239.2.0.252.
I [Oct 24 12:45:45] nimproxy: mfc entry:
                   239.2.0.252:0x00000002:joined:0.0.0.0:315578 expired.
I [Oct 24 12:45:45] nimproxy: leaved group 239.2.0.252 succesfully.
I [Oct 24 12:46:54] nimproxy: add mfc entry for 239.2.0.252.
I [Oct 24 12:46:54] nimproxy: joined group 239.2.0.252 succesfully.
I [Oct 24 12:46:54] nimproxy: add client 10.9.69.102 to group 239.2.0.252.
I [Oct 24 12:47:44] nimproxy: add client 10.9.69.105 to group 239.2.0.252.
I [Oct 24 12:48:55] nimproxy: mfc entry:
                   239.2.0.252:0x00000002:joined:0.0.0.0:315768 expired.
I [Oct 24 12:48:55] nimproxy: leaved group 239.2.0.252 succesfully.
I [Oct 24 12:49:45] nimproxy: add mfc entry for 239.2.0.252.
I [Oct 24 12:49:45] nimproxy: joined group 239.2.0.252 succesfully.
I [Oct 24 12:49:45] nimproxy: add client 10.9.69.105 to group 239.2.0.252.
I [Oct 24 12:49:46] nimproxy: add client 10.9.69.109 to group 239.2.0.252.
I [Oct 24 12:50:02] nimproxy: add client 10.9.69.102 to group 239.2.0.252.
I [Oct 24 12:52:15] nimproxy: mfc entry:
                   239.2.0.252:0x00000002:joined:0.0.0.0:315968 expired.
I [Oct 24 12:52:15] nimproxy: leaved group 239.2.0.252 succesfully.
I [Oct 24 12:53:06] nimproxy: add mfc entry for 239.2.0.252.
I [Oct 24 12:53:06] nimproxy: joined group 239.2.0.252 succesfully.
I [Oct 24 12:53:06] nimproxy: add client 10.9.69.102 to group 239.2.0.252.
I [Oct 24 12:53:06] nimproxy: add client 10.9.69.105 to group 239.2.0.252.
I [Oct 24 12:54:17] nimproxy: add client 10.9.69.109 to group 239.2.0.252.
I [Oct 24 12:56:35] nimproxy: mfc entry:
                   239.2.0.252:0x00000002:joined:0.0.0.0:316228 expired.
I [Oct 24 12:56:35] nimproxy: leaved group 239.2.0.252 succesfully.
I [Oct 24 12:57:36] nimproxy: add mfc entry for 239.2.0.252.
I [Oct 24 12:57:36] nimproxy: joined group 239.2.0.252 succesfully.
I [Oct 24 12:57:36] nimproxy: add client 10.9.69.102 to group 239.2.0.252.
I [Oct 24 12:57:46] nimproxy: add client 10.9.69.105 to group 239.2.0.252.
I [Oct 24 12:58:43] nimproxy: add client 10.9.69.109 to group 239.2.0.252.

PS successfully пишется с двумя «s».

Edited by Guest
  • 0
ndm Honored Flooder

ndm

Posted
Posted

Сообщения подправим. Перестают ли отваливаться плееры, если сделать

(config)> no service igmp-proxy

  • 0
Александр Рыжов Honored Flooder

Александр Рыжов

Posted
  • Author
Posted
Сообщения подправим. Перестают ли отваливаться плееры, если сделать

(config)> no service igmp-proxy

Проверил, перестали отваливаться, спасибо! Мне кажется, так быть не должно, по крайней мере, с включенным igmp-proxy на Asus RT-N66U таких отвалов не было.

Кстати, выполнение команды сопровождалось сообщениями:[spoiler=]

[i] Oct 24 17:33:16 nimproxy: deinit handler called. 
[i] Oct 24 17:33:16 nimproxy: leaved group 239.255.255.250 succesfully. 
[i] Oct 24 17:33:16 nimproxy: leaved group 239.2.0.252 succesfully. 
[i] Oct 24 17:33:16 nimproxy: leaved group 239.2.0.251 succesfully. 
[i] Oct 24 17:33:16 nimproxy: NDM IGMP/Multicast proxy stopped (exit status: 0). 
[i] Oct 24 17:33:16 ndm: kernel: igmpsn: unmap obsoleted 01:00:5e:00:00:fc @ 224.0.0.252 for host 00:22:5f:3d:67:ec @ 10.9.69.103
[i] Oct 24 17:33:16 ndm: kernel: igmpsn: unmap obsoleted 01:00:5e:02:00:fc @ 239.2.0.252 for host 50:32:75:63:0f:72 @ 10.9.69.105
[i] Oct 24 17:33:16 ndm: kernel: igmpsn: unmap obsoleted 01:00:5e:02:00:fc @ 239.2.0.252 for host d8:50:e6:69:6b:b8 @ 10.9.69.108
[i] Oct 24 17:33:16 ndm: kernel: igmpsn: unmap obsoleted 01:00:5e:00:00:01 @ 0.0.0.1 for host d8:50:e6:69:6b:b8 @ 10.9.69.108
[i] Oct 24 17:33:16 ndm: kernel: igmpsn: unmap obsoleted 01:00:5e:02:00:fc @ 239.2.0.252 for host e4:40:e2:d9:e4:cc @ 10.9.69.109
[i] Oct 24 17:33:16 ndm: kernel: igmpsn: unmap obsoleted 01:00:5e:02:00:fc @ 239.2.0.252 for host e4:40:e2:d9:e6:ee @ 10.9.69.102
[i] Oct 24 17:33:16 ndm: kernel: igmpsn: unmap obsoleted 01:00:5e:00:00:01 @ 0.0.0.1 for host 50:32:75:63:0f:72 @ 10.9.69.105
[i] Oct 24 17:33:16 ndm: kernel: igmpsn: unmap obsoleted 01:00:5e:00:00:fc @ 224.0.0.252 for host 94:de:80:b0:2b:07 @ 10.9.69.2
[i] Oct 24 17:33:16 ndm: kernel: igmpsn: unmap obsoleted 01:00:5e:00:00:01 @ 0.0.0.1 for host 00:90:a9:da:12:81 @ 10.9.69.3
[i] Oct 24 17:33:16 ndm: kernel: igmpsn: unmap obsoleted 01:00:5e:00:00:fd @ 224.0.0.253 for host 94:de:80:b0:2b:07 @ 10.9.69.2
[i] Oct 24 17:33:16 ndm: kernel: igmpsn: unmap obsoleted 01:00:5e:00:00:fd @ 224.0.0.253 for host 00:22:5f:3d:67:ec @ 10.9.69.103
[i] Oct 24 17:33:16 ndm: kernel: igmpsn: unmap obsoleted 01:00:5e:00:00:02 @ 0.0.0.2 for host e4:40:e2:d9:e4:cc @ 10.9.69.109
[i] Oct 24 17:33:16 ndm: kernel: igmpsn: unmap obsoleted 01:00:5e:00:00:01 @ 0.0.0.1 for host e4:40:e2:d9:e4:cc @ 10.9.69.109
[i] Oct 24 17:33:16 ndm: kernel: igmpsn: unmap obsoleted 01:00:5e:00:00:02 @ 0.0.0.2 for host 00:22:5f:3d:67:ec @ 10.9.69.103
[i] Oct 24 17:33:16 ndm: kernel: igmpsn: unmap obsoleted 01:00:5e:00:00:02 @ 0.0.0.2 for host 94:de:80:b0:2b:07 @ 10.9.69.2
[i] Oct 24 17:33:16 ndm: kernel: igmpsn: unmap obsoleted 01:00:5e:00:00:01 @ 0.0.0.1 for host e4:40:e2:d9:e6:ee @ 10.9.69.102
[i] Oct 24 17:33:16 ndm: kernel: igmpsn: unmap obsoleted 01:00:5e:00:00:03 @ 0.0.0.3 for host 00:22:5f:3d:67:ec @ 10.9.69.103
[i] Oct 24 17:33:16 ndm: kernel: igmpsn: unmap obsoleted 01:00:5e:00:00:01 @ 0.0.0.1 for host 00:22:5f:3d:67:ec @ 10.9.69.103
[i] Oct 24 17:33:16 ndm: kernel: igmpsn: unmap obsoleted 01:00:5e:00:00:03 @ 0.0.0.3 for host 94:de:80:b0:2b:07 @ 10.9.69.2
[i] Oct 24 17:33:16 ndm: kernel: igmpsn: unmap obsoleted 01:00:5e:00:00:01 @ 0.0.0.1 for host 94:de:80:b0:2b:07 @ 10.9.69.2
[i] Oct 24 17:33:16 ndm: kernel: igmpsn: unmap obsoleted 01:00:5e:00:00:02 @ 0.0.0.2 for host 00:90:a9:93:d7:4e @ 10.9.69.107
[i] Oct 24 17:33:16 ndm: kernel: igmpsn: unmap obsoleted 01:00:5e:00:00:02 @ 0.0.0.2 for host 00:90:a9:76:e4:31 @ 10.9.69.101
[i] Oct 24 17:33:16 ndm: kernel: igmpsn: unmap obsoleted 01:00:5e:00:00:01 @ 0.0.0.1 for host 00:90:a9:76:e4:31 @ 10.9.69.101
[i] Oct 24 17:33:16 ndm: kernel: igmpsn: unmap obsoleted 01:00:5e:40:98:8f @ 239.192.152.143 for host 00:90:a9:bf:09:e6 @ 169.254.9.194
[i] Oct 24 17:33:16 ndm: kernel: igmpsn: unmap obsoleted 01:00:5e:00:00:03 @ 0.0.0.3 for host 00:90:a9:bf:09:e6 @ 169.254.9.194
[i] Oct 24 17:33:16 ndm: kernel: igmpsn: unmap obsoleted 01:00:5e:7f:ff:fa @ 239.255.255.250 for host 00:90:a9:da:12:81 @ 0.0.0.0
[i] Oct 24 17:33:17 ndm: kernel: igmpsn: unmap obsoleted 01:00:5e:00:00:01 @ 0.0.0.1 for host 00:90:a9:93:d7:4e @ 10.9.69.107
[i] Oct 24 17:33:17 ndm: kernel: igmpsn: unmap obsoleted 01:00:5e:00:00:fb @ 224.0.0.251 for host 00:90:a9:da:12:81 @ 0.0.0.0
[i] Oct 24 17:33:17 ndm: kernel: igmpsn v4.0.2 unloaded
[i] Oct 24 17:33:17 ndm: Igmp::Proxy: IGMP proxy disabled.

IGMP snooping на Ethernet-портах теперь отключен? Это отнюдь не праздное любопытство:

30d03e4f400a.png

В одном из портов у меня включена VoIP приставка Linksys SPA3000 с десятимегабитным интерфейсом. Без снупинга её порт может быть зафлужен мультикаст трафиком.

  • 0
ndm Honored Flooder

ndm

Posted
Posted

Да, так снупинг выключен, но надо было понять, что причина именно в nimproxy. Так быть не должно. Попробуем исправить до релиза.

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Answer this question...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
 Share
Go to question listing

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...

Important Information

This site uses cookies. By clicking "I accept" or continuing to browse the site, you authorize their use in accordance with the Privacy Policy.

  I accept