Автор Тема: Все те же вилы...  (Прочитано 5202 раз)

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

Dr.Lecter

  • Гость
Все те же вилы...
« : 06.03.2009, 01:03:51 »
Предыдущую тему как-то поспешно закрыли... Однако проблема до сих пор не решена, 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 )
« Последнее редактирование: 06.03.2009, 12:15:49 от R@inBoW »

Оффлайн Dima

  • Администратор
  • *****
  • Сообщений: 6510
Все те же вилы...
« Ответ #1 : 06.03.2009, 11:59:16 »
To Dr.Lecter
Вот лог ОпенВПН с ВАШИМИ КЛЮЧАМИ. айпи цепляется тоже ваш, все без проблем.
Проверьте свои настройки еще раз. Айпи подписки с карты сняли?


Fri Mar 06 11:00:24 2009 OpenVPN 2.0.9 Win32-MinGW [SSL] [LZO] built on Feb  9 2007
Fri Mar 06 11:00:24 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.
Fri Mar 06 11:00:24 2009 LZO compression initialized
Fri Mar 06 11:00:24 2009 Control Channel MTU parms [ L:1574 D:138 EF:38 EB:0 ET:0 EL:0 ]
Fri Mar 06 11:00:24 2009 Data Channel MTU parms [ L:1574 D:1450 EF:42 EB:135 ET:32 EL:0 AF:3/1 ]
Fri Mar 06 11:00:24 2009 Local Options hash (VER=V4): 'd79ca330'
Fri Mar 06 11:00:24 2009 Expected Remote Options hash (VER=V4): 'f7df56b8'
Fri Mar 06 11:00:24 2009 UDPv4 link local: [undef]
Fri Mar 06 11:00:24 2009 UDPv4 link remote: 80.81.208.82:55800
Fri Mar 06 11:00:24 2009 TLS: Initial packet from 80.81.208.82:55800, sid=9de35068 634e9100
Fri Mar 06 11:00:24 2009 VERIFY OK: depth=1, /C=RU/ST=MW/L=MOSCOW/O=RadugaVPN/emailAddress=support@telecom-service.net
Fri Mar 06 11:00:24 2009 VERIFY OK: nsCertType=SERVER
Fri Mar 06 11:00:24 2009 VERIFY OK: depth=0, /C=RU/ST=MW/O=RadugaVPN/CN=RadugaVPN/emailAddress=support@telecom-service.net
Fri Mar 06 11:00:24 2009 Data Channel Encrypt: Cipher 'BF-CBC' initialized with 128 bit key
Fri Mar 06 11:00:24 2009 Data Channel Encrypt: Using 160 bit message hash 'SHA1' for HMAC authentication
Fri Mar 06 11:00:24 2009 Data Channel Decrypt: Cipher 'BF-CBC' initialized with 128 bit key
Fri Mar 06 11:00:24 2009 Data Channel Decrypt: Using 160 bit message hash 'SHA1' for HMAC authentication
Fri Mar 06 11:00:24 2009 Control Channel: TLSv1, cipher TLSv1/SSLv3 DHE-RSA-AES256-SHA, 1024 bit RSA
Fri Mar 06 11:00:24 2009 [RadugaVPN] Peer Connection Initiated with 80.81.208.82:55800
Fri Mar 06 11:00:25 2009 SENT CONTROL [RadugaVPN]: 'PUSH_REQUEST' (status=1)
Fri Mar 06 11:00:25 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,dhcp-option DNS 80.81.208.82,ifconfig 10.255.171.38 255.255.0.0'
Fri Mar 06 11:00:25 2009 OPTIONS IMPORT: timers and/or timeouts modified
Fri Mar 06 11:00:25 2009 OPTIONS IMPORT: --ifconfig/up options modified
Fri Mar 06 11:00:25 2009 OPTIONS IMPORT: route options modified
Fri Mar 06 11:00:25 2009 OPTIONS IMPORT: --ip-win32 and/or --dhcp-option options modified
Fri Mar 06 11:00:25 2009 TAP-WIN32 device [Raduga] opened: \\.\Global\{9C248AFC-1955-4B5A-8730-AE3BBF2CC96D}.tap
Fri Mar 06 11:00:25 2009 TAP-Win32 Driver Version 8.4
Fri Mar 06 11:00:25 2009 TAP-Win32 MTU=1500
Fri Mar 06 11:00:25 2009 Notified TAP-Win32 driver to set a DHCP IP/netmask of 10.255.171.38/255.255.0.0 on interface {9C248AFC-1955-4B5A-8730-AE3BBF2CC96D} [DHCP-serv: 10.255.0.0, lease-time: 31536000]
Fri Mar 06 11:00:25 2009 NOTE: FlushIpNetTable failed on interface [131076] {9C248AFC-1955-4B5A-8730-AE3BBF2CC96D} (status=259) : Дополнительные данные отсутствуют. 
Fri Mar 06 11:00:25 2009 TEST ROUTES: 0/0 succeeded len=1 ret=0 a=0 u/d=down
Fri Mar 06 11:00:25 2009 Route: Waiting for TUN/TAP interface to come up...
Fri Mar 06 11:00:26 2009 TEST ROUTES: 2/2 succeeded len=1 ret=1 a=0 u/d=up
Fri Mar 06 11:00:26 2009 route ADD 80.81.208.82 MASK 255.255.255.255 192.168.0.101
Fri Mar 06 11:00:26 2009 Route addition via IPAPI succeeded
Fri Mar 06 11:00:26 2009 route DELETE 0.0.0.0 MASK 0.0.0.0 192.168.0.101
Fri Mar 06 11:00:26 2009 Route deletion via IPAPI succeeded
Fri Mar 06 11:00:26 2009 route ADD 0.0.0.0 MASK 0.0.0.0 10.255.0.1
Fri Mar 06 11:00:26 2009 Route addition via IPAPI succeeded
Fri Mar 06 11:00:26 2009 route ADD 0.0.0.0 MASK 0.0.0.0 10.255.0.1
Fri Mar 06 11:00:26 2009 Route addition via IPAPI succeeded
Fri Mar 06 11:00:26 2009 Initialization Sequence Completed
« Последнее редактирование: 06.03.2009, 12:16:15 от R@inBoW »
1) Хочешь сделать что-то ХОРОШО, сделай это САМ...
2) Кто в саппорте служил - тот в цирке не смеется...
3) Настоящий мужчина скидок не просит и сдачу не берет!

Dr.Lecter

  • Гость
Все те же вилы...
« Ответ #2 : 07.03.2009, 11:24:48 »
Да, мне тоже начало казаться что это был какой-то локальный глюк клиента, который почему-то появился только после установки новых ключей. В интерфейсе ДВБ карты стоит адрес
192.168.238.238 / 255.255.255.0, собственно, адрес подписки я туда никогда и не вписывал, сразу ставил этот и все прекрасно работало. Все настройки программ и адаптеров я уже проверил раз эдак 15, и 4 раза переустановил ВПН клиент. Пока не помогло.
Единственная строчка в логах за которую можно еще зацепиться -
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'
Только вот с чего система решила что я " have selected '--ip-win32 dynamic' " - понятия пока не имею)). Все настройки TAP-Win32 адаптера такие же как всегда, а этой строки я вроде-бы раньше не замечал. Параметр --ip-win32 dynamic' тоже нигде не нашел, ни в файлах программы, ни в реестре (хотя там я не слишком глубоко рылся), но судя по логам, скорее всего эта опция импортируется в программу с сервера.
Ладно, покопаюсь еще где-нибудь в системе или инете, может что получится))

Dr.Lecter

  • Гость
Все те же вилы...
« Ответ #3 : 07.03.2009, 21:00:29 »
Неисповедимы пути системы... В свойствах TCP протокола TAP-Win32 Adapter-а вместо фиксированного IP aдреса подписки  проставил автоматическое назначение адресов. Иииии... Все заработало...

Оффлайн Dima

  • Администратор
  • *****
  • Сообщений: 6510
Все те же вилы...
« Ответ #4 : 10.03.2009, 12:31:20 »
Неисповедимы пути системы... В свойствах TCP протокола TAP-Win32 Adapter-а вместо фиксированного IP aдреса подписки  проставил автоматическое назначение адресов. Иииии... Все заработало...

Да, такое может может быть... неисповедимы виндоусовские прибабахи...:)
1) Хочешь сделать что-то ХОРОШО, сделай это САМ...
2) Кто в саппорте служил - тот в цирке не смеется...
3) Настоящий мужчина скидок не просит и сдачу не берет!

Budo

  • Гость
Все те же вилы...
« Ответ #5 : 19.03.2009, 06:16:54 »
У меня тоже такие же проблемы, служба поддержки толком так и не решили эту проблему

Thu Mar 19 09:04:37 2009 OpenVPN 2.0.9 Win32-MinGW [SSL] [LZO] built on Feb  9 2007
Thu Mar 19 09:04:37 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.
Thu Mar 19 09:04:37 2009 LZO compression initialized
Thu Mar 19 09:04:37 2009 Control Channel MTU parms [ L:1574 D:138 EF:38 EB:0 ET:0 EL:0 ]
Thu Mar 19 09:04:37 2009 Data Channel MTU parms [ L:1574 D:1450 EF:42 EB:135 ET:32 EL:0 AF:3/1 ]
Thu Mar 19 09:04:37 2009 Local Options hash (VER=V4): 'd79ca330'
Thu Mar 19 09:04:37 2009 Expected Remote Options hash (VER=V4): 'f7df56b8'
Thu Mar 19 09:04:37 2009 UDPv4 link local: [undef]
Thu Mar 19 09:04:37 2009 UDPv4 link remote: 80.81.208.66:55000
Thu Mar 19 09:04:38 2009 TLS: Initial packet from 80.81.208.66:55000, sid=043b9db9 199c3c4e
Thu Mar 19 09:04:41 2009 VERIFY OK: depth=1, /C=RU/ST=MW/L=MOSCOW/O=RadugaVPN/emailAddress=support@telecom-service.net
Thu Mar 19 09:04:41 2009 VERIFY OK: nsCertType=SERVER
Thu Mar 19 09:04:41 2009 VERIFY OK: depth=0, /C=RU/ST=MW/O=RadugaVPN/CN=RadugaVPN/emailAddress=support@telecom-service.net
Thu Mar 19 09:04:46 2009 Data Channel Encrypt: Cipher 'BF-CBC' initialized with 128 bit key
Thu Mar 19 09:04:46 2009 Data Channel Encrypt: Using 160 bit message hash 'SHA1' for HMAC authentication
Thu Mar 19 09:04:46 2009 Data Channel Decrypt: Cipher 'BF-CBC' initialized with 128 bit key
Thu Mar 19 09:04:46 2009 Data Channel Decrypt: Using 160 bit message hash 'SHA1' for HMAC authentication
Thu Mar 19 09:04:46 2009 Control Channel: TLSv1, cipher TLSv1/SSLv3 DHE-RSA-AES256-SHA, 1024 bit RSA
Thu Mar 19 09:04:46 2009 [RadugaVPN] Peer Connection Initiated with 80.81.208.66:55000
Thu Mar 19 09:04:47 2009 SENT CONTROL [RadugaVPN]: 'PUSH_REQUEST' (status=1)
Thu Mar 19 09:04:48 2009 PUSH: Received control message: 'PUSH_REPLY,redirect-gateway,dhcp-option DNS 80.81.208.66,route-gateway 10.251.0.1,ping 30,ping-restart 120,route 0.0.0.0 0.0.0.0 10.251.0.1,dhcp-option DNS 80.81.208.34,ifconfig 10.251.35.19 255.255.0.0'
Thu Mar 19 09:04:48 2009 OPTIONS IMPORT: timers and/or timeouts modified
Thu Mar 19 09:04:48 2009 OPTIONS IMPORT: --ifconfig/up options modified
Thu Mar 19 09:04:48 2009 OPTIONS IMPORT: route options modified
Thu Mar 19 09:04:48 2009 OPTIONS IMPORT: --ip-win32 and/or --dhcp-option options modified
Thu Mar 19 09:04:48 2009 TAP-WIN32 device [Raduga] opened: \\.\Global\{044375F6-500A-4243-867B-0F040AF4FA12}.tap
Thu Mar 19 09:04:48 2009 TAP-Win32 Driver Version 8.4
Thu Mar 19 09:04:48 2009 TAP-Win32 MTU=1500
Thu Mar 19 09:04:48 2009 Notified TAP-Win32 driver to set a DHCP IP/netmask of 10.251.35.19/255.255.0.0 on interface {044375F6-500A-4243-867B-0F040AF4FA12} [DHCP-serv: 10.251.0.0, lease-time: 31536000]
Thu Mar 19 09:04:48 2009 Successful ARP Flush on interface [2] {044375F6-500A-4243-867B-0F040AF4FA12}
Thu Mar 19 09:04:48 2009 TEST ROUTES: 0/0 succeeded len=1 ret=0 a=0 u/d=down
Thu Mar 19 09:04:48 2009 Route: Waiting for TUN/TAP interface to come up...
Thu Mar 19 09:04:50 2009 TEST ROUTES: 0/0 succeeded len=1 ret=0 a=0 u/d=down
Thu Mar 19 09:04:50 2009 Route: Waiting for TUN/TAP interface to come up...
Thu Mar 19 09:04:51 2009 TEST ROUTES: 0/0 succeeded len=1 ret=0 a=0 u/d=down
Thu Mar 19 09:04:51 2009 Route: Waiting for TUN/TAP interface to come up...
Thu Mar 19 09:04:52 2009 TEST ROUTES: 0/0 succeeded len=1 ret=0 a=0 u/d=down
Thu Mar 19 09:04:52 2009 Route: Waiting for TUN/TAP interface to come up...
Thu Mar 19 09:04:53 2009 TEST ROUTES: 0/0 succeeded len=1 ret=0 a=0 u/d=down
Thu Mar 19 09:04:53 2009 Route: Waiting for TUN/TAP interface to come up...
Thu Mar 19 09:04:54 2009 TEST ROUTES: 0/0 succeeded len=1 ret=0 a=0 u/d=down
Thu Mar 19 09:04:54 2009 Route: Waiting for TUN/TAP interface to come up...
Thu Mar 19 09:04:55 2009 TEST ROUTES: 0/0 succeeded len=1 ret=0 a=0 u/d=down
Thu Mar 19 09:04:55 2009 Route: Waiting for TUN/TAP interface to come up...
Thu Mar 19 09:04:56 2009 TEST ROUTES: 0/0 succeeded len=1 ret=0 a=0 u/d=down
Thu Mar 19 09:04:56 2009 Route: Waiting for TUN/TAP interface to come up...
Thu Mar 19 09:04:57 2009 TEST ROUTES: 0/0 succeeded len=1 ret=0 a=0 u/d=down
Thu Mar 19 09:04:57 2009 Route: Waiting for TUN/TAP interface to come up...
Thu Mar 19 09:04:58 2009 TEST ROUTES: 0/0 succeeded len=1 ret=0 a=0 u/d=down
Thu Mar 19 09:04:58 2009 Route: Waiting for TUN/TAP interface to come up...
Thu Mar 19 09:04:59 2009 TEST ROUTES: 0/0 succeeded len=1 ret=0 a=0 u/d=down
Thu Mar 19 09:04:59 2009 Route: Waiting for TUN/TAP interface to come up...
Thu Mar 19 09:05:00 2009 TEST ROUTES: 0/0 succeeded len=1 ret=0 a=0 u/d=down
Thu Mar 19 09:05:00 2009 Route: Waiting for TUN/TAP interface to come up...
Thu Mar 19 09:05:01 2009 TEST ROUTES: 0/0 succeeded len=1 ret=0 a=0 u/d=down
Thu Mar 19 09:05:01 2009 Route: Waiting for TUN/TAP interface to come up...
Thu Mar 19 09:05:03 2009 TEST ROUTES: 0/0 succeeded len=1 ret=0 a=0 u/d=down
Thu Mar 19 09:05:03 2009 Route: Waiting for TUN/TAP interface to come up...
Thu Mar 19 09:05:04 2009 TEST ROUTES: 0/0 succeeded len=1 ret=0 a=0 u/d=down
Thu Mar 19 09:05:04 2009 Route: Waiting for TUN/TAP interface to come up...
Thu Mar 19 09:05:05 2009 TEST ROUTES: 0/0 succeeded len=1 ret=0 a=0 u/d=down
Thu Mar 19 09:05:05 2009 Route: Waiting for TUN/TAP interface to come up...
Thu Mar 19 09:05:06 2009 TEST ROUTES: 0/0 succeeded len=1 ret=0 a=0 u/d=down
Thu Mar 19 09:05:06 2009 Route: Waiting for TUN/TAP interface to come up...
Thu Mar 19 09:05:08 2009 TEST ROUTES: 0/0 succeeded len=1 ret=0 a=0 u/d=down
Thu Mar 19 09:05:08 2009 Route: Waiting for TUN/TAP interface to come up...
Thu Mar 19 09:05:09 2009 TEST ROUTES: 0/0 succeeded len=1 ret=0 a=0 u/d=down
Thu Mar 19 09:05:09 2009 Route: Waiting for TUN/TAP interface to come up...
Thu Mar 19 09:05:10 2009 TEST ROUTES: 0/0 succeeded len=1 ret=0 a=0 u/d=down
Thu Mar 19 09:05:10 2009 Route: Waiting for TUN/TAP interface to come up...
Thu Mar 19 09:05:11 2009 TEST ROUTES: 0/0 succeeded len=1 ret=0 a=0 u/d=down
Thu Mar 19 09:05:11 2009 Route: Waiting for TUN/TAP interface to come up...
Thu Mar 19 09:05:12 2009 TEST ROUTES: 0/0 succeeded len=1 ret=0 a=0 u/d=down
Thu Mar 19 09:05:12 2009 Route: Waiting for TUN/TAP interface to come up...
Thu Mar 19 09:05:13 2009 TEST ROUTES: 0/0 succeeded len=1 ret=0 a=0 u/d=down
Thu Mar 19 09:05:13 2009 Route: Waiting for TUN/TAP interface to come up...
Thu Mar 19 09:05:15 2009 TEST ROUTES: 0/0 succeeded len=1 ret=0 a=0 u/d=down
Thu Mar 19 09:05:15 2009 Route: Waiting for TUN/TAP interface to come up...
Thu Mar 19 09:05:16 2009 TEST ROUTES: 0/0 succeeded len=1 ret=0 a=0 u/d=down
Thu Mar 19 09:05:16 2009 Route: Waiting for TUN/TAP interface to come up...
Thu Mar 19 09:05:17 2009 TEST ROUTES: 0/0 succeeded len=1 ret=0 a=0 u/d=down
Thu Mar 19 09:05:17 2009 Route: Waiting for TUN/TAP interface to come up...
Thu Mar 19 09:05:18 2009 TEST ROUTES: 0/0 succeeded len=1 ret=0 a=0 u/d=down
Thu Mar 19 09:05:18 2009 route ADD 80.81.208.66 MASK 255.255.255.255 192.168.4.201
Thu Mar 19 09:05:18 2009 Route addition via IPAPI succeeded
Thu Mar 19 09:05:18 2009 route DELETE 0.0.0.0 MASK 0.0.0.0 192.168.4.201
Thu Mar 19 09:05:18 2009 Route deletion via IPAPI succeeded
Thu Mar 19 09:05:18 2009 route ADD 0.0.0.0 MASK 0.0.0.0 10.251.0.1
Thu Mar 19 09:05:18 2009 Warning: route gateway is not reachable on any active network adapters: 10.251.0.1
Thu Mar 19 09:05:18 2009 Route addition via IPAPI failed
Thu Mar 19 09:05:18 2009 route ADD 0.0.0.0 MASK 0.0.0.0 10.251.0.1
Thu Mar 19 09:05:18 2009 Warning: route gateway is not reachable on any active network adapters: 10.251.0.1
Thu Mar 19 09:05:18 2009 Route addition via IPAPI failed
Thu Mar 19 09:05:18 2009 Initialization Sequence Completed With Errors ( see http://openvpn.net/faq.html#dhcpclientserv )
Thu Mar 19 09:05:30 2009 TCP/UDP: Closing socket
Thu Mar 19 09:05:30 2009 route DELETE 80.81.208.66 MASK 255.255.255.255 192.168.4.201
Thu Mar 19 09:05:30 2009 Route deletion via IPAPI succeeded
Thu Mar 19 09:05:30 2009 route DELETE 0.0.0.0 MASK 0.0.0.0 10.251.0.1
Thu Mar 19 09:05:30 2009 Warning: route gateway is not reachable on any active network adapters: 10.251.0.1
Thu Mar 19 09:05:30 2009 Route deletion via IPAPI failed
Thu Mar 19 09:05:30 2009 route ADD 0.0.0.0 MASK 0.0.0.0 192.168.4.201
Thu Mar 19 09:05:30 2009 Route addition via IPAPI succeeded
Thu Mar 19 09:05:30 2009 Closing TUN/TAP interface
Thu Mar 19 09:05:30 2009 SIGTERM[hard,] received, process exiting

Оффлайн Dima

  • Администратор
  • *****
  • Сообщений: 6510
Все те же вилы...
« Ответ #6 : 19.03.2009, 12:22:01 »
У вас либо ip подписки на карту прописан,либо какойнть антивирь или файрвол не дает приконнектиться...
1) Хочешь сделать что-то ХОРОШО, сделай это САМ...
2) Кто в саппорте служил - тот в цирке не смеется...
3) Настоящий мужчина скидок не просит и сдачу не берет!

Budo

  • Гость
Все те же вилы...
« Ответ #7 : 19.03.2009, 13:09:42 »
Удалил антивирус NOD и Ad-Aware все равно
Thu Mar 19 18:11:22 2009 OpenVPN 2.0.9 Win32-MinGW [SSL] [LZO] built on Feb  9 2007
Thu Mar 19 18:11:22 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.
Thu Mar 19 18:11:22 2009 LZO compression initialized
Thu Mar 19 18:11:22 2009 Control Channel MTU parms [ L:1574 D:138 EF:38 EB:0 ET:0 EL:0 ]
Thu Mar 19 18:11:22 2009 Data Channel MTU parms [ L:1574 D:1450 EF:42 EB:135 ET:32 EL:0 AF:3/1 ]
Thu Mar 19 18:11:22 2009 Local Options hash (VER=V4): 'd79ca330'
Thu Mar 19 18:11:22 2009 Expected Remote Options hash (VER=V4): 'f7df56b8'
Thu Mar 19 18:11:22 2009 UDPv4 link local: [undef]
Thu Mar 19 18:11:22 2009 UDPv4 link remote: 80.81.208.66:55000
Thu Mar 19 18:11:22 2009 TLS: Initial packet from 80.81.208.66:55000, sid=7151975b 33ccb151
Thu Mar 19 18:11:26 2009 VERIFY OK: depth=1, /C=RU/ST=MW/L=MOSCOW/O=RadugaVPN/emailAddress=support@telecom-service.net
Thu Mar 19 18:11:26 2009 VERIFY OK: nsCertType=SERVER
Thu Mar 19 18:11:26 2009 VERIFY OK: depth=0, /C=RU/ST=MW/O=RadugaVPN/CN=RadugaVPN/emailAddress=support@telecom-service.net
Thu Mar 19 18:11:31 2009 Data Channel Encrypt: Cipher 'BF-CBC' initialized with 128 bit key
Thu Mar 19 18:11:31 2009 Data Channel Encrypt: Using 160 bit message hash 'SHA1' for HMAC authentication
Thu Mar 19 18:11:31 2009 Data Channel Decrypt: Cipher 'BF-CBC' initialized with 128 bit key
Thu Mar 19 18:11:31 2009 Data Channel Decrypt: Using 160 bit message hash 'SHA1' for HMAC authentication
Thu Mar 19 18:11:31 2009 Control Channel: TLSv1, cipher TLSv1/SSLv3 DHE-RSA-AES256-SHA, 1024 bit RSA
Thu Mar 19 18:11:31 2009 [RadugaVPN] Peer Connection Initiated with 80.81.208.66:55000
Thu Mar 19 18:11:32 2009 SENT CONTROL [RadugaVPN]: 'PUSH_REQUEST' (status=1)
Thu Mar 19 18:11:33 2009 PUSH: Received control message: 'PUSH_REPLY,redirect-gateway,dhcp-option DNS 80.81.208.66,route-gateway 10.251.0.1,ping 30,ping-restart 120,route 0.0.0.0 0.0.0.0 10.251.0.1,dhcp-option DNS 80.81.208.34,ifconfig 10.251.35.19 255.255.0.0'
Thu Mar 19 18:11:33 2009 OPTIONS IMPORT: timers and/or timeouts modified
Thu Mar 19 18:11:33 2009 OPTIONS IMPORT: --ifconfig/up options modified
Thu Mar 19 18:11:33 2009 OPTIONS IMPORT: route options modified
Thu Mar 19 18:11:33 2009 OPTIONS IMPORT: --ip-win32 and/or --dhcp-option options modified
Thu Mar 19 18:11:33 2009 TAP-WIN32 device [Raduga] opened: \\.\Global\{044375F6-500A-4243-867B-0F040AF4FA12}.tap
Thu Mar 19 18:11:33 2009 TAP-Win32 Driver Version 8.4
Thu Mar 19 18:11:33 2009 TAP-Win32 MTU=1500
Thu Mar 19 18:11:33 2009 Notified TAP-Win32 driver to set a DHCP IP/netmask of 10.251.35.19/255.255.0.0 on interface {044375F6-500A-4243-867B-0F040AF4FA12} [DHCP-serv: 10.251.0.0, lease-time: 31536000]
Thu Mar 19 18:11:33 2009 Successful ARP Flush on interface [2] {044375F6-500A-4243-867B-0F040AF4FA12}
Thu Mar 19 18:11:33 2009 TEST ROUTES: 0/0 succeeded len=1 ret=0 a=0 u/d=down
Thu Mar 19 18:11:33 2009 Route: Waiting for TUN/TAP interface to come up...
Thu Mar 19 18:11:34 2009 TEST ROUTES: 0/0 succeeded len=1 ret=0 a=0 u/d=down
Thu Mar 19 18:11:34 2009 Route: Waiting for TUN/TAP interface to come up...
Thu Mar 19 18:11:35 2009 TEST ROUTES: 0/0 succeeded len=1 ret=0 a=0 u/d=down
Thu Mar 19 18:11:35 2009 Route: Waiting for TUN/TAP interface to come up...
Thu Mar 19 18:11:36 2009 TEST ROUTES: 0/0 succeeded len=1 ret=0 a=0 u/d=down
Thu Mar 19 18:11:36 2009 Route: Waiting for TUN/TAP interface to come up...
Thu Mar 19 18:11:37 2009 TEST ROUTES: 0/0 succeeded len=1 ret=0 a=0 u/d=down
Thu Mar 19 18:11:37 2009 Route: Waiting for TUN/TAP interface to come up...
Thu Mar 19 18:11:38 2009 TEST ROUTES: 0/0 succeeded len=1 ret=0 a=0 u/d=down
Thu Mar 19 18:11:38 2009 Route: Waiting for TUN/TAP interface to come up...
Thu Mar 19 18:11:39 2009 TEST ROUTES: 0/0 succeeded len=1 ret=0 a=0 u/d=down
Thu Mar 19 18:11:39 2009 Route: Waiting for TUN/TAP interface to come up...
Thu Mar 19 18:11:40 2009 TEST ROUTES: 0/0 succeeded len=1 ret=0 a=0 u/d=down
Thu Mar 19 18:11:40 2009 Route: Waiting for TUN/TAP interface to come up...
Thu Mar 19 18:11:41 2009 TEST ROUTES: 0/0 succeeded len=1 ret=0 a=0 u/d=down
Thu Mar 19 18:11:41 2009 Route: Waiting for TUN/TAP interface to come up...
Thu Mar 19 18:11:42 2009 TEST ROUTES: 0/0 succeeded len=1 ret=0 a=0 u/d=down
Thu Mar 19 18:11:42 2009 Route: Waiting for TUN/TAP interface to come up...
Thu Mar 19 18:11:43 2009 TEST ROUTES: 0/0 succeeded len=1 ret=0 a=0 u/d=down
Thu Mar 19 18:11:43 2009 Route: Waiting for TUN/TAP interface to come up...
Thu Mar 19 18:11:44 2009 TEST ROUTES: 0/0 succeeded len=1 ret=0 a=0 u/d=down
Thu Mar 19 18:11:44 2009 Route: Waiting for TUN/TAP interface to come up...
Thu Mar 19 18:11:45 2009 TEST ROUTES: 0/0 succeeded len=1 ret=0 a=0 u/d=down
Thu Mar 19 18:11:45 2009 Route: Waiting for TUN/TAP interface to come up...
Thu Mar 19 18:11:46 2009 TEST ROUTES: 0/0 succeeded len=1 ret=0 a=0 u/d=down
Thu Mar 19 18:11:46 2009 Route: Waiting for TUN/TAP interface to come up...
Thu Mar 19 18:11:47 2009 TEST ROUTES: 0/0 succeeded len=1 ret=0 a=0 u/d=down
Thu Mar 19 18:11:47 2009 Route: Waiting for TUN/TAP interface to come up...
Thu Mar 19 18:11:48 2009 TEST ROUTES: 0/0 succeeded len=1 ret=0 a=0 u/d=down
Thu Mar 19 18:11:48 2009 Route: Waiting for TUN/TAP interface to come up...
Thu Mar 19 18:11:49 2009 TEST ROUTES: 0/0 succeeded len=1 ret=0 a=0 u/d=down
Thu Mar 19 18:11:49 2009 Route: Waiting for TUN/TAP interface to come up...
Thu Mar 19 18:11:50 2009 TEST ROUTES: 0/0 succeeded len=1 ret=0 a=0 u/d=down
Thu Mar 19 18:11:50 2009 Route: Waiting for TUN/TAP interface to come up...
Thu Mar 19 18:11:51 2009 TEST ROUTES: 0/0 succeeded len=1 ret=0 a=0 u/d=down
Thu Mar 19 18:11:51 2009 Route: Waiting for TUN/TAP interface to come up...
Thu Mar 19 18:11:52 2009 TEST ROUTES: 0/0 succeeded len=1 ret=0 a=0 u/d=down
Thu Mar 19 18:11:52 2009 Route: Waiting for TUN/TAP interface to come up...
Thu Mar 19 18:11:54 2009 TEST ROUTES: 0/0 succeeded len=1 ret=0 a=0 u/d=down
Thu Mar 19 18:11:54 2009 Route: Waiting for TUN/TAP interface to come up...
Thu Mar 19 18:11:55 2009 TEST ROUTES: 0/0 succeeded len=1 ret=0 a=0 u/d=down
Thu Mar 19 18:11:55 2009 Route: Waiting for TUN/TAP interface to come up...
Thu Mar 19 18:11:56 2009 TEST ROUTES: 0/0 succeeded len=1 ret=0 a=0 u/d=down
Thu Mar 19 18:11:56 2009 Route: Waiting for TUN/TAP interface to come up...
Thu Mar 19 18:11:57 2009 TEST ROUTES: 0/0 succeeded len=1 ret=0 a=0 u/d=down
Thu Mar 19 18:11:57 2009 Route: Waiting for TUN/TAP interface to come up...
Thu Mar 19 18:11:59 2009 TEST ROUTES: 0/0 succeeded len=1 ret=0 a=0 u/d=down
Thu Mar 19 18:11:59 2009 Route: Waiting for TUN/TAP interface to come up...
Thu Mar 19 18:12:00 2009 TEST ROUTES: 0/0 succeeded len=1 ret=0 a=0 u/d=down
Thu Mar 19 18:12:00 2009 Route: Waiting for TUN/TAP interface to come up...
Thu Mar 19 18:12:01 2009 TEST ROUTES: 0/0 succeeded len=1 ret=0 a=0 u/d=down
Thu Mar 19 18:12:01 2009 Route: Waiting for TUN/TAP interface to come up...
Thu Mar 19 18:12:02 2009 TEST ROUTES: 0/0 succeeded len=1 ret=0 a=0 u/d=down
Thu Mar 19 18:12:02 2009 Route: Waiting for TUN/TAP interface to come up...
Thu Mar 19 18:12:03 2009 TEST ROUTES: 0/0 succeeded len=1 ret=0 a=0 u/d=down
Thu Mar 19 18:12:03 2009 route ADD 80.81.208.66 MASK 255.255.255.255 192.168.4.201
Thu Mar 19 18:12:03 2009 Route addition via IPAPI succeeded
Thu Mar 19 18:12:03 2009 route DELETE 0.0.0.0 MASK 0.0.0.0 192.168.4.201
Thu Mar 19 18:12:03 2009 Route deletion via IPAPI succeeded
Thu Mar 19 18:12:03 2009 route ADD 0.0.0.0 MASK 0.0.0.0 10.251.0.1
Thu Mar 19 18:12:03 2009 Warning: route gateway is not reachable on any active network adapters: 10.251.0.1
Thu Mar 19 18:12:03 2009 Route addition via IPAPI failed
Thu Mar 19 18:12:03 2009 route ADD 0.0.0.0 MASK 0.0.0.0 10.251.0.1
Thu Mar 19 18:12:03 2009 Warning: route gateway is not reachable on any active network adapters: 10.251.0.1
Thu Mar 19 18:12:03 2009 Route addition via IPAPI failed
Thu Mar 19 18:12:03 2009 Initialization Sequence Completed With Errors ( see http://openvpn.net/faq.html#dhcpclientserv )

Павел

  • Гость
Все те же вилы...
« Ответ #8 : 19.03.2009, 13:19:50 »
Данная строка лога Initialization Sequence Completed With Errors говорит о том что на одном из устройств прописан IP вашей подписки, вследствие чего возникает конфликт IP адресов и адаптеру ТАП присваивается "левый" IP. В командной строке выполните команду ipconfig /all и проверьте не присвоен ли какому-нибудь подключению ваш IP. На самом адаптере должно быть автоматическое присвоение IP адреса. Если IP не найдете в активных подключениях, то попробуйте присвоить этот IP одному из устройств, при этом система Windows напишет что этот IP уже присвоен и напишет конкретное устройство, возможно оно удалено и вы можете посмотреть его в диспетчере устройств.
« Последнее редактирование: 19.03.2009, 13:23:08 от Павел »

Budo

  • Гость
Все те же вилы...
« Ответ #9 : 19.03.2009, 23:05:18 »
Пришлось винд переставить, все заработало. Спасибо