Orbit

вот это оно!

Не совсем то. У вас подключение клиента происходит к гостевой сети, здесь же подключения нет тк ip-адрес не выделяется.

KN1010 - GIGAIII версии везде 3.1.0. На контроллере такой проблемы нет.

После исправления IPsec: исправлено добавление маршрута к клиентской сети на L2TP/IPsec-сервере [NDM-3758] маршрут добавляется, с сервера и клиент и его локалка пингуются но с локалки сервера нет пинга не клиента не его сети. В фаервол клиента разрешения добавил. Опцию "NAT для клиентов" выключал.

Тот же вопрос. При указании шлюза 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 * * *