KLimping

... или проблема в другом: [I] Feb 6 15:20:42 ndhcps: sending ACK of 10.1.30.89 to b2:c5:cc:c5:5d:b8. [I] Feb 6 15:20:43 ndnproxy: [42E7] answer from wrong socket (got from 35 127.0.0.1:40306 [0] to 127.0.0.1:0, exp from 25 127.0.0.1:40306 to 52871). [I] Feb 6 15:20:44 ndnproxy: [EB8B] answer from wrong socket (got from 35 127.0.0.1:40307 [0] to 127.0.0.1:0, exp from 25 127.0.0.1:40307 to 52871). [I] Feb 6 15:22:15 ndnproxy: [91BA] answer from wrong socket (got from 35 127.0.0.1:40307 [0] to 127.0.0.1:0, exp from 25 127.0.0.1:40307 to 52871). [I] Feb 6 15:22:21 ndnproxy: [F939] answer from wrong socket (got from 35 127.0.0.1:40307 [0] to 127.0.0.1:0, exp from 25 127.0.0.1:40307 to 52871). [I] Feb 6 15:23:36 ndnproxy: [F3B4] answer from wrong socket (got from 35 127.0.0.1:40307 [0] to 127.0.0.1:0, exp from 25 127.0.0.1:40307 to 52871). [I] Feb 6 15:23:36 ndnproxy: [AEF0] answer from wrong socket (got from 35 127.0.0.1:40307 [0] to 127.0.0.1:0, exp from 25 127.0.0.1:40307 to 52871). [I] Feb 6 15:25:13 ndnproxy: [24A0] answer from wrong socket (got from 35 127.0.0.1:40303 [0] to 127.0.0.1:0, exp from 25 127.0.0.1:40303 to 52871). [W] Feb 6 15:25:26 https-dns-proxy: 4638: curl response code: 400, content length: 1 [W] Feb 6 15:25:26 https-dns-proxy: 90B5: curl response code: 400, content length: 1 [W] Feb 6 15:25:27 https-dns-proxy: 9B52: curl response code: 400, content length: 1 [W] Feb 6 15:25:27 https-dns-proxy: DDEE: curl response code: 400, content length: 1 [W] Feb 6 15:25:27 https-dns-proxy: 51B1: curl response code: 400, content length: 1 [W] Feb 6 15:25:28 https-dns-proxy: D5AA: curl response code: 400, content length: 1 [I] Feb 6 15:26:17 ndhcpc: GigabitEthernet1: received ACK for 178.140.17.14 from 90.154.77.161 lease 3600 sec. [I] Feb 6 15:26:28 ndm: Dns::Manager: updating DNS-over-TLS servers addresses. [I] Feb 6 15:26:28 ndm: Dns::Manager: updating DNS-over-HTTPS servers addresses. [I] Feb 6 15:26:28 ndnproxy: [7ACD] answer from wrong socket (got from 35 77.37.251.33:53 [0] to 178.140.17.14:0, exp from 25 77.37.251.33:53 to 52871). [I] Feb 6 15:26:45 ndm: Network::Interface::Mtk::WifiMonitor: "WifiMaster0/AccessPoint0": STA(54:48:e6:c0:43:54) had disassociated by STA (reason: STA is leaving or has left BSS). [I] Feb 6 15:26:57 ndm: Network::Interface::Mtk::WifiMonitor: "WifiMaster0/AccessPoint0": STA(54:48:e6:c0:43:54) had associated. [I] Feb 6 15:26:57 ndm: Network::Interface::Mtk::WifiMonitor: "WifiMaster0/AccessPoint0": STA(54:48:e6:c0:43:54) set key done in WPA2/WPA2PSK. [I] Feb 6 15:26:57 ndhcps: DHCPDISCOVER received from 54:48:e6:c0:43:54 hostname "yeelink-light-strip6_mibt4354". [I] Feb 6 15:26:57 ndhcps: making OFFER of 10.0.171.69 to 54:48:e6:c0:43:54. [I] Feb 6 15:26:57 ndhcps: DHCPREQUEST received (STATE_SELECTING) for 10.0.171.69 from 54:48:e6:c0:43:54 hostname "yeelink-light-strip6_mibt4354". [I] Feb 6 15:26:58 ndhcps: sending ACK of 10.0.171.69 to 54:48:e6:c0:43:54. [I] Feb 6 15:27:51 ndnproxy: [1BBF] answer from wrong socket (got from 35 127.0.0.1:40303 [0] to 127.0.0.1:0, exp from 25 127.0.0.1:40303 to 52871). [W] Feb 6 15:29:29 https-dns-proxy: 5F24: curl response code: 400, content length: 1 [W] Feb 6 15:29:30 https-dns-proxy: 2389: curl response code: 400, content length: 1 [W] Feb 6 15:29:30 https-dns-proxy: B58E: curl response code: 400, content length: 1 [W] Feb 6 15:29:30 https-dns-proxy: 3BB0: curl response code: 400, content length: 1 [W] Feb 6 15:29:30 https-dns-proxy: 60DB: curl response code: 400, content length: 1 [W] Feb 6 15:29:31 https-dns-proxy: 103D: curl response code: 400, content length: 1 [I] Feb 6 15:29:51 ndnproxy: [51D6] answer from wrong socket (got from 35 127.0.0.1:40302 [0] to 127.0.0.1:0, exp from 25 127.0.0.1:40302 to 52871). [I] Feb 6 15:30:55 ndnproxy: [B521] answer from wrong socket (got from 35 127.0.0.1:40307 [0] to 127.0.0.1:0, exp from 25 127.0.0.1:40307 to 52871). [I] Feb 6 15:30:58 ndnproxy: [8905] answer from wrong socket (got from 35 127.0.0.1:40303 [0] to 127.0.0.1:0, exp from 25 127.0.0.1:40303 to 52871). [I] Feb 6 15:31:53 ndm: Network::Interface::Mtk::WifiMonitor: "WifiMaster1/AccessPoint0": STA(b0:be:83:37:07:e6) had associated. [I] Feb 6 15:31:53 ndm: Network::Interface::Mtk::WifiMonitor: "WifiMaster1/AccessPoint0": STA(b0:be:83:37:07:e6) set key done in WPA2/WPA2PSK. [I] Feb 6 15:31:55 ndhcps: DHCPREQUEST received (STATE_INIT) for 10.0.171.135 from b0:be:83:37:07:e6 hostname "M1-MacBook-Air". [I] Feb 6 15:31:56 ndhcps: sending ACK of 10.0.171.135 to b0:be:83:37:07:e6. [I] Feb 6 15:32:02 ndnproxy: [9D77] answer from wrong socket (got from 35 127.0.0.1:40303 [0] to 127.0.0.1:0, exp from 25 127.0.0.1:40303 to 52871). [I] Feb 6 15:33:35 ndnproxy: [3231] answer from wrong socket (got from 35 127.0.0.1:40307 [0] to 127.0.0.1:0, exp from 25 127.0.0.1:40307 to 52871). [I] Feb 6 15:33:37 ndnproxy: [5531] answer from wrong socket (got from 35 127.0.0.1:40307 [0] to 127.0.0.1:0, exp from 25 127.0.0.1:40307 to 52871). [I] Feb 6 15:35:38 ndm: UPnP::Service: "System": redirect rule added: udp GigabitEthernet1:56131 -> 10.0.171.135:56131. [I] Feb 6 15:35:38 ndm: UPnP::Service: "System": forward rule added: udp GigabitEthernet1 -> 10.0.171.135:56131. [I] Feb 6 15:36:31 ndnproxy: [9B08] answer from wrong socket (got from 35 127.0.0.1:40901 [0] to 127.0.0.1:0, exp from 25 127.0.0.1:40901 to 52871).

Не пойму, а у меня проблемы связаны с обсуждаемым? В логах вижу, UPnP::Service сыпет сообщениями. Перезагружал. Селф-тест ниже.

О, переключил в другой USB - и работает.

На другом кинетике на 4.6.х продолжает работать нормально (проверю ещё раз), а на Ultra II с появлением Slot 1 и Slot 2 и пункта меню для eSIM началась проблема - не соединяется, ругается SIM card invalid.

Кстати, а как у вас с соединением по SSTP? У меня на мобильных в Москве работает неплохо. А когда уезжаю в регионы, то блин нифига не работает даже в спокойной ситуации (без новых блокировок). Даже если соединение устанавливается, то трафик не идёт. Чаще всего использую приложение SSTP Connect на iOS.

Давно уже пользуюсь SSTP на KeenDNS (старый домент в этом году автоматически мигрировал в netcraze). Пока территориально в Москве, всё неплохо работает. Уезжаю в регион - и дело плохо. Даже если соединение в клиенте устанавливается, то связи никакой. В качестве альтернативы на том же Кинетике и на том же KeenDNS включил ещё IKEv2. Более-менее работает, правда бывают странные обрывы на несколько минут.

А что лучше выбрать на самом Кинетике на 4.3.6.3 в настройках IKEv2/IPsec VPN Server в разделе Optimization mode: "For maximum performance"?