Вопросы по интеграции OpenVPN в NDMS

Сергей Молоков · June 11, 2018

Extra II

Обновился с 2.12.A.6.0-2 до 2.12.B.0.0-4

При загрузке роутера OVPN не подключается

Июн 11 16:54:57 OpenVPN0
WARNING: Ignoring option 'dh' in tls-client mode, please only include this in your server configuration
Июн 11 16:54:57 OpenVPN0
OpenVPN 2.4.4 [SSL (OpenSSL)] [LZO] [LZ4] [EPOLL] [AEAD]
Июн 11 16:54:57 OpenVPN0
library versions: OpenSSL 1.1.0h 27 Mar 2018, LZO 2.10
Июн 11 16:54:57 OpenVPN0
WARNING: --ns-cert-type is DEPRECATED. Use --remote-cert-tls instead.
Июн 11 16:54:57 OpenVPN0
UDP link local (bound): [AF_INET][undef]:1194
Июн 11 16:54:57 OpenVPN0
UDP link remote: [AF_INET]xxx.xxx.xxx.xxx:1194
Июн 11 16:54:57 OpenVPN0
NOTE: UID/GID downgrade will be delayed because of --client, --pull, or --up-delay
Июн 11 16:54:57 OpenVPN0
write UDP: Network is unreachable (code=128)
Июн 11 16:54:57 OpenVPN0
Network unreachable, restarting
Июн 11 16:54:57 OpenVPN0
SIGTERM[soft,network-unreachable] received, process exiting
Июн 11 16:54:57 ndm
Service: "OpenVPN0": unexpectedly stopped.

в других подключениях отключаем ovpn подключение и снова подключаем, соединение устанавливается.

vladrnd · June 15, 2018

столкнулся с такой проблемой на 2.11.C.1.0-3 с OpenVPN. получаю по DHCP от провайдера белый IP адрес. настроен OpenVPN, установлены свои статические маршруты в него нужного мне траффика. Все бы хорошо, но вот со временем OpenVPN перестает обрабатывать эти маршруты. решается проблема путем выкл / вкл его и тогда все начинает работать исправно. как с этим бороться не понимаю. при первом осмотре VPN активен и получает IP 10.x.x.x адрес, но вот так ли это ... хотелось бы стабильного нормального openVPN.

небольшой лог (после выкл / вкл) сервиса OpenVPN

Jun 15 13:35:31ndm

Network::Interface::Supplicant: "OpenVPN1": authnentication is unchanged.

Jun 15 13:35:31ndm

Network::Interface::Base: "OpenVPN1": description saved.

Jun 15 13:35:31ndm

Network::Interface::IP: "OpenVPN1": IP address cleared.

Jun 15 13:35:31ndm

Network::Interface::IP: "OpenVPN1": global priority unchanged.

Jun 15 13:35:31ndm

Network::Interface::IP: "OpenVPN1": global priority cleared.

Jun 15 13:35:31ndm

Network::Interface::IP: "OpenVPN1": TCP-MSS adjustment enabled.

Jun 15 13:35:31ndm

Network::Interface::OpenVpn: "OpenVPN1": configuration successfully saved.

Jun 15 13:35:31ndm

Network::Interface::OpenVpn: "OpenVPN1": disable automatic routes accept via tunnel.

Jun 15 13:35:31ndm

Network::Interface::OpenVpn: "OpenVPN1": set connection via ISP.

Jun 15 13:35:31ndm

Network::Interface::Base: "OpenVPN1": interface is up.

Jun 15 13:35:31ndm

Network::Interface::Base: "OpenVPN1": schedule cleared.

Jun 15 13:35:31ndm

Core::ConfigurationSaver: saving configuration...

Jun 15 13:35:32ndm

Network::Interface::IP: "OpenVPN1": IP address cleared.

Jun 15 13:35:32ndm

Network::Interface::OpenVpn: "OpenVPN1": remove installed accepted routes.

Jun 15 13:35:32OpenVPN1

event_wait : Interrupted system call (code=4)

Jun 15 13:35:32OpenVPN1

Closing TUN/TAP interface

Jun 15 13:35:32OpenVPN1

SIGINT[hard,] received, process exiting

Jun 15 13:35:35OpenVPN1

OpenVPN 2.4.4 [SSL (OpenSSL)] [LZO] [LZ4] [EPOLL] [AEAD]

Jun 15 13:35:35OpenVPN1

library versions: OpenSSL 1.1.0h 27 Mar 2018, LZO 2.10

Jun 15 13:35:35OpenVPN1

Socket Buffers: R=[155648->155648] S=[155648->155648]

Jun 15 13:35:35OpenVPN1

UDP link local: (not bound)

Jun 15 13:35:35OpenVPN1

UDP link remote: [AF_INET]118.216.61.125:1597

Jun 15 13:35:35OpenVPN1

NOTE: UID/GID downgrade will be delayed because of --client, --pull, or --up-delay

Jun 15 13:35:35OpenVPN1

TLS: Initial packet from [AF_INET]118.216.61.125:1597, sid=50f97caa 465803f8

Jun 15 13:35:35ndm

Core::ConfigurationSaver: configuration saved.

Jun 15 13:35:35OpenVPN1

VERIFY SCRIPT OK: depth=2, C=GB, ST=Greater Manchester, L=Salford, O=COMODO CA Limited, CN=COMODO RSA Certification Authority

Jun 15 13:35:35OpenVPN1

VERIFY OK: depth=2, C=GB, ST=Greater Manchester, L=Salford, O=COMODO CA Limited, CN=COMODO RSA Certification Authority

Jun 15 13:35:35OpenVPN1

VERIFY SCRIPT OK: depth=1, C=GB, ST=Greater Manchester, L=Salford, O=COMODO CA Limited, CN=COMODO RSA Domain Validation Secure Server CA

Jun 15 13:35:35OpenVPN1

VERIFY OK: depth=1, C=GB, ST=Greater Manchester, L=Salford, O=COMODO CA Limited, CN=COMODO RSA Domain Validation Secure Server CA

Jun 15 13:35:35OpenVPN1

VERIFY SCRIPT OK: depth=0, OU=Domain Control Validated, OU=PositiveSSL Wildcard, CN=*.opengw.net

Jun 15 13:35:35OpenVPN1

VERIFY OK: depth=0, OU=Domain Control Validated, OU=PositiveSSL Wildcard, CN=*.opengw.net

Jun 15 13:35:36OpenVPN1

Control Channel: TLSv1.2, cipher TLSv1.2 ECDHE-RSA-AES256-GCM-SHA384, 2048 bit RSA

Jun 15 13:35:36OpenVPN1

[*.opengw.net] Peer Connection Initiated with [AF_INET]118.216.61.125:1597

Jun 15 13:35:36ndm

Network::Interface::OpenVpn: "OpenVPN1": added host route to remote endpoint 118.216.61.125 via 188.130.140.1.

Jun 15 13:35:37OpenVPN1

SENT CONTROL [*.opengw.net]: 'PUSH_REQUEST' (status=1)

Jun 15 13:35:38OpenVPN1

PUSH: Received control message: 'PUSH_REPLY,ping 3,ping-restart 10,ifconfig 10.211.1.253 10.211.1.254,dhcp-option DNS 10.211.254.254,dhcp-option DNS 8.8.8.8,route-gateway 10.211.1.254,redirect-gateway def1'

Jun 15 13:35:38OpenVPN1

OPTIONS IMPORT: timers and/or timeouts modified

Jun 15 13:35:38OpenVPN1

OPTIONS IMPORT: --ifconfig/up options modified

Jun 15 13:35:38OpenVPN1

OPTIONS IMPORT: route options modified

Jun 15 13:35:38OpenVPN1

OPTIONS IMPORT: route-related options modified

Jun 15 13:35:38OpenVPN1

OPTIONS IMPORT: --ip-win32 and/or --dhcp-option options modified

Jun 15 13:35:38OpenVPN1

Outgoing Data Channel: Cipher 'AES-128-CBC' initialized with 128 bit key

Jun 15 13:35:38OpenVPN1

Outgoing Data Channel: Using 160 bit message hash 'SHA1' for HMAC authentication

Jun 15 13:35:38OpenVPN1

Incoming Data Channel: Cipher 'AES-128-CBC' initialized with 128 bit key

Jun 15 13:35:38OpenVPN1

Incoming Data Channel: Using 160 bit message hash 'SHA1' for HMAC authentication

Jun 15 13:35:38OpenVPN1

TUN/TAP device tun0 opened

Jun 15 13:35:38OpenVPN1

TUN/TAP TX queue length set to 100

Jun 15 13:35:38OpenVPN1

do_ifconfig, tt->did_ifconfig_ipv6_setup=0

Jun 15 13:35:38ndm

Network::Interface::IP: "OpenVPN1": IP address is 10.211.1.253/32.

Jun 15 13:35:38ndm

Network::Interface::OpenVpn: "OpenVPN1": TUN peer address is 10.211.1.254.

Jun 15 13:35:38ndm

Network::Interface::OpenVpn: "OpenVPN1": added host route to peer 10.211.1.254 via 10.211.1.253.

Jun 15 13:35:39OpenVPN1

GID set to nobody

Jun 15 13:35:39OpenVPN1

UID set to nobody

Jun 15 13:35:39OpenVPN1

Initialization Sequence Completed

настройки сервер openvpn

###############################################################################
# OpenVPN 2.0 Sample Configuration File
# for PacketiX VPN / SoftEther VPN Server
#
# !!! AUTO-GENERATED BY SOFTETHER VPN SERVER MANAGEMENT TOOL !!!
#
# !!! YOU HAVE TO REVIEW IT BEFORE USE AND MODIFY IT AS NECESSARY !!!
#
# This configuration file is auto-generated. You might use this config file
# in order to connect to the PacketiX VPN / SoftEther VPN Server.
# However, before you try it, you should review the descriptions of the file
# to determine the necessity to modify to suitable for your real environment.
# If necessary, you have to modify a little adequately on the file.
# For example, the IP address or the hostname as a destination VPN Server
# should be confirmed.
#
# Note that to use OpenVPN 2.0, you have to put the certification file of
# the destination VPN Server on the OpenVPN Client computer when you use this
# config file. Please refer the below descriptions carefully.

###############################################################################
# Specify the type of the layer of the VPN connection.
#
# To connect to the VPN Server as a "Remote-Access VPN Client PC",
# specify 'dev tun'. (Layer-3 IP Routing Mode)
#
# To connect to the VPN Server as a bridging equipment of "Site-to-Site VPN",
# specify 'dev tap'. (Layer-2 Ethernet Bridgine Mode)

dev tun

###############################################################################
# Specify the underlying protocol beyond the Internet.
# Note that this setting must be correspond with the listening setting on
# the VPN Server.
#
# Specify either 'proto tcp' or 'proto udp'.

proto udp

###############################################################################
# The destination hostname / IP address, and port number of
# the target VPN Server.
#
# You have to specify as 'remote <HOSTNAME> <PORT>'. You can also
# specify the IP address instead of the hostname.
#
# Note that the auto-generated below hostname are a "auto-detected
# IP address" of the VPN Server. You have to confirm the correctness
# beforehand.
#
# When you want to connect to the VPN Server by using TCP protocol,
# the port number of the destination TCP port should be same as one of
# the available TCP listeners on the VPN Server.
#
# When you use UDP protocol, the port number must same as the configuration
# setting of "OpenVPN Server Compatible Function" on the VPN Server.

remote 118.216.61.125 1597

###############################################################################
# The HTTP/HTTPS proxy setting.
#
# Only if you have to use the Internet via a proxy, uncomment the below
# two lines and specify the proxy address and the port number.
# In the case of using proxy-authentication, refer the OpenVPN manual.

;http-proxy-retry
;http-proxy [proxy server] [proxy port]

###############################################################################
# The encryption and authentication algorithm.
#
# Default setting is good. Modify it as you prefer.
# When you specify an unsupported algorithm, the error will occur.
#
# The supported algorithms are as follows:
# cipher: [NULL-CIPHER] NULL AES-128-CBC AES-192-CBC AES-256-CBC BF-CBC
# CAST-CBC CAST5-CBC DES-CBC DES-EDE-CBC DES-EDE3-CBC DESX-CBC
# RC2-40-CBC RC2-64-CBC RC2-CBC
# auth: SHA SHA1 MD5 MD4 RMD160

cipher AES-128-CBC
auth SHA1

###############################################################################
# Other parameters necessary to connect to the VPN Server.
#
# It is not recommended to modify it unless you have a particular need.

resolv-retry infinite
nobind
persist-key
persist-tun
client
verb 3
#auth-user-pass

###############################################################################
# The certificate file of the destination VPN Server.
#
# The CA certificate file is embedded in the inline format.
# You can replace this CA contents if necessary.
# Please note that if the server certificate is not a self-signed, you have to
# specify the signer's root certificate (CA) here.

<ca>

-----END CERTIFICATE-----

</ca>

###############################################################################
# The client certificate file (dummy).
#
# In some implementations of OpenVPN Client software
# (for example: OpenVPN Client for iOS),
# a pair of client certificate and private key must be included on the
# configuration file due to the limitation of the client.
# So this sample configuration file has a dummy pair of client certificate
# and private key as follows.

<cert>
-----BEGIN CERTIFICATE-----

-----END CERTIFICATE-----

</cert>

<key>
-----BEGIN RSA PRIVATE KEY-----

-----END RSA PRIVATE KEY-----

</key>

Edited June 15, 2018 by vladrnd

vladrnd · June 18, 2018

ну так спецы здесь имеются ???

Сергей Молоков · June 19, 2018

В 11.06.2018 в 17:06, Сергей Молоков сказал:

Extra II

Обновился с 2.12.A.6.0-2 до 2.12.B.0.0-4

При загрузке роутера OVPN не подключается

Откатился на 2.11.C.1.0-3, все работает.

В системном мониторе нет сведений о OVPN, это норма?

16 часов назад, vladrnd сказал:

ну так спецы здесь имеются ???

видимо в отпуске, они тоже люди

Stasmin · June 21, 2018

В 15.06.2018 в 13:22, vladrnd сказал:

столкнулся с такой проблемой на 2.11.C.1.0-3 с OpenVPN. получаю по DHCP от провайдера белый IP адрес. настроен OpenVPN, установлены свои статические маршруты в него нужного мне траффика. Все бы хорошо, но вот со временем OpenVPN перестает обрабатывать эти маршруты. решается проблема путем выкл / вкл его и тогда все начинает работать исправно. как с этим бороться не понимаю. при первом осмотре VPN активен и получает IP 10.x.x.x адрес, но вот так ли это ... хотелось бы стабильного нормального openVPN.

небольшой лог (после выкл / вкл) сервиса OpenVPN

Скрытый текст

Jun 15 13:35:31ndm
Network::Interface::Supplicant: "OpenVPN1": authnentication is unchanged.

Jun 15 13:35:31ndm
Network::Interface::Base: "OpenVPN1": description saved.

Jun 15 13:35:31ndm
Network::Interface::IP: "OpenVPN1": IP address cleared.

Jun 15 13:35:31ndm
Network::Interface::IP: "OpenVPN1": global priority unchanged.

Jun 15 13:35:31ndm
Network::Interface::IP: "OpenVPN1": global priority cleared.

Jun 15 13:35:31ndm
Network::Interface::IP: "OpenVPN1": TCP-MSS adjustment enabled.

Jun 15 13:35:31ndm
Network::Interface::OpenVpn: "OpenVPN1": configuration successfully saved.

Jun 15 13:35:31ndm
Network::Interface::OpenVpn: "OpenVPN1": disable automatic routes accept via tunnel.

Jun 15 13:35:31ndm
Network::Interface::OpenVpn: "OpenVPN1": set connection via ISP.

Jun 15 13:35:31ndm
Network::Interface::Base: "OpenVPN1": interface is up.

Jun 15 13:35:31ndm
Network::Interface::Base: "OpenVPN1": schedule cleared.

Jun 15 13:35:31ndm
Core::ConfigurationSaver: saving configuration...

Jun 15 13:35:32ndm
Network::Interface::IP: "OpenVPN1": IP address cleared.

Jun 15 13:35:32ndm
Network::Interface::OpenVpn: "OpenVPN1": remove installed accepted routes.

Jun 15 13:35:32OpenVPN1
event_wait : Interrupted system call (code=4)

Jun 15 13:35:32OpenVPN1
Closing TUN/TAP interface

Jun 15 13:35:32OpenVPN1
SIGINT[hard,] received, process exiting

Jun 15 13:35:35OpenVPN1
OpenVPN 2.4.4 [SSL (OpenSSL)] [LZO] [LZ4] [EPOLL] [AEAD]

Jun 15 13:35:35OpenVPN1
library versions: OpenSSL 1.1.0h 27 Mar 2018, LZO 2.10

Jun 15 13:35:35OpenVPN1
Socket Buffers: R=[155648->155648] S=[155648->155648]

Jun 15 13:35:35OpenVPN1
UDP link local: (not bound)

Jun 15 13:35:35OpenVPN1
UDP link remote: [AF_INET]118.216.61.125:1597

Jun 15 13:35:35OpenVPN1
NOTE: UID/GID downgrade will be delayed because of --client, --pull, or --up-delay

Jun 15 13:35:35OpenVPN1
TLS: Initial packet from [AF_INET]118.216.61.125:1597, sid=50f97caa 465803f8

Jun 15 13:35:35ndm
Core::ConfigurationSaver: configuration saved.

Jun 15 13:35:35OpenVPN1
VERIFY SCRIPT OK: depth=2, C=GB, ST=Greater Manchester, L=Salford, O=COMODO CA Limited, CN=COMODO RSA Certification Authority

Jun 15 13:35:35OpenVPN1
VERIFY OK: depth=2, C=GB, ST=Greater Manchester, L=Salford, O=COMODO CA Limited, CN=COMODO RSA Certification Authority

Jun 15 13:35:35OpenVPN1
VERIFY SCRIPT OK: depth=1, C=GB, ST=Greater Manchester, L=Salford, O=COMODO CA Limited, CN=COMODO RSA Domain Validation Secure Server CA

Jun 15 13:35:35OpenVPN1
VERIFY OK: depth=1, C=GB, ST=Greater Manchester, L=Salford, O=COMODO CA Limited, CN=COMODO RSA Domain Validation Secure Server CA

Jun 15 13:35:35OpenVPN1
VERIFY SCRIPT OK: depth=0, OU=Domain Control Validated, OU=PositiveSSL Wildcard, CN=*.opengw.net

Jun 15 13:35:35OpenVPN1
VERIFY OK: depth=0, OU=Domain Control Validated, OU=PositiveSSL Wildcard, CN=*.opengw.net

Jun 15 13:35:36OpenVPN1
Control Channel: TLSv1.2, cipher TLSv1.2 ECDHE-RSA-AES256-GCM-SHA384, 2048 bit RSA

Jun 15 13:35:36OpenVPN1
[*.opengw.net] Peer Connection Initiated with [AF_INET]118.216.61.125:1597

Jun 15 13:35:36ndm
Network::Interface::OpenVpn: "OpenVPN1": added host route to remote endpoint 118.216.61.125 via 188.130.140.1.

Jun 15 13:35:37OpenVPN1
SENT CONTROL [*.opengw.net]: 'PUSH_REQUEST' (status=1)

Jun 15 13:35:38OpenVPN1
PUSH: Received control message: 'PUSH_REPLY,ping 3,ping-restart 10,ifconfig 10.211.1.253 10.211.1.254,dhcp-option DNS 10.211.254.254,dhcp-option DNS 8.8.8.8,route-gateway 10.211.1.254,redirect-gateway def1'

Jun 15 13:35:38OpenVPN1
OPTIONS IMPORT: timers and/or timeouts modified

Jun 15 13:35:38OpenVPN1
OPTIONS IMPORT: --ifconfig/up options modified

Jun 15 13:35:38OpenVPN1
OPTIONS IMPORT: route options modified

Jun 15 13:35:38OpenVPN1
OPTIONS IMPORT: route-related options modified

Jun 15 13:35:38OpenVPN1
OPTIONS IMPORT: --ip-win32 and/or --dhcp-option options modified

Jun 15 13:35:38OpenVPN1
Outgoing Data Channel: Cipher 'AES-128-CBC' initialized with 128 bit key

Jun 15 13:35:38OpenVPN1
Outgoing Data Channel: Using 160 bit message hash 'SHA1' for HMAC authentication

Jun 15 13:35:38OpenVPN1
Incoming Data Channel: Cipher 'AES-128-CBC' initialized with 128 bit key

Jun 15 13:35:38OpenVPN1
Incoming Data Channel: Using 160 bit message hash 'SHA1' for HMAC authentication

Jun 15 13:35:38OpenVPN1
TUN/TAP device tun0 opened

Jun 15 13:35:38OpenVPN1
TUN/TAP TX queue length set to 100

Jun 15 13:35:38OpenVPN1
do_ifconfig, tt->did_ifconfig_ipv6_setup=0

Jun 15 13:35:38ndm
Network::Interface::IP: "OpenVPN1": IP address is 10.211.1.253/32.

Jun 15 13:35:38ndm
Network::Interface::OpenVpn: "OpenVPN1": TUN peer address is 10.211.1.254.

Jun 15 13:35:38ndm
Network::Interface::OpenVpn: "OpenVPN1": added host route to peer 10.211.1.254 via 10.211.1.253.

Jun 15 13:35:39OpenVPN1
GID set to nobody

Jun 15 13:35:39OpenVPN1
UID set to nobody

Jun 15 13:35:39OpenVPN1
Initialization Sequence Completed

настройки сервер openvpn

###############################################################################
# OpenVPN 2.0 Sample Configuration File
# for PacketiX VPN / SoftEther VPN Server
#
# !!! AUTO-GENERATED BY SOFTETHER VPN SERVER MANAGEMENT TOOL !!!
#
# !!! YOU HAVE TO REVIEW IT BEFORE USE AND MODIFY IT AS NECESSARY !!!
#
# This configuration file is auto-generated. You might use this config file
# in order to connect to the PacketiX VPN / SoftEther VPN Server.
# However, before you try it, you should review the descriptions of the file
# to determine the necessity to modify to suitable for your real environment.
# If necessary, you have to modify a little adequately on the file.
# For example, the IP address or the hostname as a destination VPN Server
# should be confirmed.
#
# Note that to use OpenVPN 2.0, you have to put the certification file of
# the destination VPN Server on the OpenVPN Client computer when you use this
# config file. Please refer the below descriptions carefully.

###############################################################################
# Specify the type of the layer of the VPN connection.
#
# To connect to the VPN Server as a "Remote-Access VPN Client PC",
# specify 'dev tun'. (Layer-3 IP Routing Mode)
#
# To connect to the VPN Server as a bridging equipment of "Site-to-Site VPN",
# specify 'dev tap'. (Layer-2 Ethernet Bridgine Mode)

dev tun

###############################################################################
# Specify the underlying protocol beyond the Internet.
# Note that this setting must be correspond with the listening setting on
# the VPN Server.
#
# Specify either 'proto tcp' or 'proto udp'.

proto udp

###############################################################################
# The destination hostname / IP address, and port number of
# the target VPN Server.
#
# You have to specify as 'remote <HOSTNAME> <PORT>'. You can also
# specify the IP address instead of the hostname.
#
# Note that the auto-generated below hostname are a "auto-detected
# IP address" of the VPN Server. You have to confirm the correctness
# beforehand.
#
# When you want to connect to the VPN Server by using TCP protocol,
# the port number of the destination TCP port should be same as one of
# the available TCP listeners on the VPN Server.
#
# When you use UDP protocol, the port number must same as the configuration
# setting of "OpenVPN Server Compatible Function" on the VPN Server.

remote 118.216.61.125 1597

###############################################################################
# The HTTP/HTTPS proxy setting.
#
# Only if you have to use the Internet via a proxy, uncomment the below
# two lines and specify the proxy address and the port number.
# In the case of using proxy-authentication, refer the OpenVPN manual.

;http-proxy-retry
;http-proxy [proxy server] [proxy port]

###############################################################################
# The encryption and authentication algorithm.
#
# Default setting is good. Modify it as you prefer.
# When you specify an unsupported algorithm, the error will occur.
#
# The supported algorithms are as follows:
# cipher: [NULL-CIPHER] NULL AES-128-CBC AES-192-CBC AES-256-CBC BF-CBC
# CAST-CBC CAST5-CBC DES-CBC DES-EDE-CBC DES-EDE3-CBC DESX-CBC
# RC2-40-CBC RC2-64-CBC RC2-CBC
# auth: SHA SHA1 MD5 MD4 RMD160

cipher AES-128-CBC
auth SHA1

###############################################################################
# Other parameters necessary to connect to the VPN Server.
#
# It is not recommended to modify it unless you have a particular need.

resolv-retry infinite
nobind
persist-key
persist-tun
client
verb 3
#auth-user-pass

###############################################################################
# The certificate file of the destination VPN Server.
#
# The CA certificate file is embedded in the inline format.
# You can replace this CA contents if necessary.
# Please note that if the server certificate is not a self-signed, you have to
# specify the signer's root certificate (CA) here.

<ca>

-----END CERTIFICATE-----

</ca>

###############################################################################
# The client certificate file (dummy).
#
# In some implementations of OpenVPN Client software
# (for example: OpenVPN Client for iOS),
# a pair of client certificate and private key must be included on the
# configuration file due to the limitation of the client.
# So this sample configuration file has a dummy pair of client certificate
# and private key as follows.

<cert>
-----BEGIN CERTIFICATE-----

-----END CERTIFICATE-----

</cert>

<key>
-----BEGIN RSA PRIVATE KEY-----

-----END RSA PRIVATE KEY-----

</key>

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

У меня на данной прошивке тоже замечена схожая проблема, но весьма своеобразная. Вдруг перестает направлять через себя рутрекер, хотя остальное работает. Решение пока не нашел (это происходит в случайном порядке), но заметил, что маршрут в тоннель пропадает при полной работоспособности OVPN.

Советую делать бекап вашей прошивки, когда всё устраивает. А то бывает, что после обновления на новую версию что-то работает не так.

vladrnd · June 21, 2018

2 минуты назад, Stasmin сказал:

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

У меня на данной прошивке тоже замечена схожая проблема, но весьма своеобразная. Вдруг перестает направлять через себя рутрекер, хотя остальное работает. Решение пока не нашел (это происходит в случайном порядке), но заметил, что маршрут в тоннель пропадает при полной работоспособности OVPN.

Советую делать бекап вашей прошивки, когда всё устраивает. А то бывает, что после обновления на новую версию что-то работает не так.

причем тут бэкап. это проявляется еще с версии 2.11 и по сей день. т.к. заставить с этих версий работать OpenVPN с пропаданием маршрутов не удалось. Это кстати применимо к халявным OVP серверам на vpngate.net. протестировал на коммерческом сервере (hideme) - таких проблем нет, работает нормально. Остановился пока на PPTP сервисе на Amazon, развернул работает на УРА. Буду пробовать развернуть OpenVPN на днях там же, посмотрим. Может что на клиентской конфигурации прописать дополнительно ? keepalive не помог.

Le ecureuil · June 21, 2018

7 часов назад, vladrnd сказал:

причем тут бэкап. это проявляется еще с версии 2.11 и по сей день. т.к. заставить с этих версий работать OpenVPN с пропаданием маршрутов не удалось. Это кстати применимо к халявным OVP серверам на vpngate.net. протестировал на коммерческом сервере (hideme) - таких проблем нет, работает нормально. Остановился пока на PPTP сервисе на Amazon, развернул работает на УРА. Буду пробовать развернуть OpenVPN на днях там же, посмотрим. Может что на клиентской конфигурации прописать дополнительно ? keepalive не помог.

Скиньте два sefl-test: сразу после установления соединения, когда все хорошо, и второй, снятый в момент, когда "пропали маршруты". Посмотрим, что там не так со стороны прошивки.

vladrnd · June 27, 2018

В 21.06.2018 в 22:40, Le ecureuil сказал:

Скиньте два sefl-test: сразу после установления соединения, когда все хорошо, и второй, снятый в момент, когда "пропали маршруты". Посмотрим, что там не так со стороны прошивки.

скинул в приват. 7 день ни ответа ни привета.

Le ecureuil · June 29, 2018

В 27.06.2018 в 15:48, vladrnd сказал:

скинул в приват. 7 день ни ответа ни привета.

Да, я пока занят.

Но все записано, будет возможность - посмотрю.

I2M · July 2, 2018

Друзья подскажите в какую сторону копать. Есть VPS в германии с поднятым OpenVPN сервером. На работе стоит клиент на windows, трафик ходит через VPN все отлично, сайты открываются.

Поднял на Kenetic II аналогичного клиента, все подключилось, маршруты прописались вроде бы все ок. Но заблокированные сайты не открывает, кидает на заглушку провайдера.

Настройки клиента:

client
dev tun
proto udp
remote X.X.X.X 1194
nobind
<ca>
</ca>
<cert>
</cert>
<key>
</key>
<tls-auth>
</tls-auth>
key-direction 1
remote-cert-tls server
cipher AES-256-CBC
auth SHA256
compress
persist-key
persist-tun
verb 3
mute 20

Настройки сервера

port 1194
proto udp
dev tun
dev-node VPNDEV1
ca ca.crt
cert server.crt
key server.key  # This file should be kept secret
dh dh2048.pem
server 10.10.0.0 255.255.255.0
ifconfig-pool-persist ipp.txt
client-config-dir ccd
push "redirect-gateway def1"
push "dhcp-option DNS 8.8.8.8"
push "dhcp-option DNS 8.8.4.4"
keepalive 10 120
tls-server
tls-auth ta.key 0 # This file is secret
cipher AES-256-CBC
auth SHA256
comp-lzo
;user nobody
;group nogroup
persist-key
persist-tun
verb 3
mute 20
explicit-exit-notify 1

Трассировка на неработающем сайте.

starting traceroute to nnm-club.me...
traceroute to nnm-club.me (78.29.1.40), 30 hops maximum, 84 byte packets.
1 10.10.0.1 (10.10.0.1) 75.777 ms 74.989 ms 75.711 ms
2 * * *
3 static.57.3.201.138.clients.your-server.de (138.201.3.57) 76.042 ms 75.226 ms 75.594 ms
4 core24.fsn1.hetzner.com (213.239.229.21) 75.686 ms 75.908 ms 76.182 ms
5 core5.fra.hetzner.com (213.239.224.254) 84.920 ms 80.604 ms 80.230 ms
6 ae6-229.RT.IRX.FKT.DE.retn.net (87.245.245.113) 81.226 ms 80.887 ms 81.463 ms
7 ae3-8.RT.HPN.CEK.RU.retn.net (87.245.234.82) 142.581 ms 142.850 ms 144.944 ms
8 GW-InterSvyaz.retn.net (87.245.230.93) 148.920 ms 148.799 ms 149.059 ms
9 78.29.1.40 (78.29.1.40) 147.130 ms 147.515 ms 152.906 ms

Как я попадаю на заглушку от провайдера так и не пойму. Если нужны еще какие то данные, могу предоставить. Спасибо.

Le ecureuil · July 3, 2018

Проверьте DNS-ы.

I2M · July 4, 2018

В 03.07.2018 в 15:41, Le ecureuil сказал:

Проверьте DNS-ы.

Решил проблемы тем, что прописал DNS в настройках DHCP. сервера и только такой вариант и работает. Прописывание DNS в настройках основного провайдера, а так же в настройках OpenVPN результата не дает.

cmdmn · July 5, 2018

Всем добрый день! Нужно подключаться к ovpn серверу, что бы пока устанавливается подключение, ни один пакет не ушёл вне тоннеля. ip у сервера может меняться, поэтому ориентируюсь на порт 1195

До кинетика, стоит роутер, на котором закрыл всё, кроме нужного порта и днсов.

Подключение поднимается, но рвётся каждые 4 минуты и поднимается снова.

Подскажите, куда копать?

Скрытый текст


Jul 05 11:03:39ndmDhcp::Client: UsbDsl0 DHCP name servers are enabled.
Jul 05 11:03:39ndmNetwork::Interface::Mt2311::UsbDsl: opmode is set to ADSL2+, Annex A.
Jul 05 11:03:39ndmNetwork::Interface::Mt2311::UsbDsl: enabled profile(s): 8a.
Jul 05 11:03:39ndmNetwork::Interface::Mt2311::UsbDsl: enabled profile(s): 8b.
Jul 05 11:03:39ndmNetwork::Interface::Mt2311::UsbDsl: enabled profile(s): 8c.
Jul 05 11:03:39ndmNetwork::Interface::Mt2311::UsbDsl: enabled profile(s): 8d.
Jul 05 11:03:39ndmNetwork::Interface::Mt2311::UsbDsl: enabled profile(s): 12a.
Jul 05 11:03:39ndmNetwork::Interface::Mt2311::UsbDsl: enabled profile(s): 12b.
Jul 05 11:03:39ndmNetwork::Interface::Mt2311::UsbDsl: enabled profile(s): 17a.
Jul 05 11:03:39ndmNetwork::Interface::Mt2311::UsbDsl: enabled profile(s): 30a.
Jul 05 11:03:39ndmNetwork::Interface::Mt2311::UsbDsl: PSD mask not changed.
Jul 05 11:03:39ndmNetwork::Interface::Base: "UsbDsl0": interface is down.
Jul 05 11:03:39ndmNetwork::Interface::Base: "Bridge0": interface is down.
Jul 05 11:03:39ndmNetwork::Interface::Base: "Bridge0": interface is up.
Jul 05 11:03:39ndmNetwork::Interface::Repository: "Bridge0" interface created.
Jul 05 11:03:40ndmNetwork::Interface::Base: "Bridge0": renamed to "Home".
Jul 05 11:03:40ndmNetwork::Interface::Base: "Bridge0": description saved.
Jul 05 11:03:40ndmkernel: device eth2.1 entered promiscuous mode
Jul 05 11:03:40ndmkernel: device eth2 entered promiscuous mode
Jul 05 11:03:40ndmkernel: br0: port 1(eth2.1) entered forwarding state
Jul 05 11:03:40ndmkernel: br0: port 1(eth2.1) entered forwarding state
Jul 05 11:03:40ndmNetwork::Interface::Base: "Bridge0": interface is up.
Jul 05 11:03:40ndmNetwork::Interface::Mac: "Bridge0": backed up the default address 50:ff:20:07:79:fe of "Home" before changing.
Jul 05 11:03:40ndmkernel: br0: port 1(eth2.1) entered disabled state
Jul 05 11:03:40ndmkernel: br0: port 1(eth2.1) entered forwarding state
Jul 05 11:03:40ndmkernel: br0: port 1(eth2.1) entered forwarding state
Jul 05 11:03:40ndmNetwork::Interface::IP: "Bridge0": global priority unchanged.
Jul 05 11:03:40ndmNetwork::Interface::IP: "Bridge0": global priority cleared.
Jul 05 11:03:40ndmNetwork::Interface::Bridge: "Bridge0": GigabitEthernet0/Vlan1 inherited in Bridge0.
Jul 05 11:03:40ndmNetwork::Interface::Switch: "GigabitEthernet0/0": switch link up at port 1.
Jul 05 11:03:40ndmkernel: device ra4 entered promiscuous mode
Jul 05 11:03:40ndmkernel: br0: port 2(ra4) entered forwarding state
Jul 05 11:03:40ndmkernel: br0: port 2(ra4) entered forwarding state
Jul 05 11:03:40ndmkernel: br0: port 2(ra4) entered disabled state
Jul 05 11:03:40ndmkernel: br0: port 1(eth2.1) entered disabled state
Jul 05 11:03:40ndmkernel: br0: port 2(ra4) entered forwarding state
Jul 05 11:03:40ndmkernel: br0: port 2(ra4) entered forwarding state
Jul 05 11:03:40ndmkernel: br0: port 1(eth2.1) entered forwarding state
Jul 05 11:03:40ndmkernel: br0: port 1(eth2.1) entered forwarding state
Jul 05 11:03:40ndmNetwork::Interface::Bridge: "Bridge0": AccessPoint included.
Jul 05 11:03:40ndmkernel: device ra0 entered promiscuous mode
Jul 05 11:03:40ndmkernel: br0: port 3(ra0) entered forwarding state
Jul 05 11:03:40ndmkernel: br0: port 3(ra0) entered forwarding state
Jul 05 11:03:40ndmkernel: br0: port 3(ra0) entered disabled state
Jul 05 11:03:40ndmkernel: br0: port 2(ra4) entered disabled state
Jul 05 11:03:40ndmkernel: br0: port 1(eth2.1) entered disabled state
Jul 05 11:03:40ndmkernel: br0: port 3(ra0) entered forwarding state
Jul 05 11:03:40ndmkernel: br0: port 3(ra0) entered forwarding state
Jul 05 11:03:40ndmkernel: br0: port 2(ra4) entered forwarding state
Jul 05 11:03:40ndmkernel: br0: port 2(ra4) entered forwarding state
Jul 05 11:03:41ndmkernel: br0: port 1(eth2.1) entered forwarding state
Jul 05 11:03:41ndmkernel: br0: port 1(eth2.1) entered forwarding state
Jul 05 11:03:41ndmNetwork::Interface::Bridge: "Bridge0": AccessPoint_5G included.
Jul 05 11:03:41ndmNetwork::Interface::IP: "Bridge0": security level set to "private".
Jul 05 11:03:41bndstrgband steering control daemon v1.0-21 started 
Jul 05 11:03:41ndmNetwork::Interface::IP: "Bridge0": IP address is 192.168.1.1/24.
Jul 05 11:03:41ndmDhcp::Client: Bridge0 DHCP client DNS host routes are enabled.
Jul 05 11:03:41ndmDhcp::Client: Bridge0 DHCP name servers are enabled.
Jul 05 11:03:41ndmIgmp::Proxy: added downstream interface Bridge0.
Jul 05 11:03:41ndmNetwork::Interface::Base: "Bridge0": interface is up.
Jul 05 11:03:41ndmNetwork::Interface::Base: "Bridge1": interface is down.
Jul 05 11:03:41ndmNetwork::Interface::Base: "Bridge1": interface is up.
Jul 05 11:03:41ndmNetwork::Interface::Repository: "Bridge1" interface created.
Jul 05 11:03:41ndmkernel: br0: port 3(ra0) entered forwarding state
Jul 05 11:03:42ndmkernel: br0: port 2(ra4) entered forwarding state
Jul 05 11:03:42ndmkernel: br0: port 1(eth2.1) entered forwarding state
Jul 05 11:03:42ndmNetwork::Interface::Base: "Bridge1": renamed to "Guest".
Jul 05 11:03:42ndmNetwork::Interface::Base: "Bridge1": description saved.
Jul 05 11:03:42ndmTrafficControl::Manager: "Bridge1" interface rate limited to 5120 kbit/s.
Jul 05 11:03:42ndmkernel: device eth2.3 entered promiscuous mode
Jul 05 11:03:42ndmkernel: br1: port 1(eth2.3) entered forwarding state
Jul 05 11:03:42ndmkernel: br1: port 1(eth2.3) entered forwarding state
Jul 05 11:03:42ndmNetwork::Interface::Base: "Bridge1": interface is up.
Jul 05 11:03:42ndmNetwork::Interface::Mac: "Bridge1": backed up the default address 50:ff:20:07:79:fe of "Guest" before changing.
Jul 05 11:03:42ndmkernel: br1: port 1(eth2.3) entered disabled state
Jul 05 11:03:42ndmkernel: br1: port 1(eth2.3) entered forwarding state
Jul 05 11:03:42ndmkernel: br1: port 1(eth2.3) entered forwarding state
Jul 05 11:03:42ndmNetwork::Interface::IP: "Bridge1": global priority unchanged.
Jul 05 11:03:42ndmNetwork::Interface::IP: "Bridge1": global priority cleared.
Jul 05 11:03:42ndmNetwork::Interface::Bridge: "Bridge1": GigabitEthernet0/Vlan3 inherited in Bridge1.
Jul 05 11:03:42ndmkernel: device ra5 entered promiscuous mode
Jul 05 11:03:42ndmkernel: br1: port 1(eth2.3) entered disabled state
Jul 05 11:03:42ndmkernel: br1: port 1(eth2.3) entered forwarding state
Jul 05 11:03:42ndmkernel: br1: port 1(eth2.3) entered forwarding state
Jul 05 11:03:42ndmNetwork::Interface::Bridge: "Bridge1": GuestWiFi included.
Jul 05 11:03:42ndmNetwork::Interface::IP: "Bridge1": security level set to "protected".
Jul 05 11:03:42ndmNetwork::Interface::IP: "Bridge1": IP address is 10.1.30.1/24.
Jul 05 11:03:42ndmDhcp::Client: Bridge1 DHCP client DNS host routes are enabled.
Jul 05 11:03:42ndmDhcp::Client: Bridge1 DHCP name servers are enabled.
Jul 05 11:03:42ndmNetwork::Interface::Base: "Bridge1": interface is up.
Jul 05 11:03:42ndmNetwork::Interface::Base: "OpenVPN0": interface is down.
Jul 05 11:03:42ndmNetwork::Interface::Repository: "OpenVPN0" interface created.
Jul 05 11:03:43bndstrgband steering: enabled 
Jul 05 11:03:43ndmkernel: br1: port 1(eth2.3) entered forwarding state
Jul 05 11:03:43ndmNetwork::Interface::Base: "OpenVPN0": description saved.
Jul 05 11:03:43ndmNetwork::Interface::Base: "OpenVPN0": assigned role "misc" for OpenVPN0.
Jul 05 11:03:43ndmNetwork::Interface::IP: "OpenVPN0": security level set to "public".
Jul 05 11:03:43ndmDhcp::Client: OpenVPN0 DHCP client DNS host routes are enabled.
Jul 05 11:03:43ndmDhcp::Client: OpenVPN0 DHCP name servers are enabled.
Jul 05 11:03:43ndmNetwork::Interface::IP: "OpenVPN0": global priority is 33117.
Jul 05 11:03:43ndmNetwork::Interface::IP: "OpenVPN0": TCP-MSS adjustment enabled.
Jul 05 11:03:43ndmPingCheck::Profile: interface "OpenVPN0" added to profile "_WEBADMIN_OpenVPN0".
Jul 05 11:03:43ndmPingCheck::Client: set ping-check profile for interface "OpenVPN0".
Jul 05 11:03:43ndmNetwork::Interface::OpenVpn: "OpenVPN0": enable automatic routes accept via tunnel.
Jul 05 11:03:43ndmNetwork::Interface::IP: "WifiMaster0/WifiStation0": address is not available.
Jul 05 11:03:43ndmNetwork::Interface::IP: "OpenVPN0": global priority unchanged.
Jul 05 11:03:43ndmNetwork::Interface::OpenVpn: "OpenVPN0": set connection via WifiMaster0/WifiStation0.
Jul 05 11:03:43ndmNetwork::Interface::Base: "OpenVPN0": interface is up.
Jul 05 11:03:43ndmDhcp::Pool: pool "_WEBADMIN" range has been saved.
Jul 05 11:03:43ndmDhcp::Server: pool "_WEBADMIN" bound to interface Home.
Jul 05 11:03:43ndmDhcp::Server: pool "_WEBADMIN" is enabled.
Jul 05 11:03:43ndmDhcp::Pool: pool "_WEBADMIN_GUEST_AP" range has been saved.
Jul 05 11:03:43ndmDhcp::Server: pool "_WEBADMIN_GUEST_AP" bound to interface Guest.
Jul 05 11:03:43ndmDhcp::Server: pool "_WEBADMIN_GUEST_AP" is enabled.
Jul 05 11:03:43ndmHttp::Manager: port unchanged.
Jul 05 11:03:43ndmHttp::SslServer: security level changed to public.
Jul 05 11:03:43ndmHttp::Manager: security level changed to public.
Jul 05 11:03:43ndmHttp::Manager: bruteforce detection is reconfigured.
Jul 05 11:03:43ndmHttp::SslServer: load SSL certificate for domain "rx570.keenetic.pro".
Jul 05 11:03:43ndmHttp::SslServer: HTTP SSL server started.
Jul 05 11:03:43ndmHttp::Manager: proxy "giga" successfully created.
Jul 05 11:03:43ndmHttp::Manager: proxy "giga" upstream was set.
Jul 05 11:03:43ndmHttp::Manager: configured ndns domain for proxy: giga.
Jul 05 11:03:43ndmHttp::Manager: proxy security level is set to "public".
Jul 05 11:03:43ndmNetwork::Nat: a NAT rule added.
Jul 05 11:03:43ndmNetwork::Nat: a NAT rule added.
Jul 05 11:03:43ndmNetwork::StaticNat: static NAT rule has been added.
Jul 05 11:03:43ndmTelnet::Server: port unchanged.
Jul 05 11:03:43ndmTelnet::Server: security level unchanged.
Jul 05 11:03:43ndmTelnet::Server: bruteforce detection is reconfigured.
Jul 05 11:03:43ndmFtp::Server: security level unchanged.
Jul 05 11:03:43ndmNetwork::Interface::Rtx::Ppe: software PPE enabled.
Jul 05 11:03:43ndmNetwork::Interface::Rtx::Ppe: hardware PPE enabled.
Jul 05 11:03:43ndmUPnP::Manager: using LAN interface: Bridge0.
Jul 05 11:03:43ndmTorrent::Client: RPC port unchanged.
Jul 05 11:03:43ndmTorrent::Client: peer port unchanged.
Jul 05 11:03:43ndmTorrent::Client: peer port changed to 51413.
Jul 05 11:03:43ndmDhcp::Server: service enabled.
Jul 05 11:03:43ndmDns::Manager: DNS proxy enabled.
Jul 05 11:03:43ndmIgmp::Proxy: IGMP proxy enabled.
Jul 05 11:03:43ndmHttp::Manager: HTTP service was enabled.
Jul 05 11:03:43ndmCommand::LogResponse: CIFS server enabled.
Jul 05 11:03:43ndmTelnet::Server: telnet server enabled.
Jul 05 11:03:43ndmNtp::Client: NTP client enabled.
Jul 05 11:03:43ndmCloudControl::Agent: the cloud control service enabled.
Jul 05 11:03:43ndmCore::Hotplug::Manager: scanning hardware...
Jul 05 11:03:43ndmHttp::SslServer: HTTP SSL server is listening.
Jul 05 11:03:43ndmCore::Hotplug::Manager: scanning hardware: done.
Jul 05 11:03:43ndmCore::Init: system ready, core startup time is 22 seconds.
Jul 05 11:03:43ndmCore::Authenticator: generating.
Jul 05 11:03:43ndmHotspot::Discovery::Explorer: "Bridge0": Interface Bridge0 neighbour explorer started.
Jul 05 11:03:43ndmHotspot::Discovery::Explorer: "Bridge1": Interface Bridge1 neighbour explorer started.
Jul 05 11:03:43ndmkernel: Disable SMB fastpath
Jul 05 11:03:43ndmkernel: Enable SMB fastpath for 192.168.1.1/255.255.255.0
Jul 05 11:03:43ndmCore::System::DriverManager: loading /lib/modules/3.4.113/igmpsn.ko.
Jul 05 11:03:43ndmkernel: igmpsn: IGMP switch snooping module (C) 2015-2018 NDM Systems Inc., v4.1.2
Jul 05 11:03:43ndmNetwork::Interface::Rtx::WifiMaster: "WifiMaster1": auto channel mode set.
Jul 05 11:03:43ndmNetwork::Interface::Rtx::WifiMaster: "WifiMaster0": auto channel mode set.
Jul 05 11:03:43ndmkernel: br0: port 2(ra4) entered disabled state
Jul 05 11:03:43ndmkernel: br0: port 3(ra0) entered disabled state
Jul 05 11:03:43bndstrgband steering: disabled 
Jul 05 11:03:44ndmkernel: 5GHz eLNA Gain: 11 -> 10
Jul 05 11:03:44ndmkernel: 5GHz eLNA Bypass: 10 -> 8
Jul 05 11:03:45ndmkernel: br0: port 3(ra0) entered forwarding state
Jul 05 11:03:45ndmkernel: br0: port 3(ra0) entered forwarding state
Jul 05 11:03:45ndmNtp::Client: unable to communicate with "1.pool.ntp.org".
Jul 05 11:03:45ndmNtp::Client: could not synchronize, waiting...
Jul 05 11:03:45ndmkernel: br0: port 2(ra4) entered forwarding state
Jul 05 11:03:45ndmkernel: br0: port 2(ra4) entered forwarding state
Jul 05 11:03:45ndmNetwork::Interface::OpenVpn: "OpenVPN0": via interface is not ready, standby.
Jul 05 11:03:45ndmCore::System::DriverManager: loading /lib/modules/3.4.113/hw_nat.ko.
Jul 05 11:03:45ndmkernel: Ralink/MTK HW NAT 5.0.3.0-7 Module Enabled, FoE Size: 16384
Jul 05 11:03:45ndmCore::System::DriverManager: loading /lib/modules/3.4.113/fastvpn.ko.
Jul 05 11:03:45coalagentversion 0.0.6f starting.
Jul 05 11:03:45bndstrgband steering: finished 
Jul 05 11:03:45ndhcpsNDM DHCP server (version 3.2.15) started.
Jul 05 11:03:45ndhcpsNDM DHCP server (version 3.2.15) started.
Jul 05 11:03:45ndmkernel: SWNAT sizeof(bind) = 204
Jul 05 11:03:45ndmkernel: SWNAT sizeof(hashent) = 56
Jul 05 11:03:45ndmkernel: SWNAT is registered
Jul 05 11:03:45ndmkernel: SWNAT enabled
Jul 05 11:03:45ndmkernel: SWNAT caps: L2TP, PPTP, PPPoE, IPoE, MC, USB CDC/DSL
Jul 05 11:03:45ndmkernel: Fast VPN init, v4.0-109
Jul 05 11:03:45ndmkernel: PPPoE/IPoE LAN software acceleration is disabled
Jul 05 11:03:45telnetdwaiting for connections...
Jul 05 11:03:45ndmkernel: SWNAT scheduled to clear binds for 10.1.30.0/255.255.255.0
Jul 05 11:03:45ndmCore::Server: started Session /var/run/ndm.core.socket.
Jul 05 11:03:45ndmCore::Server: started Session /var/run/ndm.core.socket.
Jul 05 11:03:45ndmCore::Server: client disconnected.
Jul 05 11:03:45ndmCore::Server: client disconnected.
Jul 05 11:03:45nimproxyNDM IGMP/Multicast proxy (version 0.0.28) started.
Jul 05 11:03:46ndmkernel: Wi-Fi client: probe request: SSID=HER_VAM, BSSID=00:00:00:00:00:00
Jul 05 11:03:46ndmNetwork::Interface::OpenVpn: "OpenVPN0": via interface is not ready, standby.
Jul 05 11:03:46ndmkernel: br0: port 3(ra0) entered forwarding state
Jul 05 11:03:46ndmkernel: br0: port 2(ra4) entered forwarding state
Jul 05 11:03:47ndmHttp::Manager: new Web server configuration was applied.
Jul 05 11:03:47bndstrgband steering control daemon v1.0-21 started 
Jul 05 11:03:47ndhcpsDHCPDISCOVER received  for 192.168.1.59 from bc:5f:f4:5e:7d:b2.
Jul 05 11:03:47coalagentversion 0.0.6f starting.
Jul 05 11:03:48ndhcpsmaking OFFER of 192.168.1.59 to bc:5f:f4:5e:7d:b2.
Jul 05 11:03:48ndhcpsDHCPREQUEST received (STATE_SELECTING) for 192.168.1.59 from bc:5f:f4:5e:7d:b2.
Jul 05 11:03:48ndhcpssending ACK of 192.168.1.59 to bc:5f:f4:5e:7d:b2.
Jul 05 11:03:49bndstrgband steering: enabled 
Jul 05 11:03:49ndmkernel: ACS result: Primary Channel 52, Min Channel Busy = 0, BW = 80
Jul 05 11:03:49wmondWifiMaster1/AccessPoint0: (MT7615) BSS(ra0) channel switched to 52.
Jul 05 11:03:50ndmkernel: Wi-Fi client: probe request: SSID=HER_VAM, BSSID=00:00:00:00:00:00
Jul 05 11:03:51ndmkernel: Wi-Fi client: probe request: SSID=HER_VAM, BSSID=00:00:00:00:00:00
Jul 05 11:03:52ndmkernel: Wi-Fi client: do site survey...
Jul 05 11:03:54ndmCifs::ServerNQ: service started.
Jul 05 11:03:57ndmNtp::Client: unable to communicate with "2.pool.ntp.org".
Jul 05 11:03:57ndmNtp::Client: could not synchronize, waiting...
Jul 05 11:04:00ndmkernel: Wi-Fi client: probe request: SSID=HER_VAM, BSSID=4c:5e:0c:33:81:58
Jul 05 11:04:00ndmkernel: Wi-Fi client: probe response: SSID=HER_VAM, BSSID=4c:5e:0c:33:81:58
Jul 05 11:04:00ndmkernel: Wi-Fi client: authenticated
Jul 05 11:04:00ndmkernel: Wi-Fi client: associated
Jul 05 11:04:03ndmNetwork::Interface::OpenVpn: "OpenVPN0": via interface is not ready, standby.
Jul 05 11:04:04ndhcpcWifiMaster0/WifiStation0: NDM DHCP client (version 3.2.15) started.
Jul 05 11:04:04ndhcpcWifiMaster0/WifiStation0: created PID file "/var/run/ndhcpc-apcli1.pid".
Jul 05 11:04:05ndhcpcWifiMaster0/WifiStation0: received OFFER for 192.168.55.187 from 192.168.55.1.
Jul 05 11:04:05ndhcpcWifiMaster0/WifiStation0: received ACK for 192.168.55.187 from 192.168.55.1.
Jul 05 11:04:05ndmDhcp::Client: configuring interface WifiMaster0/WifiStation0.
Jul 05 11:04:05ndmNetwork::Interface::IP: "WifiMaster0/WifiStation0": IP address is 192.168.55.187/24.
Jul 05 11:04:05ndmDhcp::Client: obtained IP address 192.168.55.187/24.
Jul 05 11:04:05ndmDhcp::Client: interface "WifiMaster0/WifiStation0" is global, priority 500.
Jul 05 11:04:05ndmDhcp::Client: adding a default route via 192.168.55.1.
Jul 05 11:04:05ndmDhcp::Client: adding a host route to name server 85.175.46.130.
Jul 05 11:04:05ndmDhcp::Client: adding name server 85.175.46.130.
Jul 05 11:04:05ndmDns::Manager: name server 85.175.46.130 added, domain (default).
Jul 05 11:04:05ndmDhcp::Client: adding a host route to name server 85.175.46.122.
Jul 05 11:04:05ndmDhcp::Client: adding name server 85.175.46.122.
Jul 05 11:04:05ndmDns::Manager: name server 85.175.46.122 added, domain (default).
Jul 05 11:04:05ndmNetwork::InterfaceFlusher: flushed conntrack and route cache.
Jul 05 11:04:07ndmCore::Server: started Session /var/run/ndm.core.socket.
Jul 05 11:04:07upnpHTTP listening on port 44719
Jul 05 11:04:07upnpListening for NAT-PMP/PCP traffic on port 5351
Jul 05 11:04:08OpenVPN0WARNING: --keysize is DEPRECATED and will be removed in OpenVPN 2.6
Jul 05 11:04:08OpenVPN0OpenVPN 2.4.4 [SSL (OpenSSL)] [LZO] [LZ4] [EPOLL] [AEAD]
Jul 05 11:04:08OpenVPN0library versions: OpenSSL 1.1.0h  27 Mar 2018, LZO 2.10
Jul 05 11:04:08OpenVPN0WARNING: --ns-cert-type is DEPRECATED.  Use --remote-cert-tls instead.
Jul 05 11:04:08OpenVPN0Outgoing Control Channel Authentication: Using 512 bit message hash 'SHA512' for HMAC authentication
Jul 05 11:04:08OpenVPN0Incoming Control Channel Authentication: Using 512 bit message hash 'SHA512' for HMAC authentication
Jul 05 11:04:09OpenVPN0Socket Buffers: R=[155648->1048576] S=[155648->1048576]
Jul 05 11:04:09OpenVPN0UDP link local: (not bound)
Jul 05 11:04:09OpenVPN0UDP link remote: [AF_INET]208.167.233.196:1195
Jul 05 11:04:09OpenVPN0NOTE: UID/GID downgrade will be delayed because of --client, --pull, or --up-delay
Jul 05 11:04:09ndmNtp::Client: unable to communicate with "3.pool.ntp.org".
Jul 05 11:04:09ndmNtp::Client: could not synchronize, waiting...
Jul 05 11:04:09OpenVPN0TLS: Initial packet from [AF_INET]208.167.233.196:1195, sid=e85086bd 6e419857
Jul 05 11:04:09OpenVPN0VERIFY SCRIPT OK: depth=1, C=VG, ST=BVI, O=ExpressVPN, OU=ExpressVPN, CN=ExpressVPN CA, emailAddress=support@expressvpn.com
Jul 05 11:04:09OpenVPN0VERIFY OK: depth=1, C=VG, ST=BVI, O=ExpressVPN, OU=ExpressVPN, CN=ExpressVPN CA, emailAddress=support@expressvpn.com
Jul 05 11:04:09OpenVPN0VERIFY OK: nsCertType=SERVER
Jul 05 11:04:09OpenVPN0VERIFY X509NAME OK: C=VG, ST=BVI, O=ExpressVPN, OU=ExpressVPN, CN=Server-1786-1a, emailAddress=support@expressvpn.com
Jul 05 11:04:09OpenVPN0VERIFY SCRIPT OK: depth=0, C=VG, ST=BVI, O=ExpressVPN, OU=ExpressVPN, CN=Server-1786-1a, emailAddress=support@expressvpn.com
Jul 05 11:04:09OpenVPN0VERIFY OK: depth=0, C=VG, ST=BVI, O=ExpressVPN, OU=ExpressVPN, CN=Server-1786-1a, emailAddress=support@expressvpn.com
Jul 05 11:04:10OpenVPN0Control Channel: TLSv1.2, cipher TLSv1.2 DHE-RSA-AES256-GCM-SHA384, 2048 bit RSA
Jul 05 11:04:10OpenVPN0[Server-1786-1a] Peer Connection Initiated with [AF_INET]208.167.233.196:1195
Jul 05 11:04:10ndmNetwork::Interface::OpenVpn: "OpenVPN0": added host route to remote endpoint 208.167.233.196 via 192.168.55.1.
Jul 05 11:04:12OpenVPN0SENT CONTROL [Server-1786-1a]: 'PUSH_REQUEST' (status=1)
Jul 05 11:04:12OpenVPN0PUSH: Received control message: 'PUSH_REPLY,redirect-gateway def1,dhcp-option DNS 10.98.0.1,route 10.98.0.1,topology net30,ping 10,ping-restart 60,ifconfig 10.98.0.118 10.98.0.117'
Jul 05 11:04:12OpenVPN0OPTIONS IMPORT: timers and/or timeouts modified
Jul 05 11:04:12OpenVPN0OPTIONS IMPORT: --ifconfig/up options modified
Jul 05 11:04:12OpenVPN0OPTIONS IMPORT: route options modified
Jul 05 11:04:12OpenVPN0OPTIONS IMPORT: --ip-win32 and/or --dhcp-option options modified
Jul 05 11:04:12OpenVPN0Outgoing Data Channel: Cipher 'AES-256-CBC' initialized with 256 bit key
Jul 05 11:04:12OpenVPN0Outgoing Data Channel: Using 512 bit message hash 'SHA512' for HMAC authentication
Jul 05 11:04:12OpenVPN0Incoming Data Channel: Cipher 'AES-256-CBC' initialized with 256 bit key
Jul 05 11:04:12OpenVPN0Incoming Data Channel: Using 512 bit message hash 'SHA512' for HMAC authentication
Jul 05 11:04:12OpenVPN0TUN/TAP device tun0 opened
Jul 05 11:04:12OpenVPN0TUN/TAP TX queue length set to 100
Jul 05 11:04:12OpenVPN0do_ifconfig, tt->did_ifconfig_ipv6_setup=0
Jul 05 11:04:12ndmkernel: ADDRCONF(NETDEV_CHANGE): ovpn_br0: link becomes ready
Jul 05 11:04:12ndmNetwork::Interface::IP: "OpenVPN0": IP address is 10.98.0.118/32.
Jul 05 11:04:12ndmNetwork::Interface::OpenVpn: "OpenVPN0": TUN peer address is 10.98.0.117.
Jul 05 11:04:12ndmNetwork::Interface::OpenVpn: "OpenVPN0": added host route to peer 10.98.0.117 via 10.98.0.118.
Jul 05 11:04:14ndmNetwork::Interface::OpenVpn: "OpenVPN0": install accepted default route via 10.98.0.117.
Jul 05 11:04:14ndmNetwork::Interface::OpenVpn: "OpenVPN0": install accepted route to 10.98.0.1/255.255.255.255 via 10.98.0.117.
Jul 05 11:04:15ndmNetwork::Interface::OpenVpn: "OpenVPN0": adding nameserver 10.98.0.1.
Jul 05 11:04:15ndmDns::Manager: name server 10.98.0.1 added, domain (default).
Jul 05 11:04:15ndmNetwork::RoutingTable: gateway 10.98.0.117 is unreachable via OpenVPN0.
Jul 05 11:04:15ndmNetwork::Interface::OpenVpn: "OpenVPN0": failed to add a nameserver route.
Jul 05 11:04:15OpenVPN0GID set to nobody
Jul 05 11:04:15OpenVPN0UID set to nobody
Jul 05 11:04:15OpenVPN0Initialization Sequence Completed
Jul 05 11:04:15ndmNetwork::InterfaceFlusher: flushed WifiMaster0/WifiStation0 conntrack and route cache.
Jul 05 11:04:15upnpshutting down MiniUPnPd
Jul 05 11:04:15ndmCore::Server: client disconnected.
Jul 05 11:04:16ndmNetwork::InternetChecker: Internet access detected.
Jul 05 11:04:17ndmCore::Server: started Session /var/run/ndm.core.socket.
Jul 05 11:04:17upnpHTTP listening on port 55646
Jul 05 11:04:17upnpListening for NAT-PMP/PCP traffic on port 5351
Jul 05 11:06:36ndmCore::System::Clock: system time has been changed.
Jul 05 11:06:36ndmNtp::Client: time synchronized with "0.pool.ntp.org".
Jul 05 11:06:52ndmCloud::Agent: can not connect to the cloud server.
Jul 05 11:07:18ndmDns::Manager: added static record for "rx570.keenetic.pro", address 78.47.125.180.
Jul 05 11:07:19ndmHttp::Manager: activating proxy for giga.rx570.keenetic.pro to upstream 127.0.0.1:80.
Jul 05 11:07:19ndmHttp::Manager: new Web server configuration was applied.
Jul 05 11:08:52wmondWifiMaster1/AccessPoint0: (MT7615) STA(00:18:de:6d:43:ed) had associated successfully.
Jul 05 11:08:52wmondWifiMaster1/AccessPoint0: (MT7615) STA(00:18:de:6d:43:ed) set key done in WPA2/WPA2PSK.
Jul 05 11:08:52ndhcpsDHCPREQUEST received (STATE_INIT) for 192.168.1.38 from 00:18:de:6d:43:ed.
Jul 05 11:08:52ndhcpssending ACK of 192.168.1.38 to 00:18:de:6d:43:ed.
Jul 05 11:13:48ndmCore::Server: started Session /var/run/ndm.core.socket.
Jul 05 11:13:48upnpHTTP listening on port 47104
Jul 05 11:13:48upnpListening for NAT-PMP/PCP traffic on port 5351
Jul 05 11:14:02ndmNetwork::InternetChecker: Internet access lost.
Jul 05 11:14:16ndmCloud::Agent: can not connect to the cloud server.
Jul 05 11:14:36ndmPingCheck::Profile: interface OpenVPN0 connection recovered.
Jul 05 11:14:36ndmNetwork::InterfaceFlusher: flushed WifiMaster0/WifiStation0 conntrack and route cache.
Jul 05 11:14:36upnpshutting down MiniUPnPd
Jul 05 11:14:36ndmCore::Server: client disconnected.
Jul 05 11:14:39ndmCore::Server: started Session /var/run/ndm.core.socket.
Jul 05 11:14:39upnpHTTP listening on port 46406
Jul 05 11:14:39upnpListening for NAT-PMP/PCP traffic on port 5351
Jul 05 11:14:39ndmNetwork::InternetChecker: Internet access detected.
Jul 05 11:17:18ndmCore::Server: started Session /var/run/ndm.core.socket.
Jul 05 11:17:18upnpHTTP listening on port 44546
Jul 05 11:17:18upnpListening for NAT-PMP/PCP traffic on port 5351
Jul 05 11:17:33ndmNetwork::InternetChecker: Internet access lost.
Jul 05 11:17:46ndmCloud::Agent: can not connect to the cloud server.
Jul 05 11:18:07ndmPingCheck::Profile: interface OpenVPN0 connection recovered.
Jul 05 11:18:07ndmNetwork::InterfaceFlusher: flushed WifiMaster0/WifiStation0 conntrack and route cache.
Jul 05 11:18:07upnpshutting down MiniUPnPd
Jul 05 11:18:07ndmCore::Server: client disconnected.
Jul 05 11:18:09ndmCore::Server: started Session /var/run/ndm.core.socket.
Jul 05 11:18:09upnpHTTP listening on port 39952
Jul 05 11:18:09upnpListening for NAT-PMP/PCP traffic on port 5351
Jul 05 11:18:09ndmNetwork::InternetChecker: Internet access detected.
Jul 05 11:20:26ndmCore::Server: started Session /var/run/ndm.core.socket.
Jul 05 11:20:26upnpHTTP listening on port 53663
Jul 05 11:20:26upnpListening for NAT-PMP/PCP traffic on port 5351
Jul 05 11:20:41ndmNetwork::InternetChecker: Internet access lost.
Jul 05 11:20:54ndmCloud::Agent: can not connect to the cloud server.
Jul 05 11:21:15ndmPingCheck::Profile: interface OpenVPN0 connection recovered.
Jul 05 11:21:15ndmNetwork::InterfaceFlusher: flushed WifiMaster0/WifiStation0 conntrack and route cache.
Jul 05 11:21:15upnpshutting down MiniUPnPd
Jul 05 11:21:15ndmCore::Server: client disconnected.
Jul 05 11:21:17ndmCore::Server: started Session /var/run/ndm.core.socket.
Jul 05 11:21:17upnpHTTP listening on port 33743
Jul 05 11:21:17upnpListening for NAT-PMP/PCP traffic on port 5351
Jul 05 11:21:18ndmNetwork::InternetChecker: Internet access detected.
Jul 05 11:22:33ndmCore::Server: started Session /var/run/ndm.core.socket.
Jul 05 11:22:33upnpHTTP listening on port 52939
Jul 05 11:22:33upnpListening for NAT-PMP/PCP traffic on port 5351
Jul 05 11:22:47ndmNetwork::InternetChecker: Internet access lost.
Jul 05 11:23:01ndmCloud::Agent: can not connect to the cloud server.
Jul 05 11:23:21ndmPingCheck::Profile: interface OpenVPN0 connection recovered.
Jul 05 11:23:22ndmNetwork::InterfaceFlusher: flushed WifiMaster0/WifiStation0 conntrack and route cache.
Jul 05 11:23:22upnpshutting down MiniUPnPd
Jul 05 11:23:22ndmCore::Server: client disconnected.
Jul 05 11:23:24ndmCore::Server: started Session /var/run/ndm.core.socket.
Jul 05 11:23:24upnpHTTP listening on port 35546
Jul 05 11:23:24upnpListening for NAT-PMP/PCP traffic on port 5351
Jul 05 11:23:24ndmNetwork::InternetChecker: Internet access detected.
Jul 05 11:25:20ndmCore::Server: started Session /var/run/ndm.core.socket.
Jul 05 11:25:20upnpHTTP listening on port 49300
Jul 05 11:25:20upnpListening for NAT-PMP/PCP traffic on port 5351
Jul 05 11:25:35ndmNetwork::InternetChecker: Internet access lost.
Jul 05 11:25:48ndmCloud::Agent: can not connect to the cloud server.
Jul 05 11:26:09ndmPingCheck::Profile: interface OpenVPN0 connection recovered.
Jul 05 11:26:09ndmNetwork::InterfaceFlusher: flushed WifiMaster0/WifiStation0 conntrack and route cache.
Jul 05 11:26:09upnpshutting down MiniUPnPd
Jul 05 11:26:09ndmCore::Server: client disconnected.
Jul 05 11:26:11ndmCore::Server: started Session /var/run/ndm.core.socket.
Jul 05 11:26:11upnpHTTP listening on port 54576
Jul 05 11:26:11upnpListening for NAT-PMP/PCP traffic on port 5351
Jul 05 11:26:11ndmNetwork::InternetChecker: Internet access detected.
Jul 05 11:26:48ndmDns::Manager: deleted record "rx570.keenetic.pro", address 78.47.125.180.
Jul 05 11:26:48ndmDns::Manager: added static record for "rx570.keenetic.pro", address 78.47.125.180.

Edited July 5, 2018 by cmdmn

Le ecureuil · July 6, 2018

Роутер сверху немного избыточен - достаточно было создать политику с openvpn в качестве wan, и у устройств с этой политикой ничего никуда не вылетит пока openvpn не поднят.

Возможно этот роутер сверху и гадит.

July 9, 2018

Приветствую.

Роутер Extra I, соответсвенно последняя прошивка 2.8

Есть какие-то варианты использования OpenVPN на девайсе?

r13 · July 9, 2018

52 минуты назад, Александр Неизвестный сказал:

Приветствую.

Роутер Extra I, соответсвенно последняя прошивка 2.8

Есть какие-то варианты использования OpenVPN на девайсе?

Вариант тут, смотреть про дельта прошивку:

https://forum.keenetic.net/announcement/5-где-взять-тестовые-прошивки/

Сергей Молоков · July 13, 2018

В 19.06.2018 в 10:07, Сергей Молоков сказал:

В 11.06.2018 в 17:06, Сергей Молоков сказал:

Extra II

Обновился с 2.12.A.6.0-2 до 2.12.B.0.0-4

При загрузке роутера OVPN не подключается

Откатился на 2.11.C.1.0-3, все работает.

Сегодня роутер сам обновился с 2.11.C.1.0-3 на 2.12.C.0.0-1, OVPN не поднялся как и ранее я писал про 2.12.B.0.0-4

Как откатится, если он сам потом обновляется? Есть надежда, что что-то подшаманится и в следующей сборке OVPN будет сам подключаться?

r13 · July 13, 2018

13 минуты назад, Сергей Молоков сказал:

Сегодня роутер сам обновился с 2.11.C.1.0-3 на 2.12.C.0.0-1, OVPN не поднялся как и ранее я писал про 2.12.B.0.0-4

Как откатится, если он сам потом обновляется? Есть надежда, что что-то подшаманится и в следующей сборке OVPN будет сам подключаться?

Отключите автообновление.

Сергей Молоков · July 13, 2018

13 минуты назад, r13 сказал:

Отключите автообновление.

на 2.11 не видел такой галки,

а надежды, что на 2.12 починится подключение OVPN совсем нет?

cmdmn · July 13, 2018

1 минуту назад, Сергей Молоков сказал:

на 2.11 не видел такой галки,

а надежды, что на 2.12 починится подключение OVPN совсем нет?

2.12.C.0.0-1 OVPN работает. Попробуй сбросить настройки и настроить снова.

Сергей Молоков · July 13, 2018

Только что, cmdmn сказал:

Попробуй сбросить настройки и настроить снова.

Хорошо, попробую сегодня сбросить на заводские настройки и перенастроить.

Сам OVPN работает, при переподключении интернета только не поднимается,

приходится отключить его, потом снова подключить и тогда он поднимается.

Может это особенность моего Extra II

r13 · July 13, 2018

27 минут назад, Сергей Молоков сказал:

на 2.11 не видел такой галки

галка только в новом web

24 минуты назад, cmdmn сказал:

а надежды, что на 2.12 починится подключение OVPN совсем нет?

Если воспроизведут, то починят.

Edited July 13, 2018 by r13

Le ecureuil · July 14, 2018

21 час назад, Сергей Молоков сказал:

на 2.11 не видел такой галки,

а надежды, что на 2.12 починится подключение OVPN совсем нет?

Обратитесь в официальную поддержку, тогда точно починим.

dvg_lab · July 14, 2018

Да с новой прошивкой что-то сломалось. OpenVPN не подымается, иные роутеры по 2-3 раза приходится ребутать пока зацепится.

Andrey Krasvitnikov · July 23, 2018

Подскажите, есть ли планы реализации аппаратного шифрования для OpenVPN (openssl)?

Интересует в частности Keenetic Ultra KN-1810, в которой процессор MTK7621 по которому имеется такая информация:

Hardware crypto support for PacketEngine-IP-93 (EIP-93) on MTK7621

The cryptographic engine supports the following cryptographic algorithms: DES in ECB and CBC with 56-bit key Triple-DES in ECB and CBC with 3 x 56-bit key AES in ECB, CBC, ICM, CTR mode with 128-bit 192-bit and 256 bit key ARC4 in stateful, stateless mode, up to 128-bit key Automatic padding up to 255 bytes The hash engine supports the following algorithms: SHA-1, SHA-2-224, SHA-256, MD5 HMAC transforms for SHA-1, SHA-2, MD5 SSL-MAC transforms for SHA-1, MD5 The pseudo random number generator supports: ANSI X9.31 compliant; based on the AES cipher Automatic IV generation

Т.е. по факту поддерживаются почти все типы шифрования на аппаратном уровне.

Andrey Krasvitnikov · July 23, 2018

В 13.07.2018 в 15:02, Сергей Молоков сказал:

Хорошо, попробую сегодня сбросить на заводские настройки и перенастроить.

Сам OVPN работает, при переподключении интернета только не поднимается,

приходится отключить его, потом снова подключить и тогда он поднимается.

Может это особенность моего Extra II

Подтверждаю. OVPN не переподключается при переподключении инет. И так же если в конфиге прописать 2 и более адреса сервера - подключения не перебираются. Просто падает после первого и всё на этом.

Le ecureuil · July 23, 2018

1 час назад, Andrey Krasvitnikov сказал:

Подтверждаю. OVPN не переподключается при переподключении инет. И так же если в конфиге прописать 2 и более адреса сервера - подключения не перебираются. Просто падает после первого и всё на этом.

Перебор серверов пока не работает, а вот на тему падения лучше self-test приложить.

Сергей Молоков · July 24, 2018

5 часов назад, Le ecureuil сказал:

Перебор серверов пока не работает

Удивлен, что второй человек только обратил на это внимание, неужели этим никто не пользуется. Арихи удобная, очень нужная функция.

В 14.07.2018 в 13:55, Le ecureuil сказал:

Обратитесь в официальную поддержку, тогда точно починим.

Ответ: в логах системная ошибка, то есть сам интерфейс OpenVPN не стартует. У нас есть уже несколько обращений с похожим симптомом. Разработчики в курсе, будут разбираться.

5 часов назад, Le ecureuil сказал:

на тему падения лучше self-test приложить.

Тот же селф-тест, что отправлял в оф.тп, выложу здесь

Le ecureuil · July 24, 2018

8 часов назад, Сергей Молоков сказал:

Удивлен, что второй человек только обратил на это внимание, неужели этим никто не пользуется. Арихи удобная, очень нужная функция.

Ответ: в логах системная ошибка, то есть сам интерфейс OpenVPN не стартует. У нас есть уже несколько обращений с похожим симптомом. Разработчики в курсе, будут разбираться.

Тот же селф-тест, что отправлял в оф.тп, выложу здесь

Да, разбираемся с этой проблемой.

Сергей Молоков · August 24, 2018

В 24.07.2018 в 18:01, Le ecureuil сказал:

Да, разбираемся с этой проблемой.

так вроде все уже работает, спасибо, прошивка 2.12.C.1.0-3 (это я про то, что не стартовал OVPN)

Sign In

Вопросы по интеграции OpenVPN в NDMS

Recommended Posts

Link to comment

Share on other sites

Top Posters In This Topic

Popular Days

Top Posters In This Topic

Popular Days

Popular Posts

Le ecureuil

Le ecureuil

Le ecureuil

Posted Images

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Join the conversation

Recently Browsing 0 members