Автор Тема: Проблема с соединением Open VPN клиента  (Прочитано 5880 раз)

0 Пользователей и 1 Гость просматривают эту тему.

Dr.Lecter

  • Гость
После изменения конфигурации Open VPN клиента, он перестал соединяться с сервером выдавая в логах следующее:

Wed Mar 04 18:06:14 2009 OpenVPN 2.0.9 Win32-MinGW [SSL] [LZO] built on Feb  9 2007
Wed Mar 04 18:06:14 2009 IMPORTANT: OpenVPN's default port number is now 1194, based on an official port number assignment by IANA.  OpenVPN 2.0-beta16 and earlier used 5000 as the default port.
Wed Mar 04 18:06:14 2009 LZO compression initialized
Wed Mar 04 18:06:14 2009 Control Channel MTU parms [ L:1574 D:138 EF:38 EB:0 ET:0 EL:0 ]
Wed Mar 04 18:06:14 2009 Data Channel MTU parms [ L:1574 D:1450 EF:42 EB:135 ET:32 EL:0 AF:3/1 ]
Wed Mar 04 18:06:14 2009 Local Options hash (VER=V4): 'd79ca330'
Wed Mar 04 18:06:14 2009 Expected Remote Options hash (VER=V4): 'f7df56b8'
Wed Mar 04 18:06:14 2009 UDPv4 link local: [undef]
Wed Mar 04 18:06:14 2009 UDPv4 link remote: 80.81.208.82:55800
Wed Mar 04 18:06:14 2009 TLS: Initial packet from 80.81.208.82:55800, sid=32581368 351137d2
Wed Mar 04 18:06:16 2009 VERIFY OK: depth=1, /C=RU/ST=MW/L=MOSCOW/O=RadugaVPN/emailAddress=support@telecom-service.net
Wed Mar 04 18:06:16 2009 VERIFY OK: nsCertType=SERVER
Wed Mar 04 18:06:16 2009 VERIFY OK: depth=0, /C=RU/ST=MW/O=RadugaVPN/CN=RadugaVPN/emailAddress=support@telecom-service.net
Wed Mar 04 18:06:20 2009 Data Channel Encrypt: Cipher 'BF-CBC' initialized with 128 bit key
Wed Mar 04 18:06:20 2009 Data Channel Encrypt: Using 160 bit message hash 'SHA1' for HMAC authentication
Wed Mar 04 18:06:20 2009 Data Channel Decrypt: Cipher 'BF-CBC' initialized with 128 bit key
Wed Mar 04 18:06:20 2009 Data Channel Decrypt: Using 160 bit message hash 'SHA1' for HMAC authentication
Wed Mar 04 18:06:20 2009 Control Channel: TLSv1, cipher TLSv1/SSLv3 DHE-RSA-AES256-SHA, 1024 bit RSA
Wed Mar 04 18:06:20 2009 [RadugaVPN] Peer Connection Initiated with 80.81.208.82:55800
Wed Mar 04 18:06:21 2009 SENT CONTROL [RadugaVPN]: 'PUSH_REQUEST' (status=1)
Wed Mar 04 18:06:21 2009 PUSH: Received control message: 'PUSH_REPLY,redirect-gateway,dhcp-option DNS 80.81.208.82,route-gateway 10.255.0.1,ping 30,ping-restart 120,route 0.0.0.0 0.0.0.0 10.255.0.1,ifconfig 10.255.171.38 255.255.0.0'
Wed Mar 04 18:06:21 2009 OPTIONS IMPORT: timers and/or timeouts modified
Wed Mar 04 18:06:21 2009 OPTIONS IMPORT: --ifconfig/up options modified
Wed Mar 04 18:06:21 2009 OPTIONS IMPORT: route options modified
Wed Mar 04 18:06:21 2009 OPTIONS IMPORT: --ip-win32 and/or --dhcp-option options modified
Wed Mar 04 18:06:22 2009 TAP-WIN32 device [Raduga] opened: \\.\Global\{0B789EFF-88B2-4279-B0C3-DA0D4CCC67B1}.tap
Wed Mar 04 18:06:22 2009 TAP-Win32 Driver Version 8.4
Wed Mar 04 18:06:22 2009 TAP-Win32 MTU=1500
Wed Mar 04 18:06:22 2009 Notified TAP-Win32 driver to set a DHCP IP/netmask of 10.255.171.38/255.255.0.0 on interface {0B789EFF-88B2-4279-B0C3-DA0D4CCC67B1} [DHCP-serv: 10.255.0.0, lease-time: 31536000]
Wed Mar 04 18:06:22 2009 Successful ARP Flush on interface [262147] {0B789EFF-88B2-4279-B0C3-DA0D4CCC67B1}
Wed Mar 04 18:06:22 2009 WARNING: You have selected '--ip-win32 dynamic', which will not work unless the TAP-Win32 TCP/IP properties are set to 'Obtain an IP address automatically'
Wed Mar 04 18:06:22 2009 TEST ROUTES: 0/0 succeeded len=1 ret=0 a=0 u/d=down
Wed Mar 04 18:06:22 2009 Route: Waiting for TUN/TAP interface to come up...
Wed Mar 04 18:06:23 2009 TEST ROUTES: 0/0 succeeded len=1 ret=0 a=0 u/d=down

... ... ...

Wed Mar 04 18:06:49 2009 Route: Waiting for TUN/TAP interface to come up...
Wed Mar 04 18:06:50 2009 TEST ROUTES: 0/0 succeeded len=1 ret=0 a=0 u/d=down
Wed Mar 04 18:06:50 2009 Route: Waiting for TUN/TAP interface to come up...
Wed Mar 04 18:06:51 2009 TEST ROUTES: 0/0 succeeded len=1 ret=0 a=0 u/d=down
Wed Mar 04 18:06:51 2009 route ADD 80.81.208.82 MASK 255.255.255.255 92.36.114.150
Wed Mar 04 18:06:51 2009 Route addition via IPAPI succeeded
Wed Mar 04 18:06:51 2009 route DELETE 0.0.0.0 MASK 0.0.0.0 92.36.114.150
Wed Mar 04 18:06:51 2009 Route deletion via IPAPI succeeded
Wed Mar 04 18:06:51 2009 route ADD 0.0.0.0 MASK 0.0.0.0 10.255.0.1
Wed Mar 04 18:06:51 2009 Warning: route gateway is not reachable on any active network adapters: 10.255.0.1
Wed Mar 04 18:06:51 2009 Route addition via IPAPI failed
Wed Mar 04 18:06:51 2009 route ADD 0.0.0.0 MASK 0.0.0.0 10.255.0.1
Wed Mar 04 18:06:51 2009 Warning: route gateway is not reachable on any active network adapters: 10.255.0.1
Wed Mar 04 18:06:51 2009 Route addition via IPAPI failed
Wed Mar 04 18:06:51 2009 Initialization Sequence Completed With Errors ( see http://openvpn.net/faq.html#dhcpclientserv )

Пробовал заново переустанавливать и настраивать клиент, .bat файлик тоже перезапускал, но все безрезультатно.
До 11 часов утра все отлично работало, после изменений - больше нет. Испробовал вроде бы все, но до сих пор не понял, в чем проблема...

Оффлайн R@inBoW

  • Продвинутый
  • *****
  • Сообщений: 1915
Проблема с соединением Open VPN клиента
« Ответ #1 : 04.03.2009, 19:25:27 »
Новости читаем внимательно http://newforums.d-v.ru/index.php?topic=8368.0

*BIR - максимально возможная скорость, которая может меняться по мере загрузки канала
********************************
http://www.radugainternet.ru/

s.p.

  • Гость
Проблема с соединением Open VPN клиента
« Ответ #2 : 04.03.2009, 20:40:23 »
Скачал новые ключи. Тоже не могу проиконнектиться.

Wed Mar 04 21:35:32 2009 OpenVPN 2.0.9 Win32-MinGW [SSL] [LZO] built on Feb  9 2007
Wed Mar 04 21:35:32 2009 IMPORTANT: OpenVPN's default port number is now 1194, based on an official port number assignment by IANA.  OpenVPN 2.0-beta16 and earlier used 5000 as the default port.
Wed Mar 04 21:35:32 2009 LZO compression initialized
Wed Mar 04 21:35:32 2009 Control Channel MTU parms [ L:1574 D:138 EF:38 EB:0 ET:0 EL:0 ]
Wed Mar 04 21:35:32 2009 Data Channel MTU parms [ L:1574 D:1450 EF:42 EB:135 ET:32 EL:0 AF:3/1 ]
Wed Mar 04 21:35:32 2009 Local Options hash (VER=V4): 'd79ca330'
Wed Mar 04 21:35:32 2009 Expected Remote Options hash (VER=V4): 'f7df56b8'
Wed Mar 04 21:35:32 2009 UDPv4 link local: [undef]
Wed Mar 04 21:35:32 2009 UDPv4 link remote: 80.81.208.82:56000
Wed Mar 04 21:35:35 2009 read UDPv4: Connection reset by peer (WSAECONNRESET) (code=10054)
Wed Mar 04 21:35:37 2009 read UDPv4: Connection reset by peer (WSAECONNRESET) (code=10054)
Wed Mar 04 21:35:38 2009 read UDPv4: Connection reset by peer (WSAECONNRESET) (code=10054)
Wed Mar 04 21:35:40 2009 read UDPv4: Connection reset by peer (WSAECONNRESET) (code=10054)
Wed Mar 04 21:35:43 2009 read UDPv4: Connection reset by peer (WSAECONNRESET) (code=10054)
Wed Mar 04 21:35:45 2009 read UDPv4: Connection reset by peer (WSAECONNRESET) (code=10054)
Wed Mar 04 21:35:47 2009 read UDPv4: Connection reset by peer (WSAECONNRESET) (code=10054)
Wed Mar 04 21:35:49 2009 read UDPv4: Connection reset by peer (WSAECONNRESET) (code=10054)
Wed Mar 04 21:35:52 2009 read UDPv4: Connection reset by peer (WSAECONNRESET) (code=10054)
Wed Mar 04 21:35:54 2009 read UDPv4: Connection reset by peer (WSAECONNRESET) (code=10054)
Wed Mar 04 21:35:55 2009 read UDPv4: Connection reset by peer (WSAECONNRESET) (code=10054)
Wed Mar 04 21:35:57 2009 read UDPv4: Connection reset by peer (WSAECONNRESET) (code=10054)
Wed Mar 04 21:35:59 2009 read UDPv4: Connection reset by peer (WSAECONNRESET) (code=10054)
Wed Mar 04 21:36:01 2009 read UDPv4: Connection reset by peer (WSAECONNRESET) (code=10054)
Wed Mar 04 21:36:04 2009 read UDPv4: Connection reset by peer (WSAECONNRESET) (code=10054)
Wed Mar 04 21:36:07 2009 read UDPv4: Connection reset by peer (WSAECONNRESET) (code=10054)
Wed Mar 04 21:36:09 2009 read UDPv4: Connection reset by peer (WSAECONNRESET) (code=10054)
Wed Mar 04 21:36:12 2009 read UDPv4: Connection reset by peer (WSAECONNRESET) (code=10054)
Wed Mar 04 21:36:15 2009 read UDPv4: Connection reset by peer (WSAECONNRESET) (code=10054)
Wed Mar 04 21:36:18 2009 read UDPv4: Connection reset by peer (WSAECONNRESET) (code=10054)
Wed Mar 04 21:36:19 2009 read UDPv4: Connection reset by peer (WSAECONNRESET) (code=10054)
Wed Mar 04 21:36:22 2009 read UDPv4: Connection reset by peer (WSAECONNRESET) (code=10054)
Wed Mar 04 21:36:23 2009 read UDPv4: Connection reset by peer (WSAECONNRESET) (code=10054)
Wed Mar 04 21:36:25 2009 read UDPv4: Connection reset by peer (WSAECONNRESET) (code=10054)
Wed Mar 04 21:36:27 2009 read UDPv4: Connection reset by peer (WSAECONNRESET) (code=10054)
Wed Mar 04 21:36:29 2009 read UDPv4: Connection reset by peer (WSAECONNRESET) (code=10054)
Wed Mar 04 21:36:31 2009 read UDPv4: Connection reset by peer (WSAECONNRESET) (code=10054)
Wed Mar 04 21:36:32 2009 TLS Error: TLS key negotiation failed to occur within 60 seconds (check your network connectivity)
Wed Mar 04 21:36:32 2009 TLS Error: TLS handshake failed
Wed Mar 04 21:36:32 2009 TCP/UDP: Closing socket
Wed Mar 04 21:36:32 2009 SIGUSR1[soft,tls-error] received, process restarting
Wed Mar 04 21:36:32 2009 Restart pause, 2 second(s)
Wed Mar 04 21:36:34 2009 IMPORTANT: OpenVPN's default port number is now 1194, based on an official port number assignment by IANA.  OpenVPN 2.0-beta16 and earlier used 5000 as the default port.
Wed Mar 04 21:36:34 2009 Re-using SSL/TLS context
Wed Mar 04 21:36:34 2009 LZO compression initialized
Wed Mar 04 21:36:34 2009 Control Channel MTU parms [ L:1574 D:138 EF:38 EB:0 ET:0 EL:0 ]
Wed Mar 04 21:36:34 2009 Data Channel MTU parms [ L:1574 D:1450 EF:42 EB:135 ET:32 EL:0 AF:3/1 ]
Wed Mar 04 21:36:34 2009 Local Options hash (VER=V4): 'd79ca330'
Wed Mar 04 21:36:34 2009 Expected Remote Options hash (VER=V4): 'f7df56b8'
Wed Mar 04 21:36:34 2009 UDPv4 link local: [undef]
Wed Mar 04 21:36:34 2009 UDPv4 link remote: 80.81.208.82:56000
Wed Mar 04 21:36:34 2009 read UDPv4: Connection reset by peer (WSAECONNRESET) (code=10054)
Wed Mar 04 21:36:36 2009 read UDPv4: Connection reset by peer (WSAECONNRESET) (code=10054)

Dr.Lecter

  • Гость
Проблема с соединением Open VPN клиента
« Ответ #3 : 04.03.2009, 21:04:43 »
Новости читаем внимательно http://newforums.d-v.ru/index.php?topic=8368.0

Я конечно понимаю, что расчет на человека, просто не прочитавшего новости или вообще непонятно как сюда попавшего в таком деле как настройка спутникового интернета чаще всего бывает полностью оправдан, а на анализ логов у администратора может просто не быть времени...
Но к сожалению, это не мой случай, и все гораздо проще. С новостями я был знаком еще до начала процесса изменения конфига, все файлы и изменения в них тоже были изучены и применены. Антивируса сейчас нет, фаер отлично настроен и ничего не блокирует, все порты, соединения и программы разрешены и работают.
А проблема только в том, что все поставлено и настроено, но работать не хочет))[/size]

Оффлайн Dima

  • Администратор
  • *****
  • Сообщений: 6510
Проблема с соединением Open VPN клиента
« Ответ #4 : 05.03.2009, 12:03:23 »
Скачал новые ключи. Тоже не могу проиконнектиться.

Wed Mar 04 21:35:32 2009 OpenVPN 2.0.9 Win32-MinGW [SSL] [LZO] built on Feb  9 2007
Wed Mar 04 21:35:32 2009 IMPORTANT: OpenVPN's default port number is now 1194, based on an official port number assignment by IANA.  OpenVPN 2.0-beta16 and earlier used 5000 as the default port.
Wed Mar 04 21:35:32 2009 LZO compression initialized
Wed Mar 04 21:35:32 2009 Control Channel MTU parms [ L:1574 D:138 EF:38 EB:0 ET:0 EL:0 ]
Wed Mar 04 21:35:32 2009 Data Channel MTU parms [ L:1574 D:1450 EF:42 EB:135 ET:32 EL:0 AF:3/1 ]
Wed Mar 04 21:35:32 2009 Local Options hash (VER=V4): 'd79ca330'
Wed Mar 04 21:35:32 2009 Expected Remote Options hash (VER=V4): 'f7df56b8'
Wed Mar 04 21:35:32 2009 UDPv4 link local: [undef]
Wed Mar 04 21:35:32 2009 UDPv4 link remote: 80.81.208.82:56000
Wed Mar 04 21:35:35 2009 read UDPv4: Connection reset by peer (WSAECONNRESET) (code=10054)
Wed Mar 04 21:35:37 2009 read UDPv4: Connection reset by peer (WSAECONNRESET) (code=10054)
Wed Mar 04 21:35:38 2009 read UDPv4: Connection reset by peer (WSAECONNRESET) (code=10054)
Wed Mar 04 21:35:40 2009 read UDPv4: Connection reset by peer (WSAECONNRESET) (code=10054)
Wed Mar 04 21:35:43 2009 read UDPv4: Connection reset by peer (WSAECONNRESET) (code=10054)
Wed Mar 04 21:35:45 2009 read UDPv4: Connection reset by peer (WSAECONNRESET) (code=10054)
Wed Mar 04 21:35:47 2009 read UDPv4: Connection reset by peer (WSAECONNRESET) (code=10054)
Wed Mar 04 21:35:49 2009 read UDPv4: Connection reset by peer (WSAECONNRESET) (code=10054)
Wed Mar 04 21:35:52 2009 read UDPv4: Connection reset by peer (WSAECONNRESET) (code=10054)
Wed Mar 04 21:35:54 2009 read UDPv4: Connection reset by peer (WSAECONNRESET) (code=10054)
Wed Mar 04 21:35:55 2009 read UDPv4: Connection reset by peer (WSAECONNRESET) (code=10054)
Wed Mar 04 21:35:57 2009 read UDPv4: Connection reset by peer (WSAECONNRESET) (code=10054)
Wed Mar 04 21:35:59 2009 read UDPv4: Connection reset by peer (WSAECONNRESET) (code=10054)
Wed Mar 04 21:36:01 2009 read UDPv4: Connection reset by peer (WSAECONNRESET) (code=10054)
Wed Mar 04 21:36:04 2009 read UDPv4: Connection reset by peer (WSAECONNRESET) (code=10054)
Wed Mar 04 21:36:07 2009 read UDPv4: Connection reset by peer (WSAECONNRESET) (code=10054)
Wed Mar 04 21:36:09 2009 read UDPv4: Connection reset by peer (WSAECONNRESET) (code=10054)
Wed Mar 04 21:36:12 2009 read UDPv4: Connection reset by peer (WSAECONNRESET) (code=10054)
Wed Mar 04 21:36:15 2009 read UDPv4: Connection reset by peer (WSAECONNRESET) (code=10054)
Wed Mar 04 21:36:18 2009 read UDPv4: Connection reset by peer (WSAECONNRESET) (code=10054)
Wed Mar 04 21:36:19 2009 read UDPv4: Connection reset by peer (WSAECONNRESET) (code=10054)
Wed Mar 04 21:36:22 2009 read UDPv4: Connection reset by peer (WSAECONNRESET) (code=10054)
Wed Mar 04 21:36:23 2009 read UDPv4: Connection reset by peer (WSAECONNRESET) (code=10054)
Wed Mar 04 21:36:25 2009 read UDPv4: Connection reset by peer (WSAECONNRESET) (code=10054)
Wed Mar 04 21:36:27 2009 read UDPv4: Connection reset by peer (WSAECONNRESET) (code=10054)
Wed Mar 04 21:36:29 2009 read UDPv4: Connection reset by peer (WSAECONNRESET) (code=10054)
Wed Mar 04 21:36:31 2009 read UDPv4: Connection reset by peer (WSAECONNRESET) (code=10054)
Wed Mar 04 21:36:32 2009 TLS Error: TLS key negotiation failed to occur within 60 seconds (check your network connectivity)
Wed Mar 04 21:36:32 2009 TLS Error: TLS handshake failed
Wed Mar 04 21:36:32 2009 TCP/UDP: Closing socket
Wed Mar 04 21:36:32 2009 SIGUSR1[soft,tls-error] received, process restarting
Wed Mar 04 21:36:32 2009 Restart pause, 2 second(s)
Wed Mar 04 21:36:34 2009 IMPORTANT: OpenVPN's default port number is now 1194, based on an official port number assignment by IANA.  OpenVPN 2.0-beta16 and earlier used 5000 as the default port.
Wed Mar 04 21:36:34 2009 Re-using SSL/TLS context
Wed Mar 04 21:36:34 2009 LZO compression initialized
Wed Mar 04 21:36:34 2009 Control Channel MTU parms [ L:1574 D:138 EF:38 EB:0 ET:0 EL:0 ]
Wed Mar 04 21:36:34 2009 Data Channel MTU parms [ L:1574 D:1450 EF:42 EB:135 ET:32 EL:0 AF:3/1 ]
Wed Mar 04 21:36:34 2009 Local Options hash (VER=V4): 'd79ca330'
Wed Mar 04 21:36:34 2009 Expected Remote Options hash (VER=V4): 'f7df56b8'
Wed Mar 04 21:36:34 2009 UDPv4 link local: [undef]
Wed Mar 04 21:36:34 2009 UDPv4 link remote: 80.81.208.82:56000
Wed Mar 04 21:36:34 2009 read UDPv4: Connection reset by peer (WSAECONNRESET) (code=10054)
Wed Mar 04 21:36:36 2009 read UDPv4: Connection reset by peer (WSAECONNRESET) (code=10054)

ПРОВЕРЯЕМ... Отпишу результат
Спасибо, отловили багу... Исправили... :) Попробуйте сейчас, у меня с вашей подпиской OpenVPN подключается нормально. Приносим извинения.
« Последнее редактирование: 05.03.2009, 12:27:41 от Dima »
1) Хочешь сделать что-то ХОРОШО, сделай это САМ...
2) Кто в саппорте служил - тот в цирке не смеется...
3) Настоящий мужчина скидок не просит и сдачу не берет!

s.p.

  • Гость
Проблема с соединением Open VPN клиента
« Ответ #5 : 05.03.2009, 17:48:29 »
Спасибо! Все заработало!