Автор Тема: Help! Тоже не могу openvpn настроить, что б его.  (Прочитано 7904 раз)

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

FENIX

  • Гость
Все темы про vpn перечитал, но так и не понял, где собака зарыта  ???. Сделал всё по инструкции, пишет, что соединение установлено, но страницы не грузятся. Что не так, где копать, что за ошибка в конце?

Sun Jun 14 17:29:49 2009 OpenVPN 2.0.9 Win32-MinGW [SSL] [LZO] built on Feb  9 2007
Sun Jun 14 17:29:49 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.
Sun Jun 14 17:29:49 2009 LZO compression initialized
Sun Jun 14 17:29:49 2009 Control Channel MTU parms [ L:1574 D:138 EF:38 EB:0 ET:0 EL:0 ]
Sun Jun 14 17:29:49 2009 Data Channel MTU parms [ L:1574 D:1450 EF:42 EB:135 ET:32 EL:0 AF:3/1 ]
Sun Jun 14 17:29:49 2009 Local Options hash (VER=V4): 'd79ca330'
Sun Jun 14 17:29:49 2009 Expected Remote Options hash (VER=V4): 'f7df56b8'
Sun Jun 14 17:29:49 2009 UDPv4 link local: [undef]
Sun Jun 14 17:29:49 2009 UDPv4 link remote: 80.81.223.50:54200
Sun Jun 14 17:29:50 2009 TLS: Initial packet from 80.81.223.50:54200, sid=b5f91ac6 ef59ce75
Sun Jun 14 17:29:52 2009 VERIFY OK: depth=1, /C=RU/ST=MW/L=MOSCOW/O=RadugaVPN/emailAddress=support@telecom-service.net
Sun Jun 14 17:29:52 2009 VERIFY OK: nsCertType=SERVER
Sun Jun 14 17:29:52 2009 VERIFY OK: depth=0, /C=RU/ST=MW/O=RadugaVPN/CN=RadugaVPN/emailAddress=support@telecom-service.net
Sun Jun 14 17:29:56 2009 Data Channel Encrypt: Cipher 'BF-CBC' initialized with 128 bit key
Sun Jun 14 17:29:56 2009 Data Channel Encrypt: Using 160 bit message hash 'SHA1' for HMAC authentication
Sun Jun 14 17:29:56 2009 Data Channel Decrypt: Cipher 'BF-CBC' initialized with 128 bit key
Sun Jun 14 17:29:56 2009 Data Channel Decrypt: Using 160 bit message hash 'SHA1' for HMAC authentication
Sun Jun 14 17:29:56 2009 Control Channel: TLSv1, cipher TLSv1/SSLv3 DHE-RSA-AES256-SHA, 1024 bit RSA
Sun Jun 14 17:29:56 2009 [RadugaVPN] Peer Connection Initiated with 80.81.223.50:54200
Sun Jun 14 17:29:57 2009 SENT CONTROL [RadugaVPN]: 'PUSH_REQUEST' (status=1)
Sun Jun 14 17:29:57 2009 PUSH: Received control message: 'PUSH_REPLY,redirect-gateway,dhcp-option DNS 80.81.223.50,route-gateway 10.248.0.1,ping 30,ping-restart 120,route 0.0.0.0 0.0.0.0 10.248.0.1,ifconfig 10.248.38.128 255.255.0.0'
Sun Jun 14 17:29:57 2009 OPTIONS IMPORT: timers and/or timeouts modified
Sun Jun 14 17:29:57 2009 OPTIONS IMPORT: --ifconfig/up options modified
Sun Jun 14 17:29:57 2009 OPTIONS IMPORT: route options modified
Sun Jun 14 17:29:57 2009 OPTIONS IMPORT: --ip-win32 and/or --dhcp-option options modified
Sun Jun 14 17:29:57 2009 TAP-WIN32 device [Raduga] opened: \\.\Global\{EF77593E-FAE8-4497-B55D-6FB619A37D92}.tap
Sun Jun 14 17:29:57 2009 TAP-Win32 Driver Version 8.4
Sun Jun 14 17:29:57 2009 TAP-Win32 MTU=1500
Sun Jun 14 17:29:57 2009 Notified TAP-Win32 driver to set a DHCP IP/netmask of 10.248.38.128/255.255.0.0 on interface {EF77593E-FAE8-4497-B55D-6FB619A37D92} [DHCP-serv: 10.248.0.0, lease-time: 31536000]
Sun Jun 14 17:29:57 2009 Successful ARP Flush on interface [196610] {EF77593E-FAE8-4497-B55D-6FB619A37D92}
Sun Jun 14 17:29:57 2009 TEST ROUTES: 0/0 succeeded len=1 ret=0 a=0 u/d=down
Sun Jun 14 17:29:57 2009 Route: Waiting for TUN/TAP interface to come up...
Sun Jun 14 17:29:58 2009 TEST ROUTES: 0/0 succeeded len=1 ret=0 a=0 u/d=down
Sun Jun 14 17:29:58 2009 Route: Waiting for TUN/TAP interface to come up...
Sun Jun 14 17:29:59 2009 TEST ROUTES: 0/0 succeeded len=1 ret=0 a=0 u/d=down
Sun Jun 14 17:29:59 2009 Route: Waiting for TUN/TAP interface to come up...
Sun Jun 14 17:30:01 2009 TEST ROUTES: 0/0 succeeded len=1 ret=0 a=0 u/d=down
Sun Jun 14 17:30:01 2009 Route: Waiting for TUN/TAP interface to come up...
Sun Jun 14 17:30:02 2009 TEST ROUTES: 0/0 succeeded len=1 ret=0 a=0 u/d=down
Sun Jun 14 17:30:02 2009 Route: Waiting for TUN/TAP interface to come up...
Sun Jun 14 17:30:03 2009 TEST ROUTES: 0/0 succeeded len=1 ret=0 a=0 u/d=down
Sun Jun 14 17:30:03 2009 Route: Waiting for TUN/TAP interface to come up...
Sun Jun 14 17:30:04 2009 TEST ROUTES: 0/0 succeeded len=1 ret=0 a=0 u/d=down
Sun Jun 14 17:30:04 2009 Route: Waiting for TUN/TAP interface to come up...
Sun Jun 14 17:30:06 2009 TEST ROUTES: 0/0 succeeded len=1 ret=0 a=0 u/d=down
Sun Jun 14 17:30:06 2009 Route: Waiting for TUN/TAP interface to come up...
Sun Jun 14 17:30:07 2009 TEST ROUTES: 0/0 succeeded len=1 ret=0 a=0 u/d=down
Sun Jun 14 17:30:07 2009 Route: Waiting for TUN/TAP interface to come up...
Sun Jun 14 17:30:08 2009 TEST ROUTES: 0/0 succeeded len=1 ret=0 a=0 u/d=down
Sun Jun 14 17:30:08 2009 Route: Waiting for TUN/TAP interface to come up...
Sun Jun 14 17:30:09 2009 TEST ROUTES: 0/0 succeeded len=1 ret=0 a=0 u/d=down
Sun Jun 14 17:30:09 2009 Route: Waiting for TUN/TAP interface to come up...
Sun Jun 14 17:30:10 2009 TEST ROUTES: 0/0 succeeded len=1 ret=0 a=0 u/d=down
Sun Jun 14 17:30:10 2009 Route: Waiting for TUN/TAP interface to come up...
Sun Jun 14 17:30:12 2009 TEST ROUTES: 0/0 succeeded len=1 ret=0 a=0 u/d=down
Sun Jun 14 17:30:12 2009 Route: Waiting for TUN/TAP interface to come up...
Sun Jun 14 17:30:13 2009 TEST ROUTES: 0/0 succeeded len=1 ret=0 a=0 u/d=down
Sun Jun 14 17:30:13 2009 Route: Waiting for TUN/TAP interface to come up...
Sun Jun 14 17:30:14 2009 TEST ROUTES: 0/0 succeeded len=1 ret=0 a=0 u/d=down
Sun Jun 14 17:30:14 2009 Route: Waiting for TUN/TAP interface to come up...
Sun Jun 14 17:30:15 2009 TEST ROUTES: 0/0 succeeded len=1 ret=0 a=0 u/d=down
Sun Jun 14 17:30:15 2009 Route: Waiting for TUN/TAP interface to come up...
Sun Jun 14 17:30:17 2009 TEST ROUTES: 0/0 succeeded len=1 ret=0 a=0 u/d=down
Sun Jun 14 17:30:17 2009 Route: Waiting for TUN/TAP interface to come up...
Sun Jun 14 17:30:18 2009 TEST ROUTES: 0/0 succeeded len=1 ret=0 a=0 u/d=down
Sun Jun 14 17:30:18 2009 Route: Waiting for TUN/TAP interface to come up...
Sun Jun 14 17:30:19 2009 TEST ROUTES: 0/0 succeeded len=1 ret=0 a=0 u/d=down
Sun Jun 14 17:30:19 2009 Route: Waiting for TUN/TAP interface to come up...
Sun Jun 14 17:30:20 2009 TEST ROUTES: 0/0 succeeded len=1 ret=0 a=0 u/d=down
Sun Jun 14 17:30:20 2009 Route: Waiting for TUN/TAP interface to come up...
Sun Jun 14 17:30:21 2009 TEST ROUTES: 0/0 succeeded len=1 ret=0 a=0 u/d=down
Sun Jun 14 17:30:21 2009 Route: Waiting for TUN/TAP interface to come up...
Sun Jun 14 17:30:23 2009 TEST ROUTES: 0/0 succeeded len=1 ret=0 a=0 u/d=down
Sun Jun 14 17:30:23 2009 Route: Waiting for TUN/TAP interface to come up...
Sun Jun 14 17:30:24 2009 TEST ROUTES: 0/0 succeeded len=1 ret=0 a=0 u/d=down
Sun Jun 14 17:30:24 2009 Route: Waiting for TUN/TAP interface to come up...
Sun Jun 14 17:30:25 2009 TEST ROUTES: 0/0 succeeded len=1 ret=0 a=0 u/d=down
Sun Jun 14 17:30:25 2009 Route: Waiting for TUN/TAP interface to come up...
Sun Jun 14 17:30:26 2009 TEST ROUTES: 0/0 succeeded len=1 ret=0 a=0 u/d=down
Sun Jun 14 17:30:26 2009 Route: Waiting for TUN/TAP interface to come up...
Sun Jun 14 17:30:27 2009 TEST ROUTES: 0/0 succeeded len=1 ret=0 a=0 u/d=down
Sun Jun 14 17:30:27 2009 route ADD 80.81.223.50 MASK 255.255.255.255 10.23.115.180
Sun Jun 14 17:30:27 2009 Route addition via IPAPI succeeded
Sun Jun 14 17:30:27 2009 route DELETE 0.0.0.0 MASK 0.0.0.0 10.23.115.180
Sun Jun 14 17:30:27 2009 Route deletion via IPAPI succeeded
Sun Jun 14 17:30:27 2009 route ADD 0.0.0.0 MASK 0.0.0.0 10.248.0.1
Sun Jun 14 17:30:27 2009 Warning: route gateway is not reachable on any active network adapters: 10.248.0.1
Sun Jun 14 17:30:27 2009 Route addition via IPAPI failed
Sun Jun 14 17:30:27 2009 route ADD 0.0.0.0 MASK 0.0.0.0 10.248.0.1
Sun Jun 14 17:30:27 2009 Warning: route gateway is not reachable on any active network adapters: 10.248.0.1
Sun Jun 14 17:30:27 2009 Route addition via IPAPI failed
Sun Jun 14 17:30:27 2009 Initialization Sequence Completed With Errors ( see http://openvpn.net/faq.html#dhcpclientserv )

Оффлайн R@inBoW

  • Продвинутый
  • *****
  • Сообщений: 1915
FENIX, а для кого мы вот это написали?! *24*

Цитировать
Sun Jun 14 17:30:27 2009 Initialization Sequence Completed With Errors ( see http://openvpn.net/faq.html#dhcpclientserv )

4. Initialization Sequence Completed With Errors
Ошибка присвоения IP адреса адаптеру. В данном случае проверьте что для ТАП адаптера стоит автоматическое присвоение IP, если стоит, то одному вашему подключению (возможно скрытому/удаленному) уже присвоен IP подписки, измените его на например 192.168.238.238 или на любой неиспользуемый.

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

FENIX

  • Гость
Да, прошу прощения, просмотрел этот пунктик  *PARDON*. Сменил ip dvb карты подписки на 192.168.238.238 и все, пошло. Спасибо за помощь. :) Пойду, попробую через инет поиграть.