Автор Тема: Странное поведение OPEN VPN  (Прочитано 4202 раз)

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

IlyaV

  • Гость
Странное поведение OPEN VPN
« : 09.07.2009, 17:47:39 »
Соединение устанавливает, но интернета нет...
Лог:
Thu Jul 09 22:27:21 2009 OpenVPN 2.1_rc7 Win32-MinGW [SSL] [LZO2] [PKCS11] built on Feb 13 2008
Thu Jul 09 22:27:21 2009 LZO compression initialized
Thu Jul 09 22:27:21 2009 Control Channel MTU parms [ L:1574 D:138 EF:38 EB:0 ET:0 EL:0 ]
Thu Jul 09 22:27:21 2009 Data Channel MTU parms [ L:1574 D:1450 EF:42 EB:135 ET:32 EL:0 AF:3/1 ]
Thu Jul 09 22:27:21 2009 Local Options hash (VER=V4): 'd79ca330'
Thu Jul 09 22:27:21 2009 Expected Remote Options hash (VER=V4): 'f7df56b8'
Thu Jul 09 22:27:21 2009 Socket Buffers: R=[8192->8192] S=[8192->8192]
Thu Jul 09 22:27:21 2009 UDPv4 link local: [undef]
Thu Jul 09 22:27:21 2009 UDPv4 link remote: 80.81.223.50:54300
Thu Jul 09 22:27:21 2009 TLS: Initial packet from 80.81.223.50:54300, sid=3913d395 c3096feb
Thu Jul 09 22:27:22 2009 VERIFY OK: depth=1, /C=RU/ST=MW/L=MOSCOW/O=RadugaVPN/emailAddress=support@telecom-service.net
Thu Jul 09 22:27:22 2009 VERIFY OK: nsCertType=SERVER
Thu Jul 09 22:27:22 2009 VERIFY OK: depth=0, /C=RU/ST=MW/O=RadugaVPN/CN=RadugaVPN/emailAddress=support@telecom-service.net
Thu Jul 09 22:27:23 2009 Data Channel Encrypt: Cipher 'BF-CBC' initialized with 128 bit key
Thu Jul 09 22:27:23 2009 Data Channel Encrypt: Using 160 bit message hash 'SHA1' for HMAC authentication
Thu Jul 09 22:27:23 2009 Data Channel Decrypt: Cipher 'BF-CBC' initialized with 128 bit key
Thu Jul 09 22:27:23 2009 Data Channel Decrypt: Using 160 bit message hash 'SHA1' for HMAC authentication
Thu Jul 09 22:27:23 2009 Control Channel: TLSv1, cipher TLSv1/SSLv3 DHE-RSA-AES256-SHA, 1024 bit RSA
Thu Jul 09 22:27:23 2009 [RadugaVPN] Peer Connection Initiated with 80.81.223.50:54300
Thu Jul 09 22:27:24 2009 SENT CONTROL [RadugaVPN]: 'PUSH_REQUEST' (status=1)
Thu Jul 09 22:27:24 2009 PUSH: Received control message: 'PUSH_REPLY,redirect-gateway,dhcp-option DNS 80.81.223.50,route-gateway 10.245.0.1,ping 30,ping-restart 120,route 0.0.0.0 0.0.0.0 10.245.0.1,ifconfig 10.245.0.239 255.255.0.0'
Thu Jul 09 22:27:24 2009 OPTIONS IMPORT: timers and/or timeouts modified
Thu Jul 09 22:27:24 2009 OPTIONS IMPORT: --ifconfig/up options modified
Thu Jul 09 22:27:24 2009 OPTIONS IMPORT: route options modified
Thu Jul 09 22:27:24 2009 OPTIONS IMPORT: route-related options modified
Thu Jul 09 22:27:24 2009 OPTIONS IMPORT: --ip-win32 and/or --dhcp-option options modified
Thu Jul 09 22:27:24 2009 TAP-WIN32 device [Raduga] opened: \\.\Global\{4340B002-A190-42CE-A17C-DE1E20436328}.tap
Thu Jul 09 22:27:24 2009 TAP-Win32 Driver Version 9.4
Thu Jul 09 22:27:24 2009 TAP-Win32 MTU=1500
Thu Jul 09 22:27:24 2009 Notified TAP-Win32 driver to set a DHCP IP/netmask of 10.245.0.239/255.255.0.0 on interface {4340B002-A190-42CE-A17C-DE1E20436328} [DHCP-serv: 10.245.0.0, lease-time: 31536000]
Thu Jul 09 22:27:24 2009 Successful ARP Flush on interface [26] {4340B002-A190-42CE-A17C-DE1E20436328}
Thu Jul 09 22:27:29 2009 TEST ROUTES: 0/0 succeeded len=1 ret=0 a=0 u/d=down
Thu Jul 09 22:27:29 2009 Route: Waiting for TUN/TAP interface to come up...
Thu Jul 09 22:27:34 2009 TEST ROUTES: 0/0 succeeded len=1 ret=0 a=0 u/d=down
Thu Jul 09 22:27:34 2009 Route: Waiting for TUN/TAP interface to come up...
Thu Jul 09 22:27:35 2009 TEST ROUTES: 0/0 succeeded len=1 ret=0 a=0 u/d=down
Thu Jul 09 22:27:35 2009 Route: Waiting for TUN/TAP interface to come up...
Thu Jul 09 22:27:36 2009 TEST ROUTES: 0/0 succeeded len=1 ret=0 a=0 u/d=down
Thu Jul 09 22:27:36 2009 Route: Waiting for TUN/TAP interface to come up...
Thu Jul 09 22:27:37 2009 TEST ROUTES: 0/0 succeeded len=1 ret=0 a=0 u/d=down
Thu Jul 09 22:27:37 2009 Route: Waiting for TUN/TAP interface to come up...
Thu Jul 09 22:27:38 2009 TEST ROUTES: 0/0 succeeded len=1 ret=0 a=0 u/d=down
Thu Jul 09 22:27:38 2009 Route: Waiting for TUN/TAP interface to come up...
Thu Jul 09 22:27:39 2009 TEST ROUTES: 0/0 succeeded len=1 ret=0 a=0 u/d=down
Thu Jul 09 22:27:39 2009 Route: Waiting for TUN/TAP interface to come up...
Thu Jul 09 22:27:40 2009 TEST ROUTES: 0/0 succeeded len=1 ret=0 a=0 u/d=down
Thu Jul 09 22:27:40 2009 Route: Waiting for TUN/TAP interface to come up...
Thu Jul 09 22:27:41 2009 TEST ROUTES: 0/0 succeeded len=1 ret=0 a=0 u/d=down
Thu Jul 09 22:27:41 2009 Route: Waiting for TUN/TAP interface to come up...
Thu Jul 09 22:27:42 2009 TEST ROUTES: 0/0 succeeded len=1 ret=0 a=0 u/d=down
Thu Jul 09 22:27:42 2009 Route: Waiting for TUN/TAP interface to come up...
Thu Jul 09 22:27:43 2009 TEST ROUTES: 0/0 succeeded len=1 ret=0 a=0 u/d=down
Thu Jul 09 22:27:43 2009 Route: Waiting for TUN/TAP interface to come up...
Thu Jul 09 22:27:44 2009 TEST ROUTES: 0/0 succeeded len=1 ret=0 a=0 u/d=down
Thu Jul 09 22:27:44 2009 Route: Waiting for TUN/TAP interface to come up...
Thu Jul 09 22:27:45 2009 TEST ROUTES: 0/0 succeeded len=1 ret=0 a=0 u/d=down
Thu Jul 09 22:27:45 2009 Route: Waiting for TUN/TAP interface to come up...
Thu Jul 09 22:27:46 2009 TEST ROUTES: 0/0 succeeded len=1 ret=0 a=0 u/d=down
Thu Jul 09 22:27:46 2009 Route: Waiting for TUN/TAP interface to come up...
Thu Jul 09 22:27:47 2009 TEST ROUTES: 0/0 succeeded len=1 ret=0 a=0 u/d=down
Thu Jul 09 22:27:47 2009 Route: Waiting for TUN/TAP interface to come up...
Thu Jul 09 22:27:48 2009 TEST ROUTES: 0/0 succeeded len=1 ret=0 a=0 u/d=down
Thu Jul 09 22:27:48 2009 Route: Waiting for TUN/TAP interface to come up...
Thu Jul 09 22:27:49 2009 TEST ROUTES: 0/0 succeeded len=1 ret=0 a=0 u/d=down
Thu Jul 09 22:27:49 2009 Route: Waiting for TUN/TAP interface to come up...
Thu Jul 09 22:27:50 2009 TEST ROUTES: 0/0 succeeded len=1 ret=0 a=0 u/d=down
Thu Jul 09 22:27:50 2009 Route: Waiting for TUN/TAP interface to come up...
Thu Jul 09 22:27:51 2009 TEST ROUTES: 0/0 succeeded len=1 ret=0 a=0 u/d=down
Thu Jul 09 22:27:51 2009 Route: Waiting for TUN/TAP interface to come up...
Thu Jul 09 22:27:52 2009 TEST ROUTES: 0/0 succeeded len=1 ret=0 a=0 u/d=down
Thu Jul 09 22:27:52 2009 Route: Waiting for TUN/TAP interface to come up...
Thu Jul 09 22:27:53 2009 TEST ROUTES: 0/0 succeeded len=1 ret=0 a=0 u/d=down
Thu Jul 09 22:27:53 2009 Route: Waiting for TUN/TAP interface to come up...
Thu Jul 09 22:27:54 2009 TEST ROUTES: 0/0 succeeded len=1 ret=0 a=0 u/d=down
Thu Jul 09 22:27:54 2009 Route: Waiting for TUN/TAP interface to come up...
Thu Jul 09 22:27:55 2009 TEST ROUTES: 0/0 succeeded len=1 ret=0 a=0 u/d=down
Thu Jul 09 22:27:55 2009 Route: Waiting for TUN/TAP interface to come up...
Thu Jul 09 22:27:56 2009 TEST ROUTES: 0/0 succeeded len=1 ret=0 a=0 u/d=down
Thu Jul 09 22:27:56 2009 Route: Waiting for TUN/TAP interface to come up...
Thu Jul 09 22:27:57 2009 TEST ROUTES: 0/0 succeeded len=1 ret=0 a=0 u/d=down
Thu Jul 09 22:27:57 2009 Route: Waiting for TUN/TAP interface to come up...
Thu Jul 09 22:27:58 2009 TEST ROUTES: 0/0 succeeded len=1 ret=0 a=0 u/d=down
Thu Jul 09 22:27:58 2009 Route: Waiting for TUN/TAP interface to come up...
Thu Jul 09 22:27:59 2009 TEST ROUTES: 0/0 succeeded len=1 ret=0 a=0 u/d=down
Thu Jul 09 22:27:59 2009 route ADD 80.81.223.50 MASK 255.255.255.255 192.168.254.1
Thu Jul 09 22:27:59 2009 ROUTE: CreateIpForwardEntry succeeded with dwForwardMetric1=10 and dwForwardType=4
Thu Jul 09 22:27:59 2009 Route addition via IPAPI succeeded [adaptive]
Thu Jul 09 22:27:59 2009 route DELETE 0.0.0.0 MASK 0.0.0.0 192.168.254.1
Thu Jul 09 22:27:59 2009 Route deletion via IPAPI succeeded [adaptive]
Thu Jul 09 22:27:59 2009 route ADD 0.0.0.0 MASK 0.0.0.0 10.245.0.1
Thu Jul 09 22:27:59 2009 ROUTE: CreateIpForwardEntry succeeded with dwForwardMetric1=20 and dwForwardType=4
Thu Jul 09 22:27:59 2009 Route addition via IPAPI succeeded [adaptive]
Thu Jul 09 22:27:59 2009 route ADD 0.0.0.0 MASK 0.0.0.0 10.245.0.1
Thu Jul 09 22:27:59 2009 ROUTE: route addition failed using CreateIpForwardEntry: Этот объект уже существует.   [status=5010 if_index=21]
Thu Jul 09 22:27:59 2009 Route addition via IPAPI failed [adaptive]
Thu Jul 09 22:27:59 2009 Route addition fallback to route.exe
‘Ў®© ¤®Ў ў«Ґ­Ёп ¬ аиагв : ќв®в ®ЎкҐЄв 㦥 бгйҐбвўгҐв.
SYSTEM ROUTING TABLE
0.0.0.0 0.0.0.0 10.245.0.1 p=0 i=21 t=4 pr=3 a=0 h=0 m=20/0/0/0/0
10.10.45.0 255.255.255.0 10.10.45.99 p=0 i=9 t=3 pr=3 a=1929 h=0 m=266/0/0/0/0
10.10.45.99 255.255.255.255 10.10.45.99 p=0 i=9 t=3 pr=3 a=1929 h=0 m=266/0/0/0/0
10.10.45.255 255.255.255.255 10.10.45.99 p=0 i=9 t=3 pr=3 a=1929 h=0 m=266/0/0/0/0
10.245.0.0 255.255.255.0 10.245.0.239 p=0 i=21 t=3 pr=3 a=1926 h=0 m=276/0/0/0/0
10.245.0.239 255.255.255.255 10.245.0.239 p=0 i=21 t=3 pr=3 a=1926 h=0 m=276/0/0/0/0
10.245.0.255 255.255.255.255 10.245.0.239 p=0 i=21 t=3 pr=3 a=1926 h=0 m=276/0/0/0/0
80.81.223.50 255.255.255.255 192.168.254.1 p=0 i=9 t=4 pr=3 a=0 h=0 m=10/0/0/0/0
127.0.0.0 255.0.0.0 127.0.0.1 p=0 i=1 t=3 pr=3 a=1948 h=0 m=306/0/0/0/0
127.0.0.1 255.255.255.255 127.0.0.1 p=0 i=1 t=3 pr=3 a=1948 h=0 m=306/0/0/0/0
127.255.255.255 255.255.255.255 127.0.0.1 p=0 i=1 t=3 pr=3 a=1948 h=0 m=306/0/0/0/0
169.254.0.0 255.255.0.0 169.254.164.220 p=0 i=26 t=3 pr=3 a=25 h=0 m=286/0/0/0/0
169.254.164.220 255.255.255.255 169.254.164.220 p=0 i=26 t=3 pr=3 a=25 h=0 m=286/0/0/0/0
169.254.255.255 255.255.255.255 169.254.164.220 p=0 i=26 t=3 pr=3 a=25 h=0 m=286/0/0/0/0
192.168.1.0 255.255.255.0 10.10.45.99 p=0 i=9 t=3 pr=3 a=1929 h=0 m=266/0/0/0/0
192.168.1.98 255.255.255.255 10.10.45.99 p=0 i=9 t=3 pr=3 a=1929 h=0 m=266/0/0/0/0
192.168.1.255 255.255.255.255 10.10.45.99 p=0 i=9 t=3 pr=3 a=1929 h=0 m=266/0/0/0/0
192.168.222.0 255.255.255.0 10.245.0.239 p=0 i=21 t=3 pr=3 a=1926 h=0 m=276/0/0/0/0
192.168.222.222 255.255.255.255 10.245.0.239 p=0 i=21 t=3 pr=3 a=1926 h=0 m=276/0/0/0/0
192.168.222.255 255.255.255.255 10.245.0.239 p=0 i=21 t=3 pr=3 a=1926 h=0 m=276/0/0/0/0
192.168.254.0 255.255.255.0 10.10.45.99 p=0 i=9 t=3 pr=3 a=1929 h=0 m=266/0/0/0/0
192.168.254.16 255.255.255.255 10.10.45.99 p=0 i=9 t=3 pr=3 a=1929 h=0 m=266/0/0/0/0
192.168.254.255 255.255.255.255 10.10.45.99 p=0 i=9 t=3 pr=3 a=1929 h=0 m=266/0/0/0/0
224.0.0.0 240.0.0.0 127.0.0.1 p=0 i=1 t=3 pr=3 a=1948 h=0 m=306/0/0/0/0
224.0.0.0 240.0.0.0 10.10.45.99 p=0 i=9 t=3 pr=3 a=1932 h=0 m=266/0/0/0/0
224.0.0.0 240.0.0.0 10.245.0.239 p=0 i=21 t=3 pr=3 a=1929 h=0 m=276/0/0/0/0
224.0.0.0 240.0.0.0 169.254.164.220 p=0 i=26 t=3 pr=3 a=1733 h=0 m=286/0/0/0/0
255.255.255.255 255.255.255.255 127.0.0.1 p=0 i=1 t=3 pr=3 a=1948 h=0 m=306/0/0/0/0
255.255.255.255 255.255.255.255 10.10.45.99 p=0 i=9 t=3 pr=3 a=1932 h=0 m=266/0/0/0/0
255.255.255.255 255.255.255.255 10.245.0.239 p=0 i=21 t=3 pr=3 a=1929 h=0 m=276/0/0/0/0
255.255.255.255 255.255.255.255 169.254.164.220 p=0 i=26 t=3 pr=3 a=1733 h=0 m=286/0/0/0/0
SYSTEM ADAPTER LIST
TAP-Win32 Adapter V9
  Index = 26
  GUID = {4340B002-A190-42CE-A17C-DE1E20436328}
  IP = 169.254.164.220/255.255.0.0
  MAC = 00:ff:43:40:b0:02
  GATEWAY = 0.0.0.0/255.255.255.255
  DHCP SERV = 0.0.0.0/255.255.255.255
  DHCP LEASE OBTAINED = Thu Jul 09 22:27:59 2009
  DHCP LEASE EXPIRES  = Thu Jul 09 22:27:59 2009
  DNS SERV = 
TechniSat DVB-PC TV Star PCI #2
  Index = 21
  GUID = {F481C8AF-90F0-462F-A0F9-7A2D18A0ADB1}
  IP = 10.245.0.239/255.255.255.0 192.168.222.222/255.255.255.0
  MAC = 00:08:c9:e0:4f:4e
  GATEWAY = 10.245.0.1/255.255.255.255
  DNS SERV = 80.81.223.50/255.255.255.255 80.81.208.146/255.255.255.255
Realtek RTL8168/8111 Family PCI-E Gigabit Ethernet
  Index = 9
  GUID = {8C97814B-3C54-46B4-84BE-440C28A291F2}
  IP = 10.10.45.99/255.255.255.0 192.168.1.98/255.255.255.0 192.168.254.16/255.255.255.0
  MAC = 00:1a:4d:53:c1:20
  GATEWAY = 0.0.0.0/255.255.255.255
  DNS SERV = 80.81.223.50/255.255.255.255 80.81.208.146/255.255.255.255
Thu Jul 09 22:27:59 2009 Initialization Sequence Completed With Errors ( see http://openvpn.net/faq.html#dhcpclientserv )

Такая фигня началлась  неделю назад, до этого все работало. Может кто поможет в решении проблемы?
« Последнее редактирование: 09.07.2009, 17:50:59 от IlyaV »

Оффлайн R@inBoW

  • Продвинутый
  • *****
  • Сообщений: 1915
  • Откуда: Москва
Странное поведение OPEN VPN
« Ответ #1 : 09.07.2009, 18:08:13 »
Соседнюю ветку читали - мануал по ошибкам опен впн?

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

Версию опен впн другую установите скачать можно в ЛК.

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