Восстановление подключения к WB-MGE

27

Вновь пытаюсь вот как пример:

<отключение>
Oct 07 11:38:08 wirenboard-AYK5U4TB wb-mqtt-serial[3576532]: WARNING: [modbus] failed to read 14 input(s) @ 270 of device modbus:170: Serial protocol error: request timed out
Oct 07 11:38:08 wirenboard-AYK5U4TB wb-mqtt-serial[3576532]: WARNING: [serial client] Reading events failed: Serial protocol error: request timed out
Oct 07 11:38:09 wirenboard-AYK5U4TB wb-mqtt-serial[3576532]: WARNING: [modbus] failed to read 12 coil(s) @ 0 of device modbus:170: Serial protocol error: request timed out
Oct 07 11:38:09 wirenboard-AYK5U4TB wb-mqtt-serial[3576532]: WARNING: [serial client] Reading events failed: Serial protocol error: request timed out
Oct 07 11:38:10 wirenboard-AYK5U4TB wb-mqtt-serial[3576532]: WARNING: [modbus] failed to read 2 coil(s) @ 5001 of device modbus:170: Serial protocol error: request timed out
Oct 07 11:38:10 wirenboard-AYK5U4TB wb-mqtt-serial[3576532]: WARNING: [serial client] Reading events failed: Serial protocol error: request timed out
Oct 07 11:38:11 wirenboard-AYK5U4TB wb-mqtt-serial[3576532]: WARNING: [modbus] failed to read 7 coil(s) @ 5100 of device modbus:170: Serial protocol error: request timed out
Oct 07 11:38:11 wirenboard-AYK5U4TB wb-mqtt-serial[3576532]: WARNING: [serial device] device modbus:170 is disconnected
Oct 07 11:38:11 wirenboard-AYK5U4TB wb-mqtt-serial[3576532]: WARNING: [serial client] Reading events failed: Serial protocol error: request timed out
Oct 07 11:38:13 wirenboard-AYK5U4TB wb-mqtt-serial[3576532]: WARNING: [serial client] Reading events failed: Serial protocol error: request timed out
Oct 07 11:38:13 wirenboard-AYK5U4TB wb-mqtt-serial[3576532]: WARNING: [modbus] failed to read 1 holding(s) @ 97 of device modbus:113: Serial protocol error: request timed out
Oct 07 11:38:14 wirenboard-AYK5U4TB wb-mqtt-serial[3576532]: WARNING: [serial client] Reading events failed: Serial protocol error: request timed out
Oct 07 11:38:14 wirenboard-AYK5U4TB wb-mqtt-serial[3576532]: WARNING: [serial client] Reading events failed: Serial protocol error: request timed out
Oct 07 11:38:15 wirenboard-AYK5U4TB wb-mqtt-serial[3576532]: WARNING: [modbus] failed to read 1 holding(s) @ 98 of device modbus:113: Serial protocol error: request timed out
Oct 07 11:38:15 wirenboard-AYK5U4TB wb-mqtt-serial[3576532]: WARNING: [serial device] device modbus:113 is disconnected
Oct 07 11:38:18 wirenboard-AYK5U4TB wb-mqtt-serial[3576532]: WARNING: <10.0.0.71:502>: closed due to repetitive errors
Oct 07 11:38:23 wirenboard-AYK5U4TB wb-mqtt-serial[3576532]: ERROR: [serial client] Serial protocol error: <10.0.0.71:502> connect error: timeout
<Первый вывод в лог, через 5 минут>
Oct 07 11:43:28 wirenboard-AYK5U4TB wb-mqtt-serial[3576532]: ERROR: [serial client] Serial protocol error: <10.0.0.71:502> connect error: No route to host (113)
Oct 07 11:45:34 wirenboard-AYK5U4TB wb-mqtt-serial[3576532]: WARNING: [modbus] failed to read 6 input(s) @ 14360 of device modbus:125: Serial protocol error: request timed out
Oct 07 11:48:31 wirenboard-AYK5U4TB wb-mqtt-serial[3576532]: ERROR: [serial client] Serial protocol error: <10.0.0.71:502> connect error: No route to host (113)

Oct 07 11:52:01 wirenboard-AYK5U4TB wb-mqtt-serial[3576532]: INFO: [modbus] Continuous read enabled [slave_id is 113]
Oct 07 11:52:01 wirenboard-AYK5U4TB wb-mqtt-serial[3576532]: INFO: [serial client] Events are enabled for <modbus:113:input: 280>
Oct 07 11:52:01 wirenboard-AYK5U4TB wb-mqtt-serial[3576532]: INFO: [serial client] Events are disabled for <modbus:113:input: 281>
Oct 07 11:52:01 wirenboard-AYK5U4TB wb-mqtt-serial[3576532]: INFO: [serial client] Events are disabled for <modbus:113:input: 282>
Oct 07 11:52:01 wirenboard-AYK5U4TB wb-mqtt-serial[3576532]: INFO: [serial client] Events are enabled for <modbus:113:input: 283>
Oct 07 11:52:01 wirenboard-AYK5U4TB wb-mqtt-serial[3576532]: INFO: [serial client] Events are disabled for <modbus:113: reboot>
Oct 07 11:52:01 wirenboard-AYK5U4TB wb-mqtt-serial[3576532]: INFO: [serial device] device modbus:113 is connected
Oct 07 11:52:01 wirenboard-AYK5U4TB wb-mqtt-serial[3576532]: WARNING: [serial client] Restart event from unknown device modbus:11
Oct 07 11:52:03 wirenboard-AYK5U4TB wb-mqtt-serial[3576532]: INFO: [modbus] Continuous read enabled [slave_id is 170]
Oct 07 11:52:04 wirenboard-AYK5U4TB wb-mqtt-serial[3576532]: INFO: [serial client] Events are enabled for <modbus:170:input: 280>
Oct 07 11:52:04 wirenboard-AYK5U4TB wb-mqtt-serial[3576532]: INFO: [serial client] Events are disabled for <modbus:170:input: 281>
Oct 07 11:52:04 wirenboard-AYK5U4TB wb-mqtt-serial[3576532]: INFO: [serial client] Events are disabled for <modbus:170:input: 282>
Oct 07 11:52:04 wirenboard-AYK5U4TB wb-mqtt-serial[3576532]: INFO: [serial client] Events are enabled for <modbus:170:input: 283>
Oct 07 11:52:04 wirenboard-AYK5U4TB wb-mqtt-serial[3576532]: INFO: [serial client] Events are disabled for <modbus:170: reboot>
Oct 07 11:52:04 wirenboard-AYK5U4TB wb-mqtt-serial[3576532]: INFO: [serial device] device modbus:170 is connected

При этом, когда шлюз отключен драйвер пытается связаться с ним:

tcpdump host 10.0.0.71
2:05:22.566565 IP wirenboard-AYK5U4TB.local.52684 > mge.lan.502: Flags [P.], seq 1451:1459, ack 2042, win 31805, length 8
12:05:26.260128 IP wirenboard-AYK5U4TB.local.52684 > mge.lan.502: Flags [FP.], seq 1459:1562, ack 2042, win 31805, length 103
12:05:26.260599 IP wirenboard-AYK5U4TB.local.57764 > mge.lan.502: Flags [S], seq 1505431120, win 32120, options [mss 1460,sackOK,TS val 822150596 ecr 0,nop,wscale 7], length 0
12:05:26.662558 IP wirenboard-AYK5U4TB.local.52684 > mge.lan.502: Flags [FP.], seq 1451:1562, ack 2042, win 31805, length 111
12:05:27.270518 IP wirenboard-AYK5U4TB.local.57764 > mge.lan.502: Flags [S], seq 1505431120, win 32120, options [mss 1460,sackOK,TS val 822151606 ecr 0,nop,wscale 7], length 0
12:05:28.294545 IP wirenboard-AYK5U4TB.local.57764 > mge.lan.502: Flags [S], seq 1505431120, win 32120, options [mss 1460,sackOK,TS val 822152630 ecr 0,nop,wscale 7], length 0
12:05:28.596207 ARP, Request who-has mge.lan tell wirenboard-AWI3MCGC.local, length 46
12:05:29.318548 IP wirenboard-AYK5U4TB.local.57764 > mge.lan.502: Flags [S], seq 1505431120, win 32120, options [mss 1460,sackOK,TS val 822153654 ecr 0,nop,wscale 7], length 0
12:05:29.635621 ARP, Request who-has mge.lan tell wirenboard-AWI3MCGC.local, length 46
12:05:30.342569 IP wirenboard-AYK5U4TB.local.57764 > mge.lan.502: Flags [S], seq 1505431120, win 32120, options [mss 1460,sackOK,TS val 822154678 ecr 0,nop,wscale 7], length 0
12:05:30.675559 ARP, Request who-has mge.lan tell wirenboard-AWI3MCGC.local, length 46
12:05:31.715682 ARP, Request who-has mge.lan tell wirenboard-AWI3MCGC.local, length 46
12:05:31.797604 IP wirenboard-AYK5U4TB.local.37892 > mge.lan.502: Flags [S], seq 1849987850, win 32120, options [mss 1460,sackOK,TS val 822156133 ecr 0,nop,wscale 7], length 0
12:05:32.755521 ARP, Request who-has mge.lan tell wirenboard-AWI3MCGC.local, length 46
12:05:32.806539 IP wirenboard-AYK5U4TB.local.37892 > mge.lan.502: Flags [S], seq 1849987850, win 32120, options [mss 1460,sackOK,TS val 822157142 ecr 0,nop,wscale 7], length 0
12:05:33.795576 ARP, Request who-has mge.lan tell wirenboard-AWI3MCGC.local, length 46
12:05:33.830549 IP wirenboard-AYK5U4TB.local.37892 > mge.lan.502: Flags [S], seq 1849987850, win 32120, options [mss 1460,sackOK,TS val 822158166 ecr 0,nop,wscale 7], length 0
12:05:34.598546 IP wirenboard-AYK5U4TB.local.52684 > mge.lan.502: Flags [FP.], seq 1451:1562, ack 2042, win 31805, length 111
12:05:34.835820 ARP, Request who-has mge.lan tell wirenboard-AWI3MCGC.local, length 46
12:05:34.854570 IP wirenboard-AYK5U4TB.local.37892 > mge.lan.502: Flags [S], seq 1849987850, win 32120, options [mss 1460,sackOK,TS val 822159190 ecr 0,nop,wscale 7], length 0
12:05:35.875552 ARP, Request who-has mge.lan tell wirenboard-AWI3MCGC.local, length 46
12:05:35.878543 IP wirenboard-AYK5U4TB.local.37892 > mge.lan.502: Flags [S], seq 1849987850, win 32120, options [mss 1460,sackOK,TS val 822160214 ecr 0,nop,wscale 7], length 0
12:05:36.925551 ARP, Request who-has mge.lan tell wirenboard-AWI3MCGC.local, length 46
12:05:37.305073 IP wirenboard-AYK5U4TB.local.34306 > mge.lan.502: Flags [S], seq 22376492, win 32120, options [mss 1460,sackOK,TS val 822161640 ecr 0,nop,wscale 7], length 0
12:05:38.310530 IP wirenboard-AYK5U4TB.local.34306 > mge.lan.502: Flags [S], seq 22376492, win 32120, options [mss 1460,sackOK,TS val 822162646 ecr 0,nop,wscale 7], length 0
12:05:38.837359 ARP, Request who-has mge.lan tell wirenboard-AWI3MCGC.local, length 46
12:05:39.334553 IP wirenboard-AYK5U4TB.local.34306 > mge.lan.502: Flags [S], seq 22376492, win 32120, options [mss 1460,sackOK,TS val 822163670 ecr 0,nop,wscale 7], length 0
12:05:39.875572 ARP, Request who-has mge.lan tell wirenboard-AWI3MCGC.local, length 46
12:05:40.358564 IP wirenboard-AYK5U4TB.local.34306 > mge.lan.502: Flags [S], seq 22376492, win 32120, options [mss 1460,sackOK,TS val 822164694 ecr 0,nop,wscale 7], length 0
12:05:40.915563 ARP, Request who-has mge.lan tell wirenboard-AWI3MCGC.local, length 46
12:05:41.382555 IP wirenboard-AYK5U4TB.local.34306 > mge.lan.502: Flags [S], seq 22376492, win 32120, options [mss 1460,sackOK,TS val 822165718 ecr 0,nop,wscale 7], length 0
12:05:41.955806 ARP, Request who-has mge.lan tell wirenboard-AWI3MCGC.local, length 46
12:05:42.812628 IP wirenboard-AYK5U4TB.local.34312 > mge.lan.502: Flags [S], seq 1199629948, win 32120, options [mss 1460,sackOK,TS val 822167148 ecr 0,nop,wscale 7], length 0
12:05:43.005520 ARP, Request who-has mge.lan tell wirenboard-AWI3MCGC.local, length 46

Проверьте пожалуйста.
Вот так выглядит восстановление связи:

12:07:37.766533 ARP, Request who-has mge.lan tell wirenboard-AYK5U4TB.local, length 28
12:07:38.195871 ARP, Request who-has mge.lan tell wirenboard-AWI3MCGC.local, length 46
12:07:38.790513 ARP, Request who-has mge.lan tell wirenboard-AYK5U4TB.local, length 28
12:07:39.245593 ARP, Request who-has mge.lan tell wirenboard-AWI3MCGC.local, length 46
12:07:40.275567 ARP, Request who-has mge.lan tell wirenboard-AWI3MCGC.local, length 46
12:07:41.820567 ARP, Request who-has mge.lan tell wirenboard-AYK5U4TB.local, length 28
12:07:42.197383 ARP, Request who-has mge.lan tell wirenboard-AWI3MCGC.local, length 46
12:07:42.822519 ARP, Request who-has mge.lan tell wirenboard-AYK5U4TB.local, length 28
12:07:43.235558 ARP, Request who-has mge.lan tell wirenboard-AWI3MCGC.local, length 46
12:07:43.846508 ARP, Request who-has mge.lan tell wirenboard-AYK5U4TB.local, length 28
12:07:44.275579 ARP, Request who-has mge.lan tell wirenboard-AWI3MCGC.local, length 46
12:07:45.315727 ARP, Request who-has mge.lan tell wirenboard-AWI3MCGC.local, length 46
12:07:46.039375 ARP, Request who-has mge.lan tell 0.0.0.0, length 46
12:07:46.136141 ARP, Request who-has mge.lan tell 0.0.0.0, length 46
12:07:46.355541 ARP, Request who-has mge.lan tell wirenboard-AWI3MCGC.local, length 46
12:07:46.875461 ARP, Request who-has mge.lan tell wirenboard-AYK5U4TB.local, length 28
12:07:46.875606 ARP, Reply mge.lan is-at 9c:a5:25:bb:de:e1 (oui Unknown), length 46
12:07:46.875646 IP wirenboard-AYK5U4TB.local.54166 > mge.lan.502: Flags [S], seq 1189868758, win 32120, options [mss 1460,sackOK,TS val 822291210 ecr 0,nop,wscale 7], length 0
12:07:46.875782 IP mge.lan.502 > wirenboard-AYK5U4TB.local.54166: Flags [S.], seq 6524, ack 1189868759, win 2920, options [mss 1460], length 0
12:07:46.875933 IP wirenboard-AYK5U4TB.local.54166 > mge.lan.502: Flags [.], ack 1, win 32120, length 0
12:07:46.876489 IP wirenboard-AYK5U4TB.local.54166 > mge.lan.502: Flags [P.], seq 1:10, ack 1, win 32120, length 9
12:07:46.886146 IP mge.lan.502 > wirenboard-AYK5U4TB.local.54166: Flags [.], ack 10, win 2911, length 0
12:07:46.941211 IP mge.lan.502 > wirenboard-AYK5U4TB.local.54166: Flags [P.], seq 1:27, ack 10, win 2911, length 26
12:07:46.941351 IP wirenboard-AYK5U4TB.local.54166 > mge.lan.502: Flags [.], ack 27, win 32094, length 0
12:07:46.943538 IP wirenboard-AYK5U4TB.local.54166 > mge.lan.502: Flags [P.], seq 10:19, ack 27, win 32094, length 9
12:07:46.968179 IP mge.lan.502 > wirenboard-AYK5U4TB.local.54166: Flags [P.], seq 27:29, ack 19, win 2902, length 2
12:07:47.005196 IP mge.lan.502 > wirenboard-AYK5U4TB.local.54166: Flags [P.], seq 29:53, ack 19, win 2902, length 24
12:07:47.005317 IP wirenboard-AYK5U4TB.local.54166 > mge.lan.502: Flags [.], ack 53, win 32068, length 0
12:07:47.009888 IP wirenboard-AYK5U4TB.local.54166 > mge.lan.502: Flags [P.], seq 19:28, ack 53, win 32068, length 9
12:07:47.057150 IP mge.lan.502 > wirenboard-AYK5U4TB.local.54166: Flags [P.], seq 53:63, ack 28, win 2893, length 10
12:07:47.059859 IP wirenboard-AYK5U4TB.local.54166 > mge.lan.502: Flags [P.], seq 28:37, ack 63, win 32058, length 9
12:07:47.111179 IP mge.lan.502 > wirenboard-AYK5U4TB.local.54166: Flags [P.], seq 63:82, ack 37, win 2884, length 19
12:07:47.111748 IP wirenboard-AYK5U4TB.local.54166 > mge.lan.502: Flags [P.], seq 37:46, ack 82, win 32039, length 9
12:07:47.136093 ARP, Request who-has mge.lan tell mge.lan, length 46
12:07:47.136206 IP mge.lan.502 > wirenboard-AYK5U4TB.local.54166: Flags [.], ack 46, win 2875, length 0
12:07:47.136318 ARP, Request who-has wirenboard-AWI3MCGC.local tell mge.lan, length 46
12:07:47.158350 IP mge.lan.502 > wirenboard-AYK5U4TB.local.54166: Flags [P.], seq 82:92, ack 46, win 2875, length 10
12:07:47.170778 IP wirenboard-AYK5U4TB.local.54166 > mge.lan.502: Flags [P.], seq 46:54, ack 92, win 32029, length 8
12:07:47.200343 IP mge.lan.502 > wirenboard-AYK5U4TB.local.54166: Flags [P.], seq 92:100, ack 54, win 2867, length 8
12:07:47.200828 IP wirenboard-AYK5U4TB.local.54166 > mge.lan.502: Flags [P.], seq 54:73, ack 100, win 32021, length 19
12:07:47.243347 IP mge.lan.502 > wirenboard-AYK5U4TB.local.54166: Flags [P.], seq 100:108, ack 73, win 2848, length 8
12:07:47.286487 IP wirenboard-AYK5U4TB.local.54166 > mge.lan.502: Flags [.], ack 108, win 32013, length 0
28

Это я отлично понимаю, что так должно быть. Но по какой-то причине у меня не так (притом именно на WB8, на WB6.7 все нормально было с теми же конфигами):

У меня при отключении модуля он обещает подождать до определенного времени (246572842) и еще раз попробовать:

2024-10-05T11:26:14.875Z [wb-mqtt-serial] WARNING: [serial device] device modbus:74 is disconnected
2024-10-05T11:26:14.868Z [wb-mqtt-serial] WARNING: [serial device] device modbus:146 is disconnected
2024-10-05T11:26:14.362Z [wb-mqtt-serial] DEBUG: [serial client] <192.168.214.14:20109>246572342: Wait until 246572842
2024-10-05T11:26:14.358Z [wb-mqtt-serial] ERROR: [serial client] Serial protocol error: <192.168.214.14:20109> connect error: timeout
2024-10-05T11:26:09.351Z [wb-mqtt-serial] WARNING: <192.168.214.14:20109>: closed due to repetitive errors
2024-10-05T11:26:09.351Z [wb-mqtt-serial] WARNING: <192.168.214.14:20109>: closed due to repetitive errors
2024-10-05T11:26:09.348Z [wb-mqtt-serial] DEBUG: [serial client] Failed to open session: Serial protocol error: request timed out [slave_id is modbus:85]
2024-10-05T11:26:08.837Z [wb-mqtt-serial] DEBUG: [port] 192.168.214.14:20109: Write: 55 06 00 72 00 01 e5 c5
2024-10-05T11:26:08.837Z [wb-mqtt-serial] DEBUG: [port] 192.168.214.14:20109: Sleep 0 us
2024-10-05T11:26:08.837Z [wb-mqtt-serial] DEBUG: [modbus] write 1 (type 0)(s) @ 114 of device modbus:85
2024-10-05T11:26:08.837Z [wb-mqtt-serial] DEBUG: [port] 192.168.214.14:20109: Sleep 8000 us
2024-10-05T11:26:08.837Z [wb-mqtt-serial] DEBUG: [serial client] <192.168.214.14:20109>246566820: Wait until 246566820

Но по факту не одной попытки в логе не было. Почти 5 минут, пока был выключен модуль, полная тишина в логе, и попыток подключиться нет вообще. Следующая запись уже при перезагрузке wb-mqtt-serial:

2024-10-05T11:30:45.532Z [wb-mqtt-serial] INFO: [signal handling] Received signal 15
2024-10-05T11:26:14.875Z [wb-mqtt-serial] WARNING: [serial device] device modbus:74 is disconnected
2024-10-05T11:26:14.868Z [wb-mqtt-serial] WARNING: [serial device] device modbus:146 is disconnected
2024-10-05T11:26:14.362Z [wb-mqtt-serial] DEBUG: [serial client] <192.168.214.14:20109>246572342: Wait until 246572842

Но при этом при перезагрузке он mqtt-serial он ругается, что не смог остановить сервис, может он зависает?

2024-10-05T11:31:46.538Z [wb-mqtt-serial] INFO: [mqtt] Default host and port detected, checking if UNIX socket exists on /var/run/mosquitto/mosquitto.sock
2024-10-05T11:31:45.533Z [wb-mqtt-serial] terminate called without an active exception
2024-10-05T11:31:45.531Z [wb-mqtt-serial] ERROR: [serial] Driver takes too long to stop. Exiting.

Могу при необходимости повторить эксперимент и подождать больше 4,5 минут, но не думаю, что в этом есть смысл - когда отключали свет модуль не переподключился даже за час, и думаю в логах будет так же час тишины.

29

В лог - пишет раз в 5 минут.
А отправляются ли пакеты на шлюз?

30

Хорошо, попробую дольше подождать и приложить лог. Посмотрим.

Пакеты - как отследить? Если смотреть по показаниям самого WB-MGE, то там по нулям. траффик появляется только после перезапуска wb-mqtt-serial.

31

Пакеты прямо на интерфейсе контроллера проще всего дампить. Я же пример привел.

32

Свежий лог + tcpdump. Теперь ждал 12 минут.

18:06:00 - модуль выключен
18:06:35 - модуль включен
18:18:30 - сервис mqtt-serial запущен на перезагрузку
18:19:32 - сервис запустился

20241007.zip (179,1 КБ)

33

Отлично. А подключите для проверки шлюз через обычный, простой свич.
То есть - чтобы пакеты не проходили через роутер.

34

Сделал. Подключил через отдельный хаб без роутера, результат тот же. Снял логи.
Тайминг:
10:36:00 - Выключение WB-MGE
10:36:10 - Включение WB-MGE
10:48:30 - Начало перезапуска mqtt-serial
10:49:30 - mqtt-serial запустился

20241009.zip (193,9 КБ)

35

Так, вижу что шлюз на ack отвечает.

10:36:01.080534 IP wirenboard-A32RE5MO.local.32864 > 192.168.214.14.20109: Flags [P.], seq 9164:9173, ack 8742, win 31813, length 9
10:36:01.292229 IP wirenboard-A32RE5MO.local.32864 > 192.168.214.14.20109: Flags [P.], seq 9164:9173, ack 8742, win 31813, length 9
10:36:01.728227 IP wirenboard-A32RE5MO.local.32864 > 192.168.214.14.20109: Flags [P.], seq 9164:9173, ack 8742, win 31813, length 9
10:36:02.592222 IP wirenboard-A32RE5MO.local.32864 > 192.168.214.14.20109: Flags [P.], seq 9164:9173, ack 8742, win 31813, length 9
10:36:04.288175 IP wirenboard-A32RE5MO.local.32864 > 192.168.214.14.20109: Flags [P.], seq 9164:9173, ack 8742, win 31813, length 9
10:36:07.680270 IP wirenboard-A32RE5MO.local.32864 > 192.168.214.14.20109: Flags [P.], seq 9164:9173, ack 8742, win 31813, length 9
10:36:09.847519 IP wirenboard-A32RE5MO.local.32864 > 192.168.214.14.20109: Flags [FP.], seq 9173:9282, ack 8742, win 31813, length 109
10:36:09.847764 IP wirenboard-A32RE5MO.local.36266 > 192.168.214.14.20109: Flags [S], seq 638457925, win 32120, options [mss 1460,sackOK,TS val 1888924957 ecr 0,nop,wscale 7], length 0
10:36:10.848190 IP wirenboard-A32RE5MO.local.36266 > 192.168.214.14.20109: Flags [S], seq 638457925, win 32120, options [mss 1460,sackOK,TS val 1888925958 ecr 0,nop,wscale 7], length 0
10:36:11.872239 IP wirenboard-A32RE5MO.local.36266 > 192.168.214.14.20109: Flags [S], seq 638457925, win 32120, options [mss 1460,sackOK,TS val 1888926982 ecr 0,nop,wscale 7], length 0
10:36:12.896185 IP wirenboard-A32RE5MO.local.36266 > 192.168.214.14.20109: Flags [S], seq 638457925, win 32120, options [mss 1460,sackOK,TS val 1888928006 ecr 0,nop,wscale 7], length 0
10:36:13.920185 IP wirenboard-A32RE5MO.local.36266 > 192.168.214.14.20109: Flags [S], seq 638457925, win 32120, options [mss 1460,sackOK,TS val 1888929030 ecr 0,nop,wscale 7], length 0
10:36:14.592264 IP wirenboard-A32RE5MO.local.32864 > 192.168.214.14.20109: Flags [FP.], seq 9164:9282, ack 8742, win 31813, length 118
10:36:14.976674 ARP, Request who-has 192.168.214.14 tell 192.168.214.14, length 46
10:36:28.160192 IP wirenboard-A32RE5MO.local.32864 > 192.168.214.14.20109: Flags [FP.], seq 9164:9282, ack 8742, win 31813, length 118
10:36:28.161010 IP 192.168.214.14.20109 > wirenboard-A32RE5MO.local.32864: Flags [R.], seq 8743, ack 9283, win 2920, length 0
10:36:28.161046 IP wirenboard-A32RE5MO.local.32864 > 192.168.214.14.20109: Flags [.], ack 8742, win 31813, length 0
10:36:28.161559 IP 192.168.214.14.20109 > wirenboard-A32RE5MO.local.32864: Flags [R.], seq 8743, ack 9283, win 2920, length 0
10:36:55.552178 IP wirenboard-A32RE5MO.local.32864 > 192.168.214.14.20109: Flags [FP.], seq 9164:9282, ack 8742, win 31813, length 118
10:36:55.556550 IP 192.168.214.14.20109 > wirenboard-A32RE5MO.local.32864: Flags [R.], seq 8743, ack 9283, win 2920, length 0
10:36:55.556570 IP wirenboard-A32RE5MO.local.32864 > 192.168.214.14.20109: Flags [.], ack 8742, win 31813, length 0
10:36:55.563929 IP 192.168.214.14.20109 > wirenboard-A32RE5MO.local.32864: Flags [R.], seq 8743, ack 9283, win 2920, length 0
10:37:00.672151 ARP, Request who-has 192.168.214.14 tell wirenboard-A32RE5MO.local, length 28
10:37:00.672637 ARP, Reply 192.168.214.14 is-at a6:4c:5e:02:32:b8 (oui Unknown), length 50

Позову разработчиков.

36

Пока, к сожалению решения нет.

37

Понял, спасибо за информацию, но хотя бы повторить/понять проблему получилось?

38

Нет, не получилось. В том-то и дело. Сегодня еще попробую.

39

По -прежнему не получается.