-
Posts
4,467 -
Joined
-
Last visited
-
Days Won
76
Content Type
Profiles
Forums
Gallery
Downloads
Blogs
Events
Posts posted by vasek00
-
-
Не помню, но последняя
Еще одно
Или еще
-
21 час назад, Vladislav Proskuryakov сказал:
Сейчас данные параметры можно СТАТИЧЕСКИ получить командой "show associations" либо через консоль, либо через отправку в http://192.168.x.1/a (https://keendns/a)
Каждый раз вводить команду для получения обновленной информации не удобно.
Считаю, что тем кому актуальна диагностическая информация по скорости подключения клиентов, также не помешают данные параметры для оценки затухания сигнала и общего качества wifi покрытия.
Не сколько раз уже на данном форуме упоминал так же по данному направлению, а именно хотя бы rssi для клиента.
-
3 часа назад, Vadim-85 сказал:
Решил попробовать просто Extra 2 поставить в режиме усилитель/ретранслятор, так вот скорость стала 170-180 и это связь между роутерами на 2.4 Ггц. Связал по 5 Ггц - скорость опять около 50. И я понял, что по mesh, что просто как усилитель/ретранслятор в связке на 5 Ггц скорость выше 60 мегабит Extra 2 не даёт. Можно как-нибудь решить проблему?
При схеме не совсем прямая видимость
Клиент Wifi --- 5GHz --- KN10 --- 5GHz --- ExtII --- 5GHz --- ТВ NAS ----------- LAN ------+ Линк между роутерами 585/525
На текущем клиенте Windows ПК wifi копирование с NAS -- 273Мбит ~34МБ (съем показаний с KN10). Так же на ТВ просмотр АВАТАР 4К зависон на ТВ (поток фильма 80-110 и до 130Мб), копирование сразу же упало до 25МБ, при остановке копирования проблем на ТВ не было. Фильм слабее идет без проблем даже при копирование файла с NAS. Думаю оптимальный поток Wifi ExtII-KN10 в районе ~ 300Мбит
При схеме
HDD/USB3 --- KN10 --- 5GHz --- ExtII --- 5GHz --- ТВ
фильм 4К Великая стена поток 80-103Мб проблем не возникало.
ЦитатаТак же нужно еще учесть что в ExtraII/KN1710 стоит 7612, а в KN1711 например стоит 7613 а он имеет на своем борту Full MAC offload что позволяет снять нагрузку по обработке беспроводного трафика с CPU, весь трафик между клиентами внутри диапазона, а также в схемах ТД дает 0% нагрузки на CPU. Полноценная реализация Airtime обеспечивает равномерное распределение эфирного времени между клиентами, что позволяет избежать ситуации, при которой один клиент, подключенный с низким рэйтом (например, работающий в непрямой видимости и на удалении от AP), занимает весь эфир, а остальные находятся в ожидании, в соответствии с принципами распределения эфирного времени в 802.11.
-
19 часов назад, Le ecureuil сказал:
Там сперва нужно создать профиль pingcheck и привязать его к интерфейсу.
! ping-check profile WG_Cloud host 8.8.8.8 update-interval 10 mode icmp max-fails 5 ! interface Wireguard0 description Cloud-warp security-level public ip address 10.16.16.98 255.255.255.0 ip mtu 1324 ip global 350 ip tcp adjust-mss pmtu wireguard listen-port ххххх wireguard peer bmXOC+F1FxEMF9dyiK2H5/1SUtzH0JuVo51h2wPfgyo= !Cloudflare-warp endpoint engage.cloudflareclient.com:2408 keepalive-interval 30 allow-ips 0.0.0.0 0.0.0.0 allow-ips 10.16.16.0 255.255.255.0 ! ping-check profile WG_Cloud up
Пока такая связка отрабатывает, посмотрим что будет дальше, т.е. при проблеме на канале у основного роутера, на данном KN30 уже нет цикл.затыков типа.
Скрытый текстФев 12 08:32:53 kernel wireguard: Wireguard0: handshake for peer "bmXOC+F1FxEMF9dyiK2H5/1SUtzH0JuVo51h2wPfgyo=" (2) (162.159.192.1:2408) did not complete after 5 seconds, retrying (try 4) Фев 12 08:32:58 kernel wireguard: Wireguard0: retrying handshake with peer "bmXOC+F1FxEMF9dyiK2H5/1SUtzH0JuVo51h2wPfgyo=" (2) (162.159.192.1:2408) because we stopped hearing back after 15 seconds Фев 12 08:32:58 kernel wireguard: Wireguard0: handshake for peer "bmXOC+F1FxEMF9dyiK2H5/1SUtzH0JuVo51h2wPfgyo=" (2) (162.159.192.1:2408) did not complete after 5 seconds, retrying (try 2)
- 1
-
Отписываюсь по данной команде в данном случае через cli при использование на KN30 WG
(config)> interface Wireguard0 Core::Configurator: Done. (config-if)> ping-check restart PingCheck::Client error[41617060]: interface "Wireguard0" has no assigned profile. (config-if)> ping-check restart Wireguard0 PingCheck::Client error[41617060]: interface "Wireguard0" has no assigned profile. (config-if)>
-
46 минут назад, Le ecureuil сказал:
Есть же pingcheck с restart-interface, зачем изобретать что-то еще?
т.е. на данном интерфейсе
interface Wireguard0 description Cloud-warp security-level public
нужно поставить (config-if)> ping-check restart [ ‹interface› ]
Попробуем. Отпишусь.
-
29 минут назад, Le ecureuil сказал:
Нужны не выдержки из self-test, а он целиком. Я вроде ясно написал, неужели где-то двусмысленность закралась?
В следующий раз когда будет такое поведение обязательно скину, в данный момент данного файла нет, так как не думал писать сначала, а потом все же написал.
Второй вопрос по восстановлению WG?
-
Проверка описанного выше еще раз сегодня пока не получилась.
Есть еще вопрос возможно ли изменить контроль состояния WG при данной схеме, так как при проблеме на основном роутере с интернетом (т.е. соединение поднято заново с новым IP) то второй роутер с WG не может поднять соединения идет цикл восстановления WG как долго не в курсе но за 7мин которые ниже так и не дождался. Возможен ли счетчик повторов цикла, после например 3 повтора выполнить выкл/вкл WG.
Фев 12 08:35:30 ndm Network::Interface::Base: "Wireguard0": interface is down. и через 3-5сек. Фев 12 08:35:34 ndm Network::Interface::Base: "Wireguard0": interface is up.
В 12:08:27 на основном смена IP адреса на интернет канале и как итог на KN30 который по LAN c WG цикл по восстановлению канала WG
Скрытый текстФев 12 08:18:35 ndm Network::Interface::Switch: "GigabitEthernet0/2": switch link up at port 3 (1000FD/AN).Фев 12 08:18:42 ndm Netfilter::Util::Conntrack: flushed 4 IPv4 connections for 192.168.130.2.Фев 12 08:27:17 kernelwireguard: Wireguard0: retrying handshake with peer "bmXOC+F1FxEMF9dyiK2H5/1SUtzH0JuVo51h2wPfgyo=" (2) (162.159.192.1:2408) because we stopped hearing back after 15 secondsФев 12 08:27:22 kernel wireguard: Wireguard0: handshake for peer "bmXOC+F1FxEMF9dyiK2H5/1SUtzH0JuVo51h2wPfgyo=" (2) (162.159.192.1:2408) did not complete after 5 seconds, retrying (try 2)Фев 12 08:27:28 kernelwireguard: Wireguard0: handshake for peer "bmXOC+F1FxEMF9dyiK2H5/1SUtzH0JuVo51h2wPfgyo=" (2) (162.159.192.1:2408) did not complete after 5 seconds, retrying (try 3)Фев 12 08:27:32 kernel wireguard: Wireguard0: retrying handshake with peer "bmXOC+F1FxEMF9dyiK2H5/1SUtzH0JuVo51h2wPfgyo=" (2) (162.159.192.1:2408) because we stopped hearing back after 15 secondsФев 12 08:27:36 ndm Network::InternetChecker: Internet access lost (status: 0x0003).Фев 12 08:27:48 kernel wireguard: Wireguard0: retrying handshake with peer "bmXOC+F1FxEMF9dyiK2H5/1SUtzH0JuVo51h2wPfgyo=" (2) (162.159.192.1:2408) because we stopped hearing back after 15 secondsФев 12 08:27:53 kernel wireguard: Wireguard0: handshake for peer "bmXOC+F1FxEMF9dyiK2H5/1SUtzH0JuVo51h2wPfgyo=" (2) (162.159.192.1:2408) did not complete after 5 seconds, retrying (try 2)Фев 12 08:27:57 ndm Core::Ndss: [8021] cannot connect to the server.Фев 12 08:27:58 kernel wireguard: Wireguard0: handshake for peer "bmXOC+F1FxEMF9dyiK2H5/1SUtzH0JuVo51h2wPfgyo=" (2) (162.159.192.1:2408) did not complete after 5 seconds, retrying (try 2)Фев 12 08:28:03 kernel wireguard: Wireguard0: retrying handshake with peer "bmXOC+F1FxEMF9dyiK2H5/1SUtzH0JuVo51h2wPfgyo=" (2) (162.159.192.1:2408) because we stopped hearing back after 15 secondsФев 12 08:28:03 kernel wireguard: Wireguard0: handshake for peer "bmXOC+F1FxEMF9dyiK2H5/1SUtzH0JuVo51h2wPfgyo=" (2) (162.159.192.1:2408) did not complete after 5 seconds, retrying (try 2)Фев 12 08:28:14 kernel Core::Syslog: last message repeated 2 times.Фев 12 08:28:19 kernel wireguard: Wireguard0: retrying handshake with peer "bmXOC+F1FxEMF9dyiK2H5/1SUtzH0JuVo51h2wPfgyo=" (2) (162.159.192.1:2408) because we stopped hearing back after 15 secondsФев 12 08:28:20 kernel wireguard: Wireguard0: handshake for peer "bmXOC+F1FxEMF9dyiK2H5/1SUtzH0JuVo51h2wPfgyo=" (2) (162.159.192.1:2408) did not complete after 5 seconds, retrying (try 2)Фев 12 08:28:30 kernel Core::Syslog: last message repeated 3 times.Фев 12 08:28:34 kernel wireguard: Wireguard0: retrying handshake with peer "bmXOC+F1FxEMF9dyiK2H5/1SUtzH0JuVo51h2wPfgyo=" (2) (162.159.192.1:2408) because we stopped hearing back after 15 secondsФев 12 08:28:35 kernel wireguard: Wireguard0: handshake for peer "bmXOC+F1FxEMF9dyiK2H5/1SUtzH0JuVo51h2wPfgyo=" (2) (162.159.192.1:2408) did not complete after 5 seconds, retrying (try 2)Фев 12 08:28:39 ndm Network::InterfaceFlusher: flushed Wireguard0 conntrack and route cache.Фев 12 08:28:39 upnp shutting down MiniUPnPdФев 12 08:28:39 ndm Core::Session: client disconnected.Фев 12 08:28:41 kernel wireguard: Wireguard0: handshake for peer "bmXOC+F1FxEMF9dyiK2H5/1SUtzH0JuVo51h2wPfgyo=" (2) (162.159.192.1:2408) did not complete after 5 seconds, retrying (try 2)Фев 12 08:28:41 ndm Core::Server: started Session /var/run/ndm.core.socket.Фев 12 08:28:41 upnp HTTP listening on port 51043Фев 12 08:28:41 upnp Listening for NAT-PMP/PCP traffic on port 5351Фев 12 08:28:45 ndm Wireguard::Interface: "Wireguard0": interface "Wireguard0" is global, priority 350.Фев 12 08:28:45 ndm Wireguard::Interface: "Wireguard0": adding default route via Wireguard0.Фев 12 08:28:45 ndm Network::InterfaceFlusher: flushed Bridge0 conntrack and route cache.Фев 12 08:28:45 upnp shutting down MiniUPnPdФев 12 08:28:45 ndm Core::Session: client disconnected.Фев 12 08:28:47 ndm Core::Server: started Session /var/run/ndm.core.socket.Фев 12 08:28:47 upnp HTTP listening on port 50557Фев 12 08:28:47 upnp Listening for NAT-PMP/PCP traffic on port 5351Фев 12 08:29:01 kernel wireguard: Wireguard0: retrying handshake with peer "bmXOC+F1FxEMF9dyiK2H5/1SUtzH0JuVo51h2wPfgyo=" (2) (162.159.192.1:2408) because we stopped hearing back after 15 secondsФев 12 08:29:06 kernel wireguard: Wireguard0: handshake for peer "bmXOC+F1FxEMF9dyiK2H5/1SUtzH0JuVo51h2wPfgyo=" (2) (162.159.192.1:2408) did not complete after 5 seconds, retrying (try 2)Фев 12 08:29:11 kernel wireguard: Wireguard0: handshake for peer "bmXOC+F1FxEMF9dyiK2H5/1SUtzH0JuVo51h2wPfgyo=" (2) (162.159.192.1:2408) did not complete after 5 seconds, retrying (try 3)Фев 12 08:29:15 ndm Cloud::Agent: can not connect to the cloud server.Фев 12 08:29:16 kernel wireguard: Wireguard0: retrying handshake with peer "bmXOC+F1FxEMF9dyiK2H5/1SUtzH0JuVo51h2wPfgyo=" (2) (162.159.192.1:2408) because we stopped hearing back after 15 secondsФев 12 08:29:16 kernel wireguard: Wireguard0: handshake for peer "bmXOC+F1FxEMF9dyiK2H5/1SUtzH0JuVo51h2wPfgyo=" (2) (162.159.192.1:2408) did not complete after 5 seconds, retrying (try 2)Фев 12 08:29:21 kernel wireguard: Wireguard0: handshake for peer "bmXOC+F1FxEMF9dyiK2H5/1SUtzH0JuVo51h2wPfgyo=" (2) (162.159.192.1:2408) did not complete after 5 seconds, retrying (try 3)Фев 12 08:29:27 kernel wireguard: Wireguard0: handshake for peer "bmXOC+F1FxEMF9dyiK2H5/1SUtzH0JuVo51h2wPfgyo=" (2) (162.159.192.1:2408) did not complete after 5 seconds, retrying (try 4)Фев 12 08:29:31 kernel wireguard: Wireguard0: retrying handshake with peer "bmXOC+F1FxEMF9dyiK2H5/1SUtzH0JuVo51h2wPfgyo=" (2) (162.159.192.1:2408) because we stopped hearing back after 15 secondsФев 12 08:29:32 kernel wireguard: Wireguard0: handshake for peer "bmXOC+F1FxEMF9dyiK2H5/1SUtzH0JuVo51h2wPfgyo=" (2) (162.159.192.1:2408) did not complete after 5 seconds, retrying (try 2)Фев 12 08:29:37 kernel wireguard: Wireguard0: handshake for peer "bmXOC+F1FxEMF9dyiK2H5/1SUtzH0JuVo51h2wPfgyo=" (2) (162.159.192.1:2408) did not complete after 5 seconds, retrying (try 3)Фев 12 08:29:43 kernel wireguard: Wireguard0: handshake for peer "bmXOC+F1FxEMF9dyiK2H5/1SUtzH0JuVo51h2wPfgyo=" (2) (162.159.192.1:2408) did not complete after 5 seconds, retrying (try 4)Фев 12 08:29:46 kernel wireguard: Wireguard0: retrying handshake with peer "bmXOC+F1FxEMF9dyiK2H5/1SUtzH0JuVo51h2wPfgyo=" (2) (162.159.192.1:2408) because we stopped hearing back after 15 secondsФев 12 08:29:48 kernel wireguard: Wireguard0: handshake for peer "bmXOC+F1FxEMF9dyiK2H5/1SUtzH0JuVo51h2wPfgyo=" (2) (162.159.192.1:2408) did not complete after 5 seconds, retrying (try 2)Фев 12 08:29:54 kernel wireguard: Wireguard0: handshake for peer "bmXOC+F1FxEMF9dyiK2H5/1SUtzH0JuVo51h2wPfgyo=" (2) (162.159.192.1:2408) did not complete after 5 seconds, retrying (try 3)Фев 12 08:29:59 kernel wireguard: Wireguard0: handshake for peer "bmXOC+F1FxEMF9dyiK2H5/1SUtzH0JuVo51h2wPfgyo=" (2) (162.159.192.1:2408) did not complete after 5 seconds, retrying (try 4)Фев 12 08:30:03 kernel wireguard: Wireguard0: retrying handshake with peer "bmXOC+F1FxEMF9dyiK2H5/1SUtzH0JuVo51h2wPfgyo=" (2) (162.159.192.1:2408) because we stopped hearing back after 15 secondsФев 12 08:30:04 kernel wireguard: Wireguard0: handshake for peer "bmXOC+F1FxEMF9dyiK2H5/1SUtzH0JuVo51h2wPfgyo=" (2) (162.159.192.1:2408) did not complete after 5 seconds, retrying (try 2)Фев 12 08:30:09 kernel wireguard: Wireguard0: handshake for peer "bmXOC+F1FxEMF9dyiK2H5/1SUtzH0JuVo51h2wPfgyo=" (2) (162.159.192.1:2408) did not complete after 5 seconds, retrying (try 3)Фев 12 08:30:15 kernel wireguard: Wireguard0: handshake for peer "bmXOC+F1FxEMF9dyiK2H5/1SUtzH0JuVo51h2wPfgyo=" (2) (162.159.192.1:2408) did not complete after 5 seconds, retrying (try 4)Фев 12 08:30:19 kernel wireguard: Wireguard0: retrying handshake with peer "bmXOC+F1FxEMF9dyiK2H5/1SUtzH0JuVo51h2wPfgyo=" (2) (162.159.192.1:2408) because we stopped hearing back after 15 secondsФев 12 08:30:20 kernel wireguard: Wireguard0: handshake for peer "bmXOC+F1FxEMF9dyiK2H5/1SUtzH0JuVo51h2wPfgyo=" (2) (162.159.192.1:2408) did not complete after 5 seconds, retrying (try 2)Фев 12 08:30:25 kernel wireguard: Wireguard0: handshake for peer "bmXOC+F1FxEMF9dyiK2H5/1SUtzH0JuVo51h2wPfgyo=" (2) (162.159.192.1:2408) did not complete after 5 seconds, retrying (try 3)Фев 12 08:30:30 kernel wireguard: Wireguard0: handshake for peer "bmXOC+F1FxEMF9dyiK2H5/1SUtzH0JuVo51h2wPfgyo=" (2) (162.159.192.1:2408) did not complete after 5 seconds, retrying (try 4)Фев 12 08:30:35 kernel wireguard: Wireguard0: retrying handshake with peer "bmXOC+F1FxEMF9dyiK2H5/1SUtzH0JuVo51h2wPfgyo=" (2) (162.159.192.1:2408) because we stopped hearing back after 15 secondsФев 12 08:30:36 kernel wireguard: Wireguard0: handshake for peer "bmXOC+F1FxEMF9dyiK2H5/1SUtzH0JuVo51h2wPfgyo=" (2) (162.159.192.1:2408) did not complete after 5 seconds, retrying (try 2)Фев 12 08:30:41 kernel wireguard: Wireguard0: handshake for peer "bmXOC+F1FxEMF9dyiK2H5/1SUtzH0JuVo51h2wPfgyo=" (2) (162.159.192.1:2408) did not complete after 5 seconds, retrying (try 3)Фев 12 08:30:51 kernel wireguard: Wireguard0: retrying handshake with peer "bmXOC+F1FxEMF9dyiK2H5/1SUtzH0JuVo51h2wPfgyo=" (2) (162.159.192.1:2408) because we stopped hearing back after 15 secondsФев 12 08:30:57 kernel wireguard: Wireguard0: handshake for peer "bmXOC+F1FxEMF9dyiK2H5/1SUtzH0JuVo51h2wPfgyo=" (2) (162.159.192.1:2408) did not complete after 5 seconds, retrying (try 2)Фев 12 08:31:02 kernel wireguard: Wireguard0: handshake for peer "bmXOC+F1FxEMF9dyiK2H5/1SUtzH0JuVo51h2wPfgyo=" (2) (162.159.192.1:2408) did not complete after 5 seconds, retrying (try 2)Фев 12 08:31:18 kernel Core::Syslog: last message repeated 4 times.Фев 12 08:31:22 kernel wireguard: Wireguard0: retrying handshake with peer "bmXOC+F1FxEMF9dyiK2H5/1SUtzH0JuVo51h2wPfgyo=" (2) (162.159.192.1:2408) because we stopped hearing back after 15 secondsФев 12 08:31:23 kernel wireguard: Wireguard0: handshake for peer "bmXOC+F1FxEMF9dyiK2H5/1SUtzH0JuVo51h2wPfgyo=" (2) (162.159.192.1:2408) did not complete after 5 seconds, retrying (try 2)Фев 12 08:31:34 kernel wireguard: Wireguard0: handshake for peer "bmXOC+F1FxEMF9dyiK2H5/1SUtzH0JuVo51h2wPfgyo=" (2) (162.159.192.1:2408) did not complete after 5 seconds, retrying (try 2)Фев 12 08:31:44 kernel Core::Syslog: last message repeated 5 times.Фев 12 08:31:48 ndm Network::InterfaceFlusher: flushed Wireguard0 conntrack and route cache.Фев 12 08:31:48 upnp shutting down MiniUPnPdФев 12 08:31:48 ndm Core::Session: client disconnected.Фев 12 08:31:50 kernel wireguard: Wireguard0: handshake for peer "bmXOC+F1FxEMF9dyiK2H5/1SUtzH0JuVo51h2wPfgyo=" (2) (162.159.192.1:2408) did not complete after 5 seconds, retrying (try 2)Фев 12 08:31:50 kernel wireguard: Wireguard0: invalid handshake response from 162.159.192.1:2408Фев 12 08:31:50 ndm Core::Server: started Session /var/run/ndm.core.socket.Фев 12 08:31:50 upnp HTTP listening on port 53871Фев 12 08:31:50 upnp Listening for NAT-PMP/PCP traffic on port 5351Фев 12 08:31:54 ndm Wireguard::Interface: "Wireguard0": interface "Wireguard0" is global, priority 350.Фев 12 08:31:54 ndm Wireguard::Interface: "Wireguard0": adding default route via Wireguard0.Фев 12 08:31:54 ndm Network::InterfaceFlusher: flushed Bridge0 conntrack and route cache.Фев 12 08:31:54 upnp shutting down MiniUPnPdФев 12 08:31:54 ndm Core::Session: client disconnected.Фев 12 08:31:56 ndm Core::Server: started Session /var/run/ndm.core.socket.Фев 12 08:31:56 upnp HTTP listening on port 53161Фев 12 08:31:56 upnp Listening for NAT-PMP/PCP traffic on port 5351Фев 12 08:32:11 kernel wireguard: Wireguard0: retrying handshake with peer "bmXOC+F1FxEMF9dyiK2H5/1SUtzH0JuVo51h2wPfgyo=" (2) (162.159.192.1:2408) because we stopped hearing back after 15 secondsФев 12 08:32:16 kernel wireguard: Wireguard0: handshake for peer "bmXOC+F1FxEMF9dyiK2H5/1SUtzH0JuVo51h2wPfgyo=" (2) (162.159.192.1:2408) did not complete after 5 seconds, retrying (try 2)Фев 12 08:32:21 kernel wireguard: Wireguard0: handshake for peer "bmXOC+F1FxEMF9dyiK2H5/1SUtzH0JuVo51h2wPfgyo=" (2) (162.159.192.1:2408) did not complete after 5 seconds, retrying (try 3)Фев 12 08:32:26 kernel wireguard: Wireguard0: retrying handshake with peer "bmXOC+F1FxEMF9dyiK2H5/1SUtzH0JuVo51h2wPfgyo=" (2) (162.159.192.1:2408) because we stopped hearing back after 15 secondsФев 12 08:32:26 kernel wireguard: Wireguard0: handshake for peer "bmXOC+F1FxEMF9dyiK2H5/1SUtzH0JuVo51h2wPfgyo=" (2) (162.159.192.1:2408) did not complete after 5 seconds, retrying (try 2)Фев 12 08:32:32 kernel wireguard: Wireguard0: handshake for peer "bmXOC+F1FxEMF9dyiK2H5/1SUtzH0JuVo51h2wPfgyo=" (2) (162.159.192.1:2408) did not complete after 5 seconds, retrying (try 3)Фев 12 08:32:37 kernel wireguard: Wireguard0: handshake for peer "bmXOC+F1FxEMF9dyiK2H5/1SUtzH0JuVo51h2wPfgyo=" (2) (162.159.192.1:2408) did not complete after 5 seconds, retrying (try 4)Фев 12 08:32:41 kernel wireguard: Wireguard0: retrying handshake with peer "bmXOC+F1FxEMF9dyiK2H5/1SUtzH0JuVo51h2wPfgyo=" (2) (162.159.192.1:2408) because we stopped hearing back after 15 secondsФев 12 08:32:42 kernel wireguard: Wireguard0: handshake for peer "bmXOC+F1FxEMF9dyiK2H5/1SUtzH0JuVo51h2wPfgyo=" (2) (162.159.192.1:2408) did not complete after 5 seconds, retrying (try 2)Фев 12 08:32:47 kernel wireguard: Wireguard0: handshake for peer "bmXOC+F1FxEMF9dyiK2H5/1SUtzH0JuVo51h2wPfgyo=" (2) (162.159.192.1:2408) did not complete after 5 seconds, retrying (try 3)Фев 12 08:32:53 kernel wireguard: Wireguard0: handshake for peer "bmXOC+F1FxEMF9dyiK2H5/1SUtzH0JuVo51h2wPfgyo=" (2) (162.159.192.1:2408) did not complete after 5 seconds, retrying (try 4)Фев 12 08:32:58 kernel wireguard: Wireguard0: retrying handshake with peer "bmXOC+F1FxEMF9dyiK2H5/1SUtzH0JuVo51h2wPfgyo=" (2) (162.159.192.1:2408) because we stopped hearing back after 15 secondsФев 12 08:32:58 kernel wireguard: Wireguard0: handshake for peer "bmXOC+F1FxEMF9dyiK2H5/1SUtzH0JuVo51h2wPfgyo=" (2) (162.159.192.1:2408) did not complete after 5 seconds, retrying (try 2)Фев 12 08:33:04 kernel wireguard: Wireguard0: handshake for peer "bmXOC+F1FxEMF9dyiK2H5/1SUtzH0JuVo51h2wPfgyo=" (2) (162.159.192.1:2408) did not complete after 5 seconds, retrying (try 3)Фев 12 08:33:09 kernel wireguard: Wireguard0: handshake for peer "bmXOC+F1FxEMF9dyiK2H5/1SUtzH0JuVo51h2wPfgyo=" (2) (162.159.192.1:2408) did not complete after 5 seconds, retrying (try 4)....
Фев 12 08:33:46 kernel wireguard: Wireguard0: retrying handshake with peer "bmXOC+F1FxEMF9dyiK2H5/1SUtzH0JuVo51h2wPfgyo=" (2) (162.159.192.1:2408) because we stopped hearing back after 15 secondsФев 12 08:33:47 kernel wireguard: Wireguard0: handshake for peer "bmXOC+F1FxEMF9dyiK2H5/1SUtzH0JuVo51h2wPfgyo=" (2) (162.159.192.1:2408) did not complete after 5 seconds, retrying (try 2)Фев 12 08:33:57 kernel wireguard: Wireguard0: handshake for peer "bmXOC+F1FxEMF9dyiK2H5/1SUtzH0JuVo51h2wPfgyo=" (2) (162.159.192.1:2408) did not complete after 5 seconds, retrying (try 2)Фев 12 08:34:08 kernel Core::Syslog: last message repeated 3 times.Фев 12 08:34:09 ndm Core::Ndss: [9983] cannot connect to the server.Фев 12 08:34:13 kernel wireguard: Wireguard0: handshake for peer "bmXOC+F1FxEMF9dyiK2H5/1SUtzH0JuVo51h2wPfgyo=" (2) (162.159.192.1:2408) did not complete after 5 seconds, retrying (try 2)Фев 12 08:34:17 kernel wireguard: Wireguard0: retrying handshake with peer "bmXOC+F1FxEMF9dyiK2H5/1SUtzH0JuVo51h2wPfgyo=" (2) (162.159.192.1:2408) because we stopped hearing back after 15 secondsФев 12 08:34:19 kernel wireguard: Wireguard0: handshake for peer "bmXOC+F1FxEMF9dyiK2H5/1SUtzH0JuVo51h2wPfgyo=" (2) (162.159.192.1:2408) did not complete after 5 seconds, retrying (try 2)Фев 12 08:34:29 kernel Core::Syslog: last message repeated 2 times.Фев 12 08:34:34 kernel wireguard: Wireguard0: retrying handshake with peer "bmXOC+F1FxEMF9dyiK2H5/1SUtzH0JuVo51h2wPfgyo=" (2) (162.159.192.1:2408) because we stopped hearing back after 15 secondsФев 12 08:34:49 kernel Core::Syslog: last message repeated 3 times.Фев 12 08:34:55 kernel wireguard: Wireguard0: handshake for peer "bmXOC+F1FxEMF9dyiK2H5/1SUtzH0JuVo51h2wPfgyo=" (2) (162.159.192.1:2408) did not complete after 5 seconds, retrying (try 2)Фев 12 08:34:58 ndm Network::InterfaceFlusher: flushed Wireguard0 conntrack and route cache.Фев 12 08:34:58 upnp shutting down MiniUPnPdФев 12 08:34:58 ndm Core::Session: client disconnected.Фев 12 08:35:00 ndm Core::Server: started Session /var/run/ndm.core.socket.Фев 12 08:35:00 upnp HTTP listening on port 49485Фев 12 08:35:00 upnp Listening for NAT-PMP/PCP traffic on port 5351Фев 12 08:35:00 kernel wireguard: Wireguard0: handshake for peer "bmXOC+F1FxEMF9dyiK2H5/1SUtzH0JuVo51h2wPfgyo=" (2) (162.159.192.1:2408) did not complete after 5 seconds, retrying (try 2)Фев 12 08:35:00 kernel wireguard: Wireguard0: invalid handshake response from 162.159.192.1:2408Фев 12 08:35:03 ndm Wireguard::Interface: "Wireguard0": interface "Wireguard0" is global, priority 350.Фев 12 08:35:03 ndm Wireguard::Interface: "Wireguard0": adding default route via Wireguard0.Фев 12 08:35:03 ndm Network::InterfaceFlusher: flushed Bridge0 conntrack and route cache.Фев 12 08:35:03 upnp shutting down MiniUPnPdФев 12 08:35:03 ndm Core::Session: client disconnected.Фев 12 08:35:05 ndm Core::Server: started Session /var/run/ndm.core.socket.Фев 12 08:35:05 upnp HTTP listening on port 50297Фев 12 08:35:05 upnp Listening for NAT-PMP/PCP traffic on port 5351Фев 12 08:35:19 kernel wireguard: Wireguard0: retrying handshake with peer "bmXOC+F1FxEMF9dyiK2H5/1SUtzH0JuVo51h2wPfgyo=" (2) (162.159.192.1:2408) because we stopped hearing back after 15 secondsФев 12 08:35:24 kernel wireguard: Wireguard0: handshake for peer "bmXOC+F1FxEMF9dyiK2H5/1SUtzH0JuVo51h2wPfgyo=" (2) (162.159.192.1:2408) did not complete after 5 seconds, retrying (try 2)Фев 12 08:35:29 kernel wireguard: Wireguard0: handshake for peer "bmXOC+F1FxEMF9dyiK2H5/1SUtzH0JuVo51h2wPfgyo=" (2) (162.159.192.1:2408) did not complete after 5 seconds, retrying (try 3)И так будет по кругуВыкл/вкл в WEB Wireguard********************************Фев 12 08:35:30 ndm Network::Interface::Base: "Wireguard0": interface is down.Фев 12 08:35:30 ndm Core::ConfigurationSaver: saving configuration...Фев 12 08:35:30 kernel wireguard: Wireguard0: peer "bmXOC+F1FxEMF9dyiK2H5/1SUtzH0JuVo51h2wPfgyo=" (2) (162.159.192.1:2408) destroyedФев 12 08:35:30 ndm Network::InterfaceFlusher: flushed Wireguard0 conntrack and route cache.Фев 12 08:35:30 upnp shutting down MiniUPnPdФев 12 08:35:30 ndm Core::Session: client disconnected.Фев 12 08:35:32 ndm Core::Server: started Session /var/run/ndm.core.socket.Фев 12 08:35:32 upnp HTTP listening on port 51895Фев 12 08:35:32 upnp Listening for NAT-PMP/PCP traffic on port 5351Фев 12 08:35:33 ndm Core::ConfigurationSaver: configuration saved.Фев 12 08:35:34 ndm Network::Interface::Base: "Wireguard0": interface is up.Фев 12 08:35:34 ndm Core::ConfigurationSaver: saving configuration...Фев 12 08:35:34 kernel wireguard: Wireguard0: peer "bmXOC+F1FxEMF9dyiK2H5/1SUtzH0JuVo51h2wPfgyo=" (3) createdФев 12 08:35:37 ndm Wireguard::Interface: "Wireguard0": unable to resolve peer "bmXOC+F1FxEMF9dyiK2H5/1SUtzH0JuVo51h2wPfgyo=" endpoint "engage.cloudflareclient.com".Фев 12 08:35:37 ndm Wireguard::Interface: "Wireguard0": endpoint "engage.cloudflareclient.com" is unavailable, schedule retry.Фев 12 08:35:37 ndm Wireguard::Interface: "Wireguard0": interface "Wireguard0" is global, priority 350.Фев 12 08:35:37 ndm Wireguard::Interface: "Wireguard0": adding default route via Wireguard0.Фев 12 08:35:38 ndm Core::ConfigurationSaver: configuration saved.Фев 12 08:35:38 ndm Network::InterfaceFlusher: flushed Bridge0 conntrack and route cache.Фев 12 08:35:38 upnp shutting down MiniUPnPdФев 12 08:35:38 ndm Core::Session: client disconnected.Фев 12 08:35:40 ndm Core::Server: started Session /var/run/ndm.core.socket.Фев 12 08:35:40 upnp HTTP listening on port 53425Фев 12 08:35:40 upnp Listening for NAT-PMP/PCP traffic on port 5351Фев 12 08:35:42 ndm Wireguard::Interface: "Wireguard0": added a host route to peer "bmXOC+F1FxEMF9dyiK2H5/1SUtzH0JuVo51h2wPfgyo=" (162.159.192.1) via 192.168.130.97 (Bridge0).Фев 12 08:35:57 ndm Network::InternetChecker: Internet access detected. -
Делал бегло выжимку по проблеме выше processes и thread все что не по 0/0/0/0
Скрытый текст<file name="proc:loadavg"> <![CDATA[ 3.69 3.32 1.63 1/124 10072 <!-- show processes --> <process> <name>ndm</name> <oom-adj>-16</oom-adj> <oom-score>0</oom-score> <oom-score-adj>-999</oom-score-adj> <state>S (sleeping)</state> <pid>247</pid> <ppid>1</ppid> <vm-size>40112 kB</vm-size> <vm-rss>17080 kB</vm-rss> <vm-data>22124 kB</vm-data> <vm-stk>132 kB</vm-stk> <vm-exe>4 kB</vm-exe> <vm-lib>17504 kB</vm-lib> <vm-swap>0 kB</vm-swap> <threads>38</threads> <fds>36</fds> <statistics> <interval>30</interval> <cpu> <now>280658.186009</now> <min>0</min> <max>42</max> <avg>12</avg> <cur>9</cur> </cpu> </statistics> </process> <process> <name>nginx: worker process</name> <oom-adj>-8</oom-adj> <oom-score>0</oom-score> <oom-score-adj>-500</oom-score-adj> <state>S (sleeping)</state> <pid>6526</pid> <ppid>541</ppid> <vm-size>8024 kB</vm-size> <vm-rss>2784 kB</vm-rss> <vm-data>2252 kB</vm-data> <vm-stk>132 kB</vm-stk> <vm-exe>1212 kB</vm-exe> <vm-lib>2940 kB</vm-lib> <vm-swap>0 kB</vm-swap> <threads>1</threads> <fds>26</fds> <statistics> <interval>30</interval> <cpu> <now>280658.186212</now> <min>0</min> <max>4</max> <avg>0</avg> <cur>0</cur> </cpu> </statistics> </process> <process> <name>kworker/1:2</name> <oom-adj>0</oom-adj> <oom-score>0</oom-score> <oom-score-adj>0</oom-score-adj> <state>S (sleeping)</state> <pid>8989</pid> <ppid>2</ppid> <threads>1</threads> <fds>0</fds> <statistics> <interval>30</interval> <cpu> <now>280658.186223</now> <min>0</min> <max>13</max> <avg>1</avg> <cur>0</cur> </cpu> </statistics> </process> <process> <name>kworker/0:1</name> <oom-adj>0</oom-adj> <oom-score>0</oom-score> <oom-score-adj>0</oom-score-adj> <state>S (sleeping)</state> <pid>9154</pid> <ppid>2</ppid> <threads>1</threads> <fds>0</fds> <statistics> <interval>30</interval> <cpu> <now>280658.186236</now> <min>0</min> <max>19</max> <avg>5</avg> <cur>1</cur> </cpu> </statistics> </process> <process> <name>kworker/3:0</name> <oom-adj>0</oom-adj> <oom-score>0</oom-score> <oom-score-adj>0</oom-score-adj> <state>S (sleeping)</state> <pid>9404</pid> <ppid>2</ppid> <threads>1</threads> <fds>0</fds> <statistics> <interval>30</interval> <cpu> <now>280658.186248</now> <min>0</min> <max>24</max> <avg>5</avg> <cur>0</cur> </cpu> </statistics> </process> <process> <name>kworker/2:2</name> <oom-adj>0</oom-adj> <oom-score>0</oom-score> <oom-score-adj>0</oom-score-adj> <state>S (sleeping)</state> <pid>9597</pid> <ppid>2</ppid> <threads>1</threads> <fds>0</fds> <statistics> <interval>30</interval> <cpu> <now>280658.186261</now> <min>0</min> <max>7</max> <avg>0</avg> <cur>0</cur> </cpu> </statistics> </process> <process> <name>kworker/2:0</name> <oom-adj>0</oom-adj> <oom-score>0</oom-score> <oom-score-adj>0</oom-score-adj> <state>S (sleeping)</state> <pid>9660</pid> <ppid>2</ppid> <threads>1</threads> <fds>0</fds> <statistics> <interval>30</interval> <cpu> <now>280658.186274</now> <min>0</min> <max>8</max> <avg>1</avg> <cur>0</cur> </cpu> </statistics> </process> <process> <name>kworker/3:2</name> <oom-adj>0</oom-adj> <oom-score>0</oom-score> <oom-score-adj>0</oom-score-adj> <state>S (sleeping)</state> <pid>9698</pid> <ppid>2</ppid> <threads>1</threads> <fds>0</fds> <statistics> <interval>30</interval> <cpu> <now>280658.186286</now> <min>0</min> <max>6</max> <avg>0</avg> <cur>0</cur> </cpu> </statistics> </process> <process> <name>kworker/2:3</name> <oom-adj>0</oom-adj> <oom-score>0</oom-score> <oom-score-adj>0</oom-score-adj> <state>S (sleeping)</state> <pid>9709</pid> <ppid>2</ppid> <threads>1</threads> <fds>0</fds> <statistics> <interval>30</interval> <cpu> <now>280658.186311</now> <min>0</min> <max>8</max> <avg>1</avg> <cur>0</cur> </cpu> </statistics> </process> <process> <name>kworker/0:2</name> <oom-adj>0</oom-adj> <oom-score>0</oom-score> <oom-score-adj>0</oom-score-adj> <state>S (sleeping)</state> <pid>9710</pid> <ppid>2</ppid> <threads>1</threads> <fds>0</fds> <statistics> <interval>30</interval> <cpu> <now>280658.186324</now> <min>0</min> <max>5</max> <avg>1</avg> <cur>0</cur> </cpu> </statistics> </process> <process> <name>kworker/1:3</name> <oom-adj>0</oom-adj> <oom-score>0</oom-score> <oom-score-adj>0</oom-score-adj> <state>S (sleeping)</state> <pid>9737</pid> <ppid>2</ppid> <threads>1</threads> <fds>0</fds> <statistics> <interval>30</interval> <cpu> <now>280658.186350</now> <min>0</min> <max>12</max> <avg>3</avg> <cur>0</cur> </cpu> </statistics> </process> <process> <name>kworker/0:0</name> <oom-adj>0</oom-adj> <oom-score>0</oom-score> <oom-score-adj>0</oom-score-adj> <state>S (sleeping)</state> <pid>9969</pid> <ppid>2</ppid> <threads>1</threads> <fds>0</fds> <statistics> <interval>30</interval> <cpu> <now>280658.186403</now> <min>0</min> <max>20</max> <avg>6</avg> <cur>0</cur> </cpu> </statistics> </process> <!-- show system --> <hostname>S-KN</hostname> <domainname>WORKGROUP</domainname> <cpuload>16</cpuload> <memory>74232/131072</memory> <swap>0/0</swap> <memtotal>131072</memtotal> <memfree>31984</memfree> <membuffers>9872</membuffers> <memcache>14984</memcache> <swaptotal>0</swaptotal> <swapfree>0</swapfree> <uptime>280658</uptime> <!-- show system cpustat --> <interval>54</interval> <busy> <cur>16</cur> <min>16</min> <max>87</max> <avg>58</avg> </busy> <user> <cur>2</cur> <min>0</min> <max>12</max> <avg>2</avg> </user> <nice> <cur>0</cur> <min>0</min> <max>0</max> <avg>0</avg> </nice> <system> <cur>13</cur> <min>13</min> <max>85</max> <avg>54</avg> </system> <iowait> <cur>4</cur> <min>0</min> <max>13</max> <avg>3</avg> </iowait> <irq> <cur>0</cur> <min>0</min> <max>0</max> <avg>0</avg> </irq> <sirq> <cur>0</cur> <min>0</min> <max>1</max> <avg>0</avg> </sirq> <!-- show threads --> <threads> <thread> <name>Syslog</name> <tid>250</tid> <lock_list_complete>yes</lock_list_complete> <locks/> <statistics> <interval>30</interval> <cpu> <now>280658.182042</now> <min>0</min> <max>2</max> <avg>0</avg> <cur>0</cur> </cpu> </statistics> </thread> <thread> <name>Internet checker</name> <tid>359</tid> <lock_list_complete>yes</lock_list_complete> <locks/> <statistics> <interval>30</interval> <cpu> <now>280658.182155</now> <min>0</min> <max>2</max> <avg>0</avg> <cur>0</cur> </cpu> </statistics> </thread> <thread> <name>Kernel neighbour netlink listener</name> <tid>358</tid> <lock_list_complete>yes</lock_list_complete> <locks/> <statistics> <interval>30</interval> <cpu> <now>280658.182146</now> <min>0</min> <max>2</max> <avg>0</avg> <cur>0</cur> </cpu> </statistics> </thread> <thread> <name>SCGI Session /var/run/ndm.scgi.socket</name> <tid>10068</tid> <lock_list_complete>yes</lock_list_complete> <locks/> <statistics> <interval>7</interval> <cpu> <now>280658.182327</now> <min>0</min> <max>23</max> <avg>6</avg> <cur>7</cur> </cpu> </statistics> </thread> <thread> <name>Feedback listener</name> <tid>364</tid> <lock_list_complete>yes</lock_list_complete> <locks/> <statistics> <interval>30</interval> <cpu> <now>280658.182186</now> <min>0</min> <max>3</max> <avg>0</avg> <cur>0</cur> </cpu> </statistics> </thread> <thread> <name>Cloud agent service</name> <tid>378</tid> <lock_list_complete>yes</lock_list_complete> <locks/> <statistics> <interval>30</interval> <cpu> <now>280658.182216</now> <min>0</min> <max>7</max> <avg>0</avg> <cur>0</cur> </cpu> </statistics> </thread> <thread> <name>Main task queue</name> <tid>252</tid> <lock_list_complete>yes</lock_list_complete> <locks> <lock> <precedence> <name>TASK_QUEUE_THREAD</name> <order>155</order> </precedence> <state>WAITING</state> <since>Feb 11 15:34:11</since> <duration>22.660662</duration> </lock> </locks> <statistics> <interval>30</interval> <cpu> <now>280658.182066</now> <min>0</min> <max>4</max> <avg>0</avg> <cur>0</cur> </cpu> </statistics> </thread> <thread> <name>Timer</name> <tid>251</tid> <lock_list_complete>yes</lock_list_complete> <locks> <lock> <precedence> <name>ALARM_QUEUE</name> <order>160</order> </precedence> <state>WAITING</state> <since>Feb 11 15:34:33</since> <duration>0.162482</duration> </lock> </locks> <statistics> <interval>30</interval> <cpu> <now>280658.182058</now> <min>0</min> <max>6</max> <avg>0</avg> <cur>0</cur> </cpu> </statistics> </thread> <thread> <name>Event sender</name> <tid>253</tid> <lock_list_complete>yes</lock_list_complete> <locks> <lock> <precedence> <name>EVENT_SENDER_QUEUE</name> <order>162</order> </precedence> <state>WAITING</state> <since>Feb 11 15:34:33</since> <duration>0.356465</duration> </lock> </locks> <statistics> <interval>30</interval> <cpu> <now>280658.182074</now> <min>0</min> <max>4</max> <avg>0</avg> <cur>0</cur> </cpu> </statistics> </thread> <thread> <name>Queue::QCNTFZTAYTFLGJHM::http/rci</name> <tid>9750</tid> <lock_list_complete>yes</lock_list_complete> <locks> <lock> <precedence> <name>TASK_QUEUE_THREAD</name> <order>155</order> </precedence> <state>WAITING</state> <since>Feb 11 15:34:33</since> <duration>0.356701</duration> </lock> </locks> <statistics> <interval>30</interval> <cpu> <now>280658.182310</now> <min>0</min> <max>19</max> <avg>5</avg> <cur>0</cur> </cpu> </statistics> </thread> </threads>
-
3 часа назад, Le ecureuil сказал:
Приложите self-test когда все "еле дышит".
Облегчил конф KN30 убрал все лишнее по клиентам но с тем же набором компонентов, повторил пять раз и проблема описанная выше не повторилась, конечно подъем WG дольше, чем просто выключить включить но WEB работал как и всегда в том же ритме.
Будем наблюдать, как только будет результат скину self.
-
На роутерах стоит 3.6 Beta 2 но было и ранее на 3.6.
На Kn3010 подключенный по LAN и режим "основной" поднят Wireguad на Cloudflare Warp все работает стандартно, но бывают моменты когда при
KN3010(LAN)-----(LAN)KN1810(PPPoe)----Интернет
роутер KN3010 входит в ступор, т.е. на нем WEB еле дышит страницы WEB могут не открываться или открываються через долгое время.
1. KN3010 WG поднят и работает.
2. На КN1810 перезагружаю интернет канал PPPoE несколько сек. и он поднят
3. В это время на KN3010 сделать практически не чего не возможно пока WG не станет активным, как только WG ОК то и WEB становиться ОК
Скрытый текстpeer "bmXOC+F1FxEMF9dyiK2H5/1SUtzH0JuVo51h2wPfgyo= 162.159.192.1:2408 для WG Cloudflare Warp [I] Feb 11 12:40:29 ndm: Netfilter::Util::Conntrack: flushed 14 IPv4 connections for 192.168.130.10. [I] Feb 11 15:26:34 kernel: wireguard: Wireguard0: retrying handshake with peer "bmXOC+F1FxEMF9dyiK2H5/1SUtzH0JuVo51h2wPfgyo=" (4) (162.159.192.1:2408) because we stopped hearing back after 15 seconds [I] Feb 11 15:26:39 kernel: wireguard: Wireguard0: handshake for peer "bmXOC+F1FxEMF9dyiK2H5/1SUtzH0JuVo51h2wPfgyo=" (4) (162.159.192.1:2408) did not complete after 5 seconds, retrying (try 2) [I] Feb 11 15:26:45 kernel: wireguard: Wireguard0: handshake for peer "bmXOC+F1FxEMF9dyiK2H5/1SUtzH0JuVo51h2wPfgyo=" (4) (162.159.192.1:2408) did not complete after 5 seconds, retrying (try 3) [I] Feb 11 15:26:49 kernel: wireguard: Wireguard0: retrying handshake with peer "bmXOC+F1FxEMF9dyiK2H5/1SUtzH0JuVo51h2wPfgyo=" (4) (162.159.192.1:2408) because we stopped hearing back after 15 seconds [I] Feb 11 15:26:50 kernel: wireguard: Wireguard0: handshake for peer "bmXOC+F1FxEMF9dyiK2H5/1SUtzH0JuVo51h2wPfgyo=" (4) (162.159.192.1:2408) did not complete after 5 seconds, retrying (try 2) [I] Feb 11 15:26:55 kernel: wireguard: Wireguard0: handshake for peer "bmXOC+F1FxEMF9dyiK2H5/1SUtzH0JuVo51h2wPfgyo=" (4) (162.159.192.1:2408) did not complete after 5 seconds, retrying (try 3) [I] Feb 11 15:26:58 ndm: Network::InternetChecker: Internet access lost (status: 0x0003). [I] Feb 11 15:27:01 kernel: wireguard: Wireguard0: handshake for peer "bmXOC+F1FxEMF9dyiK2H5/1SUtzH0JuVo51h2wPfgyo=" (4) (162.159.192.1:2408) did not complete after 5 seconds, retrying (try 4) [I] Feb 11 15:27:05 kernel: wireguard: Wireguard0: retrying handshake with peer "bmXOC+F1FxEMF9dyiK2H5/1SUtzH0JuVo51h2wPfgyo=" (4) (162.159.192.1:2408) because we stopped hearing back after 15 seconds [I] Feb 11 15:27:11 kernel: wireguard: Wireguard0: handshake for peer "bmXOC+F1FxEMF9dyiK2H5/1SUtzH0JuVo51h2wPfgyo=" (4) (162.159.192.1:2408) did not complete after 5 seconds, retrying (try 2) [I] Feb 11 15:27:16 kernel: wireguard: Wireguard0: handshake for peer "bmXOC+F1FxEMF9dyiK2H5/1SUtzH0JuVo51h2wPfgyo=" (4) (162.159.192.1:2408) did not complete after 5 seconds, retrying (try 2) [I] Feb 11 15:27:20 kernel: wireguard: Wireguard0: retrying handshake with peer "bmXOC+F1FxEMF9dyiK2H5/1SUtzH0JuVo51h2wPfgyo=" (4) (162.159.192.1:2408) because we stopped hearing back after 15 seconds [I] Feb 11 15:27:36 kernel: wireguard: Wireguard0: retrying handshake with peer "bmXOC+F1FxEMF9dyiK2H5/1SUtzH0JuVo51h2wPfgyo=" (4) (162.159.192.1:2408) because we stopped hearing back after 15 seconds [I] Feb 11 15:27:53 kernel: Core::Syslog: last message repeated 2 times. [I] Feb 11 15:27:58 kernel: wireguard: Wireguard0: handshake for peer "bmXOC+F1FxEMF9dyiK2H5/1SUtzH0JuVo51h2wPfgyo=" (4) (162.159.192.1:2408) did not complete after 5 seconds, retrying (try 2) [I] Feb 11 15:28:03 kernel: wireguard: Wireguard0: handshake for peer "bmXOC+F1FxEMF9dyiK2H5/1SUtzH0JuVo51h2wPfgyo=" (4) (162.159.192.1:2408) did not complete after 5 seconds, retrying (try 2) [I] Feb 11 15:28:06 ndm: Network::InterfaceFlusher: flushed Wireguard0 conntrack and route cache. [I] Feb 11 15:28:06 upnp: shutting down MiniUPnPd [I] Feb 11 15:28:06 ndm: Core::Session: client disconnected. [I] Feb 11 15:28:08 ndm: Core::Server: started Session /var/run/ndm.core.socket. [I] Feb 11 15:28:08 upnp: HTTP listening on port 52565 [I] Feb 11 15:28:08 upnp: Listening for NAT-PMP/PCP traffic on port 5351 [I] Feb 11 15:28:08 kernel: wireguard: Wireguard0: handshake for peer "bmXOC+F1FxEMF9dyiK2H5/1SUtzH0JuVo51h2wPfgyo=" (4) (162.159.192.1:2408) did not complete after 5 seconds, retrying (try 2) [I] Feb 11 15:28:12 ndm: Wireguard::Interface: "Wireguard0": interface "Wireguard0" is global, priority 350. [I] Feb 11 15:28:12 ndm: Wireguard::Interface: "Wireguard0": adding default route via Wireguard0. [I] Feb 11 15:28:12 ndm: Network::InterfaceFlusher: flushed Bridge0 conntrack and route cache. [I] Feb 11 15:28:12 upnp: shutting down MiniUPnPd [I] Feb 11 15:28:12 ndm: Core::Session: client disconnected. [I] Feb 11 15:28:14 ndm: Core::Server: started Session /var/run/ndm.core.socket. [I] Feb 11 15:28:14 upnp: HTTP listening on port 51699 [I] Feb 11 15:28:14 upnp: Listening for NAT-PMP/PCP traffic on port 5351 [I] Feb 11 15:28:28 kernel: wireguard: Wireguard0: retrying handshake with peer "bmXOC+F1FxEMF9dyiK2H5/1SUtzH0JuVo51h2wPfgyo=" (4) (162.159.192.1:2408) because we stopped hearing back after 15 seconds [I] Feb 11 15:28:33 kernel: wireguard: Wireguard0: handshake for peer "bmXOC+F1FxEMF9dyiK2H5/1SUtzH0JuVo51h2wPfgyo=" (4) (162.159.192.1:2408) did not complete after 5 seconds, retrying (try 2) [I] Feb 11 15:28:38 kernel: wireguard: Wireguard0: handshake for peer "bmXOC+F1FxEMF9dyiK2H5/1SUtzH0JuVo51h2wPfgyo=" (4) (162.159.192.1:2408) did not complete after 5 seconds, retrying (try 3) [E] Feb 11 15:28:42 ndm: Cloud::Agent: can not connect to the cloud server. [I] Feb 11 15:28:43 kernel: wireguard: Wireguard0: retrying handshake with peer "bmXOC+F1FxEMF9dyiK2H5/1SUtzH0JuVo51h2wPfgyo=" (4) (162.159.192.1:2408) because we stopped hearing back after 15 seconds [I] Feb 11 15:28:43 kernel: wireguard: Wireguard0: handshake for peer "bmXOC+F1FxEMF9dyiK2H5/1SUtzH0JuVo51h2wPfgyo=" (4) (162.159.192.1:2408) did not complete after 5 seconds, retrying (try 2) [I] Feb 11 15:28:49 kernel: wireguard: Wireguard0: handshake for peer "bmXOC+F1FxEMF9dyiK2H5/1SUtzH0JuVo51h2wPfgyo=" (4) (162.159.192.1:2408) did not complete after 5 seconds, retrying (try 3) [I] Feb 11 15:28:54 kernel: wireguard: Wireguard0: handshake for peer "bmXOC+F1FxEMF9dyiK2H5/1SUtzH0JuVo51h2wPfgyo=" (4) (162.159.192.1:2408) did not complete after 5 seconds, retrying (try 4) [I] Feb 11 15:28:58 kernel: wireguard: Wireguard0: retrying handshake with peer "bmXOC+F1FxEMF9dyiK2H5/1SUtzH0JuVo51h2wPfgyo=" (4) (162.159.192.1:2408) because we stopped hearing back after 15 seconds [I] Feb 11 15:28:59 kernel: wireguard: Wireguard0: handshake for peer "bmXOC+F1FxEMF9dyiK2H5/1SUtzH0JuVo51h2wPfgyo=" (4) (162.159.192.1:2408) did not complete after 5 seconds, retrying (try 2) [I] Feb 11 15:29:05 kernel: wireguard: Wireguard0: handshake for peer "bmXOC+F1FxEMF9dyiK2H5/1SUtzH0JuVo51h2wPfgyo=" (4) (162.159.192.1:2408) did not complete after 5 seconds, retrying (try 3) [I] Feb 11 15:29:10 kernel: wireguard: Wireguard0: handshake for peer "bmXOC+F1FxEMF9dyiK2H5/1SUtzH0JuVo51h2wPfgyo=" (4) (162.159.192.1:2408) did not complete after 5 seconds, retrying (try 4) [I] Feb 11 15:29:14 kernel: wireguard: Wireguard0: retrying handshake with peer "bmXOC+F1FxEMF9dyiK2H5/1SUtzH0JuVo51h2wPfgyo=" (4) (162.159.192.1:2408) because we stopped hearing back after 15 seconds [I] Feb 11 15:29:16 kernel: wireguard: Wireguard0: handshake for peer "bmXOC+F1FxEMF9dyiK2H5/1SUtzH0JuVo51h2wPfgyo=" (4) (162.159.192.1:2408) did not complete after 5 seconds, retrying (try 2) [I] Feb 11 15:29:21 kernel: wireguard: Wireguard0: handshake for peer "bmXOC+F1FxEMF9dyiK2H5/1SUtzH0JuVo51h2wPfgyo=" (4) (162.159.192.1:2408) did not complete after 5 seconds, retrying (try 3) [I] Feb 11 15:29:26 kernel: wireguard: Wireguard0: handshake for peer "bmXOC+F1FxEMF9dyiK2H5/1SUtzH0JuVo51h2wPfgyo=" (4) (162.159.192.1:2408) did not complete after 5 seconds, retrying (try 4) [I] Feb 11 15:29:29 kernel: wireguard: Wireguard0: retrying handshake with peer "bmXOC+F1FxEMF9dyiK2H5/1SUtzH0JuVo51h2wPfgyo=" (4) (162.159.192.1:2408) because we stopped hearing back after 15 seconds [I] Feb 11 15:29:31 kernel: wireguard: Wireguard0: handshake for peer "bmXOC+F1FxEMF9dyiK2H5/1SUtzH0JuVo51h2wPfgyo=" (4) (162.159.192.1:2408) did not complete after 5 seconds, retrying (try 2) [I] Feb 11 15:29:36 kernel: wireguard: Wireguard0: handshake for peer "bmXOC+F1FxEMF9dyiK2H5/1SUtzH0JuVo51h2wPfgyo=" (4) (162.159.192.1:2408) did not complete after 5 seconds, retrying (try 3) [I] Feb 11 15:29:42 kernel: wireguard: Wireguard0: handshake for peer "bmXOC+F1FxEMF9dyiK2H5/1SUtzH0JuVo51h2wPfgyo=" (4) (162.159.192.1:2408) did not complete after 5 seconds, retrying (try 4) [I] Feb 11 15:29:45 kernel: wireguard: Wireguard0: retrying handshake with peer "bmXOC+F1FxEMF9dyiK2H5/1SUtzH0JuVo51h2wPfgyo=" (4) (162.159.192.1:2408) because we stopped hearing back after 15 seconds [I] Feb 11 15:29:47 kernel: wireguard: Wireguard0: handshake for peer "bmXOC+F1FxEMF9dyiK2H5/1SUtzH0JuVo51h2wPfgyo=" (4) (162.159.192.1:2408) did not complete after 5 seconds, retrying (try 2) [I] Feb 11 15:29:52 kernel: wireguard: Wireguard0: handshake for peer "bmXOC+F1FxEMF9dyiK2H5/1SUtzH0JuVo51h2wPfgyo=" (4) (162.159.192.1:2408) did not complete after 5 seconds, retrying (try 3) [I] Feb 11 15:29:57 kernel: wireguard: Wireguard0: handshake for peer "bmXOC+F1FxEMF9dyiK2H5/1SUtzH0JuVo51h2wPfgyo=" (4) (162.159.192.1:2408) did not complete after 5 seconds, retrying (try 4) [I] Feb 11 15:30:00 kernel: wireguard: Wireguard0: retrying handshake with peer "bmXOC+F1FxEMF9dyiK2H5/1SUtzH0JuVo51h2wPfgyo=" (4) (162.159.192.1:2408) because we stopped hearing back after 15 seconds [I] Feb 11 15:30:03 kernel: wireguard: Wireguard0: handshake for peer "bmXOC+F1FxEMF9dyiK2H5/1SUtzH0JuVo51h2wPfgyo=" (4) (162.159.192.1:2408) did not complete after 5 seconds, retrying (try 2) [I] Feb 11 15:30:09 kernel: wireguard: Wireguard0: handshake for peer "bmXOC+F1FxEMF9dyiK2H5/1SUtzH0JuVo51h2wPfgyo=" (4) (162.159.192.1:2408) did not complete after 5 seconds, retrying (try 3) [I] Feb 11 15:30:15 kernel: wireguard: Wireguard0: retrying handshake with peer "bmXOC+F1FxEMF9dyiK2H5/1SUtzH0JuVo51h2wPfgyo=" (4) (162.159.192.1:2408) because we stopped hearing back after 15 seconds [I] Feb 11 15:31:01 kernel: Core::Syslog: last message repeated 3 times. [E] Feb 11 15:31:05 ndm: Core::Ndss: [9823] cannot connect to the server. [I] Feb 11 15:31:16 kernel: wireguard: Wireguard0: retrying handshake with peer "bmXOC+F1FxEMF9dyiK2H5/1SUtzH0JuVo51h2wPfgyo=" (4) (162.159.192.1:2408) because we stopped hearing back after 15 seconds [I] Feb 11 15:31:18 ndm: Network::InterfaceFlusher: flushed Wireguard0 conntrack and route cache. [I] Feb 11 15:31:18 upnp: shutting down MiniUPnPd [I] Feb 11 15:31:18 ndm: Core::Session: client disconnected. [I] Feb 11 15:31:19 kernel: wireguard: Wireguard0: handshake for peer "bmXOC+F1FxEMF9dyiK2H5/1SUtzH0JuVo51h2wPfgyo=" (4) (162.159.192.1:2408) did not complete after 5 seconds, retrying (try 2) [I] Feb 11 15:31:20 ndm: Core::Server: started Session /var/run/ndm.core.socket. [I] Feb 11 15:31:20 upnp: HTTP listening on port 51751 [I] Feb 11 15:31:20 upnp: Listening for NAT-PMP/PCP traffic on port 5351 [I] Feb 11 15:31:22 ndm: Wireguard::Interface: "Wireguard0": interface "Wireguard0" is global, priority 350. [I] Feb 11 15:31:22 ndm: Wireguard::Interface: "Wireguard0": adding default route via Wireguard0. [I] Feb 11 15:31:23 ndm: Network::InterfaceFlusher: flushed Bridge0 conntrack and route cache. [I] Feb 11 15:31:23 upnp: shutting down MiniUPnPd [I] Feb 11 15:31:23 ndm: Core::Session: client disconnected. [I] Feb 11 15:31:25 ndm: Core::Server: started Session /var/run/ndm.core.socket. [I] Feb 11 15:31:25 upnp: HTTP listening on port 50061 [I] Feb 11 15:31:25 upnp: Listening for NAT-PMP/PCP traffic on port 5351 [I] Feb 11 15:31:40 kernel: wireguard: Wireguard0: retrying handshake with peer "bmXOC+F1FxEMF9dyiK2H5/1SUtzH0JuVo51h2wPfgyo=" (4) (162.159.192.1:2408) because we stopped hearing back after 15 seconds [I] Feb 11 15:31:45 kernel: wireguard: Wireguard0: handshake for peer "bmXOC+F1FxEMF9dyiK2H5/1SUtzH0JuVo51h2wPfgyo=" (4) (162.159.192.1:2408) did not complete after 5 seconds, retrying (try 2) [I] Feb 11 15:31:51 kernel: wireguard: Wireguard0: handshake for peer "bmXOC+F1FxEMF9dyiK2H5/1SUtzH0JuVo51h2wPfgyo=" (4) (162.159.192.1:2408) did not complete after 5 seconds, retrying (try 3) [I] Feb 11 15:31:55 kernel: wireguard: Wireguard0: retrying handshake with peer "bmXOC+F1FxEMF9dyiK2H5/1SUtzH0JuVo51h2wPfgyo=" (4) (162.159.192.1:2408) because we stopped hearing back after 15 seconds [I] Feb 11 15:31:56 kernel: wireguard: Wireguard0: handshake for peer "bmXOC+F1FxEMF9dyiK2H5/1SUtzH0JuVo51h2wPfgyo=" (4) (162.159.192.1:2408) did not complete after 5 seconds, retrying (try 2) [I] Feb 11 15:32:01 kernel: wireguard: Wireguard0: handshake for peer "bmXOC+F1FxEMF9dyiK2H5/1SUtzH0JuVo51h2wPfgyo=" (4) (162.159.192.1:2408) did not complete after 5 seconds, retrying (try 3) [I] Feb 11 15:32:06 kernel: wireguard: Wireguard0: handshake for peer "bmXOC+F1FxEMF9dyiK2H5/1SUtzH0JuVo51h2wPfgyo=" (4) (162.159.192.1:2408) did not complete after 5 seconds, retrying (try 4) [I] Feb 11 15:32:11 kernel: wireguard: Wireguard0: retrying handshake with peer "bmXOC+F1FxEMF9dyiK2H5/1SUtzH0JuVo51h2wPfgyo=" (4) (162.159.192.1:2408) because we stopped hearing back after 15 seconds [I] Feb 11 15:32:12 kernel: wireguard: Wireguard0: handshake for peer "bmXOC+F1FxEMF9dyiK2H5/1SUtzH0JuVo51h2wPfgyo=" (4) (162.159.192.1:2408) did not complete after 5 seconds, retrying (try 2) [I] Feb 11 15:32:17 kernel: wireguard: Wireguard0: handshake for peer "bmXOC+F1FxEMF9dyiK2H5/1SUtzH0JuVo51h2wPfgyo=" (4) (162.159.192.1:2408) did not complete after 5 seconds, retrying (try 3) [I] Feb 11 15:32:24 kernel: wireguard: Wireguard0: handshake for peer "bmXOC+F1FxEMF9dyiK2H5/1SUtzH0JuVo51h2wPfgyo=" (4) (162.159.192.1:2408) did not complete after 5 seconds, retrying (try 4) [I] Feb 11 15:32:26 kernel: wireguard: Wireguard0: retrying handshake with peer "bmXOC+F1FxEMF9dyiK2H5/1SUtzH0JuVo51h2wPfgyo=" (4) (162.159.192.1:2408) because we stopped hearing back after 15 seconds [I] Feb 11 15:32:27 kernel: wireguard: Wireguard0: handshake for peer "bmXOC+F1FxEMF9dyiK2H5/1SUtzH0JuVo51h2wPfgyo=" (4) (162.159.192.1:2408) did not complete after 5 seconds, retrying (try 2) [I] Feb 11 15:32:33 kernel: wireguard: Wireguard0: handshake for peer "bmXOC+F1FxEMF9dyiK2H5/1SUtzH0JuVo51h2wPfgyo=" (4) (162.159.192.1:2408) did not complete after 5 seconds, retrying (try 3) [I] Feb 11 15:32:39 kernel: wireguard: Wireguard0: handshake for peer "bmXOC+F1FxEMF9dyiK2H5/1SUtzH0JuVo51h2wPfgyo=" (4) (162.159.192.1:2408) did not complete after 5 seconds, retrying (try 4) [I] Feb 11 15:32:42 kernel: wireguard: Wireguard0: retrying handshake with peer "bmXOC+F1FxEMF9dyiK2H5/1SUtzH0JuVo51h2wPfgyo=" (4) (162.159.192.1:2408) because we stopped hearing back after 15 seconds [I] Feb 11 15:32:43 kernel: wireguard: Wireguard0: handshake for peer "bmXOC+F1FxEMF9dyiK2H5/1SUtzH0JuVo51h2wPfgyo=" (4) (162.159.192.1:2408) did not complete after 5 seconds, retrying (try 2) [I] Feb 11 15:32:49 kernel: wireguard: Wireguard0: handshake for peer "bmXOC+F1FxEMF9dyiK2H5/1SUtzH0JuVo51h2wPfgyo=" (4) (162.159.192.1:2408) did not complete after 5 seconds, retrying (try 3) [I] Feb 11 15:32:54 kernel: wireguard: Wireguard0: handshake for peer "bmXOC+F1FxEMF9dyiK2H5/1SUtzH0JuVo51h2wPfgyo=" (4) (162.159.192.1:2408) did not complete after 5 seconds, retrying (try 4) [I] Feb 11 15:32:57 kernel: wireguard: Wireguard0: retrying handshake with peer "bmXOC+F1FxEMF9dyiK2H5/1SUtzH0JuVo51h2wPfgyo=" (4) (162.159.192.1:2408) because we stopped hearing back after 15 seconds [I] Feb 11 15:32:59 kernel: wireguard: Wireguard0: handshake for peer "bmXOC+F1FxEMF9dyiK2H5/1SUtzH0JuVo51h2wPfgyo=" (4) (162.159.192.1:2408) did not complete after 5 seconds, retrying (try 2) [I] Feb 11 15:33:05 kernel: wireguard: Wireguard0: handshake for peer "bmXOC+F1FxEMF9dyiK2H5/1SUtzH0JuVo51h2wPfgyo=" (4) (162.159.192.1:2408) did not complete after 5 seconds, retrying (try 3) [I] Feb 11 15:33:10 kernel: wireguard: Wireguard0: handshake for peer "bmXOC+F1FxEMF9dyiK2H5/1SUtzH0JuVo51h2wPfgyo=" (4) (162.159.192.1:2408) did not complete after 5 seconds, retrying (try 4) [I] Feb 11 15:33:12 kernel: wireguard: Wireguard0: retrying handshake with peer "bmXOC+F1FxEMF9dyiK2H5/1SUtzH0JuVo51h2wPfgyo=" (4) (162.159.192.1:2408) because we stopped hearing back after 15 seconds [I] Feb 11 15:33:15 kernel: wireguard: Wireguard0: handshake for peer "bmXOC+F1FxEMF9dyiK2H5/1SUtzH0JuVo51h2wPfgyo=" (4) (162.159.192.1:2408) did not complete after 5 seconds, retrying (try 2) [I] Feb 11 15:33:27 kernel: wireguard: Wireguard0: retrying handshake with peer "bmXOC+F1FxEMF9dyiK2H5/1SUtzH0JuVo51h2wPfgyo=" (4) (162.159.192.1:2408) because we stopped hearing back after 15 seconds [I] Feb 11 15:33:58 kernel: Core::Syslog: last message repeated 2 times. [E] Feb 11 15:34:09 ndm: Core::Ndss: [9957] cannot connect to the server. [I] Feb 11 15:34:13 kernel: wireguard: Wireguard0: retrying handshake with peer "bmXOC+F1FxEMF9dyiK2H5/1SUtzH0JuVo51h2wPfgyo=" (4) (162.159.192.1:2408) because we stopped hearing back after 15 seconds [I] Feb 11 15:34:21 kernel: wireguard: Wireguard0: handshake for peer "bmXOC+F1FxEMF9dyiK2H5/1SUtzH0JuVo51h2wPfgyo=" (4) (162.159.192.1:2408) did not complete after 5 seconds, retrying (try 2) [I] Feb 11 15:34:26 kernel: wireguard: Wireguard0: handshake for peer "bmXOC+F1FxEMF9dyiK2H5/1SUtzH0JuVo51h2wPfgyo=" (4) (162.159.192.1:2408) did not complete after 5 seconds, retrying (try 2)
Можно конечно подумать что это на другой стороне дурит но если на KN3010 сделать выкл. WG а потом включить его в 15:47 то проблем с подъемом нет
[I] Feb 11 15:46:24 ndm: Core::ConfigurationSaver: configuration saved. [I] Feb 11 15:46:33 ndm: Network::InternetChecker: Internet access detected. [I] Feb 11 15:46:55 ndm: Network::Interface::Base: "Wireguard0": interface is up. [I] Feb 11 15:46:55 ndm: Core::ConfigurationSaver: saving configuration... [I] Feb 11 15:46:55 kernel: wireguard: Wireguard0: peer "bmXOC+F1FxEMF9dyiK2H5/1SUtzH0JuVo51h2wPfgyo=" (5) created [I] Feb 11 15:46:56 ndm: Wireguard::Interface: "Wireguard0": added a host route to peer "bmXOC+F1FxEMF9dyiK2H5/1SUtzH0JuVo51h2wPfgyo=" (162.159.192.1) via 192.168.130.97 (Bridge0). [I] Feb 11 15:46:56 ndm: Wireguard::Interface: "Wireguard0": interface "Wireguard0" is global, priority 350. [I] Feb 11 15:46:56 ndm: Wireguard::Interface: "Wireguard0": adding default route via Wireguard0. [I] Feb 11 15:46:57 ndm: Network::InterfaceFlusher: flushed Bridge0 conntrack and route cache. [I] Feb 11 15:46:57 upnp: shutting down MiniUPnPd [I] Feb 11 15:46:57 ndm: Core::Session: client disconnected. [I] Feb 11 15:46:58 ndm: Core::ConfigurationSaver: configuration saved. [I] Feb 11 15:46:59 ndm: Core::Server: started Session /var/run/ndm.core.socket. [I] Feb 11 15:46:59 upnp: HTTP listening on port 50883 [I] Feb 11 15:46:59 upnp: Listening for NAT-PMP/PCP traffic on port 5351
Так можно делать сколько угодно, будет все ОК.
В момент проблемы описанной выше по монитору KN3010 заметил передачу с него на KN1810 под весь поток канала интернета KN1810 (он 100Мбит)
На KN3010 для работы в таком режиме только
interface Wireguard0 description Cloud-warp security-level public ip address 10.16.16.98 255.255.255.0 ip mtu 1324 ip global 350 ip tcp adjust-mss pmtu wireguard listen-port ххххх wireguard peer bmXOC+F1FxEMF9dyiK2H5/1SUtzH0JuVo51h2wPfgyo= !Cloudflare-warp endpoint engage.cloudflareclient.com:2408 keepalive-interval 30 allow-ips 0.0.0.0 0.0.0.0 allow-ips 10.16.16.0 255.255.255.0 ip route default 192.168.130.97 Home ip name-server 192.168.130.97 "" on Home
KN1810 - 192.168.130.97
Такое же поведение наблюдал на самом KN1810 при передергивание PPPoE при поднятом WG - WEB роутера входил в ступор. При простом же переключение (вкл/выкл) WG все моментально.
-
Тут есть маленькая ремарка с которой нужно считаться
Выдержки ниже
И как итог
Скрытый текстisolate-private interface GigabitEthernet0/Vlan3 description "Guest VLAN" security-level protected .... up ! interface GigabitEthernet1 (родной WAN порт, отключенный) rename ISP description "Broadband connection" mac address factory wan security-level public .... ip global 700 down interface Bridge0 rename Home description "Home Lan" .... security-level private interface Bridge1 description Guest ..... security-level protected
- 1
-
10 часов назад, Василий Залукаев сказал:
Суть такая, есть сеть с локальными ресурсами. Туда воткнут city. Надо по кабелю и по wifi передать эту сеть дальше. Это режим Точка доступа/Ретранслятор. Проблем не возникло. Но есть потребность - часть пользователей надо подключить по wifi в отдельную сеть чтобы им выдавались там свои ip адреса и основным шлюзом для них был city чтобы они могли получать инет. Как я понял функционала роутинга (NAT) в режиме AP у кинетиков нет. Да и даже dhcp сервера в таком раскладе не поднять. Я попробовал удалить интерфейс "провайдер", все загнал в "домашнюю сеть", создал "гостевую сеть", все "так" как я хочу, по проводу и по wifi у части клиентов локальные ip адреса, у части "гостевые", им выдаются шлюз гостевой ip роутера, DNS, но роутинга нет. Я не могу для гостевой сети создать маршрут в основным шлюзом к примеру локальным ip роутера, или шлюза локальной сети. Поле становится красным и не дает сохранить. На микротике 3 раза мышкой клацнуть, даже на ростелекомовском роутере это на изи сделать просто нажав "изолировать сеть" и все прекрасно работает (перевел его в АП просто удалив все варианты WAN подключений, но и с ними бы работало). У зухеля же выходит только когда он в режиме роутер и все его клиенты находятся за NAT. ВОзможно ли такое сделать? Спасибо.
Вопрос а зачем его переводить в Точка доступа/Ретранслятор, что мешает его использовать в режиме "Основной" подключив его по LAN, так принципиально название или потратить 5мин для настройки того что нужно.
Режим Точка доступа/Ретранслятор - пере конфигурация сетевых интерфейсов, не загружать не нужные службы и прописать нужный маршрут.
а микротике 3 раза мышкой клацнуть, даже на ростелекомовском роутере это на изи сделать просто нажав "изолировать сеть" и все прекрасно работает (перевел его в АП просто удалив все варианты WAN подключений, но и с ними бы работало). У зухеля же выходит только когда он в режиме роутер и все его клиенты находятся за NAT. ВОзможно ли такое сделать?
Ставите его в основной режим, как и сказали отключить WAN + прописать маршрут по умолчанию и DNS => и делайте что хотите на нем.
-
В наличие 36B2 и настроено schedule2 на работу с wifi 5 на KN1810
schedule schedule2 description 50work action start 0 7 * action stop 0 22 * interface WifiMaster1/AccessPoint0 up schedule schedule2
Вопрос какое отношение TSMB может иметь к данному расписанию по вкл/выкл Wifi
Скрытый текст[I] Feb 6 22:00:00 ndm: Network::Interface::Base: "WifiMaster1/AccessPoint0": disabled by "schedule2". [I] Feb 6 22:00:03 kernel: TSMB module stopped. [I] Feb 6 22:00:05 kernel: TSMB module version 3020.9.24.3 started from process 20312! [I] Feb 6 22:00:09 ndm: Cifs::ServerTsmb: service started. [I] Feb 7 22:00:00 kernel: br0: port 4(rai0) entered disabled state [I] Feb 7 22:00:00 ndm: Network::Interface::Base: "WifiMaster1/AccessPoint0": disabled by "schedule2". [I] Feb 7 22:00:02 kernel: TSMB module stopped. [I] Feb 7 22:00:04 kernel: TSMB module version 3020.9.24.3 started from process 21437! [I] Feb 7 22:00:09 ndm: Cifs::ServerTsmb: service started. [I] Feb 8 07:00:00 kernel: IPv6: ADDRCONF(NETDEV_UP): rai0: link is not ready [I] Feb 8 07:00:00 kernel: IPv6: ADDRCONF(NETDEV_CHANGE): rai0: link becomes ready [I] Feb 8 07:00:00 kernel: br0: port 4(rai0) entered blocking state [I] Feb 8 07:00:00 kernel: br0: port 4(rai0) entered forwarding state [I] Feb 8 07:00:00 ndm: Network::Interface::Base: "WifiMaster1/AccessPoint0": enabled by "schedule2". [I] Feb 8 07:00:03 kernel: TSMB module stopped. [I] Feb 8 07:00:05 kernel: TSMB module version 3020.9.24.3 started from process 32034! [I] Feb 8 07:00:09 ndm: Cifs::ServerTsmb: service started.
-
42 минуты назад, ant101 сказал:
Добрый день.
Не могу удалить (уже пустую) папку на примонтированной USB флешке.
Пробовал через Веб_интерфейс или через FTP клиента - в логе одинаковое сообщение что папка не пустая.
Пробовал разными пользователями.
Как удалить папку?
Спасибо.ncftp /Old > ls -la
drwx------ 1 root 1000 4096 Feb 7 18:32 .
drwx------ 1 root 1000 4096 Feb 7 18:32 ..
drwx------ 1 root 1000 4096 Feb 7 18:03 Big2
ncftp /Old > ls -al Big2/
drwx------ 1 root 1000 4096 Feb 7 18:03 .
drwx------ 1 root 1000 4096 Feb 7 18:03 ..
ncftp /Old >Не вижу проблем
Скрытый текст/opt/home # cd Anti /opt/home/Anti # ls -l -rw-r--r-- 1 root root 1267 Mar 19 2020 unblock.txt -rwxr-xr-x 1 root root 983 Mar 19 2020 unblock_ipset.sh /opt/home/Anti # cd .. /opt/home # ls -l drwxr-xr-x 3 root root 1024 Feb 3 09:29 AdGuard drwxr-xr-x 2 root root 1024 Mar 19 2020 Anti drwxr-xr-x 2 root root 1024 Nov 28 15:13 NextDns drwxr-xr-x 2 root root 1024 Jan 13 11:52 WG drwxr-xr-x 2 root root 1024 Dec 8 12:06 Warp drwxr-xr-x 2 root root 1024 Jan 11 13:32 ZMP drwxr-xr-x 2 root root 1024 Mar 29 2019 blocklists -rw------- 1 root root 328 Mar 29 2019 dht.dat drwxr-xr-x 2 root root 1024 Dec 25 2019 download drwxr-xr-x 3 root root 1024 Aug 3 2020 keenetic-grafana-monitoring -rwxr-xr-x 1 root root 496 Mar 6 2020 proba_cam drwxr-xr-x 2 root root 1024 Mar 29 2019 resume -rw------- 1 root root 2403 Mar 29 2019 settings.json -rw------- 1 root root 137 Mar 29 2019 stats.json -rw-r--r-- 1 root root 8610451 Sep 16 11:44 syncthing_1.6.0-rc.5-1_mipsel-3.4.ipk drwxr-xr-x 2 root root 1024 Mar 29 2019 torrents drwxr-xr-x 2 root root 1024 Mar 29 2019 watch drwxr-xr-x 2 root root 1024 Dec 30 18:11 А70 /opt/home # rm -r Anti /орt/home #
-
15 часов назад, kamikadze69 сказал:
что это означает?
Скрытый текст3.24.2 dns-proxy intercept enable Описание Включить перехват DNS-запросов. По умолчанию настройка включена. Команда с префиксом no отключает перехват. (config-dnspx)> intercept enable (config-dnspx)> no intercept enable 3.06 Добавлена команда dns-proxy intercept enable.
- 2
-
В 08.01.2021 в 17:41, keenet07 сказал:
Если второй роутер в локалке. Если он достаточно продвинутый, как кинетик и на нем можно запустить какой-нибудь VPN сервер с открытым NAT. А потом с вашего кинетика подключиться к этому серверу в качестве клиента и когда на вашем интернета не будет с помощью правил маршрутизации пустить весь трафик сквозь VPN туннель. Может быть даже удастся его настроить в качестве резервного канала, чтоб автоматом переключал. Не знаю, возможно в этой схеме потребуются ещё какие-то доработки со стороны программистов Кинетика. Пробуйте!
Есть KN3010 (режим основной) подключен по LAN к основному роутеру, WAN выключен ну т.е. интернета на нем нет NAT ни какого (только LAN), по умолчанию маршрут и DNS на основной в лок.сети.
На нем KN30 поднят Cloud-warp на базе WireGuard и даже "Доменное имя" хххх.keenetic.pro через облако и доступ из интернета. Есть клиенты которые имеют в качестве шлюза/DNS адрес KN30 и проблем на нем как и у клиентов нет.
Если заместо KN30 будет какой либо другой то все должно работать. Была когда то схема "Клиент---Роутер--LAN--Keenetic---Интернет"
-
9 часов назад, Sorrel сказал:
Уже в бетатест прошивка перетекает, 3.6 Beta 0, а описанная проблема с места так и не сдвинулась. Если к релизу не поправят, можно ждать оправданный хейт со стороны пользователей, на уровне как было с проблемой сваливания в 40мгц вайфая в релизе 3.5.1. Аналогично все жаловались в бетатестировании, но надо было дотащить проблему до релиза. Тут думаю так же будет 🤷♂️
PS. Проблемы с пингом описанные в шапке пропали, все остальное без изменений.
Auto-negotiation, но скорость соединения с провайдером снизилась с 700мб по тарифу (3.4/3.5 выдавали даже больше этого значения +- 730, полный дуплекс 1000мбит), до значений 400-550мбит.
Как Auto-negotiation может влиять на скорость 700Мбит или 500Мбит если он
Auto-Negotiation - автоматическое определение типа сети 1000Мбит или 100Мбит.
На скорость сети может влиять так сказать управление сетевыми заторами например Explicit Congestion Notification (ECN). Алгоритмы работы позволяют уведомлять сетевые устройства о заторе в сети без необходимости отбрасывания пакетов. В работе ECN принимают участие два устройства, т.е. на обоих концах источник и приемник используют TCP с ECN.
Данный механизм так же использует например Windows - контроль перегрузки CTCP и уведомления о перегрузки ECN (
netsh interface tcp ....)
Как то встречал на
На стороне Keenetic есть такой параметр как - "flow-control" для портов switch. В seltest он есть
Скрытый текст<interface name="0"> <id>GigabitEthernet1/0</id> <index>0</index> <interface-name>0</interface-name> .... <flow-control>off</flow-control> .... </interface> Это WAN порт <port name="3"> <id>GigabitEthernet0/2</id> <index>2</index> <interface-name>3</interface-name> .... <flow-control>on</flow-control> .... </port> Это LAN порт
Или команда в 192.168.1.1/а и набрать "show interface GigabitEthernet1/0"
Но не забываем и про клиента Windows на его стороне управление сетевой - свойства сетевой
-
Есть небольшая путаница при отображение WEB тек.состояния каналов "вторичных" VPN, т.е. каналов которые подняты на основе интернет канала.
Например на одном единственном канале Интернет (значение основной) на нем поднят VPN WG и получил значение резервный (данный канал к резерву ни какого отношения не имеет. Резервный более правильное отношение если есть второй например канал Интернета или 4G канал). Так же при пропадание основного канала при описанной схеме выше, происходит переключение резервного канала VPN WG на основной и потом при восстановление основного переключение обратно.
Данная информация в WEB не напрягает, но возможно ли изменить данное отображение по отношению к "вторичным" каналам VPN про которые идет речь, назвать их по другому не резервными. Например если согласно скрина то около надписи RT какой-то значек о наличие поднятого на данном канале еще одного, саму же информацию спрятать в раздел Подробнее о соединении или еще одна строка Подробное о соединении VPN. Как то так или может еще лучше.
-
Второй вариант запуска если Keenetic подключен в качестве второго роутера но по LAN сети.
-
Схема
Интернет---KN1---LAN---KN2---LAN---ПК
KN2 в режиме основного роутера соединен с KN1 через LAN порты, на нем на KN2 поднят WG Cloudflare warp, на клиенте установлен IP шлюза KN2 в итоге все запустилось, да и странно было бы если бы не запустилось.
Скрытый текстSpeedtest на клиенте ПК
<file name="proc:net/dev"> <![CDATA[ Inter-| Receive | Transmit face |bytes packets errs drop fifo frame compressed multicast|bytes packets errs drop fifo colls carrier compressed ... lo: 506651 10078 0 0 0 0 0 0 506651 10078 0 0 0 0 0 0 apcli0: 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 eth2: 416040199 860757 0 0 0 0 0 92926 453206989 836736 0 0 0 0 0 0 eth2.3: 0 0 0 0 0 0 0 0 738 7 0 0 0 0 0 0 ... eth3: 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 nwg0: 175624841 189601 0 0 0 0 0 0 175697452 225425 0 0 0 0 0 0 eth2.1: 396663317 786079 0 4 0 0 0 92926 440251357 789510 0 0 0 0 0 0 br0: 396629625 785898 0 0 0 0 0 92787 429197769 789505 0 0 0 0 0 0 ... Hosts: idx: 28, addr: 10.16.132.98, mask: 255.255.255.0, subnet: 10.16.132.0, seclevel: 3, local: 0 idx: 25, addr: 192.168.130.98, mask: 0.0.0.0, subnet: 0.0.0.0, seclevel: 1, local: 1 idx: 24, addr: 0.0.0.0, mask: 0.0.0.0, subnet: 0.0.0.0, seclevel: 2, local: 0 idx: 23, addr: 0.0.0.0, mask: 0.0.0.0, subnet: 0.0.0.0, seclevel: 1, local: 0
-
2 часа назад, r777ay сказал:
Мне не разу не удалось запустить CF Warp при помощи Web Privat Key Поэтому меня удивил ваш пост , однако у вас работало.
И сейчас работает, перенос ключа "PrivateKey" из "wgcf_2.1.4_linux_mipsle_softfloat generate" в Web.
-
Решил вопрос пересозданием ключа заново, только не в WEB роутера а из https://github.com/ViRb3/wgcf/releases
для wgcf_2.1.4_linux_mipsle_softfloat
Скрытый текст/opt/home/Warp # ls wgcf-account.toml wgcf-profile.conf wgcf_2.1.4_linux_mips_softfloat wgcf_2.1.4_linux_mipsle_softfloat /opt/home/Warp # ./wgcf_2.1.4_linux_mipsle_softfloat 2021/01/11 09:17:58 Using config file: wgcf-account.toml wgcf is a utility for Cloudflare Warp that allows you to create and manage accounts, assign license keys, and generate WireGuard profiles. Made by Victor (@ViRb3). Project website: https://github.com/ViRb3/wgcf Usage: wgcf [flags] wgcf [command] Available Commands: generate Generates a WireGuard profile from the current Cloudflare Warp account help Help about any command register Registers a new Cloudflare Warp device and creates a new account, preparing it for connection status Prints the status of the current Cloudflare Warp device trace Prints trace information about the current internet connection update Updates the current Cloudflare Warp account, preparing it for connection Flags: --config string Configuration file (default "wgcf-account.toml") -h, --help help for wgcf Use "wgcf [command] --help" for more information about a command. /opt/home/Warp # /opt/home/Warp # ./wgcf_2.1.4_linux_mipsle_softfloat generate 2021/01/11 09:18:46 Using config file: wgcf-account.toml 2021/01/11 09:18:48 ======================================= 2021/01/11 09:18:48 Device name : 157874 2021/01/11 09:18:48 Device model : PC 2021/01/11 09:18:48 Device active : true 2021/01/11 09:18:48 Account type : free 2021/01/11 09:18:48 Role : child 2021/01/11 09:18:48 Premium data : 0.000000 2021/01/11 09:18:48 Quota : 0.000000 2021/01/11 09:18:48 ======================================= 2021/01/11 09:18:48 Successfully generated WireGuard profile: wgcf-profile.conf /opt/home/Warp #
Файл wgcf-profile.conf, нужный параметр "PrivateKey" подставил в WEB
[Interface] PrivateKey = mOe........UU= Address = 172.16.0.2/32 Address = fd01:5ca1:ab1e:856b:cb0e:178a:ae79:f716/128 DNS = 1.1.1.1 MTU = 1280 [Peer] PublicKey = bmXOC+F1FxEMF9dyiK2H5/1SUtzH0JuVo51h2wPfgyo= AllowedIPs = 0.0.0.0/0 AllowedIPs = ::/0 Endpoint = engage.cloudflareclient.com:2408
параметры Adress и DNS подставил свои.
Так же запустилось и на втором роутере при установке ключа "PrivateKey" из "wgcf_2.1.4_linux_mipsle_softfloat generate" файл "wgcf-profile.conf"
-
После не продолжительной работы wireguard на роутере с Cloudflare warp c начала декабря 2020 и ПО 3.6.А.10 по 3.6.А.14 работало (как бы) но после обновления 3.6.А.15 перестал но не сразу. Так де не получилось днем ранее на 3.6.А.15 KN1010 поднять вообще (ошибка нет приема). Месяц удачного использования, как то странно.
На ПК при установленном ПО пока работает (дата установки такая же как и на роутере) сервис Cloudflare warp или же обычный WG на ПК с сервисом Cloudflare warp.
По логам
Скрытый текстЯнв 11 09:42:06 kernel wireguard: Wireguard2: handshake for peer "bmXOC+F1FxEMF9dyiK2H5/1SUtzH0JuVo51h2wPfgyo=" (4) (162.159.192.1:2408) did not complete after 5 seconds, retrying (try 6) Янв 11 09:42:11 kernel wireguard: Wireguard2: handshake for peer "bmXOC+F1FxEMF9dyiK2H5/1SUtzH0JuVo51h2wPfgyo=" (4) (162.159.192.1:2408) did not complete after 5 seconds, retrying (try 7) Янв 11 09:42:16 kernel wireguard: Wireguard2: handshake for peer "bmXOC+F1FxEMF9dyiK2H5/1SUtzH0JuVo51h2wPfgyo=" (4) (162.159.192.1:2408) did not complete after 5 seconds, retrying (try 8) Янв 11 09:42:22 kernel wireguard: Wireguard2: handshake for peer "bmXOC+F1FxEMF9dyiK2H5/1SUtzH0JuVo51h2wPfgyo=" (4) (162.159.192.1:2408) did not complete after 5 seconds, retrying (try 9) Янв 11 09:42:27 kernel wireguard: Wireguard2: handshake for peer "bmXOC+F1FxEMF9dyiK2H5/1SUtzH0JuVo51h2wPfgyo=" (4) (162.159.192.1:2408) did not complete after 5 seconds, retrying (try 10) Янв 11 09:42:32 kernel wireguard: Wireguard2: handshake for peer "bmXOC+F1FxEMF9dyiK2H5/1SUtzH0JuVo51h2wPfgyo=" (4) (162.159.192.1:2408) did not complete after 5 seconds, retrying (try 11) Янв 11 09:42:38 kernel wireguard: Wireguard2: handshake for peer "bmXOC+F1FxEMF9dyiK2H5/1SUtzH0JuVo51h2wPfgyo=" (4) (162.159.192.1:2408) did not complete after 5 seconds, retrying (try 12) Янв 11 09:42:43 kernel wireguard: Wireguard2: handshake for peer "bmXOC+F1FxEMF9dyiK2H5/1SUtzH0JuVo51h2wPfgyo=" (4) (162.159.192.1:2408) did not complete after 5 seconds, retrying (try 13) Янв 11 09:42:48 kernel wireguard: Wireguard2: handshake for peer "bmXOC+F1FxEMF9dyiK2H5/1SUtzH0JuVo51h2wPfgyo=" (4) (162.159.192.1:2408) did not complete after 5 seconds, retrying (try 14) Янв 11 09:42:53 kernel wireguard: Wireguard2: handshake for peer "bmXOC+F1FxEMF9dyiK2H5/1SUtzH0JuVo51h2wPfgyo=" (4) (162.159.192.1:2408) did not complete after 5 seconds, retrying (try 15) Янв 11 09:42:59 kernel wireguard: Wireguard2: handshake for peer "bmXOC+F1FxEMF9dyiK2H5/1SUtzH0JuVo51h2wPfgyo=" (4) (162.159.192.1:2408) did not complete after 5 seconds, retrying (try 16) Янв 11 09:43:04 kernel wireguard: Wireguard2: handshake for peer "bmXOC+F1FxEMF9dyiK2H5/1SUtzH0JuVo51h2wPfgyo=" (4) (162.159.192.1:2408) did not complete after 5 seconds, retrying (try 17) Янв 11 09:43:09 kernel wireguard: Wireguard2: handshake for peer "bmXOC+F1FxEMF9dyiK2H5/1SUtzH0JuVo51h2wPfgyo=" (4) (162.159.192.1:2408) did not complete after 5 seconds, retrying (try 18) Янв 11 09:43:14 kernel wireguard: Wireguard2: handshake for peer "bmXOC+F1FxEMF9dyiK2H5/1SUtzH0JuVo51h2wPfgyo=" (4) (162.159.192.1:2408) did not complete after 5 seconds, retrying (try 19) Янв 11 09:43:20 kernel wireguard: Wireguard2: handshake for peer "bmXOC+F1FxEMF9dyiK2H5/1SUtzH0JuVo51h2wPfgyo=" (4) (162.159.192.1:2408) did not complete after 5 seconds, retrying (try 20) Янв 11 09:43:25 kernel wireguard: Wireguard2: handshake for peer "bmXOC+F1FxEMF9dyiK2H5/1SUtzH0JuVo51h2wPfgyo=" (4) (162.159.192.1:2408) did not complete after 20 attempts, giving up Янв 11 09:44:37 ndm Wireguard::Interface: "Wireguard2": peer "bmXOC+F1FxEMF9dyiK2H5/1SUtzH0JuVo51h2wPfgyo=" went offline, update configuration. Янв 11 09:45:45 kernel wireguard: Wireguard2: zeroing out all keys for peer "bmXOC+F1FxEMF9dyiK2H5/1SUtzH0JuVo51h2wPfgyo=" (4) (162.159.192.1:2408), since we haven't received a new one in 540 seconds Янв 11 09:47:42 ndm Wireguard::Interface: "Wireguard2": peer "bmXOC+F1FxEMF9dyiK2H5/1SUtzH0JuVo51h2wPfgyo=" went offline, update configuration. Янв 11 09:48:34 kernel wireguard: Wireguard2: handshake for peer "bmXOC+F1FxEMF9dyiK2H5/1SUtzH0JuVo51h2wPfgyo=" (4) (162.159.192.1:2408) did not complete after 5 seconds, retrying (try 2) Янв 11 09:48:40 kernel wireguard: Wireguard2: handshake for peer "bmXOC+F1FxEMF9dyiK2H5/1SUtzH0JuVo51h2wPfgyo=" (4) (162.159.192.1:2408) did not complete after 5 seconds, retrying (try 3) Янв 11 09:48:45 kernel wireguard: Wireguard2: handshake for peer "bmXOC+F1FxEMF9dyiK2H5/1SUtzH0JuVo51h2wPfgyo=" (4) (162.159.192.1:2408) did not complete after 5 seconds, retrying (try 4) Янв 11 09:48:50 kernel wireguard: Wireguard2: handshake for peer "bmXOC+F1FxEMF9dyiK2H5/1SUtzH0JuVo51h2wPfgyo=" (4) (162.159.192.1:2408) did not complete after 5 seconds, retrying (try 5) Янв 11 09:48:56 kernel wireguard: Wireguard2: handshake for peer "bmXOC+F1FxEMF9dyiK2H5/1SUtzH0JuVo51h2wPfgyo=" (4) (162.159.192.1:2408) did not complete after 5 seconds, retrying (try 6)
по конф файлу который с самого начала
! access-list _WEBADMIN_Wireguard2 permit ip 0.0.0.0 0.0.0.0 0.0.0.0 0.0.0.0 permit description Cloud-local isolate-private interface Wireguard2 description warp security-level public ip address 10.16.132.97 255.255.255.255 ip mtu 1324 ip access-group _WEBADMIN_Wireguard2 in ip global 7178 ip tcp adjust-mss pmtu wireguard peer bmXOC+F1FxEMF9dyiK2H5/1SUtzH0JuVo51h2wPfgyo= !cloudwarp endpoint engage.cloudflareclient.com:2408 keepalive-interval 300 allow-ips 0.0.0.0 0.0.0.0 allow-ips 10.16.132.0 255.255.255.0 ! up ip name-server 192.168.130.97 "" on Home ip name-server 192.168.130.97 "" on Wireguard2 ip policy Policy0 description Inet-2 permit global Wireguard2 no permit global PPPoE0
show ip hotspot: Отсутсвует ключ link для устройств подключенных через промежуточные кинетики
in 3.6
Posted
ПК --- LAN --- KN30 --- LAN --- KN18
Все на месте у клиента который подключен к KN30 проводом, "show ip hotspot" на KN18
"host": [ ... "mac": "50:хх:хх:хх:хх:6b", "via": "50:хх:хх:хх:хх:6b", "ip": "192.168.1.9", "hostname": "", "name": "S-KN", "system-mode": "router", "interface": { "id": "Bridge0", "name": "Home", "description": "Home Lan" }, "registered": true, "access": "permit", "schedule": "", "active": true, "rxbytes": 219926917, "txbytes": 43143617, "uptime": 125292, "first-seen": 125848, "last-seen": 1, "link": "up", "auto-negotiation": true, "speed": 1000, "duplex": true, "port": "3", "http-port": 80, "description": "Keenetic Speedster (NDMS 3.06.B.3.0-0): KN-3010", "firmware": "3.06.B.3.0-0", "traffic-shape": { "rx": 0, "tx": 0, "mode": "mac", "schedule": "" }, "mac-access": { "Bridge0": "permit" } }, { "mac": "70:хх:хх:хх:хх:e2", "via": "70:хх:хх:хх:хх:e2", "ip": "192.168.1.2", - клиент через S-KN "hostname": "", "name": "PS", "interface": { "id": "Bridge0", "name": "Home", "description": "Home Lan" }, "registered": true, "access": "permit", "schedule": "", "active": true, "rxbytes": 501769416, "txbytes": 39988026, "uptime": 637, "first-seen": 125848, "last-seen": 1, "link": "up", "auto-negotiation": true, "speed": 1000, "duplex": true, "port": "3", "traffic-shape": { "rx": 0, "tx": 0, "mode": "mac", "schedule": "" }, "mac-access": { "Bridge0": "permit" } }, { "mac": "хх:xx:xx:xx:xx:85", ... "name": "Home", ... "registered": true, ... "link": "down", ...
На 36В3 оба роутера в основном режиме