Orbit

Тот же вопрос. При указании шлюза WG в external 3proxy его игнорирует, а команду route он вообще не знает.

4.3 Beta 3 не поправлено.

Первое сообщение повнимательней прочтите!

Так нет его там! И сервер как интерфейс в конфиге не значится.

ip route 192.168.41.0 255.255.255.0 192.168.7.201 L2TPVPN auto !and1_L2TPVPN { "prompt": "(config)", "status": [ { "status": "error", "code": "7405600", "ident": "Command::Base", "message": "no such command: L2TPVPN." } ] }

Менял диапазон, без разницы. { "id": "PPPoE0", "index": 0, "interface-name": "PPPoE0", "type": "PPPoE", "description": "rostelecom", "traits": [ "Ip", "Ip6", "Supplicant", "Peer", "Ppp", "Pppoe" ], "link": "up", "connected": "yes", "state": "up", "role": [ "inet" ], "mtu": 1492, "tx-queue-length": 1000, "address": "5.138.248.210", "mask": "255.255.255.255", "global": true, "defaultgw": true, "priority": 63486, "security-level": "public", "ipv6": { "defaultgw": false }, "auth-type": "none", "uptime": 36311, "remote": "100.106.0.1", "fail": "no", "via": "GigabitEthernet1", "last-change": "36311.156623", "session-id": 5975, "ac-mac": "f8:13:08:32:20:7b", "summary": { "layer": { "conf": "running", "link": "running", "ipv4": "running", "ipv6": "disabled", "ctrl": "running" } }, "prompt": "(config)" } { "id": "GigabitEthernet1", "index": 1, "interface-name": "ISP", "type": "GigabitEthernet", "description": "rostelecom", "traits": [ "Mac", "Ethernet", "Ip", "Ip6", "Supplicant", "EthernetIp", "MtkSfpEthernet" ], "link": "up", "connected": "yes", "state": "up", "mtu": 1500, "tx-queue-length": 2000, "global": false, "security-level": "public", "usedby": [ "PPPoE0" ], "ipv6": { "addresses": [ { "address": "fe80::52ff:20ff:fe19:a565", "prefix-length": 64, "proto": "KERNEL", "valid-lifetime": "infinite" } ] }, "mac": "50:ff:20:19:a5:65", "auth-type": "none", "port": { "id": "GigabitEthernet1/0", "index": 0, "interface-name": "0", "label": "0", "type": "Port", "traits": [ "EthernetPort", "MtkSfpEthernetPort" ], "link": "up", "speed": "100", "duplex": "full", "auto-negotiation": "on", "flow-control": "off", "eee": "off", "cable-diagnostics": false, "transceiver": "internal", "sfp-combo": true }, "summary": { "layer": { "conf": "running", "link": "running", "ipv4": "disabled", "ipv6": "disabled", "ctrl": "running" } }, "prompt": "(config)" }

Да это и понятно. Думал может в cli надо что добавить.

Ещё что заметил. После соединения клиента в основном соединении выскакивает прописанный шлюз но на доступ к интернету он не влияет.

{ "route": [ { "destination": "0.0.0.0/0", "gateway": "0.0.0.0", "interface": "PPPoE0", "metric": 0, "flags": "U", "rejecting": false, "proto": "boot", "floating": false, "static": false }, { "destination": "2.16.21.16/32", "gateway": "0.0.0.0", "interface": "Wireguard3", "metric": 0, "flags": "U", "rejecting": false, "proto": "static", "floating": false, "static": false }, { "destination": "8.8.8.8/32", "gateway": "0.0.0.0", "interface": "Wireguard3", "metric": 0, "flags": "U", "rejecting": false, "proto": "boot", "floating": false, "static": false }, { "destination": "10.1.30.0/24", "gateway": "0.0.0.0", "interface": "Bridge1", "metric": 0, "flags": "U", "rejecting": false, "proto": "kernel", "floating": false, "static": false }, { "destination": "85.175.46.122/32", "gateway": "0.0.0.0", "interface": "PPPoE0", "metric": 0, "flags": "U", "rejecting": false, "proto": "boot", "floating": false, "static": false }, { "destination": "85.175.46.130/32", "gateway": "0.0.0.0", "interface": "PPPoE0", "metric": 0, "flags": "U", "rejecting": false, "proto": "boot", "floating": false, "static": false }, { "destination": "100.106.0.1/32", "gateway": "0.0.0.0", "interface": "PPPoE0", "metric": 0, "flags": "U", "rejecting": false, "proto": "kernel", "floating": false, "static": false }, { "destination": "104.21.77.10/32", "gateway": "0.0.0.0", "interface": "Wireguard3", "metric": 0, "flags": "U", "rejecting": false, "proto": "static", "floating": false, "static": false }, { "destination": "172.16.7.2/32", "gateway": "0.0.0.0", "interface": "L2TPVPN", "metric": 0, "flags": "U", "rejecting": false, "proto": "kernel", "floating": false, "static": false }, { "destination": "172.16.40.0/24", "gateway": "0.0.0.0", "interface": "Wireguard3", "metric": 0, "flags": "U", "rejecting": false, "proto": "kernel", "floating": false, "static": false }, { "destination": "172.16.77.0/24", "gateway": "0.0.0.0", "interface": "Wireguard2", "metric": 0, "flags": "U", "rejecting": false, "proto": "kernel", "floating": false, "static": false }, { "destination": "172.16.88.0/24", "gateway": "0.0.0.0", "interface": "Wireguard0", "metric": 0, "flags": "U", "rejecting": false, "proto": "kernel", "floating": false, "static": false }, { "destination": "172.30.10.66/32", "gateway": "0.0.0.0", "interface": "Wireguard3", "metric": 0, "flags": "U", "rejecting": false, "proto": "static", "floating": false, "static": false }, { "destination": "172.67.182.196/32", "gateway": "0.0.0.0", "interface": "Wireguard3", "metric": 0, "flags": "U", "rejecting": false, "proto": "static", "floating": false, "static": false }, { "destination": "172.67.203.20/32", "gateway": "0.0.0.0", "interface": "Wireguard3", "metric": 0, "flags": "U", "rejecting": false, "proto": "static", "floating": false, "static": false }, { "destination": "192.168.8.0/24", "gateway": "0.0.0.0", "interface": "Wireguard0", "metric": 0, "flags": "U", "rejecting": false, "proto": "static", "floating": false, "static": false }, { "destination": "192.168.40.0/24", "gateway": "0.0.0.0", "interface": "Wireguard3", "metric": 0, "flags": "U", "rejecting": false, "proto": "static", "floating": false, "static": false }, { "destination": "192.168.41.0/24", "gateway": "172.16.7.2", "interface": "PPPoE0", "metric": 0, "flags": "U", "rejecting": false, "proto": "boot", "floating": false, "static": false }, { "destination": "192.168.77.0/24", "gateway": "0.0.0.0", "interface": "Bridge0", "metric": 0, "flags": "U", "rejecting": false, "proto": "kernel", "floating": false, "static": false }, { "destination": "192.168.87.0/24", "gateway": "0.0.0.0", "interface": "Wireguard0", "metric": 0, "flags": "U", "rejecting": false, "proto": "static", "floating": false, "static": false }, { "destination": "192.168.88.0/24", "gateway": "0.0.0.0", "interface": "Wireguard0", "metric": 0, "flags": "U", "rejecting": false, "proto": "static", "floating": false, "static": false }, { "destination": "193.46.255.29/32", "gateway": "0.0.0.0", "interface": "Wireguard3", "metric": 0, "flags": "U", "rejecting": false, "proto": "static", "floating": false, "static": false } ], "prompt": "(config)" } { "destination": "192.168.41.0/24", "gateway": "172.16.7.2", "interface": "PPPoE0", "metric": 0, "flags": "U", "rejecting": false, "proto": "boot", "floating": false, "static": false },

Команды если не сложно.

Добрый день. Работает ли данная инструкция https://help.keenetic.com/hc/ru/articles/360001390359-Маршрутизация-сетей-через-VPN на 4.3 Beta 2 KN-1010 ? Пробовал l2tp/ipsec и pptp. Везде запрос идёт к провайдеру вместо ip клиента. Судя по таблице всё правильно интерфейс прописывается провайдера. Как задать маршрут на ip клиента? starting traceroute to 192.168.41.1... traceroute to 192.168.41.1 (192.168.41.1), 30 hops maximum, 84 byte packets. 1 100.65.0.1 (100.65.0.1) 8.543 ms 8.099 ms 7.912 ms 2 178.34.129.8 (178.34.129.8) 6.370 ms 6.499 ms 6.474 ms 3 * * *

А у кого нибудь работает М100-1 на Ultra 2.16.D.12.0-11 ? Qualcomm CDMA Technologies MSM Версия ПО MF1.08_1KY_02 1 [Jun 04 2012 20:00:00] Оператор Yota Две минуты и перегружается в эти две минуты интернета нет. Такое же поведение и на KN-1010 4.3 Alpha 10.1. Сам модем на компе работает нормально. 1.txt

А как откатится с 2.16.D.12.0-10 на 2.04.C.7.0-6? Пробовал в веб выбрать стабильную 2.05 получаю циклическую перезагрузку. log.txt [C] Jan 1 03:00:17 ndm: lib::libndmWifiRtx: system failed [0xcffd0216]. И возможно в этом причина сломанного 5 Ггц на 2.16.

Это ясно, а поконкретней. Не хочется совсем укатать.

Малость доигрался с прошивками влил в Ultry от Ketnetic II Как восстановить через uart и что? U-Boot 1.1.3 [4.0.0.3-15] (Mar 24 2016 - 16:49:31) Board: Ralink APSoC DRAM: 128 MB relocate_code Pointer at: 87fb4000 flash manufacture id: c2, device id 20 18 find flash: MX25L12805D ============================================ Ralink UBoot Version: 4.0.0.3_NDMS -------------------------------------------- ASIC 6856_MP (Port5<->None) DRAM component: 1024 Mbits DDR, width 16 DRAM bus: 16 bit Total memory: 128 MBytes Flash component: SPI Flash Date:Mar 24 2016 Time:16:49:31 ============================================ icache: sets:512, ways:4, linesz:32 ,total:65536 dcache: sets:256, ways:4, linesz:32 ,total:32768 ##### The CPU freq = 700 MHZ #### estimate memory size = 128 Mbytes Please choose the operation: 1: Load system code to SDRAM via TFTP. 2: Load system code then write to Flash via TFTP. 3: Boot system code via Flash (default). 4: Enter boot command line interface. 7: Load Boot Loader code then write to Flash via Serial. 9: Load Boot Loader code then write to Flash via TFTP. 0 3: System Boot system code via Flash. ## Booting image at b0050000 ... Image Name: ZyXEL Keenetic II Created: 2022-08-08 11:54:40 UTC Image Type: MIPS Linux Kernel Image (lzma compressed) Data Size: 1301208 Bytes = 1.2 MB Load Address: 80020000 Entry Point: 802e5110 Verifying Checksum ... OK Uncompressing Kernel Image ... OK No initrd ## Transferring control to Linux (at address 802e5110) ... ## Giving linux memsize in MB, 128

Да, что то в бедной ultre вместе с 5ГГцами и WirelessISP приговорили

Кстати, а для Keenetic II вырезали в последней версии поддержку этого модема? Всё отлично работает, причина была в бракованных кабелях microusb.

(config)> interface usb wwan-force-connected Command::Base error[7405600]: no such command: wwan-force-connected. (config)> Модем E5776 Перезагрузить Статус Подключен Версия ПО 22.265.11.02.260 Модель Keenetic Ultra Версия ОС 2.16.D.12.0-11

Поддерживает ли эта версия прошивки ku_ra_draft_2.16.D.12.0-11 команды interface usb wwan-force-connected interface web-api address

Как убрать ошибку? 03-13-2023 11:48:21 User.Error 192.168.77.1 Mar 13 11:48:19 Keenetic-1300 ndm: Network::Ip6::RoutingTable: __clone()+0x6c 03-13-2023 11:48:21 User.Error 192.168.77.1 Mar 13 11:48:19 Keenetic-1300 ndm: Network::Ip6::RoutingTable: start()+0xcc 03-13-2023 11:48:21 User.Error 192.168.77.1 Mar 13 11:48:19 Keenetic-1300 ndm: Network::Ip6::RoutingTable: Thread::StartRoutine_(void*)+0x420 03-13-2023 11:48:21 User.Error 192.168.77.1 Mar 13 11:48:19 Keenetic-1300 ndm: Network::Ip6::RoutingTable: Task::Thread::Run()+0x38 03-13-2023 11:48:21 User.Error 192.168.77.1 Mar 13 11:48:19 Keenetic-1300 ndm: Network::Ip6::RoutingTable: Task::Thread::Run_()+0x464 03-13-2023 11:48:21 User.Error 192.168.77.1 Mar 13 11:48:19 Keenetic-1300 ndm: Network::Ip6::RoutingTable: Core::Scgi::ThreadPool::Task_::Run()+0x208 03-13-2023 11:48:21 User.Error 192.168.77.1 Mar 13 11:48:19 Keenetic-1300 ndm: Network::Ip6::RoutingTable: Core::Scgi::ThreadPool::Task_::ProcessJsonRequest_(Core::Configurator&, Core::Scgi::Request const&, Core::Scgi::Trace&, Array<char>&, Io::OStream&)+0x54c 03-13-2023 11:48:21 User.Error 192.168.77.1 Mar 13 11:48:19 Keenetic-1300 ndm: Network::Ip6::RoutingTable: Core::Scgi::Tools::JsonPost(Core::Configurator&, Core::Scgi::Request const&, Json::Document const&, Core::Scgi::Trace&, Json::Document&, bool*)+0x1dc 03-13-2023 11:48:21 User.Error 192.168.77.1 Mar 13 11:48:19 Keenetic-1300 ndm: Network::Ip6::RoutingTable: Core::Scgi::Tools::(anonymous namespace)::JsonPostValue_(Core::Configurator&, Command::Request const&, Core::Scgi::Trace&, Json::Value const*, Json::Object*)+0x184 03-13-2023 11:48:21 User.Error 192.168.77.1 Mar 13 11:48:19 Keenetic-1300 ndm: Network::Ip6::RoutingTable: Core::Scgi::Tools::(anonymous namespace)::JsonPostObject_(Core::Configurator&, Command::Request const&, Core::Scgi::Trace&, Json::Object const*, Json::Object*)+0xf1c 03-13-2023 11:48:21 User.Error 192.168.77.1 Mar 13 11:48:19 Keenetic-1300 ndm: Network::Ip6::RoutingTable: Core::Scgi::Tools::(anonymous namespace)::JsonPostValue_(Core::Configurator&, Command::Request const&, Core::Scgi::Trace&, Json::Value const*, Json::Object*)+0x184 03-13-2023 11:48:21 User.Error 192.168.77.1 Mar 13 11:48:19 Keenetic-1300 ndm: Network::Ip6::RoutingTable: Core::Scgi::Tools::(anonymous namespace)::JsonPostObject_(Core::Configurator&, Command::Request const&, Core::Scgi::Trace&, Json::Object const*, Json::Object*)+0xf1c 03-13-2023 11:48:21 User.Error 192.168.77.1 Mar 13 11:48:19 Keenetic-1300 ndm: Network::Ip6::RoutingTable: Core::Scgi::Tools::(anonymous namespace)::JsonPostValue_(Core::Configurator&, Command::Request const&, Core::Scgi::Trace&, Json::Value const*, Json::Object*)+0x184 03-13-2023 11:48:21 User.Error 192.168.77.1 Mar 13 11:48:19 Keenetic-1300 ndm: Network::Ip6::RoutingTable: Core::Scgi::Tools::(anonymous namespace)::JsonPostObject_(Core::Configurator&, Command::Request const&, Core::Scgi::Trace&, Json::Object const*, Json::Object*)+0xf1c 03-13-2023 11:48:21 User.Error 192.168.77.1 Mar 13 11:48:19 Keenetic-1300 ndm: Network::Ip6::RoutingTable: Core::Scgi::Tools::(anonymous namespace)::JsonPostValue_(Core::Configurator&, Command::Request const&, Core::Scgi::Trace&, Json::Value const*, Json::Object*)+0x184 03-13-2023 11:48:21 User.Error 192.168.77.1 Mar 13 11:48:19 Keenetic-1300 ndm: Network::Ip6::RoutingTable: Core::Scgi::Tools::(anonymous namespace)::JsonPostObject_(Core::Configurator&, Command::Request const&, Core::Scgi::Trace&, Json::Object const*, Json::Object*)+0xa38 03-13-2023 11:48:21 User.Error 192.168.77.1 Mar 13 11:48:19 Keenetic-1300 ndm: Network::Ip6::RoutingTable: Core::Configurator::Serve(Command::Request const&, Command::Response&)+0x5a0 03-13-2023 11:48:21 User.Error 192.168.77.1 Mar 13 11:48:19 Keenetic-1300 ndm: Network::Ip6::RoutingTable: Core::Configurator::Execute(Command::Base const*, Command::Request const&, Command::Response&)+0x274 03-13-2023 11:48:21 User.Error 192.168.77.1 Mar 13 11:48:19 Keenetic-1300 ndm: Network::Ip6::RoutingTable: Command::(anonymous namespace)::ShowIpv6Route::Execute(Command::Request const&, Command::Response&) const+0x118 03-13-2023 11:48:21 User.Error 192.168.77.1 Mar 13 11:48:19 Keenetic-1300 ndm: Network::Ip6::RoutingTable: Network::Ip6::RoutingTable::GetRoutes(AutoPVector<Network::Ip6::RoutingTable::Entry, StdDeleter>&, CString const&, Network::Ip6::CBlock const&, unsigned int, Log::VerboseT) const+0xb8 03-13-2023 11:48:21 User.Error 192.168.77.1 Mar 13 11:48:19 Keenetic-1300 ndm: Network::Ip6::RoutingTable: Network::Ip6::RoutingTable::GetRoutes_(AutoPVector<Network::Ip6::RoutingTable::Entry, StdDeleter>&, LockedPtr<Network::Interface::Ip6 const> const&, Network::Ip6::CBlock const&, unsigned int, bool, Log::VerboseT) const+0xfc 03-13-2023 11:48:21 User.Error 192.168.77.1 Mar 13 11:48:19 Keenetic-1300 ndm: Network::Ip6::RoutingTable: "Queue::BVOFTLCNTRGPKQMC::http/rci" (29883) backtrace:

В веб основной системы шел, там не надо ничего менять. А на 222 нужный вам логин root пароль от админа.

Порт другой попробуйте типа 222.

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