Copying with the attached logs forwarded to the devel list for more expert
opinion
Hi,
Thanks for the logs.
The repeated
.. Route: Waiting for TUN/TAP interface to come up...
in the logs is the same as what I wrote about previously -- I think setting
the tunnel IP by dhcp fails but openvpn tags this as a not-fatal route
setting error, the GUI only sees the final "CONNECTED, SUCCESS..." message
and wrongly reports as if all is well...
That said I do not know why the the adapter fails to set the IP the second
time -- possibly some misbehaviour in the tap-driver when the IP is
changed in a quick succession? Just guessing.
Selva
---------- Forwarded message ----------
From: Dmitry Melekhov <d...@belkam.com>
Date: Thu, Dec 29, 2016 at 12:02 AM
Subject: Fwd: Re: [Openvpn-users] 2.4, windows tap driver problem
To: selva.n...@gmail.com
Hello!
Message to mail list was blocked before moderator approval, so forwarding
to you directly.
Thank you!
-------- Перенаправленное сообщение --------
Тема: Re: [Openvpn-users] 2.4, windows tap driver problem
Дата: Thu, 29 Dec 2016 09:00:53 +0400
От: Dmitry Melekhov <d...@belkam.com> <d...@belkam.com>
Кому: openvpn-us...@lists.sourceforge.net
29.12.2016 07:30, Selva Nair пишет:
On Wed, Dec 28, 2016 at 10:07 PM, Dmitry Melekhov < <d...@belkam.com>
d...@belkam.com> wrote:
> On Wed, Dec 28, 2016 at 1:43 AM, Dmitry Melekhov < <d...@belkam.com>
> d...@belkam.com> wrote:
>
>> Just installed 2.4 on windows 7.
>>
>> Connecting to on server, tun is set to, let's say to 10.1.10.6,
>>
>> everything is fine.
>>
>> Disconnect.
>>
>> Change remote in config, connect to another server,
>> tun address should be 192.168.31.6, gui says so,
>>
>> but real address on tun is 10.1.10.6.
>>
>>
>> Reboot solves problem, but on next connection sequence it is reproduced.
>>
>
>
> I tried to reproduce this but fortunately no luck :)
>
> As Gert said, logs please. Also please include an output of ipconfig /all
> showing the settings on tun adapters with each connection up.
>
> I sent logs to Gert already...connection
>
> but, afair, only failed connection..
This rings a bell. I've seen connection failures in the past when the same
tap adapter is used with different remotes in a succession. The connection
fails with something like repeated "TEST ROUTES: 0/0 succeeded len=-1 ret=0
a=0 u/d=down" which indicates setting IP by dhcp didn't succeed. Without
logs, not sure that's what you are seeing, though.
Never seen it lately as I now use explicitly named dev nodes (--dev-node
name option) so that each connection uses a fixed adapter node. And no idea
why it happens. Could be tap-driver related so someone else may have a clue.
OK, here are
1. ipconfig before first connection:
C:\>ipconfig /all
Настройка протокола IP для Windows
Имя компьютера . . . . . . . . . : JNK-W7
Основной DNS-суффикс . . . . . . : ad.belkam.com
Тип узла. . . . . . . . . . . . . : Гибридный
IP-маршрутизация включена . . . . : Нет
WINS-прокси включен . . . . . . . : Нет
Порядок просмотра суффиксов DNS . : ad.belkam.com
p98.belkam.com
Ethernet adapter Подключение по локальной сети 2:
Состояние среды. . . . . . . . : Среда передачи недоступна.
DNS-суффикс подключения . . . . . :
Описание. . . . . . . . . . . . . : TAP-Windows Adapter V9
Физический адрес. . . . . . . . . : 00-FF-BE-79-4D-53
DHCP включен. . . . . . . . . . . : Да
Автонастройка включена. . . . . . : Да
Ethernet adapter Подключение по локальной сети:
DNS-суффикс подключения . . . . . : p98.belkam.com
Описание. . . . . . . . . . . . . : Адаптер рабочего стола Intel(R)
PRO/1000
MT
Физический адрес. . . . . . . . . : 08-00-27-6D-1B-5A
DHCP включен. . . . . . . . . . . : Да
Автонастройка включена. . . . . . : Да
Локальный IPv6-адрес канала . . . :
fe80::fdd4:7bac:502c:dacd%10(Основной)
IPv4-адрес. . . . . . . . . . . . : 192.168.22.44(Основной)
Маска подсети . . . . . . . . . . : 255.255.255.0
Аренда получена. . . . . . . . . . : 29 декабря 2016 г. 8:35:07
Срок аренды истекает. . . . . . . . . . : 29 декабря 2016 г. 14:35:07
Основной шлюз. . . . . . . . . : 192.168.22.221
DHCP-сервер. . . . . . . . . . . : 192.168.22.222
IAID DHCPv6 . . . . . . . . . . . : 235405351
DUID клиента DHCPv6 . . . . . . . :
00-01-00-01-13-1E-AD-C1-08-00-27-6D-1B-5A
DNS-серверы. . . . . . . . . . . : 192.168.22.222
192.168.22.99
Основной WINS-сервер. . . . . . . : 192.168.22.91
NetBios через TCP/IP. . . . . . . . : Включен
Туннельный адаптер isatap.p98.belkam.com:
Состояние среды. . . . . . . . : Среда передачи недоступна.
DNS-суффикс подключения . . . . . : p98.belkam.com
Описание. . . . . . . . . . . . . : Адаптер Microsoft ISATAP
Физический адрес. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP включен. . . . . . . . . . . : Нет
Автонастройка включена. . . . . . : Да
Туннельный адаптер Подключение по локальной сети*:
Состояние среды. . . . . . . . : Среда передачи недоступна.
DNS-суффикс подключения . . . . . :
Описание. . . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface
Физический адрес. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP включен. . . . . . . . . . . : Нет
Автонастройка включена. . . . . . : Да
Туннельный адаптер isatap.{BE794D53-798C-40DC-8B64-4CE37589133F}:
Состояние среды. . . . . . . . : Среда передачи недоступна.
DNS-суффикс подключения . . . . . :
Описание. . . . . . . . . . . . . : Адаптер Microsoft ISATAP #2
Физический адрес. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP включен. . . . . . . . . . . : Нет
Автонастройка включена. . . . . . : Да
2. ipconfig before second connection
C:\>ipconfig /all
Настройка протокола IP для Windows
Имя компьютера . . . . . . . . . : JNK-W7
Основной DNS-суффикс . . . . . . : ad.belkam.com
Тип узла. . . . . . . . . . . . . : Гибридный
IP-маршрутизация включена . . . . : Нет
WINS-прокси включен . . . . . . . : Нет
Порядок просмотра суффиксов DNS . : ad.belkam.com
p98.belkam.com
Ethernet adapter Подключение по локальной сети 2:
DNS-суффикс подключения . . . . . :
Описание. . . . . . . . . . . . . : TAP-Windows Adapter V9
Физический адрес. . . . . . . . . : 00-FF-BE-79-4D-53
DHCP включен. . . . . . . . . . . : Да
Автонастройка включена. . . . . . : Да
IPv4-адрес. . . . . . . . . . . . : 10.1.10.6(Основной)
Маска подсети . . . . . . . . . . : 255.255.255.0
Аренда получена. . . . . . . . . . : 29 декабря 2016 г. 8:48:39
Срок аренды истекает. . . . . . . . . . : 29 декабря 2017 г. 8:48:39
Основной шлюз. . . . . . . . . :
DHCP-сервер. . . . . . . . . . . : 10.1.10.254
DNS-серверы. . . . . . . . . . . : 10.1.1.1
Основной WINS-сервер. . . . . . . : 192.168.22.220
NetBios через TCP/IP. . . . . . . . : Включен
Ethernet adapter Подключение по локальной сети:
DNS-суффикс подключения . . . . . : p98.belkam.com
Описание. . . . . . . . . . . . . : Адаптер рабочего стола Intel(R)
PRO/1000
MT
Физический адрес. . . . . . . . . : 08-00-27-6D-1B-5A
DHCP включен. . . . . . . . . . . : Да
Автонастройка включена. . . . . . : Да
Локальный IPv6-адрес канала . . . :
fe80::fdd4:7bac:502c:dacd%10(Основной)
IPv4-адрес. . . . . . . . . . . . : 192.168.22.44(Основной)
Маска подсети . . . . . . . . . . : 255.255.255.0
Аренда получена. . . . . . . . . . : 29 декабря 2016 г. 8:35:07
Срок аренды истекает. . . . . . . . . . : 29 декабря 2016 г. 14:35:08
Основной шлюз. . . . . . . . . : 192.168.22.221
DHCP-сервер. . . . . . . . . . . : 192.168.22.222
IAID DHCPv6 . . . . . . . . . . . : 235405351
DUID клиента DHCPv6 . . . . . . . :
00-01-00-01-13-1E-AD-C1-08-00-27-6D-1B-5A
DNS-серверы. . . . . . . . . . . : 192.168.22.222
192.168.22.99
Основной WINS-сервер. . . . . . . : 192.168.22.91
NetBios через TCP/IP. . . . . . . . : Включен
Туннельный адаптер isatap.p98.belkam.com:
Состояние среды. . . . . . . . : Среда передачи недоступна.
DNS-суффикс подключения . . . . . : p98.belkam.com
Описание. . . . . . . . . . . . . : Адаптер Microsoft ISATAP
Физический адрес. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP включен. . . . . . . . . . . : Нет
Автонастройка включена. . . . . . : Да
Туннельный адаптер Подключение по локальной сети*:
Состояние среды. . . . . . . . : Среда передачи недоступна.
DNS-суффикс подключения . . . . . :
Описание. . . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface
Физический адрес. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP включен. . . . . . . . . . . : Нет
Автонастройка включена. . . . . . : Да
Туннельный адаптер isatap.{BE794D53-798C-40DC-8B64-4CE37589133F}:
Состояние среды. . . . . . . . : Среда передачи недоступна.
DNS-суффикс подключения . . . . . :
Описание. . . . . . . . . . . . . : Адаптер Microsoft ISATAP #2
Физический адрес. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP включен. . . . . . . . . . . : Нет
Автонастройка включена. . . . . . : Да
Logs are attached.
Thank you!
Thu Dec 29 08:48:31 2016 OpenVPN 2.4.0 x86_64-w64-mingw32 [SSL
(OpenSSL)] [LZO] [LZ4] [PKCS11] [AEAD] built on Dec 27 2016
Thu Dec 29 08:48:31 2016 Windows version 6.1 (Windows 7) 64bit
Thu Dec 29 08:48:31 2016 library versions: OpenSSL 1.0.2i 22 Sep 2016,
LZO 2.09
Enter Management Password:
Thu Dec 29 08:48:31 2016 MANAGEMENT: TCP Socket listening on
[AF_INET]127.0.0.1:25340
Thu Dec 29 08:48:31 2016 Need hold release from management interface,
waiting...
Thu Dec 29 08:48:32 2016 MANAGEMENT: Client connected from
[AF_INET]127.0.0.1:25340
Thu Dec 29 08:48:32 2016 MANAGEMENT: CMD 'state on'
Thu Dec 29 08:48:32 2016 MANAGEMENT: CMD 'log all on'
Thu Dec 29 08:48:32 2016 MANAGEMENT: CMD 'hold off'
Thu Dec 29 08:48:32 2016 MANAGEMENT: CMD 'hold release'
Thu Dec 29 08:48:35 2016 MANAGEMENT: CMD 'username "Auth" "jnk"'
Thu Dec 29 08:48:35 2016 MANAGEMENT: CMD 'password [...]'
Thu Dec 29 08:48:35 2016 WARNING: No server certificate verification
method has been enabled. See http://openvpn.net/howto.html#mitm for
more info.
Thu Dec 29 08:48:35 2016 TCP/UDP: Preserving recently used remote
address: [AF_INET]77.79.133.152:1194
Thu Dec 29 08:48:35 2016 Socket Buffers: R=[8192->8192] S=[8192->8192]
Thu Dec 29 08:48:35 2016 Attempting to establish TCP connection with
[AF_INET]77.79.133.152:1194 [nonblock]
Thu Dec 29 08:48:35 2016 MANAGEMENT: >STATE:1482986915,TCP_CONNECT,,,,,,
Thu Dec 29 08:48:36 2016 TCP connection established with
[AF_INET]77.79.133.152:1194
Thu Dec 29 08:48:36 2016 TCP_CLIENT link local: (not bound)
Thu Dec 29 08:48:36 2016 TCP_CLIENT link remote: [AF_INET]77.79.133.152:1194
Thu Dec 29 08:48:36 2016 MANAGEMENT: >STATE:1482986916,WAIT,,,,,,
Thu Dec 29 08:48:37 2016 MANAGEMENT: >STATE:1482986917,AUTH,,,,,,
Thu Dec 29 08:48:37 2016 TLS: Initial packet from
[AF_INET]77.79.133.152:1194, sid=18c35265 ecfe7a2b
Thu Dec 29 08:48:37 2016 WARNING: this configuration may cache passwords
in memory -- use the auth-nocache option to prevent this
Thu Dec 29 08:48:37 2016 VERIFY OK: depth=1, C=RU, ST=Udm, L=Izhevsk,
O=Belkam, OU=UIT, CN=vpn.belkam.com, emailAddress=supp...@belkam.com
Thu Dec 29 08:48:37 2016 VERIFY OK: depth=0, C=RU, ST=Udm, L=Izhevsk,
O=Belkam, OU=UIT, CN=inetgw-nsk, emailAddress=supp...@belkam.com
Thu Dec 29 08:48:37 2016 WARNING: 'link-mtu' is used inconsistently,
local='link-mtu 1544', remote='link-mtu 1559'
Thu Dec 29 08:48:37 2016 WARNING: 'comp-lzo' is present in local config
but missing in remote config, local='comp-lzo'
Thu Dec 29 08:48:37 2016 WARNING: 'cipher' is used inconsistently,
local='cipher BF-CBC', remote='cipher AES-256-CBC'
Thu Dec 29 08:48:37 2016 WARNING: 'keysize' is used inconsistently,
local='keysize 128', remote='keysize 256'
Thu Dec 29 08:48:37 2016 Control Channel: TLSv1.2, cipher TLSv1/SSLv3
ECDHE-RSA-AES256-GCM-SHA384, 1024 bit RSA
Thu Dec 29 08:48:37 2016 [inetgw-nsk] Peer Connection Initiated with
[AF_INET]77.79.133.152:1194
Thu Dec 29 08:48:38 2016 MANAGEMENT: >STATE:1482986918,GET_CONFIG,,,,,,
Thu Dec 29 08:48:38 2016 SENT CONTROL [inetgw-nsk]: 'PUSH_REQUEST'
(status=1)
Thu Dec 29 08:48:39 2016 PUSH: Received control message:
'PUSH_REPLY,dhcp-option DNS 10.1.1.1,dhcp-option WINS
192.168.22.220,route-gateway 10.1.10.1,topology subnet,ping
10,ping-restart 120,route 192.168.0.0 255.255.0.0,route 10.0.0.0
255.0.0.0,compress lz4,ifconfig 10.1.10.6 255.255.255.0,peer-id 0,cipher
AES-256-GCM'
Thu Dec 29 08:48:39 2016 OPTIONS IMPORT: timers and/or timeouts modified
Thu Dec 29 08:48:39 2016 OPTIONS IMPORT: compression parms modified
Thu Dec 29 08:48:39 2016 OPTIONS IMPORT: --ifconfig/up options modified
Thu Dec 29 08:48:39 2016 OPTIONS IMPORT: route options modified
Thu Dec 29 08:48:39 2016 OPTIONS IMPORT: route-related options modified
Thu Dec 29 08:48:39 2016 OPTIONS IMPORT: --ip-win32 and/or --dhcp-option
options modified
Thu Dec 29 08:48:39 2016 OPTIONS IMPORT: peer-id set
Thu Dec 29 08:48:39 2016 OPTIONS IMPORT: adjusting link_mtu to 1627
Thu Dec 29 08:48:39 2016 OPTIONS IMPORT: data channel crypto options
modified
Thu Dec 29 08:48:39 2016 Data Channel Encrypt: Cipher 'AES-256-GCM'
initialized with 256 bit key
Thu Dec 29 08:48:39 2016 Data Channel Decrypt: Cipher 'AES-256-GCM'
initialized with 256 bit key
Thu Dec 29 08:48:39 2016 interactive service msg_channel=324
Thu Dec 29 08:48:39 2016 ROUTE_GATEWAY 192.168.22.221/255.255.255.0 I=10
HWADDR=08:00:27:6d:1b:5a
Thu Dec 29 08:48:39 2016 open_tun
Thu Dec 29 08:48:39 2016 TAP-WIN32 device [ÐодклÑÑение по локалÑной ÑеÑи
2] opened: \\.\Global\{BE794D53-798C-40DC-8B64-4CE37589133F}.tap
Thu Dec 29 08:48:39 2016 TAP-Windows Driver Version 9.21
Thu Dec 29 08:48:39 2016 Set TAP-Windows TUN subnet mode
network/local/netmask = 10.1.10.0/10.1.10.6/255.255.255.0 [SUCCEEDED]
Thu Dec 29 08:48:39 2016 Notified TAP-Windows driver to set a DHCP
IP/netmask of 10.1.10.6/255.255.255.0 on interface
{BE794D53-798C-40DC-8B64-4CE37589133F} [DHCP-serv: 10.1.10.254,
lease-time: 31536000]
Thu Dec 29 08:48:39 2016 Successful ARP Flush on interface [18]
{BE794D53-798C-40DC-8B64-4CE37589133F}
Thu Dec 29 08:48:39 2016 do_ifconfig, tt->did_ifconfig_ipv6_setup=0
Thu Dec 29 08:48:39 2016 MANAGEMENT:
> STATE:1482986919,ASSIGN_IP,,10.1.10.6,,,,
Thu Dec 29 08:48:44 2016 TEST ROUTES: 2/2 succeeded len=2 ret=1 a=0 u/d=up
Thu Dec 29 08:48:44 2016 MANAGEMENT: >STATE:1482986924,ADD_ROUTES,,,,,,
Thu Dec 29 08:48:44 2016 C:\Windows\system32\route.exe ADD 192.168.0.0
MASK 255.255.0.0 10.1.10.1
Thu Dec 29 08:48:44 2016 Route addition via service succeeded
Thu Dec 29 08:48:44 2016 C:\Windows\system32\route.exe ADD 10.0.0.0 MASK
255.0.0.0 10.1.10.1
Thu Dec 29 08:48:44 2016 Route addition via service succeeded
Thu Dec 29 08:48:44 2016 Initialization Sequence Completed
Thu Dec 29 08:48:44 2016 MANAGEMENT:
> STATE:1482986924,CONNECTED,SUCCESS,10.1.10.6,77.79.133.152,1194,192.168.22.44,54761
Thu Dec 29 08:51:46 2016 OpenVPN 2.4.0 x86_64-w64-mingw32 [SSL
(OpenSSL)] [LZO] [LZ4] [PKCS11] [AEAD] built on Dec 27 2016
Thu Dec 29 08:51:46 2016 Windows version 6.1 (Windows 7) 64bit
Thu Dec 29 08:51:46 2016 library versions: OpenSSL 1.0.2i 22 Sep 2016,
LZO 2.09
Enter Management Password:
Thu Dec 29 08:51:46 2016 MANAGEMENT: TCP Socket listening on
[AF_INET]127.0.0.1:25340
Thu Dec 29 08:51:46 2016 Need hold release from management interface,
waiting...
Thu Dec 29 08:51:46 2016 MANAGEMENT: Client connected from
[AF_INET]127.0.0.1:25340
Thu Dec 29 08:51:46 2016 MANAGEMENT: CMD 'state on'
Thu Dec 29 08:51:46 2016 MANAGEMENT: CMD 'log all on'
Thu Dec 29 08:51:46 2016 MANAGEMENT: CMD 'hold off'
Thu Dec 29 08:51:46 2016 MANAGEMENT: CMD 'hold release'
Thu Dec 29 08:51:51 2016 MANAGEMENT: CMD 'username "Auth" "jnk"'
Thu Dec 29 08:51:51 2016 MANAGEMENT: CMD 'password [...]'
Thu Dec 29 08:51:51 2016 WARNING: No server certificate verification
method has been enabled. See http://openvpn.net/howto.html#mitm for
more info.
Thu Dec 29 08:51:51 2016 TCP/UDP: Preserving recently used remote
address: [AF_INET]78.85.14.181:1194
Thu Dec 29 08:51:51 2016 Socket Buffers: R=[8192->8192] S=[8192->8192]
Thu Dec 29 08:51:51 2016 Attempting to establish TCP connection with
[AF_INET]78.85.14.181:1194 [nonblock]
Thu Dec 29 08:51:51 2016 MANAGEMENT: >STATE:1482987111,TCP_CONNECT,,,,,,
Thu Dec 29 08:51:52 2016 TCP connection established with
[AF_INET]78.85.14.181:1194
Thu Dec 29 08:51:52 2016 TCP_CLIENT link local: (not bound)
Thu Dec 29 08:51:52 2016 TCP_CLIENT link remote: [AF_INET]78.85.14.181:1194
Thu Dec 29 08:51:52 2016 MANAGEMENT: >STATE:1482987112,WAIT,,,,,,
Thu Dec 29 08:51:52 2016 MANAGEMENT: >STATE:1482987112,AUTH,,,,,,
Thu Dec 29 08:51:52 2016 TLS: Initial packet from
[AF_INET]78.85.14.181:1194, sid=e4c74ac0 d0059f59
Thu Dec 29 08:51:52 2016 WARNING: this configuration may cache passwords
in memory -- use the auth-nocache option to prevent this
Thu Dec 29 08:51:52 2016 VERIFY OK: depth=1, C=RU, ST=Udm, L=Izhevsk,
O=Belkam, OU=UIT, CN=vpn.belkam.com, emailAddress=supp...@belkam.com
Thu Dec 29 08:51:52 2016 VERIFY OK: depth=0, C=RU, ST=Udm, L=Izhevsk,
O=Belkam, OU=UIT, CN=inetgw2, emailAddress=supp...@belkam.com
Thu Dec 29 08:51:54 2016 Control Channel: TLSv1, cipher TLSv1/SSLv3
DHE-RSA-AES256-SHA, 1024 bit RSA
Thu Dec 29 08:51:54 2016 [inetgw2] Peer Connection Initiated with
[AF_INET]78.85.14.181:1194
Thu Dec 29 08:51:55 2016 MANAGEMENT: >STATE:1482987115,GET_CONFIG,,,,,,
Thu Dec 29 08:51:55 2016 SENT CONTROL [inetgw2]: 'PUSH_REQUEST' (status=1)
Thu Dec 29 08:51:55 2016 PUSH: Received control message:
'PUSH_REPLY,dhcp-option DNS 192.168.22.254,dhcp-option WINS
192.168.22.220,route-gateway 192.168.31.1,topology subnet,ping
10,ping-restart 120,route 192.168.0.0 255.255.0.0,route 10.0.0.0
255.0.0.0,ifconfig 192.168.31.6 255.255.255.0'
Thu Dec 29 08:51:55 2016 OPTIONS IMPORT: timers and/or timeouts modified
Thu Dec 29 08:51:55 2016 OPTIONS IMPORT: --ifconfig/up options modified
Thu Dec 29 08:51:55 2016 OPTIONS IMPORT: route options modified
Thu Dec 29 08:51:55 2016 OPTIONS IMPORT: route-related options modified
Thu Dec 29 08:51:55 2016 OPTIONS IMPORT: --ip-win32 and/or --dhcp-option
options modified
Thu Dec 29 08:51:55 2016 Data Channel Encrypt: Cipher 'BF-CBC'
initialized with 128 bit key
Thu Dec 29 08:51:55 2016 WARNING: INSECURE cipher with block size less
than 128 bit (64 bit). This allows attacks like SWEET32. Mitigate by
using a --cipher with a larger block size (e.g. AES-256-CBC).
Thu Dec 29 08:51:55 2016 Data Channel Encrypt: Using 160 bit message
hash 'SHA1' for HMAC authentication
Thu Dec 29 08:51:55 2016 Data Channel Decrypt: Cipher 'BF-CBC'
initialized with 128 bit key
Thu Dec 29 08:51:55 2016 WARNING: INSECURE cipher with block size less
than 128 bit (64 bit). This allows attacks like SWEET32. Mitigate by
using a --cipher with a larger block size (e.g. AES-256-CBC).
Thu Dec 29 08:51:55 2016 Data Channel Decrypt: Using 160 bit message
hash 'SHA1' for HMAC authentication
Thu Dec 29 08:51:55 2016 WARNING: cipher with small block size in use,
reducing reneg-bytes to 64MB to mitigate SWEET32 attacks.
Thu Dec 29 08:51:55 2016 interactive service msg_channel=352
Thu Dec 29 08:51:55 2016 ROUTE_GATEWAY 192.168.22.221/255.255.255.0 I=10
HWADDR=08:00:27:6d:1b:5a
Thu Dec 29 08:51:55 2016 open_tun
Thu Dec 29 08:51:55 2016 TAP-WIN32 device [ÐодклÑÑение по локалÑной ÑеÑи
2] opened: \\.\Global\{BE794D53-798C-40DC-8B64-4CE37589133F}.tap
Thu Dec 29 08:51:55 2016 TAP-Windows Driver Version 9.21
Thu Dec 29 08:51:55 2016 Set TAP-Windows TUN subnet mode
network/local/netmask = 192.168.31.0/192.168.31.6/255.255.255.0 [SUCCEEDED]
Thu Dec 29 08:51:55 2016 Notified TAP-Windows driver to set a DHCP
IP/netmask of 192.168.31.6/255.255.255.0 on interface
{BE794D53-798C-40DC-8B64-4CE37589133F} [DHCP-serv: 192.168.31.254,
lease-time: 31536000]
Thu Dec 29 08:51:55 2016 Successful ARP Flush on interface [18]
{BE794D53-798C-40DC-8B64-4CE37589133F}
Thu Dec 29 08:51:55 2016 do_ifconfig, tt->did_ifconfig_ipv6_setup=0
Thu Dec 29 08:51:55 2016 MANAGEMENT:
> STATE:1482987115,ASSIGN_IP,,192.168.31.6,,,,
Thu Dec 29 08:52:00 2016 TEST ROUTES: 0/0 succeeded len=-1 ret=0 a=0
u/d=down
Thu Dec 29 08:52:00 2016 Route: Waiting for TUN/TAP interface to come up...
Thu Dec 29 08:52:05 2016 TEST ROUTES: 0/0 succeeded len=-1 ret=0 a=0
u/d=down
Thu Dec 29 08:52:05 2016 Route: Waiting for TUN/TAP interface to come up...
Thu Dec 29 08:52:06 2016 TEST ROUTES: 0/0 succeeded len=-1 ret=0 a=0
u/d=down
Thu Dec 29 08:52:06 2016 Route: Waiting for TUN/TAP interface to come up...
Thu Dec 29 08:52:07 2016 TEST ROUTES: 0/0 succeeded len=-1 ret=0 a=0
u/d=down
Thu Dec 29 08:52:07 2016 Route: Waiting for TUN/TAP interface to come up...
Thu Dec 29 08:52:08 2016 TEST ROUTES: 0/0 succeeded len=-1 ret=0 a=0
u/d=down
Thu Dec 29 08:52:08 2016 Route: Waiting for TUN/TAP interface to come up...
Thu Dec 29 08:52:09 2016 TEST ROUTES: 0/0 succeeded len=-1 ret=0 a=0
u/d=down
Thu Dec 29 08:52:09 2016 Route: Waiting for TUN/TAP interface to come up...
Thu Dec 29 08:52:10 2016 TEST ROUTES: 0/0 succeeded len=-1 ret=0 a=0
u/d=down
Thu Dec 29 08:52:10 2016 Route: Waiting for TUN/TAP interface to come up...
Thu Dec 29 08:52:11 2016 TEST ROUTES: 0/0 succeeded len=-1 ret=0 a=0
u/d=down
Thu Dec 29 08:52:11 2016 Route: Waiting for TUN/TAP interface to come up...
Thu Dec 29 08:52:12 2016 TEST ROUTES: 0/0 succeeded len=-1 ret=0 a=0
u/d=down
Thu Dec 29 08:52:12 2016 Route: Waiting for TUN/TAP interface to come up...
Thu Dec 29 08:52:13 2016 TEST ROUTES: 0/0 succeeded len=-1 ret=0 a=0
u/d=down
Thu Dec 29 08:52:13 2016 Route: Waiting for TUN/TAP interface to come up...
Thu Dec 29 08:52:14 2016 TEST ROUTES: 0/0 succeeded len=-1 ret=0 a=0
u/d=down
Thu Dec 29 08:52:14 2016 Route: Waiting for TUN/TAP interface to come up...
Thu Dec 29 08:52:15 2016 TEST ROUTES: 0/0 succeeded len=-1 ret=0 a=0
u/d=down
Thu Dec 29 08:52:15 2016 Route: Waiting for TUN/TAP interface to come up...
Thu Dec 29 08:52:16 2016 TEST ROUTES: 0/0 succeeded len=-1 ret=0 a=0
u/d=down
Thu Dec 29 08:52:16 2016 Route: Waiting for TUN/TAP interface to come up...
Thu Dec 29 08:52:17 2016 TEST ROUTES: 0/0 succeeded len=-1 ret=0 a=0
u/d=down
Thu Dec 29 08:52:17 2016 Route: Waiting for TUN/TAP interface to come up...
Thu Dec 29 08:52:18 2016 TEST ROUTES: 0/0 succeeded len=-1 ret=0 a=0
u/d=down
Thu Dec 29 08:52:18 2016 Route: Waiting for TUN/TAP interface to come up...
Thu Dec 29 08:52:19 2016 TEST ROUTES: 0/0 succeeded len=-1 ret=0 a=0
u/d=down
Thu Dec 29 08:52:19 2016 Route: Waiting for TUN/TAP interface to come up...
Thu Dec 29 08:52:20 2016 TEST ROUTES: 0/0 succeeded len=-1 ret=0 a=0
u/d=down
Thu Dec 29 08:52:20 2016 Route: Waiting for TUN/TAP interface to come up...
Thu Dec 29 08:52:21 2016 TEST ROUTES: 0/0 succeeded len=-1 ret=0 a=0
u/d=down
Thu Dec 29 08:52:21 2016 Route: Waiting for TUN/TAP interface to come up...
Thu Dec 29 08:52:22 2016 TEST ROUTES: 0/0 succeeded len=-1 ret=0 a=0
u/d=down
Thu Dec 29 08:52:22 2016 Route: Waiting for TUN/TAP interface to come up...
Thu Dec 29 08:52:23 2016 TEST ROUTES: 0/0 succeeded len=-1 ret=0 a=0
u/d=down
Thu Dec 29 08:52:23 2016 Route: Waiting for TUN/TAP interface to come up...
Thu Dec 29 08:52:24 2016 TEST ROUTES: 0/0 succeeded len=-1 ret=0 a=0
u/d=down
Thu Dec 29 08:52:24 2016 Route: Waiting for TUN/TAP interface to come up...
Thu Dec 29 08:52:25 2016 TEST ROUTES: 0/0 succeeded len=-1 ret=0 a=0
u/d=down
Thu Dec 29 08:52:25 2016 Route: Waiting for TUN/TAP interface to come up...
Thu Dec 29 08:52:26 2016 TEST ROUTES: 0/0 succeeded len=-1 ret=0 a=0
u/d=down
Thu Dec 29 08:52:26 2016 Route: Waiting for TUN/TAP interface to come up...
Thu Dec 29 08:52:28 2016 TEST ROUTES: 0/0 succeeded len=-1 ret=0 a=0
u/d=down
Thu Dec 29 08:52:28 2016 Route: Waiting for TUN/TAP interface to come up...
Thu Dec 29 08:52:29 2016 TEST ROUTES: 0/0 succeeded len=-1 ret=0 a=0
u/d=down
Thu Dec 29 08:52:29 2016 Route: Waiting for TUN/TAP interface to come up...
Thu Dec 29 08:52:30 2016 TEST ROUTES: 0/0 succeeded len=-1 ret=0 a=0
u/d=down
Thu Dec 29 08:52:30 2016 MANAGEMENT: >STATE:1482987150,ADD_ROUTES,,,,,,
Thu Dec 29 08:52:30 2016 C:\Windows\system32\route.exe ADD 192.168.0.0
MASK 255.255.0.0 192.168.31.1
Thu Dec 29 08:52:30 2016 Warning: route gateway is not reachable on any
active network adapters: 192.168.31.1
Thu Dec 29 08:52:30 2016 Route addition via service failed
Thu Dec 29 08:52:30 2016 C:\Windows\system32\route.exe ADD 10.0.0.0 MASK
255.0.0.0 192.168.31.1
Thu Dec 29 08:52:30 2016 Warning: route gateway is not reachable on any
active network adapters: 192.168.31.1
Thu Dec 29 08:52:30 2016 Route addition via service failed
SYSTEM ROUTING TABLE
0.0.0.0 0.0.0.0 192.168.22.221 p=0 i=10 t=4 pr=3 a=1042 h=0 m=10/0/0/0/0
10.1.10.0 255.255.255.0 10.1.10.6 p=0 i=18 t=3 pr=3 a=231 h=0 m=276/0/0/0/0
10.1.10.6 255.255.255.255 10.1.10.6 p=0 i=18 t=3 pr=3 a=231 h=0
m=276/0/0/0/0
10.1.10.255 255.255.255.255 10.1.10.6 p=0 i=18 t=3 pr=3 a=231 h=0
m=276/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=1057 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=1057 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=1057 h=0
m=306/0/0/0/0
192.168.22.0 255.255.255.0 192.168.22.44 p=0 i=10 t=3 pr=3 a=1042 h=0
m=266/0/0/0/0
192.168.22.44 255.255.255.255 192.168.22.44 p=0 i=10 t=3 pr=3 a=1042 h=0
m=266/0/0/0/0
192.168.22.255 255.255.255.255 192.168.22.44 p=0 i=10 t=3 pr=3 a=1042
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=1057 h=0 m=306/0/0/0/0
224.0.0.0 240.0.0.0 192.168.22.44 p=0 i=10 t=3 pr=3 a=1052 h=0 m=266/0/0/0/0
224.0.0.0 240.0.0.0 10.1.10.6 p=0 i=18 t=3 pr=3 a=321 h=0 m=276/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=1057 h=0
m=306/0/0/0/0
255.255.255.255 255.255.255.255 192.168.22.44 p=0 i=10 t=3 pr=3 a=1052
h=0 m=266/0/0/0/0
255.255.255.255 255.255.255.255 10.1.10.6 p=0 i=18 t=3 pr=3 a=321 h=0
m=276/0/0/0/0
SYSTEM ADAPTER LIST
TAP-Windows Adapter V9
Index = 18
GUID = {BE794D53-798C-40DC-8B64-4CE37589133F}
IP = 10.1.10.6/255.255.255.0
MAC = 00:ff:be:79:4d:53
GATEWAY = 0.0.0.0/255.255.255.255
DHCP SERV = 10.1.10.254/255.255.255.255
DHCP LEASE OBTAINED = Thu Dec 29 08:48:39 2016
DHCP LEASE EXPIRES = Fri Dec 29 08:48:39 2017
PRI WINS = 192.168.22.220/255.255.255.255
SEC WINS =
DNS SERV = 10.1.1.1/255.255.255.255
Index = 10
GUID = {A4E36638-F664-4D96-A46F-9EFB3EE72F74}
IP = 192.168.22.44/255.255.255.0
MAC = 08:00:27:6d:1b:5a
GATEWAY = 192.168.22.221/255.255.255.255
DHCP SERV = 192.168.22.222/255.255.255.255
DHCP LEASE OBTAINED = Thu Dec 29 08:35:07 2016
DHCP LEASE EXPIRES = Thu Dec 29 14:35:07 2016
PRI WINS = 192.168.22.91/255.255.255.255
SEC WINS =
DNS SERV = 192.168.22.222/255.255.255.255 192.168.22.99/255.255.255.255
Thu Dec 29 08:52:30 2016 Initialization Sequence Completed With Errors (
see http://openvpn.net/faq.html#dhcpclientserv )
Thu Dec 29 08:52:30 2016 MANAGEMENT:
> STATE:1482987150,CONNECTED,ERROR,192.168.31.6,78.85.14.181,1194,192.168.22.44,54529
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, SlashDot.org! http://sdm.link/slashdot
_______________________________________________
Openvpn-devel mailing list
Openvpn-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/openvpn-devel
