YuraseK
Full Member | Редактировать | Профиль | Сообщение | Цитировать | Сообщить модератору Очень странное поведение OpenVPN 2.3.6 при работе в качестве клиента на Windows Server 2012 R2. Возникают странные разрывы соединения, при этом автоматическое переподключение OpenVPN не проходит успешно. Cервером OpenVPN выступает комьютер на Windows Server 2012 R2. Все клиенты - это Windows Server 2003 R2 и Windows Server 2008 R2. Таким образом проблемы наблюдаются только с клиентом на базе Windows Server 2012 R2. Канал, поверх которого выполняется соединение, на 100 % стабилен. После возникновения разрыва перезапуск службы OpenVPN на клиенте не проходит успешно. В процессах остаётся неубиваемый openvpn.exe. Приходится перезагружать ПК. Конфигурация клиента Цитата: client dev tap proto udp remote 192.168.100.2 1194 nobind persist-key persist-tun ca ca.crt cert server.crt key server.key tls-auth ta.key 1 ns-cert-type server cipher AES-256-CBC comp-lzo verb 3 log-append server.log | Конфигурация сервера Цитата: port 1194 proto udp dev tap ca ca.crt cert proxy.crt key proxy.key dh dh2048.pem server-bridge client-to-client keepalive 10 60 tls-auth ta.key 0 cipher AES-256-CBC comp-lzo persist-key persist-tun log-append openvpn.log verb 3 max-routes-per-client 4096 crl-verify crl.pem | Лог клиента Цитата: //начало работы службы и лога Wed Nov 11 15:40:15 2015 OpenVPN 2.3.6 x86_64-w64-mingw32 [SSL (OpenSSL)] [LZO] [PKCS11] [IPv6] built on Dec 1 2014 Wed Nov 11 15:40:15 2015 library versions: OpenSSL 1.0.1j 15 Oct 2014, LZO 2.08 Wed Nov 11 15:40:16 2015 Control Channel Authentication: using 'ta.key' as a OpenVPN static key file Wed Nov 11 15:40:16 2015 Outgoing Control Channel Authentication: Using 160 bit message hash 'SHA1' for HMAC authentication Wed Nov 11 15:40:16 2015 Incoming Control Channel Authentication: Using 160 bit message hash 'SHA1' for HMAC authentication Wed Nov 11 15:40:16 2015 Socket Buffers: R=[65536->65536] S=[65536->65536] Wed Nov 11 15:40:16 2015 UDPv4 link local: [undef] Wed Nov 11 15:40:16 2015 UDPv4 link remote: [AF_INET]192.168.100.2:1194 Wed Nov 11 15:40:18 2015 TLS: Initial packet from [AF_INET]192.168.100.2:1194, sid=28de849b 75320d9a Wed Nov 11 15:40:18 2015 VERIFY OK: depth=1, C=RU, ST=Msk, L=Msk, O=Company, OU=General, CN=proxy, name=proxy, emailAddress=admin@company.com Wed Nov 11 15:40:18 2015 VERIFY OK: nsCertType=SERVER Wed Nov 11 15:40:18 2015 VERIFY OK: depth=0, C=RU, ST=Msk, L=Msk, O=Company, OU=General, CN=proxy, name=proxy, emailAddress=admin@company.com Wed Nov 11 15:40:18 2015 Data Channel Encrypt: Cipher 'AES-256-CBC' initialized with 256 bit key Wed Nov 11 15:40:18 2015 Data Channel Encrypt: Using 160 bit message hash 'SHA1' for HMAC authentication Wed Nov 11 15:40:18 2015 Data Channel Decrypt: Cipher 'AES-256-CBC' initialized with 256 bit key Wed Nov 11 15:40:18 2015 Data Channel Decrypt: Using 160 bit message hash 'SHA1' for HMAC authentication Wed Nov 11 15:40:18 2015 Control Channel: TLSv1, cipher TLSv1/SSLv3 DHE-RSA-AES256-SHA, 2048 bit RSA Wed Nov 11 15:40:18 2015 [proxy] Peer Connection Initiated with [AF_INET]192.168.100.2:1194 Wed Nov 11 15:40:20 2015 SENT CONTROL [proxy]: 'PUSH_REQUEST' (status=1) Wed Nov 11 15:40:20 2015 PUSH: Received control message: 'PUSH_REPLY,route-proxy dhcp,ping 10,ping-restart 60' Wed Nov 11 15:40:20 2015 OPTIONS IMPORT: timers and/or timeouts modified Wed Nov 11 15:40:20 2015 OPTIONS IMPORT: route-related options modified Wed Nov 11 15:40:20 2015 open_tun, tt->ipv6=0 Wed Nov 11 15:40:20 2015 TAP-WIN32 device [OpenVPN] opened: \\.\Global\{B2BDB612-3EF7-42C1-89E4-980FB525B67F}.tap Wed Nov 11 15:40:20 2015 TAP-Windows Driver Version 9.21 Wed Nov 11 15:40:20 2015 NOTE: FlushIpNetTable failed on interface [16] {B2BDB612-3EF7-42C1-89E4-980FB525B67F} (status=1168) : Элемент не найден. Wed Nov 11 15:40:25 2015 TEST ROUTES: 0/0 succeeded len=0 ret=1 a=0 u/d=up Wed Nov 11 15:40:25 2015 Initialization Sequence Completed //блок лога повторяется каждый час Wed Nov 11 16:40:17 2015 VERIFY OK: depth=1, C=RU, ST=Msk, L=Msk, O=Company, OU=General, CN=proxy, name=proxy, emailAddress=admin@company.com Wed Nov 11 16:40:17 2015 VERIFY OK: nsCertType=SERVER Wed Nov 11 16:40:17 2015 VERIFY OK: depth=0, C=RU, ST=Msk, L=Msk, O=Company, OU=General, CN=proxy, name=proxy, emailAddress=admin@company.com Wed Nov 11 16:40:17 2015 Data Channel Encrypt: Cipher 'AES-256-CBC' initialized with 256 bit key Wed Nov 11 16:40:17 2015 Data Channel Encrypt: Using 160 bit message hash 'SHA1' for HMAC authentication Wed Nov 11 16:40:17 2015 Data Channel Decrypt: Cipher 'AES-256-CBC' initialized with 256 bit key Wed Nov 11 16:40:17 2015 Data Channel Decrypt: Using 160 bit message hash 'SHA1' for HMAC authentication Wed Nov 11 16:40:17 2015 Control Channel: TLSv1, cipher TLSv1/SSLv3 DHE-RSA-AES256-SHA, 2048 bit RSA ... //пропущены повторяющиеся блоки (меняются только в большую сторону значения bytes и pkts) Wed Nov 11 22:40:17 2015 TLS: soft reset sec=0 bytes=588646472/0 pkts=1039096/0 Wed Nov 11 22:40:17 2015 VERIFY OK: depth=1, C=RU, ST=Msk, L=Msk, O=Company, OU=General, CN=proxy, name=proxy, emailAddress=admin@company.com Wed Nov 11 22:40:17 2015 VERIFY OK: nsCertType=SERVER Wed Nov 11 22:40:17 2015 VERIFY OK: depth=0, C=RU, ST=Msk, L=Msk, O=Company, OU=General, CN=proxy, name=proxy, emailAddress=admin@company.com Wed Nov 11 22:40:17 2015 Data Channel Encrypt: Cipher 'AES-256-CBC' initialized with 256 bit key Wed Nov 11 22:40:17 2015 Data Channel Encrypt: Using 160 bit message hash 'SHA1' for HMAC authentication Wed Nov 11 22:40:17 2015 Data Channel Decrypt: Cipher 'AES-256-CBC' initialized with 256 bit key Wed Nov 11 22:40:17 2015 Data Channel Decrypt: Using 160 bit message hash 'SHA1' for HMAC authentication Wed Nov 11 22:40:17 2015 Control Channel: TLSv1, cipher TLSv1/SSLv3 DHE-RSA-AES256-SHA, 2048 bit RSA //начало необъяснимой проблемы (блок лога постоянно повторяется, меняется только значение sid) Wed Nov 11 23:11:59 2015 [proxy] Inactivity timeout (--ping-restart), restarting Wed Nov 11 23:11:59 2015 SIGUSR1[soft,ping-restart] received, process restarting Wed Nov 11 23:11:59 2015 Restart pause, 2 second(s) Wed Nov 11 23:12:01 2015 Socket Buffers: R=[65536->65536] S=[65536->65536] Wed Nov 11 23:12:01 2015 UDPv4 link local: [undef] Wed Nov 11 23:12:01 2015 UDPv4 link remote: [AF_INET]192.168.100.2:1194 Wed Nov 11 23:12:01 2015 TLS: Initial packet from [AF_INET]192.168.100.2:1194, sid=ad8be507 20078c2e Wed Nov 11 23:12:01 2015 VERIFY OK: depth=1, C=RU, ST=Msk, L=Msk, O=Company, OU=General, CN=proxy, name=proxy, emailAddress=admin@company.com Wed Nov 11 23:12:01 2015 VERIFY OK: nsCertType=SERVER Wed Nov 11 23:12:01 2015 VERIFY OK: depth=0, C=RU, ST=Msk, L=Msk, O=Company, OU=General, CN=proxy, name=proxy, emailAddress=admin@company.com Wed Nov 11 23:12:01 2015 Data Channel Encrypt: Cipher 'AES-256-CBC' initialized with 256 bit key Wed Nov 11 23:12:01 2015 Data Channel Encrypt: Using 160 bit message hash 'SHA1' for HMAC authentication Wed Nov 11 23:12:01 2015 Data Channel Decrypt: Cipher 'AES-256-CBC' initialized with 256 bit key Wed Nov 11 23:12:01 2015 Data Channel Decrypt: Using 160 bit message hash 'SHA1' for HMAC authentication Wed Nov 11 23:12:01 2015 Control Channel: TLSv1, cipher TLSv1/SSLv3 DHE-RSA-AES256-SHA, 2048 bit RSA Wed Nov 11 23:12:01 2015 [proxy] Peer Connection Initiated with [AF_INET]192.168.100.2:1194 Wed Nov 11 23:12:03 2015 SENT CONTROL [proxy]: 'PUSH_REQUEST' (status=1) Wed Nov 11 23:12:08 2015 SENT CONTROL [proxy]: 'PUSH_REQUEST' (status=1) Wed Nov 11 23:12:13 2015 SENT CONTROL [proxy]: 'PUSH_REQUEST' (status=1) Wed Nov 11 23:12:18 2015 SENT CONTROL [proxy]: 'PUSH_REQUEST' (status=1) Wed Nov 11 23:12:23 2015 SENT CONTROL [proxy]: 'PUSH_REQUEST' (status=1) Wed Nov 11 23:12:28 2015 SENT CONTROL [proxy]: 'PUSH_REQUEST' (status=1) Wed Nov 11 23:12:33 2015 SENT CONTROL [proxy]: 'PUSH_REQUEST' (status=1) Wed Nov 11 23:12:38 2015 SENT CONTROL [proxy]: 'PUSH_REQUEST' (status=1) Wed Nov 11 23:12:43 2015 SENT CONTROL [proxy]: 'PUSH_REQUEST' (status=1) Wed Nov 11 23:12:48 2015 SENT CONTROL [proxy]: 'PUSH_REQUEST' (status=1) Wed Nov 11 23:12:53 2015 SENT CONTROL [proxy]: 'PUSH_REQUEST' (status=1) Wed Nov 11 23:12:58 2015 SENT CONTROL [proxy]: 'PUSH_REQUEST' (status=1) Сервер почему-то не отвечает на PUSH_REQUEST. | Лог сервера Цитата: Wed Nov 11 23:11:58 2015 read UDPv4: Connection reset by peer (WSAECONNRESET) (code=10054) Wed Nov 11 23:11:59 2015 read UDPv4: Connection reset by peer (WSAECONNRESET) (code=10054) Wed Nov 11 23:12:00 2015 read UDPv4: Connection reset by peer (WSAECONNRESET) (code=10054) Wed Nov 11 23:12:00 2015 192.168.100.1:56124 TLS: Initial packet from [AF_INET]192.168.100.1:56124, sid=833208f7 0a621eda Wed Nov 11 23:12:01 2015 192.168.100.1:56124 CRL CHECK OK: C=RU, ST=Msk, L=Msk, O=Company, OU=General, CN=proxy, name=proxy, emailAddress=admin@company.com Wed Nov 11 23:12:01 2015 192.168.100.1:56124 VERIFY OK: depth=1, C=RU, ST=Msk, L=Msk, O=Company, OU=General, CN=proxy, name=proxy, emailAddress=admin@company.com Wed Nov 11 23:12:01 2015 192.168.100.1:56124 CRL CHECK OK: C=RU, ST=Msk, L=Msk, O=Company, OU=G, CN=server, name=., emailAddress=admin@company.com Wed Nov 11 23:12:01 2015 192.168.100.1:56124 VERIFY OK: depth=0, C=RU, ST=Msk, L=Msk, O=Company, OU=G, CN=server, name=., emailAddress=admin@company.com Wed Nov 11 23:12:01 2015 192.168.100.1:56124 Data Channel Encrypt: Cipher 'AES-256-CBC' initialized with 256 bit key Wed Nov 11 23:12:01 2015 192.168.100.1:56124 Data Channel Encrypt: Using 160 bit message hash 'SHA1' for HMAC authentication Wed Nov 11 23:12:01 2015 192.168.100.1:56124 Data Channel Decrypt: Cipher 'AES-256-CBC' initialized with 256 bit key Wed Nov 11 23:12:01 2015 192.168.100.1:56124 Data Channel Decrypt: Using 160 bit message hash 'SHA1' for HMAC authentication Wed Nov 11 23:12:01 2015 192.168.100.1:56124 Control Channel: TLSv1, cipher TLSv1/SSLv3 DHE-RSA-AES256-SHA, 2048 bit RSA Wed Nov 11 23:12:01 2015 192.168.100.1:56124 [server] Peer Connection Initiated with [AF_INET]192.168.100.1:56124 Wed Nov 11 23:12:01 2015 MULTI: new connection by client 'server' will cause previous active sessions by this client to be dropped. Remember to use the --duplicate-cn option if you want multiple clients using the same certificate or username to concurrently connect. Wed Nov 11 23:12:01 2015 MULTI: no dynamic or static remote --ifconfig address is available for server/192.168.100.1:56124 Wed Nov 11 23:12:02 2015 server/192.168.100.1:56124 PUSH: Received control message: 'PUSH_REQUEST' Wed Nov 11 23:12:02 2015 server/192.168.100.1:56124 send_push_reply(): safe_cap=940 Wed Nov 11 23:12:02 2015 server/192.168.100.1:56124 SENT CONTROL [server]: 'PUSH_REPLY,route-proxy dhcp,ping 10,ping-restart 60' (status=1) Wed Nov 11 23:12:07 2015 server/192.168.100.1:56124 PUSH: Received control message: 'PUSH_REQUEST' Wed Nov 11 23:12:13 2015 server/192.168.100.1:56124 PUSH: Received control message: 'PUSH_REQUEST' Wed Nov 11 23:12:18 2015 server/192.168.100.1:56124 PUSH: Received control message: 'PUSH_REQUEST' Wed Nov 11 23:13:01 2015 read UDPv4: Connection reset by peer (WSAECONNRESET) (code=10054) ... Wed Nov 11 23:13:04 2015 read UDPv4: Connection reset by peer (WSAECONNRESET) (code=10054) Wed Nov 11 23:13:04 2015 192.168.100.1:60238 TLS: Initial packet from [AF_INET]192.168.100.1:60238, sid=c5ac6671 3f69009a Wed Nov 11 23:13:05 2015 192.168.100.1:60238 CRL CHECK OK: C=RU, ST=Msk, L=Msk, O=Company, OU=General, CN=proxy, name=proxy, emailAddress=admin@company.com Wed Nov 11 23:13:05 2015 192.168.100.1:60238 VERIFY OK: depth=1, C=RU, ST=Msk, L=Msk, O=Company, OU=General, CN=proxy, name=proxy, emailAddress=admin@company.com Wed Nov 11 23:13:05 2015 192.168.100.1:60238 CRL CHECK OK: C=RU, ST=Msk, L=Msk, O=Company, OU=G, CN=server, name=., emailAddress=admin@company.com Wed Nov 11 23:13:05 2015 192.168.100.1:60238 VERIFY OK: depth=0, C=RU, ST=Msk, L=Msk, O=Company, OU=G, CN=server, name=., emailAddress=admin@company.com Wed Nov 11 23:13:05 2015 192.168.100.1:60238 Data Channel Encrypt: Cipher 'AES-256-CBC' initialized with 256 bit key Wed Nov 11 23:13:05 2015 192.168.100.1:60238 Data Channel Encrypt: Using 160 bit message hash 'SHA1' for HMAC authentication Wed Nov 11 23:13:05 2015 192.168.100.1:60238 Data Channel Decrypt: Cipher 'AES-256-CBC' initialized with 256 bit key Wed Nov 11 23:13:05 2015 192.168.100.1:60238 Data Channel Decrypt: Using 160 bit message hash 'SHA1' for HMAC authentication Wed Nov 11 23:13:05 2015 192.168.100.1:60238 Control Channel: TLSv1, cipher TLSv1/SSLv3 DHE-RSA-AES256-SHA, 2048 bit RSA Wed Nov 11 23:13:05 2015 192.168.100.1:60238 [server] Peer Connection Initiated with [AF_INET]192.168.100.1:60238 Wed Nov 11 23:13:05 2015 MULTI: new connection by client 'server' will cause previous active sessions by this client to be dropped. Remember to use the --duplicate-cn option if you want multiple clients using the same certificate or username to concurrently connect. Wed Nov 11 23:13:05 2015 MULTI: no dynamic or static remote --ifconfig address is available for server/192.168.100.1:60238 Wed Nov 11 23:13:06 2015 server/192.168.100.1:60238 PUSH: Received control message: 'PUSH_REQUEST' Wed Nov 11 23:13:06 2015 server/192.168.100.1:60238 send_push_reply(): safe_cap=940 Wed Nov 11 23:13:06 2015 server/192.168.100.1:60238 SENT CONTROL [server]: 'PUSH_REPLY,route-proxy dhcp,ping 10,ping-restart 60' (status=1) Wed Nov 11 23:13:11 2015 server/192.168.100.1:60238 PUSH: Received control message: 'PUSH_REQUEST' Wed Nov 11 23:13:16 2015 server/192.168.100.1:60238 PUSH: Received control message: 'PUSH_REQUEST' Wed Nov 11 23:13:21 2015 server/192.168.100.1:60238 PUSH: Received control message: 'PUSH_REQUEST' Wed Nov 11 23:14:05 2015 read UDPv4: Connection reset by peer (WSAECONNRESET) (code=10054) ... Wed Nov 11 23:14:08 2015 read UDPv4: Connection reset by peer (WSAECONNRESET) (code=10054) Wed Nov 11 23:14:09 2015 192.168.100.1:55086 TLS: Initial packet from [AF_INET]192.168.100.1:55086, sid=c124b9cb 9acac1c2 Wed Nov 11 23:14:09 2015 192.168.100.1:55086 CRL CHECK OK: C=RU, ST=Msk, L=Msk, O=Company, OU=General, CN=proxy, name=proxy, emailAddress=admin@company.com Wed Nov 11 23:14:09 2015 192.168.100.1:55086 VERIFY OK: depth=1, C=RU, ST=Msk, L=Msk, O=Company, OU=General, CN=proxy, name=proxy, emailAddress=admin@company.com Wed Nov 11 23:14:09 2015 192.168.100.1:55086 CRL CHECK OK: C=RU, ST=Msk, L=Msk, O=Company, OU=G, CN=server, name=., emailAddress=admin@company.com Wed Nov 11 23:14:09 2015 192.168.100.1:55086 VERIFY OK: depth=0, C=RU, ST=Msk, L=Msk, O=Company, OU=G, CN=server, name=., emailAddress=admin@company.com Wed Nov 11 23:14:09 2015 192.168.100.1:55086 Data Channel Encrypt: Cipher 'AES-256-CBC' initialized with 256 bit key Wed Nov 11 23:14:09 2015 192.168.100.1:55086 Data Channel Encrypt: Using 160 bit message hash 'SHA1' for HMAC authentication Wed Nov 11 23:14:09 2015 192.168.100.1:55086 Data Channel Decrypt: Cipher 'AES-256-CBC' initialized with 256 bit key Wed Nov 11 23:14:09 2015 192.168.100.1:55086 Data Channel Decrypt: Using 160 bit message hash 'SHA1' for HMAC authentication Wed Nov 11 23:14:09 2015 192.168.100.1:55086 Control Channel: TLSv1, cipher TLSv1/SSLv3 DHE-RSA-AES256-SHA, 2048 bit RSA Wed Nov 11 23:14:09 2015 192.168.100.1:55086 [server] Peer Connection Initiated with [AF_INET]192.168.100.1:55086 Wed Nov 11 23:14:09 2015 MULTI: new connection by client 'server' will cause previous active sessions by this client to be dropped. Remember to use the --duplicate-cn option if you want multiple clients using the same certificate or username to concurrently connect. Wed Nov 11 23:14:09 2015 MULTI: no dynamic or static remote --ifconfig address is available for server/192.168.100.1:55086 Wed Nov 11 23:14:10 2015 server/192.168.100.1:55086 PUSH: Received control message: 'PUSH_REQUEST' Wed Nov 11 23:14:10 2015 server/192.168.100.1:55086 send_push_reply(): safe_cap=940 Wed Nov 11 23:14:10 2015 server/192.168.100.1:55086 SENT CONTROL [server]: 'PUSH_REPLY,route-proxy dhcp,ping 10,ping-restart 60' (status=1) Wed Nov 11 23:14:15 2015 server/192.168.100.1:55086 PUSH: Received control message: 'PUSH_REQUEST' Wed Nov 11 23:14:20 2015 server/192.168.100.1:55086 PUSH: Received control message: 'PUSH_REQUEST' Wed Nov 11 23:14:26 2015 server/192.168.100.1:55086 PUSH: Received control message: 'PUSH_REQUEST' Wed Nov 11 23:15:08 2015 read UDPv4: Connection reset by peer (WSAECONNRESET) (code=10054) ... Wed Nov 11 23:15:12 2015 read UDPv4: Connection reset by peer (WSAECONNRESET) (code=10054) Wed Nov 11 23:15:12 2015 192.168.100.1:51469 TLS: Initial packet from [AF_INET]192.168.100.1:51469, sid=49ef6d20 d7f4ed3c Wed Nov 11 23:15:12 2015 192.168.100.1:51469 CRL CHECK OK: C=RU, ST=Msk, L=Msk, O=Company, OU=General, CN=proxy, name=proxy, emailAddress=admin@company.com Wed Nov 11 23:15:12 2015 192.168.100.1:51469 VERIFY OK: depth=1, C=RU, ST=Msk, L=Msk, O=Company, OU=General, CN=proxy, name=proxy, emailAddress=admin@company.com Wed Nov 11 23:15:12 2015 192.168.100.1:51469 CRL CHECK OK: C=RU, ST=Msk, L=Msk, O=Company, OU=G, CN=server, name=., emailAddress=admin@company.com Wed Nov 11 23:15:12 2015 192.168.100.1:51469 VERIFY OK: depth=0, C=RU, ST=Msk, L=Msk, O=Company, OU=G, CN=server, name=., emailAddress=admin@company.com Wed Nov 11 23:15:12 2015 192.168.100.1:51469 Data Channel Encrypt: Cipher 'AES-256-CBC' initialized with 256 bit key Wed Nov 11 23:15:12 2015 192.168.100.1:51469 Data Channel Encrypt: Using 160 bit message hash 'SHA1' for HMAC authentication Wed Nov 11 23:15:12 2015 192.168.100.1:51469 Data Channel Decrypt: Cipher 'AES-256-CBC' initialized with 256 bit key Wed Nov 11 23:15:12 2015 192.168.100.1:51469 Data Channel Decrypt: Using 160 bit message hash 'SHA1' for HMAC authentication Wed Nov 11 23:15:12 2015 192.168.100.1:51469 Control Channel: TLSv1, cipher TLSv1/SSLv3 DHE-RSA-AES256-SHA, 2048 bit RSA Wed Nov 11 23:15:12 2015 192.168.100.1:51469 [server] Peer Connection Initiated with [AF_INET]192.168.100.1:51469 Wed Nov 11 23:15:12 2015 MULTI: new connection by client 'server' will cause previous active sessions by this client to be dropped. Remember to use the --duplicate-cn option if you want multiple clients using the same certificate or username to concurrently connect. Wed Nov 11 23:15:12 2015 MULTI: no dynamic or static remote --ifconfig address is available for server/192.168.100.1:51469 Wed Nov 11 23:15:14 2015 server/192.168.100.1:51469 PUSH: Received control message: 'PUSH_REQUEST' Wed Nov 11 23:15:14 2015 server/192.168.100.1:51469 send_push_reply(): safe_cap=940 Wed Nov 11 23:15:14 2015 server/192.168.100.1:51469 SENT CONTROL [server]: 'PUSH_REPLY,route-proxy dhcp,ping 10,ping-restart 60' (status=1) Wed Nov 11 23:15:19 2015 server/192.168.100.1:51469 PUSH: Received control message: 'PUSH_REQUEST' Wed Nov 11 23:15:24 2015 server/192.168.100.1:51469 PUSH: Received control message: 'PUSH_REQUEST' Wed Nov 11 23:15:29 2015 server/192.168.100.1:51469 PUSH: Received control message: 'PUSH_REQUEST' Wed Nov 11 23:16:12 2015 read UDPv4: Connection reset by peer (WSAECONNRESET) (code=10054) ... Wed Nov 11 23:16:16 2015 read UDPv4: Connection reset by peer (WSAECONNRESET) (code=10054) | Таким образом не ясна причина возникновения разрыва соединения, после которого сервер считает, что соединение активно и не позволяет выполнить тому же клиенту повторное подключение. Я пока включил на сервере опцию duplicate-cn, чтобы было возможно повторное подключение. Может кто сталкивался с таким поведением OpenVPN? | Всего записей: 566 | Зарегистр. 12-12-2003 | Отправлено: 11:29 12-11-2015 | Исправлено: YuraseK, 11:58 12-11-2015 |
|