Release of dhcp assigned ip address lease on tap windows adapter failed

TinCanTech wrote: ↑

Thu Oct 06, 2022 1:21 pm

Please post the complete (sanitized) client log at —verb 4

I have tested many open-as(>=2.8.8) versions. Even the default settings are the same as long as the community client is used.

2022-10-08 15:35:17 DEPRECATED OPTION: —cipher set to ‘AES-256-CBC’ but missing in —data-ciphers (AES-256-GCM:AES-128-GCM). Future OpenVPN version will ignore —cipher for cipher negotiations. Add ‘AES-256-CBC’ to —data-ciphers or change —cipher ‘AES-256-CBC’ to —data-ciphers-fallback ‘AES-256-CBC’ to silence this warning.
2022-10-08 15:35:17 OpenVPN 2.5.7 Windows-MSVC [SSL (OpenSSL)] [LZO] [LZ4] [PKCS11] [AEAD] built on May 27 2022
2022-10-08 15:35:17 Windows version 10.0 (Windows 10 or greater) 64bit
2022-10-08 15:35:17 library versions: OpenSSL 1.1.1o 3 May 2022, LZO 2.10
2022-10-08 15:35:17 MANAGEMENT: TCP Socket listening on [AF_INET]127.0.0.1:25340
2022-10-08 15:35:17 Need hold release from management interface, waiting…
2022-10-08 15:35:18 MANAGEMENT: Client connected from [AF_INET]127.0.0.1:25340
2022-10-08 15:35:18 MANAGEMENT: CMD ‘state on’
2022-10-08 15:35:18 MANAGEMENT: CMD ‘log all on’
2022-10-08 15:35:18 MANAGEMENT: CMD ‘echo all on’
2022-10-08 15:35:18 MANAGEMENT: CMD ‘bytecount 5’
2022-10-08 15:35:18 MANAGEMENT: CMD ‘hold off’
2022-10-08 15:35:18 MANAGEMENT: CMD ‘hold release’
2022-10-08 15:35:19 MANAGEMENT: CMD ‘username «Auth» «shilh»‘
2022-10-08 15:35:19 MANAGEMENT: CMD ‘password […]’
2022-10-08 15:35:19 Outgoing Control Channel Encryption: Cipher ‘AES-256-CTR’ initialized with 256 bit key
2022-10-08 15:35:19 Outgoing Control Channel Encryption: Using 256 bit message hash ‘SHA256’ for HMAC authentication
2022-10-08 15:35:19 Incoming Control Channel Encryption: Cipher ‘AES-256-CTR’ initialized with 256 bit key
2022-10-08 15:35:19 Incoming Control Channel Encryption: Using 256 bit message hash ‘SHA256’ for HMAC authentication
2022-10-08 15:35:19 TCP/UDP: Preserving recently used remote address: [AF_INET]192.168.245.132:1194
2022-10-08 15:35:19 Socket Buffers: R=[131072->131072] S=[131072->131072]
2022-10-08 15:35:19 UDP link local: (not bound)
2022-10-08 15:35:19 UDP link remote: [AF_INET]192.168.245.132:1194
2022-10-08 15:35:19 MANAGEMENT: >STATE:1665214519,WAIT,,,,,,
2022-10-08 15:35:19 MANAGEMENT: >STATE:1665214519,AUTH,,,,,,
2022-10-08 15:35:19 TLS: Initial packet from [AF_INET]192.168.245.132:1194, sid=03d09c25 d941d9be
2022-10-08 15:35:19 VERIFY OK: depth=1, CN=OpenVPN CA
2022-10-08 15:35:19 VERIFY KU OK
2022-10-08 15:35:19 Validating certificate extended key usage
2022-10-08 15:35:19 ++ Certificate has EKU (str) TLS Web Server Authentication, expects TLS Web Server Authentication
2022-10-08 15:35:19 VERIFY EKU OK
2022-10-08 15:35:19 VERIFY OK: depth=0, CN=OpenVPN Server
2022-10-08 15:35:19 Control Channel: TLSv1.3, cipher TLSv1.3 TLS_AES_256_GCM_SHA384, peer certificate: 2048 bit RSA, signature: RSA-SHA256
2022-10-08 15:35:19 [OpenVPN Server] Peer Connection Initiated with [AF_INET]192.168.245.132:1194
2022-10-08 15:35:20 MANAGEMENT: >STATE:1665214520,GET_CONFIG,,,,,,
2022-10-08 15:35:20 SENT CONTROL [OpenVPN Server]: ‘PUSH_REQUEST’ (status=1)
2022-10-08 15:35:20 PUSH: Received control message: ‘PUSH_REPLY,explicit-exit-notify,topology subnet,route-delay 5 30,dhcp-pre-release,dhcp-renew,dhcp-release,route-metric 101,ping 12,ping-restart 50,redirect-gateway def1,redirect-gateway bypass-dhcp,redirect-gateway autolocal,route-gateway 172.27.232.1,dhcp-option DNS 192.168.245.2,register-dns,block-ipv6,ifconfig 172.27.232.3 255.255.248.0,peer-id 0,auth-tokenSESS_ID,cipher AES-256-GCM’
2022-10-08 15:35:20 Obsolete option —dhcp-release detected. This is now on by default
2022-10-08 15:35:20 WARNING: You have specified redirect-gateway and redirect-private at the same time (or the same option multiple times). This is not well supported and may lead to unexpected results
2022-10-08 15:35:20 WARNING: You have specified redirect-gateway and redirect-private at the same time (or the same option multiple times). This is not well supported and may lead to unexpected results
2022-10-08 15:35:20 WARNING: this configuration may cache passwords in memory — use the auth-nocache option to prevent this
2022-10-08 15:35:20 OPTIONS IMPORT: timers and/or timeouts modified
2022-10-08 15:35:20 OPTIONS IMPORT: explicit notify parm(s) modified
2022-10-08 15:35:20 OPTIONS IMPORT: —ifconfig/up options modified
2022-10-08 15:35:20 OPTIONS IMPORT: route options modified
2022-10-08 15:35:20 OPTIONS IMPORT: route-related options modified
2022-10-08 15:35:20 OPTIONS IMPORT: —ip-win32 and/or —dhcp-option options modified
2022-10-08 15:35:20 OPTIONS IMPORT: peer-id set
2022-10-08 15:35:20 OPTIONS IMPORT: adjusting link_mtu to 1624
2022-10-08 15:35:20 OPTIONS IMPORT: data channel crypto options modified
2022-10-08 15:35:20 Data Channel: using negotiated cipher ‘AES-256-GCM’
2022-10-08 15:35:20 Outgoing Data Channel: Cipher ‘AES-256-GCM’ initialized with 256 bit key
2022-10-08 15:35:20 Incoming Data Channel: Cipher ‘AES-256-GCM’ initialized with 256 bit key
2022-10-08 15:35:20 interactive service msg_channel=504
2022-10-08 15:35:20 open_tun
2022-10-08 15:35:20 tap-windows6 device [OpenVPN TAP-Windows6] opened
2022-10-08 15:35:20 TAP-Windows Driver Version 9.24
2022-10-08 15:35:20 Set TAP-Windows TUN subnet mode network/local/netmask = 172.27.232.0/172.27.232.3/255.255.248.0 [SUCCEEDED]
2022-10-08 15:35:20 Notified TAP-Windows driver to set a DHCP IP/netmask of 172.27.232.3/255.255.248.0 on interface {086AB4A5-A7CE-4CDC-A454-745D2B6D7362} [DHCP-serv: 172.27.232.0, lease-time: 31536000]
2022-10-08 15:35:20 Successful ARP Flush on interface [11] {086AB4A5-A7CE-4CDC-A454-745D2B6D7362}
2022-10-08 15:35:20 NOTE: Release of DHCP-assigned IP address lease on TAP-Windows adapter failed: The system cannot find the specified file。 (code=2)
2022-10-08 15:35:20 WARNING: Failed to renew DHCP IP address lease on TAP-Windows adapter: The system cannot find the specified file。 (code=2)
2022-10-08 15:35:20 MANAGEMENT: >STATE:1665214520,ASSIGN_IP,,172.27.232.3,,,,
2022-10-08 15:35:20 IPv4 MTU set to 1500 on interface 11 using service
2022-10-08 15:35:25 TEST ROUTES: 1/1 succeeded len=0 ret=1 a=0 u/d=up
2022-10-08 15:35:25 C:\Windows\system32\route.exe ADD 0.0.0.0 MASK 128.0.0.0 172.27.232.1
2022-10-08 15:35:25 Route addition via service succeeded
2022-10-08 15:35:25 C:\Windows\system32\route.exe ADD 128.0.0.0 MASK 128.0.0.0 172.27.232.1
2022-10-08 15:35:25 Route addition via service succeeded
2022-10-08 15:35:25 Initialization Sequence Completed
2022-10-08 15:35:25 Register_dns request sent to the service
2022-10-08 15:35:25 MANAGEMENT: >STATE:1665214525,CONNECTED,SUCCESS,172.27.232.3,192.168.245.132,1194,,

Источник

Skip to content

Got a problem with Viscosity or need help? Ask here!

Aniki18: Posts: 9; Joined: Sat Jan 19, 2013 5:06 am

I have two connections to the same OpenVPN server. They both use the same Viscosity virtual adapter (i.e. their dev-node value is the same). Sometimes this error is thrown when the VPN is trying to connect:

Feb 16 03:59:43: NOTE: Release of DHCP-assigned IP address lease on TAP-Win32 adapter failed: The parameter is incorrect. (code=87)
Feb 16 03:59:43: WARNING: Failed to renew DHCP IP address lease on TAP-Win32 adapter: The system cannot find the file specified. (code=2)

This happens seemingly at random and it doesn’t matter which connection I use. When I go in to device manager after this happens, the virtual adapter is always disabled. It usually works if I reconnect, but I’d like to find a way to avoid these errors all together.

Eric: Posts: 1146; Joined: Sun Jan 03, 2010 3:27 am

Hi Aniki18,

Is this happening when you disconnect one connection then connect with the other?
Does this ever happen after opening Viscosity after a reboot?
Are you trying to connect with both connections simultaneously at all?
Also is this only happening when you connect, or does it sometimes happen when you are already connected?

Regards,

Eric

Aniki18: Posts: 9; Joined: Sat Jan 19, 2013 5:06 am

Hi Eric,

1). Probably not. I don’t usually switch from one connection to another immediately, and I just tested that and it seemed to work fine.
2). I usually put my PC in hibernate, but I have noticed that it happens more often after waking or booting up. But, it can happen at other times as well.
3). No
4). No

The only difference between the two connections is that one runs some scripts. When I used to have the connections running off of two separate virtual adapters, the errors where much more frequent. I thought I solved the problem by switching to one virtual adapter, but it still happens from time to time. Thanks for the response .

Last edited by Aniki18 on Mon Feb 18, 2013 4:14 pm, edited 1 time in total.

Eric: Posts: 1146; Joined: Sun Jan 03, 2010 3:27 am

Hi Aniki18,

Thanks for the feedback. If you disable «Reconnect activate connections on wake», can you test two things for us:

1) If you are hibernating your PC with connections active, do they still try to reconnect when you wake your computer?
2) Does this help the situation at all if you manually reconnect after waking/booting your pc.

Thanks,

Eric.

Aniki18: Posts: 9; Joined: Sat Jan 19, 2013 5:06 am

I actually suspected that this might be a cause of the problem, so I disabled «Reconnect on wake» a while ago, but the errors continued to happen.

Eric: Posts: 1146; Joined: Sun Jan 03, 2010 3:27 am

Hi Aniki18,

Thanks for the reply. Are you able to post a copy of the complete log when a connection fails? When the connection fails, does Viscosity claim it is still trying to connect, or does it disconnect?

Regards,

Eric

Aniki18: Posts: 9; Joined: Sat Jan 19, 2013 5:06 am

Hey again Eric,

Yeah, it definitely appears to be happening on wake. I hibernated and woke the PC up and reproduced the error. Here’s the log:

Code: Select all

Feb 17 09:47:27: State changed to Connecting
Feb 17 09:47:27: Viscosity 1.4.2 (1178)
Feb 17 09:47:27: Running on Microsoft Windows 8 Pro
Feb 17 09:47:27: Bringing up interface...
Feb 17 09:47:27: Checking reachability status of connection...
Feb 17 09:47:29: Connection is reachable. Starting connection attempt.
Feb 17 09:47:29: OpenVPN 2.2.2 Win32-MSVC++ [SSL] [LZO2] [PKCS11] built on Jan  4 2012Feb 17 09:47:33: NOTE: OpenVPN 2.1 requires '--script-security 2' or higher to call user-defined scripts or executables
Feb 17 09:47:33: Control Channel Authentication: using 'ta.key' as a OpenVPN static key file
Feb 17 09:47:33: LZO compression initialized
Feb 17 09:47:33: UDPv4 link local: [undef]
Feb 17 09:47:33: UDPv4 link remote: 95.219.223.187:1194
Feb 17 09:47:33: WARNING: this configuration may cache passwords in memory -- use the auth-nocache option to prevent this
Feb 17 09:47:35: [OpenVPN_Server] Peer Connection Initiated with 95.219.223.187:1194
Feb 17 09:47:37: Unrecognized option or missing parameter(s) in [PUSH-OPTIONS]:17: auth-token (2.2.2)
Feb 17 09:47:37: TAP-WIN32 device [Plex] opened: \\.\Global\{27C5B2AE-7256-4F89-BC9A-EE705B3E7436}.tap
Feb 17 09:47:37: Set TAP-Win32 TUN subnet mode network/local/netmask = 5.5.0.0/5.5.0.77/255.255.240.0 [SUCCEEDED]
Feb 17 09:47:37: Notified TAP-Win32 driver to set a DHCP IP/netmask of 5.5.0.77/255.255.240.0 on interface {27C5B2AE-7256-4F89-BC9A-EE705B3E7436} [DHCP-serv: 5.5.15.254, lease-time: 31536000]
Feb 17 09:47:37: Successful ARP Flush on interface [26] {27C5B2AE-7256-4F89-BC9A-EE705B3E7436}
Feb 17 09:47:37: NOTE: Release of DHCP-assigned IP address lease on TAP-Win32 adapter failed: The system cannot find the file specified.   (code=2)
Feb 17 09:47:37: WARNING: Failed to renew DHCP IP address lease on TAP-Win32 adapter: The system cannot find the file specified.   (code=2)
Feb 17 09:48:12: Warning: route gateway is not reachable on any active network adapters: 5.5.0.1
Feb 17 09:48:12: Warning: route gateway is not reachable on any active network adapters: 5.5.0.1
Feb 17 09:48:12: SYSTEM ROUTING TABLE
Feb 17 09:48:12: 0.0.0.0 0.0.0.0 192.168.2.1 p=0 i=12 t=4 pr=3 a=97929 h=0 m=21/0/0/0/0
Feb 17 09:48:12: 0.0.0.0 128.0.0.0 5.5.0.1 p=0 i=12 t=4 pr=3 a=0 h=0 m=21/0/0/0/0
Feb 17 09:48:12: 95.219.223.187 255.255.255.255 192.168.2.1 p=0 i=12 t=4 pr=3 a=0 h=0 m=20/0/0/0/0
Feb 17 09:48:12: 127.0.0.0 255.0.0.0 127.0.0.1 p=0 i=1 t=3 pr=2 a=97945 h=0 m=306/0/0/0/0
Feb 17 09:48:12: 127.0.0.1 255.255.255.255 127.0.0.1 p=0 i=1 t=3 pr=2 a=97945 h=0 m=306/0/0/0/0
Feb 17 09:48:12: 127.255.255.255 255.255.255.255 127.0.0.1 p=0 i=1 t=3 pr=2 a=97945 h=0 m=306/0/0/0/0
Feb 17 09:48:12: 128.0.0.0 128.0.0.0 5.5.0.1 p=0 i=12 t=4 pr=3 a=0 h=0 m=21/0/0/0/0
Feb 17 09:48:12: 192.168.2.0 255.255.255.0 192.168.2.150 p=0 i=12 t=3 pr=2 a=97926 h=0 m=276/0/0/0/0
Feb 17 09:48:12: 192.168.2.150 255.255.255.255 192.168.2.150 p=0 i=12 t=3 pr=2 a=97926 h=0 m=276/0/0/0/0
Feb 17 09:48:12: 192.168.2.255 255.255.255.255 192.168.2.150 p=0 i=12 t=3 pr=2 a=97926 h=0 m=276/0/0/0/0
Feb 17 09:48:12: 224.0.0.0 240.0.0.0 127.0.0.1 p=0 i=1 t=3 pr=2 a=97945 h=0 m=306/0/0/0/0
Feb 17 09:48:12: 224.0.0.0 240.0.0.0 192.168.2.150 p=0 i=12 t=3 pr=2 a=97929 h=0 m=276/0/0/0/0
Feb 17 09:48:12: 255.255.255.255 255.255.255.255 127.0.0.1 p=0 i=1 t=3 pr=2 a=97945 h=0 m=306/0/0/0/0
Feb 17 09:48:12: 255.255.255.255 255.255.255.255 192.168.2.150 p=0 i=12 t=3 pr=2 a=97929 h=0 m=276/0/0/0/0
Feb 17 09:48:12: SYSTEM ADAPTER LIST
Feb 17 09:48:12: Viscosity Virtual Adapter V9.1
Feb 17 09:48:12:   Index = 26
Feb 17 09:48:12:   GUID = {27C5B2AE-7256-4F89-BC9A-EE705B3E7436}
Feb 17 09:48:12:   IP = 0.0.0.0/0.0.0.0 
Feb 17 09:48:12:   MAC = 00:ff:27:c5:b2:ae
Feb 17 09:48:12:   GATEWAY = 0.0.0.0/255.255.255.255 
Feb 17 09:48:12:   DHCP SERV =  
Feb 17 09:48:12:   DHCP LEASE OBTAINED = Sun Feb 17 21:48:12 2013
Feb 17 09:48:12:   DHCP LEASE EXPIRES  = Wed May 06 07:33:56 1970
Feb 17 09:48:12:   DNS SERV =  
Feb 17 09:48:12: Microsoft Wi-Fi Direct Virtual Adapter #3
Feb 17 09:48:12:   Index = 20
Feb 17 09:48:12:   GUID = {813F268C-24A2-471E-B836-274B7C81559D}
Feb 17 09:48:12:   IP = 0.0.0.0/0.0.0.0 
Feb 17 09:48:12:   MAC = de:85:de:7c:ba:5f
Feb 17 09:48:12:   GATEWAY = 0.0.0.0/255.255.255.255 
Feb 17 09:48:12:   DHCP SERV =  
Feb 17 09:48:12:   DHCP LEASE OBTAINED = Sun Feb 17 21:48:12 2013
Feb 17 09:48:12:   DHCP LEASE EXPIRES  = Wed May 06 07:44:36 1970
Feb 17 09:48:12:   DNS SERV =  
Feb 17 09:48:12: Broadcom 802.11n Network Adapter
Feb 17 09:48:12:   Index = 19
Feb 17 09:48:12:   GUID = {0A416E8E-BF62-454F-9485-5F12E3A7185A}
Feb 17 09:48:12:   IP = 0.0.0.0/0.0.0.0 
Feb 17 09:48:12:   MAC = dc:85:de:7c:ba:5f
Feb 17 09:48:12:   GATEWAY = 0.0.0.0/255.255.255.255 
Feb 17 09:48:12:   DHCP SERV =  
Feb 17 09:48:12:   DHCP LEASE OBTAINED = Sun Feb 17 21:48:12 2013
Feb 17 09:48:12:   DHCP LEASE EXPIRES  = Wed May 06 07:55:16 1970
Feb 17 09:48:12:   DNS SERV =  
Feb 17 09:48:12: Bluetooth Device (Personal Area Network)
Feb 17 09:48:12:   Index = 16
Feb 17 09:48:12:   GUID = {065858F4-9DEF-46D5-ADDC-35751F9CA7A3}
Feb 17 09:48:12:   IP = 0.0.0.0/0.0.0.0 
Feb 17 09:48:12:   MAC = dc:85:de:67:27:5e
Feb 17 09:48:12:   GATEWAY = 0.0.0.0/255.255.255.255 
Feb 17 09:48:12:   DHCP SERV =  
Feb 17 09:48:12:   DHCP LEASE OBTAINED = Sun Feb 17 21:48:12 2013
Feb 17 09:48:12:   DHCP LEASE EXPIRES  = Wed Dec 31 16:00:00 1969
Feb 17 09:48:12:   DNS SERV =  
Feb 17 09:48:12: Intel(R) 82579V Gigabit Network Connection
Feb 17 09:48:12:   Index = 12
Feb 17 09:48:12:   GUID = {FC070ACD-3DD6-423A-8AB4-25CF4508DCB1}
Feb 17 09:48:12:   IP = 192.168.2.150/255.255.255.0 
Feb 17 09:48:12:   MAC = 50:46:5d:4f:1d:9c
Feb 17 09:48:12:   GATEWAY = 192.168.2.1/255.255.255.255 
Feb 17 09:48:12:   DNS SERV = 192.168.2.1/255.255.255.255 
Feb 17 09:48:12: Initialization Sequence Completed With Errors ( see http://openvpn.net/faq.html#dhcpclientserv )
Feb 17 09:48:12: State changed to Connected

It still appears that it is connected, but it doesn’t work. Then, after disconnecting and reconnecting, it works fine. Not a huge deal for me, but I’m trying to make this setup girlfriend-proof .

Eric: Posts: 1146; Joined: Sun Jan 03, 2010 3:27 am

Hi Aniki18,

Thanks for that log. You can confirm the adapter is disabled when the log says the connection is connected? If so, we have some updates in the next version which should solve this specific issue, if not we’ll need to look elsewhere.

Regards,

Eric

Aniki18: Posts: 9; Joined: Sat Jan 19, 2013 5:06 am

Hmmm… Weird, now I can’t seem to replicate the problem. I’ll get back to you when it happens again.

Aniki18: Posts: 9; Joined: Sat Jan 19, 2013 5:06 am

Hello again,

Same problem occurred this morning, but this time it was not after a wake or reboot, it was after switching from one connection to another. It says connected and the adapter is enabled, but it gives the same DHCP error in the log.

Log from 1st connection (worked fine):

Code: Select all

Feb 18 12:44:43: State changed to Connecting
Feb 18 12:44:43: Viscosity 1.4.2 (1178)
Feb 18 12:44:43: Running on Microsoft Windows 8 Pro
Feb 18 12:44:43: Bringing up interface...
Feb 18 12:44:43: Checking reachability status of connection...
Feb 18 12:44:44: Connection is reachable. Starting connection attempt.
Feb 18 12:44:44: OpenVPN 2.2.2 Win32-MSVC++ [SSL] [LZO2] [PKCS11] built on Jan  4 2012
Feb 18 12:44:48: NOTE: OpenVPN 2.1 requires '--script-security 2' or higher to call user-defined scripts or executables
Feb 18 12:44:48: Control Channel Authentication: using 'ta.key' as a OpenVPN static key file
Feb 18 12:44:48: LZO compression initialized
Feb 18 12:44:48: UDPv4 link local: [undef]
Feb 18 12:44:48: UDPv4 link remote: 95.219.223.187:1194
Feb 18 12:44:48: WARNING: this configuration may cache passwords in memory -- use the auth-nocache option to prevent this
Feb 18 12:44:50: [OpenVPN_Server] Peer Connection Initiated with 95.219.223.187:1194
Feb 18 12:44:56: Unrecognized option or missing parameter(s) in [PUSH-OPTIONS]:17: auth-token (2.2.2)
Feb 18 12:44:56: TAP-WIN32 device [Plex] opened: \\.\Global\{27C5B2AE-7256-4F89-BC9A-EE705B3E7436}.tap
Feb 18 12:44:56: Set TAP-Win32 TUN subnet mode network/local/netmask = 5.5.0.0/5.5.0.2/255.255.240.0 [SUCCEEDED]
Feb 18 12:44:56: Notified TAP-Win32 driver to set a DHCP IP/netmask of 5.5.0.2/255.255.240.0 on interface {27C5B2AE-7256-4F89-BC9A-EE705B3E7436} [DHCP-serv: 5.5.15.254, lease-time: 31536000]
Feb 18 12:44:56: Successful ARP Flush on interface [26] {27C5B2AE-7256-4F89-BC9A-EE705B3E7436}
Feb 18 12:45:01: State changed to Disconnecting
Feb 18 12:45:01: State changed to Disconnected

Log from 2nd connection (errors):

Code: Select all

Feb 18 12:45:02: State changed to Connecting
Feb 18 12:45:03: Viscosity 1.4.2 (1178)
Feb 18 12:45:03: Running on Microsoft Windows 8 Pro
Feb 18 12:45:03: Bringing up interface...
Feb 18 12:45:03: Checking reachability status of connection...
Feb 18 12:45:04: Connection is reachable. Starting connection attempt.
Feb 18 12:45:04: OpenVPN 2.2.2 Win32-MSVC++ [SSL] [LZO2] [PKCS11] built on Jan  4 2012
Feb 18 12:45:04: NOTE: OpenVPN 2.1 requires '--script-security 2' or higher to call user-defined scripts or executables
Feb 18 12:45:04: Control Channel Authentication: using 'ta.key' as a OpenVPN static key file
Feb 18 12:45:04: LZO compression initialized
Feb 18 12:45:04: UDPv4 link local: [undef]
Feb 18 12:45:04: UDPv4 link remote: 95.219.223.187:1194
Feb 18 12:45:05: WARNING: this configuration may cache passwords in memory -- use the auth-nocache option to prevent this
Feb 18 12:45:06: [OpenVPN_Server] Peer Connection Initiated with 95.219.223.187:1194
Feb 18 12:45:09: Unrecognized option or missing parameter(s) in [PUSH-OPTIONS]:17: auth-token (2.2.2)
Feb 18 12:45:09: TAP-WIN32 device [Plex] opened: \\.\Global\{27C5B2AE-7256-4F89-BC9A-EE705B3E7436}.tap
Feb 18 12:45:09: Set TAP-Win32 TUN subnet mode network/local/netmask = 5.5.0.0/5.5.0.3/255.255.240.0 [SUCCEEDED]
Feb 18 12:45:09: Notified TAP-Win32 driver to set a DHCP IP/netmask of 5.5.0.3/255.255.240.0 on interface {27C5B2AE-7256-4F89-BC9A-EE705B3E7436} [DHCP-serv: 5.5.15.254, lease-time: 31536000]
Feb 18 12:45:09: Successful ARP Flush on interface [26] {27C5B2AE-7256-4F89-BC9A-EE705B3E7436}
Feb 18 12:45:09: NOTE: Release of DHCP-assigned IP address lease on TAP-Win32 adapter failed: The system cannot find the file specified.   (code=2)
Feb 18 12:45:09: WARNING: Failed to renew DHCP IP address lease on TAP-Win32 adapter: The system cannot find the file specified.   (code=2)
Feb 18 12:45:44: Warning: route gateway is not reachable on any active network adapters: 5.5.0.1
Feb 18 12:45:44: Warning: route gateway is not reachable on any active network adapters: 5.5.0.1
Feb 18 12:45:44: SYSTEM ROUTING TABLE
Feb 18 12:45:44: 0.0.0.0 0.0.0.0 192.168.2.1 p=0 i=12 t=4 pr=3 a=151766 h=0 m=21/0/0/0/0
Feb 18 12:45:44: 0.0.0.0 128.0.0.0 5.5.0.1 p=0 i=12 t=4 pr=3 a=0 h=0 m=21/0/0/0/0
Feb 18 12:45:44: 95.219.223.187 255.255.255.255 192.168.2.1 p=0 i=12 t=4 pr=3 a=0 h=0 m=20/0/0/0/0
Feb 18 12:45:44: 127.0.0.0 255.0.0.0 127.0.0.1 p=0 i=1 t=3 pr=2 a=151782 h=0 m=306/0/0/0/0
Feb 18 12:45:44: 127.0.0.1 255.255.255.255 127.0.0.1 p=0 i=1 t=3 pr=2 a=151782 h=0 m=306/0/0/0/0
Feb 18 12:45:44: 127.255.255.255 255.255.255.255 127.0.0.1 p=0 i=1 t=3 pr=2 a=151782 h=0 m=306/0/0/0/0
Feb 18 12:45:44: 128.0.0.0 128.0.0.0 5.5.0.1 p=0 i=12 t=4 pr=3 a=0 h=0 m=21/0/0/0/0
Feb 18 12:45:44: 192.168.2.0 255.255.255.0 192.168.2.150 p=0 i=12 t=3 pr=2 a=151763 h=0 m=276/0/0/0/0
Feb 18 12:45:44: 192.168.2.150 255.255.255.255 192.168.2.150 p=0 i=12 t=3 pr=2 a=151763 h=0 m=276/0/0/0/0
Feb 18 12:45:44: 192.168.2.255 255.255.255.255 192.168.2.150 p=0 i=12 t=3 pr=2 a=151763 h=0 m=276/0/0/0/0
Feb 18 12:45:44: 224.0.0.0 240.0.0.0 127.0.0.1 p=0 i=1 t=3 pr=2 a=151782 h=0 m=306/0/0/0/0
Feb 18 12:45:44: 224.0.0.0 240.0.0.0 192.168.2.150 p=0 i=12 t=3 pr=2 a=151766 h=0 m=276/0/0/0/0
Feb 18 12:45:44: 255.255.255.255 255.255.255.255 127.0.0.1 p=0 i=1 t=3 pr=2 a=151782 h=0 m=306/0/0/0/0
Feb 18 12:45:44: 255.255.255.255 255.255.255.255 192.168.2.150 p=0 i=12 t=3 pr=2 a=151766 h=0 m=276/0/0/0/0
Feb 18 12:45:44: SYSTEM ADAPTER LIST
Feb 18 12:45:44: Viscosity Virtual Adapter V9.1
Feb 18 12:45:44:   Index = 26
Feb 18 12:45:44:   GUID = {27C5B2AE-7256-4F89-BC9A-EE705B3E7436}
Feb 18 12:45:44:   IP = 0.0.0.0/0.0.0.0 
Feb 18 12:45:44:   MAC = 00:ff:27:c5:b2:ae
Feb 18 12:45:44:   GATEWAY = 0.0.0.0/255.255.255.255 
Feb 18 12:45:44:   DHCP SERV =  
Feb 18 12:45:44:   DHCP LEASE OBTAINED = Mon Feb 18 12:45:44 2013
Feb 18 12:45:44:   DHCP LEASE EXPIRES  = Sun May 03 11:02:28 1970
Feb 18 12:45:44:   DNS SERV =  
Feb 18 12:45:44: Microsoft Wi-Fi Direct Virtual Adapter #3
Feb 18 12:45:44:   Index = 20
Feb 18 12:45:44:   GUID = {813F268C-24A2-471E-B836-274B7C81559D}
Feb 18 12:45:44:   IP = 0.0.0.0/0.0.0.0 
Feb 18 12:45:44:   MAC = de:85:de:7c:ba:5f
Feb 18 12:45:44:   GATEWAY = 0.0.0.0/255.255.255.255 
Feb 18 12:45:44:   DHCP SERV =  
Feb 18 12:45:44:   DHCP LEASE OBTAINED = Mon Feb 18 12:45:44 2013
Feb 18 12:45:44:   DHCP LEASE EXPIRES  = Sun May 03 11:13:08 1970
Feb 18 12:45:44:   DNS SERV =  
Feb 18 12:45:44: Broadcom 802.11n Network Adapter
Feb 18 12:45:44:   Index = 19
Feb 18 12:45:44:   GUID = {0A416E8E-BF62-454F-9485-5F12E3A7185A}
Feb 18 12:45:44:   IP = 0.0.0.0/0.0.0.0 
Feb 18 12:45:44:   MAC = dc:85:de:7c:ba:5f
Feb 18 12:45:44:   GATEWAY = 0.0.0.0/255.255.255.255 
Feb 18 12:45:44:   DHCP SERV =  
Feb 18 12:45:44:   DHCP LEASE OBTAINED = Mon Feb 18 12:45:44 2013
Feb 18 12:45:44:   DHCP LEASE EXPIRES  = Sun May 03 11:23:48 1970
Feb 18 12:45:44:   DNS SERV =  
Feb 18 12:45:44: Bluetooth Device (Personal Area Network)
Feb 18 12:45:44:   Index = 16
Feb 18 12:45:44:   GUID = {065858F4-9DEF-46D5-ADDC-35751F9CA7A3}
Feb 18 12:45:44:   IP = 0.0.0.0/0.0.0.0 
Feb 18 12:45:44:   MAC = dc:85:de:67:27:5e
Feb 18 12:45:44:   GATEWAY = 0.0.0.0/255.255.255.255 
Feb 18 12:45:44:   DHCP SERV =  
Feb 18 12:45:44:   DHCP LEASE OBTAINED = Mon Feb 18 12:45:44 2013
Feb 18 12:45:44:   DHCP LEASE EXPIRES  = Wed Dec 31 16:00:00 1969
Feb 18 12:45:44:   DNS SERV =  
Feb 18 12:45:44: Intel(R) 82579V Gigabit Network Connection
Feb 18 12:45:44:   Index = 12
Feb 18 12:45:44:   GUID = {FC070ACD-3DD6-423A-8AB4-25CF4508DCB1}
Feb 18 12:45:44:   IP = 192.168.2.150/255.255.255.0 
Feb 18 12:45:44:   MAC = 50:46:5d:4f:1d:9c
Feb 18 12:45:44:   GATEWAY = 192.168.2.1/255.255.255.255 
Feb 18 12:45:44:   DNS SERV = 192.168.2.1/255.255.255.255 
Feb 18 12:45:44: Initialization Sequence Completed With Errors ( see http://openvpn.net/faq.html#dhcpclientserv )
Feb 18 12:45:44: State changed to Connected

As a random test, I changed my assigned IP from dynamic to static in OpenVPN-AS, but it didn’t help .

Источник

View previous topic :: View next topic

Author

Message

Jules13
DD-WRT Novice

Joined: 10 Jun 2017
Posts: 36

Posted: Sat Nov 04, 2017 17:24 Post subject: OpenVPN Client config Issue

Hi guys,

I need your help for my OpenVPN config

Here are the settings on my dd wrt router

Code:

Start Type : System

Config as : Server

Server Mode: TUN

Network 192.168.1.0/24 (my local network is 192.168.1.1)

Netmask 255.255.255.0

Port 1194

Tunnel Protocol UDP

Encryption Cypher AES 256 CBC

Hash Algorythm: SHA1

I generate the certificate with this guide using windows

https://www.dd-wrt.com/wiki/index.php/VPN_(the_easy_way)_v24%2B#Creating_Certificates

I put this in the additionnal config

Code:

push «route 192.168.1.0 255.255.255.0»

push «dhcp-option DNS 192.168.66.1»

server 192.168.66.0 255.255.255.0

dev tun0

proto udp

keepalive 10 120

dh /tmp/openvpn/dh.pem

ca /tmp/openvpn/ca.crt

cert /tmp/openvpn/cert.pem

key /tmp/openvpn/key.pem

# Only use crl-verify if you are using the revoke list — otherwise leave it commented out

# crl-verify /tmp/openvpn/ca.crl

# management parameter allows DD-WRT\s OpenVPN Status web page to access the server\s management port

# port must be 5001 for scripts embedded in firmware to work

management localhost 5001

I put nothing in the TLS Auth key and in the certificate revoke list like the guide

Then i put this in my client config (windows)

Code:

client

remote-cert-tls server

dev tun0

proto udp

remote MYDOMAINNAME 1194

resolv-retry infinite

nobind

persist-key

persist-tun

float

;mute-replay-warnings

route-delay 30

ca C:\\Program Files\\OpenVPN\\easy-rsa\\keys\\ca.crt

cert C:\\Program Files\\OpenVPN\\easy-rsa\\keys\\client1.crt

key C:\\Program Files\\OpenVPN\\easy-rsa\\keys\\client1.key

remote-cert-tls server

tls-auth ta.key 1

cipher AES-256-CBC

Thank you for your help

Jules13

Back to top

Sponsor

Jules13
DD-WRT Novice

Joined: 10 Jun 2017
Posts: 36

Posted: Sun Nov 05, 2017 8:29 Post subject: Re: OpenVPN Client config Issue

jxm wrote:

Jules13 wrote:

Hi guys,

I need your help for my OpenVPN config

Here are the settings on my dd wrt router

Code:

Start Type : System

Config as : Server

Server Mode: TUN

Network 192.168.1.0/24 (my local network is 192.168.1.1)

Netmask 255.255.255.0

The VPN network has to be different to the local network.

https://openvpn.net/index.php/open-source/documentation/howto.html#config

Ok so i can put 192.168.66.0/24

But for the netmask

Do i enter 255.255.255.0 or 255.255.0.0 or another thing

Thank you for your help

Jules13

Back to top

Jules13
DD-WRT Novice

Joined: 10 Jun 2017
Posts: 36

Posted: Sun Nov 05, 2017 8:35 Post subject:

And I still have an error on the confiog file on my computer:

I got this

Code:

Option error: Unrecognized option or missing or extra parameter(s) in: C:\Users\Jules\OpenVPN\clientconfig\clientconfig.ovpn:20: ca (2.4.4)

So i dont know what is wrong in my file but if oyou can help me

Thanks

Jules[/code]

Back to top

Jules13
DD-WRT Novice

Joined: 10 Jun 2017
Posts: 36

Posted: Sun Nov 05, 2017 9:49 Post subject:

jxm wrote:

The vpn netwoek will be 192.168.66.0 (omit the /24 here)

Netmask is 255.255.255.0.

The client error message tells you the error is in line 20. Count down 20 lines (you include blank lines) and you will see the line pointing to your ca certificate. Looks to me like you have made a mistake putting all those double backslashes in the path names. Change them all to single backslashes.

I replaced by one backslash like this but then i got another error:

—ca C:\Program Files\OpenVPN\easy-rsa\keys\ca.crt

Options warning: Bad backslash (‘\’) usage in client1.ovpn:16: remember that backslashes are treated as shell-escapes and if you need to pass backslash characters as part of a Windows filename, you should use double backslashes such as «c:\\openvpn\\static.key»

Thank you for the help

Back to top

Jules13
DD-WRT Novice

Joined: 10 Jun 2017
Posts: 36

Posted: Sun Nov 05, 2017 10:23 Post subject:
I realised my error, You just need to put <ca> ——BEGIN CERTIFICATE—- CERTIFICATE —-END CERTIFICATE—— </ca> And not the access like i did. Now i will test this and i come back

Back to top

Jules13
DD-WRT Novice

Joined: 10 Jun 2017
Posts: 36

Posted: Sun Nov 05, 2017 10:44 Post subject:

Jules13 wrote:

I realised my error,

You just need to put

<ca>

——BEGIN CERTIFICATE—-

CERTIFICATE

—-END CERTIFICATE——

</ca>

And not the access like i did.

Now i will test this and i come back

It seems i can now connect to my VPN.

But it still dont change the External IP adress (i used my phone cellular connection, made a ip test then activate the VPN and the ip didnt change)

On my windows settings it says that the WIndows TAP Adapters got no internet then it switch on the wifi.

So have you got an explaination for this?

And if it is TUN i should be able to join my local devices with my VPN? or i missunderstood something?

Here are the logs with the 2 errors all the connecting process is OK

Sun Nov 05 14:04:52 2017 NOTE: Release of DHCP-assigned IP address lease on TAP-Windows adapter failed: Le fichier spécifié est introuvable. (translation : specified folder is unfindable) (code=2)

Sun Nov 05 14:04:52 2017 SIGTERM[hard,] received, process exiting

Thank you

Jules13

Back to top

Jules13
DD-WRT Novice

Joined: 10 Jun 2017
Posts: 36

Posted: Sun Nov 05, 2017 16:46 Post subject:

If my DHCP for VPN isnt working

It can be due to the additionnal config

I entered this in the additionnal config (followed the tuto on dd wrt website)

push «route 192.168.66.0 255.255.255.0»

push «dhcp-option DNS 192.168.66.1»

server 192.168.66.0 255.255.255.0

dev tun0

proto udp

keepalive 10 120

dh /tmp/openvpn/dh.pem

ca /tmp/openvpn/ca.crt

cert /tmp/openvpn/cert.pem

key /tmp/openvpn/key.pem

Back to top

Display posts from previous:

Page 1 of 1

Navigation

You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
You cannot attach files in this forum
You cannot download files in this forum

Источник

Hi.

So I followed this video: https://www.youtube.com/watch?v=xiy52Hn5bTc

I had this running on my old network. It’s used for me to get access to my work network from home.

So, I recently switched ISP both at home and work to the same new one.

I setup PFsense and OpenVPN.

When I boot my PC, I can connect. However, after disconnecting and then trying to reconnect nothing happends.
These are the logs:

Tue Dec 12 21:31:17 2017 Initialization Sequence Completed With Errors ( see http://openvpn.net/faq.html#dhcpclientserv )
Tue Dec 12 21:34:47 2017 Warning: route gateway is not reachable on any active network adapters: 172.16.0.1
Tue Dec 12 21:34:47 2017 env_block: add PATH=C:\WINDOWS\System32;C:\WINDOWS;C:\WINDOWS\System32\Wbem
Tue Dec 12 21:34:47 2017 Warning: route gateway is not reachable on any active network adapters: 172.16.0.1
Tue Dec 12 21:34:47 2017 env_block: add PATH=C:\WINDOWS\System32;C:\WINDOWS;C:\WINDOWS\System32\Wbem
Tue Dec 12 21:34:47 2017 NOTE: Release of DHCP-assigned IP address lease on TAP-Windows adapter failed: An address has not yet been associated with the network endpoint. (code=1228)
Tue Dec 12 21:34:47 2017 SIGHUP[hard,] received, process restarting
Tue Dec 12 21:34:47 2017 OpenVPN 2.4.4 x86_64-w64-mingw32 [SSL (OpenSSL)] [LZO] [LZ4] [PKCS11] [AEAD] built on Sep 26 2017
Tue Dec 12 21:34:47 2017 Windows version 6.2 (Windows 8 or greater) 64bit
Tue Dec 12 21:34:47 2017 library versions: OpenSSL 1.0.2l 25 May 2017, LZO 2.10
Tue Dec 12 21:34:52 2017 TCP/UDP: Preserving recently used remote address: [AF_INET]xx.xxx.xxx.xx:1194
Tue Dec 12 21:34:52 2017 UDP link local (bound): [AF_INET][undef]:1194
Tue Dec 12 21:34:52 2017 UDP link remote: [AF_INET]xx.xxx.xxx.xx:1194
Tue Dec 12 21:34:52 2017 [www.safesurf.dk] Peer Connection Initiated with [AF_INET]xx.xxx.xxx.xx:1194
Tue Dec 12 21:34:53 2017 open_tun
Tue Dec 12 21:34:53 2017 TAP-WIN32 device [Ethernet 3] opened: \.\Global{734D00E0-401D-46F7-B1E7-420E4AB1DF67}.tap
Tue Dec 12 21:34:53 2017 Set TAP-Windows TUN subnet mode network/local/netmask = 172.16.0.0/172.16.0.2/255.255.255.0 [SUCCEEDED]
Tue Dec 12 21:34:53 2017 Notified TAP-Windows driver to set a DHCP IP/netmask of 172.16.0.2/255.255.255.0 on interface {734D00E0-401D-46F7-B1E7-420E4AB1DF67} [DHCP-serv: 172.16.0.254, lease-time: 31536000]
Tue Dec 12 21:34:53 2017 Successful ARP Flush on interface [12] {734D00E0-401D-46F7-B1E7-420E4AB1DF67}
Tue Dec 12 21:34:53 2017 do_ifconfig, tt->did_ifconfig_ipv6_setup=0
Tue Dec 12 21:35:28 2017 Warning: route gateway is not reachable on any active network adapters: 172.16.0.1
Tue Dec 12 21:35:28 2017 env_block: add PATH=C:\WINDOWS\System32;C:\WINDOWS;C:\WINDOWS\System32\Wbem
Tue Dec 12 21:35:28 2017 Warning: route gateway is not reachable on any active network adapters: 172.16.0.1
Tue Dec 12 21:35:28 2017 env_block: add PATH=C:\WINDOWS\System32;C:\WINDOWS;C:\WINDOWS\System32\Wbem
SYSTEM ROUTING TABLE
0.0.0.0 0.0.0.0 10.0.0.1 p=0 i=37 t=4 pr=3 a=4252 h=0 m=25/0/0/0/0
0.0.0.0 0.0.0.0 25.0.0.1 p=0 i=6 t=4 pr=3 a=2213 h=0 m=9256/0/0/0/0
0.0.0.0 128.0.0.0 172.16.0.1 p=0 i=37 t=4 pr=3 a=0 h=0 m=26/0/0/0/0
10.0.0.0 255.255.255.0 10.0.0.17 p=0 i=37 t=3 pr=2 a=4252 h=0 m=281/0/0/0/0
10.0.0.17 255.255.255.255 10.0.0.17 p=0 i=37 t=3 pr=2 a=4252 h=0 m=281/0/0/0/0
10.0.0.255 255.255.255.255 10.0.0.17 p=0 i=37 t=3 pr=2 a=4252 h=0 m=281/0/0/0/0
25.0.0.0 255.0.0.0 25.68.1.73 p=0 i=6 t=3 pr=2 a=2212 h=0 m=9256/0/0/0/0
25.68.1.73 255.255.255.255 25.68.1.73 p=0 i=6 t=3 pr=2 a=2212 h=0 m=9256/0/0/0/0
25.255.255.255 255.255.255.255 25.68.1.73 p=0 i=6 t=3 pr=2 a=2212 h=0 m=9256/0/0/0/0
xx.xxx.xxx.xx 255.255.255.255 10.0.0.1 p=0 i=37 t=4 pr=3 a=0 h=0 m=25/0/0/0/0
127.0.0.0 255.0.0.0 127.0.0.1 p=0 i=1 t=3 pr=2 a=4271 h=0 m=331/0/0/0/0
127.0.0.1 255.255.255.255 127.0.0.1 p=0 i=1 t=3 pr=2 a=4271 h=0 m=331/0/0/0/0
127.255.255.255 255.255.255.255 127.0.0.1 p=0 i=1 t=3 pr=2 a=4271 h=0 m=331/0/0/0/0
128.0.0.0 128.0.0.0 172.16.0.1 p=0 i=37 t=4 pr=3 a=0 h=0 m=26/0/0/0/0
169.254.0.0 255.255.0.0 169.254.225.200 p=0 i=12 t=3 pr=2 a=281 h=0 m=291/0/0/0/0
169.254.225.200 255.255.255.255 169.254.225.200 p=0 i=12 t=3 pr=2 a=281 h=0 m=291/0/0/0/0
169.254.255.255 255.255.255.255 169.254.225.200 p=0 i=12 t=3 pr=2 a=281 h=0 m=291/0/0/0/0
224.0.0.0 240.0.0.0 127.0.0.1 p=0 i=1 t=3 pr=2 a=4271 h=0 m=331/0/0/0/0
224.0.0.0 240.0.0.0 10.0.0.17 p=0 i=37 t=3 pr=2 a=4259 h=0 m=281/0/0/0/0
224.0.0.0 240.0.0.0 25.68.1.73 p=0 i=6 t=3 pr=2 a=2213 h=0 m=9256/0/0/0/0
224.0.0.0 240.0.0.0 169.254.225.200 p=0 i=12 t=3 pr=2 a=378 h=0 m=291/0/0/0/0
255.255.255.255 255.255.255.255 127.0.0.1 p=0 i=1 t=3 pr=2 a=4271 h=0 m=331/0/0/0/0
255.255.255.255 255.255.255.255 10.0.0.17 p=0 i=37 t=3 pr=2 a=4259 h=0 m=281/0/0/0/0
255.255.255.255 255.255.255.255 25.68.1.73 p=0 i=6 t=3 pr=2 a=2213 h=0 m=9256/0/0/0/0
255.255.255.255 255.255.255.255 169.254.225.200 p=0 i=12 t=3 pr=2 a=378 h=0 m=291/0/0/0/0
SYSTEM ADAPTER LIST
Intel(R) 82579V Gigabit Network Connection
Index = 37
GUID = {EEFB3D55-B31A-4562-8806-BC209AC7BA0B}
IP = 10.0.0.17/255.255.255.0
MAC = 30:85:a9:b2:0f:c9
GATEWAY = 10.0.0.1/255.255.255.255
DHCP SERV = 10.0.0.1/255.255.255.255
DHCP LEASE OBTAINED = Tue Dec 12 17:26:49 2017
DHCP LEASE EXPIRES = Wed Dec 13 17:26:49 2017
DNS SERV = 10.0.0.1/255.255.255.255
LogMeIn Hamachi Virtual Ethernet Adapter
Index = 6
GUID = {35D2D616-5D13-422C-B8CC-0FC2AF19B0B2}
IP = 25.68.1.73/255.0.0.0
MAC = 7a:79:19:44:01:49
GATEWAY = 25.0.0.1/255.255.255.255
DHCP SERV = 25.0.0.1/255.255.255.255
DHCP LEASE OBTAINED = Tue Dec 12 18:00:49 2017
DHCP LEASE EXPIRES = Wed Dec 12 18:00:49 2018
DNS SERV =
TAP-Windows Adapter V9
Index = 12
GUID = {734D00E0-401D-46F7-B1E7-420E4AB1DF67}
IP = 169.254.225.200/255.255.0.0
MAC = 00:ff:73:4d:00:e0
GATEWAY = 0.0.0.0/255.255.255.255
DHCP SERV = 0.0.0.0/255.255.255.255
DHCP LEASE OBTAINED = Tue Dec 12 21:35:28 2017
DHCP LEASE EXPIRES = Tue Dec 12 21:35:28 2017
DNS SERV =
The Broadcom 802.11 Network Adapter provides wireless local area networking.
Index = 7
GUID = {3DA5EF78-91FA-4975-80D1-6A36270A3755}
IP = 0.0.0.0/0.0.0.0
MAC = dc:85:de:57:16:90
GATEWAY = 0.0.0.0/255.255.255.255
DHCP SERV =
DHCP LEASE OBTAINED = Tue Dec 12 21:35:28 2017
DHCP LEASE EXPIRES = Tue Dec 12 21:35:28 2017
DNS SERV =
Microsoft Hosted Network Virtual Adapter
Index = 14
GUID = {5CF15D9A-01CB-491A-8ACB-1DBE80F45FAB}
IP = 0.0.0.0/0.0.0.0
MAC = dc:85:de:57:16:90
GATEWAY = 0.0.0.0/255.255.255.255
DHCP SERV =
DHCP LEASE OBTAINED = Tue Dec 12 21:35:28 2017
DHCP LEASE EXPIRES = Tue Dec 12 21:35:28 2017
DNS SERV =
Microsoft Wi-Fi Direct Virtual Adapter
Index = 26
GUID = {C5DC4ADC-C746-4A0D-98D1-0F604C1DD5F3}
IP = 0.0.0.0/0.0.0.0
MAC = de:85:de:57:16:90
GATEWAY = 0.0.0.0/255.255.255.255
DHCP SERV =
DHCP LEASE OBTAINED = Tue Dec 12 21:35:28 2017
DHCP LEASE EXPIRES = Tue Dec 12 21:35:28 2017
DNS SERV =
Tue Dec 12 21:35:28 2017 Initialization Sequence Completed With Errors ( see http://openvpn.net/faq.html#dhcpclientserv )

I had this working on my old setup just fine. But now it only works first time.

These are the configs:
http://prntscr.com/hmnk7h
http://prntscr.com/hmnkdi
http://prntscr.com/hmnkmp
http://prntscr.com/hmnkqe

So when the openVPN client is just yellow, I see this in pfsense:
http://prntscr.com/hmnmlb

So it has established some kind of connection. However, I cannot ping PFsense nor anything else.

I would be so happy if someone would lead me a way. I read a other post about this saying something about IP’s, but I am unsure what should be wrong here….

Rules on WAN: http://prntscr.com/hmnn8d

The OpenVPN rule is also added.

Источник

! 2019.04.06 18:16:46 — Connecting to Saiph (Canada, Toronto, Ontario)
. 2019.04.06 18:16:47 — OpenVPN > OpenVPN 2.4.6 x86_64-w64-mingw32 [sSL (OpenSSL)] [LZO] [LZ4] [PKCS11] [AEAD] built on Apr 27 2018
. 2019.04.06 18:16:47 — OpenVPN > Windows version 6.2 (Windows 8 or greater) 64bit
. 2019.04.06 18:16:47 — OpenVPN > library versions: OpenSSL 1.1.0h 27 Mar 2018, LZO 2.10
. 2019.04.06 18:16:47 — Connection to OpenVPN Management Interface
. 2019.04.06 18:16:47 — OpenVPN > MANAGEMENT: TCP Socket listening on [AF_INET]127.0.0.1:3100
. 2019.04.06 18:16:47 — OpenVPN > Outgoing Control Channel Encryption: Cipher ‘AES-256-CTR’ initialized with 256 bit key
. 2019.04.06 18:16:47 — OpenVPN > Outgoing Control Channel Encryption: Using 256 bit message hash ‘SHA256’ for HMAC authentication
. 2019.04.06 18:16:47 — OpenVPN > Incoming Control Channel Encryption: Cipher ‘AES-256-CTR’ initialized with 256 bit key
. 2019.04.06 18:16:47 — OpenVPN > Incoming Control Channel Encryption: Using 256 bit message hash ‘SHA256’ for HMAC authentication
. 2019.04.06 18:16:47 — OpenVPN > TCP/UDP: Preserving recently used remote address: [AF_INET]184.75.223.229:443
. 2019.04.06 18:16:47 — OpenVPN > Socket Buffers: R=[65536->262144] S=[65536->262144]
. 2019.04.06 18:16:47 — OpenVPN > UDP link local: (not bound)
. 2019.04.06 18:16:47 — OpenVPN > UDP link remote: [AF_INET]184.75.223.229:443
. 2019.04.06 18:16:47 — OpenVPN > TLS: Initial packet from [AF_INET]184.75.223.229:443, sid=65964aab 45f42e76
. 2019.04.06 18:16:47 — OpenVPN > MANAGEMENT: Client connected from [AF_INET]127.0.0.1:3100
. 2019.04.06 18:16:47 — OpenVPN > VERIFY OK: depth=1, C=IT, ST=IT, L=Perugia, O=airvpn.org, CN=airvpn.org CA, emailAddress=info@airvpn.org
. 2019.04.06 18:16:47 — OpenVPN > VERIFY KU OK
. 2019.04.06 18:16:47 — OpenVPN > Validating certificate extended key usage
. 2019.04.06 18:16:47 — OpenVPN > ++ Certificate has EKU (str) TLS Web Server Authentication, expects TLS Web Server Authentication
. 2019.04.06 18:16:47 — OpenVPN > VERIFY EKU OK
. 2019.04.06 18:16:47 — OpenVPN > VERIFY OK: depth=0, C=IT, ST=IT, L=Perugia, O=airvpn.org, CN=Saiph, emailAddress=info@airvpn.org
. 2019.04.06 18:16:47 — OpenVPN > Control Channel: TLSv1.2, cipher TLSv1.2 DHE-RSA-AES256-GCM-SHA384, 4096 bit RSA
. 2019.04.06 18:16:47 — OpenVPN > [saiph] Peer Connection Initiated with [AF_INET]184.75.223.229:443
. 2019.04.06 18:16:48 — OpenVPN > SENT CONTROL [saiph]: ‘PUSH_REQUEST’ (status=1)
. 2019.04.06 18:16:48 — OpenVPN > PUSH: Received control message: ‘PUSH_REPLY,comp-lzo no,redirect-gateway ipv6 def1 bypass-dhcp,dhcp-option DNS 10.28.250.1,dhcp-option DNS6 fde6:7a:7d20:18fa::1,tun-ipv6,route-gateway 10.28.250.1,topology subnet,ping 10,ping-restart 60,ifconfig-ipv6 fde6:7a:7d20:18fa::10a9/64 fde6:7a:7d20:18fa::1,ifconfig 10.28.250.171 255.255.255.0,peer-id 1,cipher AES-256-GCM’
. 2019.04.06 18:16:48 — OpenVPN > Pushed option removed by filter: ‘redirect-gateway ipv6 def1 bypass-dhcp’
. 2019.04.06 18:16:48 — OpenVPN > OPTIONS IMPORT: timers and/or timeouts modified
. 2019.04.06 18:16:48 — OpenVPN > OPTIONS IMPORT: compression parms modified
. 2019.04.06 18:16:48 — OpenVPN > OPTIONS IMPORT: —ifconfig/up options modified
. 2019.04.06 18:16:48 — OpenVPN > OPTIONS IMPORT: route-related options modified
. 2019.04.06 18:16:48 — OpenVPN > OPTIONS IMPORT: —ip-win32 and/or —dhcp-option options modified
. 2019.04.06 18:16:48 — OpenVPN > OPTIONS IMPORT: peer-id set
. 2019.04.06 18:16:48 — OpenVPN > OPTIONS IMPORT: adjusting link_mtu to 1625
. 2019.04.06 18:16:48 — OpenVPN > OPTIONS IMPORT: data channel crypto options modified
. 2019.04.06 18:16:48 — OpenVPN > Data Channel: using negotiated cipher ‘AES-256-GCM’
. 2019.04.06 18:16:48 — OpenVPN > Outgoing Data Channel: Cipher ‘AES-256-GCM’ initialized with 256 bit key
. 2019.04.06 18:16:48 — OpenVPN > Incoming Data Channel: Cipher ‘AES-256-GCM’ initialized with 256 bit key
. 2019.04.06 18:16:48 — OpenVPN > interactive service msg_channel=0
. 2019.04.06 18:16:48 — OpenVPN > ROUTE_GATEWAY 192.168.0.1/255.255.255.0 I=13 HWADDR=5c:f9:dd:78:0e:aa
. 2019.04.06 18:16:48 — OpenVPN > GDG6: remote_host_ipv6=n/a
. 2019.04.06 18:16:48 — OpenVPN > GetBestInterfaceEx() returned if=13
. 2019.04.06 18:16:48 — OpenVPN > GDG6: II=13 DP=::/0 NH=fe80::d604:cdff:fe87:a51f
. 2019.04.06 18:16:48 — OpenVPN > GDG6: Metric=256, Loopback=0, AA=1, I=0
. 2019.04.06 18:16:48 — OpenVPN > ROUTE6_GATEWAY fe80::d604:cdff:fe87:a51f I=13
. 2019.04.06 18:16:48 — OpenVPN > open_tun
. 2019.04.06 18:16:48 — OpenVPN > TAP-WIN32 device [Ethernet 2] opened: \\.\Global\{0ABEC94F-76D1-4CE9-89E7-E1810E356D0E}.tap
. 2019.04.06 18:16:48 — OpenVPN > TAP-Windows Driver Version 9.21
. 2019.04.06 18:16:48 — OpenVPN > Set TAP-Windows TUN subnet mode network/local/netmask = 10.28.250.0/10.28.250.171/255.255.255.0 [sUCCEEDED]
. 2019.04.06 18:16:48 — OpenVPN > Notified TAP-Windows driver to set a DHCP IP/netmask of 10.28.250.171/255.255.255.0 on interface {0ABEC94F-76D1-4CE9-89E7-E1810E356D0E} [DHCP-serv: 10.28.250.254, lease-time: 31536000]
. 2019.04.06 18:16:48 — OpenVPN > Successful ARP Flush on interface [2] {0ABEC94F-76D1-4CE9-89E7-E1810E356D0E}
. 2019.04.06 18:16:48 — OpenVPN > do_ifconfig, tt->did_ifconfig_ipv6_setup=1
. 2019.04.06 18:16:49 — OpenVPN > NETSH: C:\WINDOWS\system32\netsh.exe interface ipv6 set address interface=2 fde6:7a:7d20:18fa::10a9 store=active
. 2019.04.06 18:16:50 — OpenVPN > NETSH: C:\WINDOWS\system32\netsh.exe interface ipv6 set dns Ethernet 2 static fde6:7a:7d20:18fa::1 validate=no
. 2019.04.06 18:16:50 — Detected an OpenVPN bug (On-Link route on VPN range), autofix.
. 2019.04.06 18:16:50 — OpenVPN > add_route_ipv6(fde6:7a:7d20:18fa::/64 -> fde6:7a:7d20:18fa::10a9 metric 0) dev Ethernet 2
. 2019.04.06 18:16:50 — OpenVPN > C:\WINDOWS\system32\netsh.exe interface ipv6 add route fde6:7a:7d20:18fa::/64 interface=2 fe80::8 store=active
. 2019.04.06 18:16:50 — OpenVPN > env_block: add PATH=C:\WINDOWS\System32;C:\WINDOWS;C:\WINDOWS\System32\Wbem
. 2019.04.06 18:16:55 — OpenVPN > TEST ROUTES: 0/0 succeeded len=-1 ret=0 a=0 u/d=down
. 2019.04.06 18:16:55 — OpenVPN > Route: Waiting for TUN/TAP interface to come up…
. 2019.04.06 18:16:55 — Eddie Windows Interface Hack executed (Ethernet 2)
. 2019.04.06 18:17:00 — OpenVPN > TEST ROUTES: 0/0 succeeded len=-1 ret=0 a=0 u/d=down
. 2019.04.06 18:17:00 — OpenVPN > Route: Waiting for TUN/TAP interface to come up…
. 2019.04.06 18:17:00 — Eddie Windows Interface Hack executed (Ethernet 2)
. 2019.04.06 18:17:01 — OpenVPN > TEST ROUTES: 0/0 succeeded len=-1 ret=0 a=0 u/d=down
. 2019.04.06 18:17:01 — OpenVPN > Route: Waiting for TUN/TAP interface to come up…
. 2019.04.06 18:17:01 — Eddie Windows Interface Hack executed (Ethernet 2)
. 2019.04.06 18:17:02 — OpenVPN > TEST ROUTES: 0/0 succeeded len=-1 ret=0 a=0 u/d=down
. 2019.04.06 18:17:02 — OpenVPN > Route: Waiting for TUN/TAP interface to come up…
. 2019.04.06 18:17:02 — Eddie Windows Interface Hack executed (Ethernet 2)
. 2019.04.06 18:17:03 — OpenVPN > TEST ROUTES: 0/0 succeeded len=-1 ret=0 a=0 u/d=down
. 2019.04.06 18:17:03 — OpenVPN > Route: Waiting for TUN/TAP interface to come up…
. 2019.04.06 18:17:03 — Eddie Windows Interface Hack executed (Ethernet 2)
. 2019.04.06 18:17:04 — OpenVPN > TEST ROUTES: 0/0 succeeded len=-1 ret=0 a=0 u/d=down
. 2019.04.06 18:17:04 — OpenVPN > Route: Waiting for TUN/TAP interface to come up…
. 2019.04.06 18:17:04 — Eddie Windows Interface Hack executed (Ethernet 2)
. 2019.04.06 18:17:05 — OpenVPN > TEST ROUTES: 0/0 succeeded len=-1 ret=0 a=0 u/d=down
. 2019.04.06 18:17:05 — OpenVPN > Route: Waiting for TUN/TAP interface to come up…
. 2019.04.06 18:17:05 — Eddie Windows Interface Hack executed (Ethernet 2)
. 2019.04.06 18:17:06 — OpenVPN > TEST ROUTES: 0/0 succeeded len=-1 ret=0 a=0 u/d=down
. 2019.04.06 18:17:06 — OpenVPN > Route: Waiting for TUN/TAP interface to come up…
. 2019.04.06 18:17:06 — Eddie Windows Interface Hack executed (Ethernet 2)
. 2019.04.06 18:17:07 — OpenVPN > TEST ROUTES: 0/0 succeeded len=-1 ret=0 a=0 u/d=down
. 2019.04.06 18:17:07 — OpenVPN > Route: Waiting for TUN/TAP interface to come up…
. 2019.04.06 18:17:07 — Eddie Windows Interface Hack executed (Ethernet 2)
. 2019.04.06 18:17:09 — OpenVPN > TEST ROUTES: 0/0 succeeded len=-1 ret=0 a=0 u/d=down
. 2019.04.06 18:17:09 — OpenVPN > Route: Waiting for TUN/TAP interface to come up…
. 2019.04.06 18:17:09 — Eddie Windows Interface Hack executed (Ethernet 2)
. 2019.04.06 18:17:10 — OpenVPN > TEST ROUTES: 0/0 succeeded len=-1 ret=0 a=0 u/d=down
. 2019.04.06 18:17:10 — OpenVPN > Route: Waiting for TUN/TAP interface to come up…
. 2019.04.06 18:17:10 — Eddie Windows Interface Hack executed (Ethernet 2)
. 2019.04.06 18:17:11 — OpenVPN > TEST ROUTES: 0/0 succeeded len=-1 ret=0 a=0 u/d=down
. 2019.04.06 18:17:11 — OpenVPN > Route: Waiting for TUN/TAP interface to come up…
. 2019.04.06 18:17:11 — Eddie Windows Interface Hack executed (Ethernet 2)
. 2019.04.06 18:17:12 — OpenVPN > TEST ROUTES: 0/0 succeeded len=-1 ret=0 a=0 u/d=down
. 2019.04.06 18:17:12 — OpenVPN > Route: Waiting for TUN/TAP interface to come up…
. 2019.04.06 18:17:12 — Eddie Windows Interface Hack executed (Ethernet 2)
. 2019.04.06 18:17:13 — OpenVPN > TEST ROUTES: 0/0 succeeded len=-1 ret=0 a=0 u/d=down
. 2019.04.06 18:17:13 — OpenVPN > Route: Waiting for TUN/TAP interface to come up…
. 2019.04.06 18:17:13 — Eddie Windows Interface Hack executed (Ethernet 2)
. 2019.04.06 18:17:14 — OpenVPN > TEST ROUTES: 0/0 succeeded len=-1 ret=0 a=0 u/d=down
. 2019.04.06 18:17:14 — OpenVPN > Route: Waiting for TUN/TAP interface to come up…
. 2019.04.06 18:17:14 — Eddie Windows Interface Hack executed (Ethernet 2)
. 2019.04.06 18:17:16 — OpenVPN > TEST ROUTES: 0/0 succeeded len=-1 ret=0 a=0 u/d=down
. 2019.04.06 18:17:16 — OpenVPN > Route: Waiting for TUN/TAP interface to come up…
. 2019.04.06 18:17:16 — Eddie Windows Interface Hack executed (Ethernet 2)
. 2019.04.06 18:17:17 — OpenVPN > TEST ROUTES: 0/0 succeeded len=-1 ret=0 a=0 u/d=down
. 2019.04.06 18:17:17 — OpenVPN > Route: Waiting for TUN/TAP interface to come up…
. 2019.04.06 18:17:17 — Eddie Windows Interface Hack executed (Ethernet 2)
. 2019.04.06 18:17:18 — OpenVPN > TEST ROUTES: 0/0 succeeded len=-1 ret=0 a=0 u/d=down
. 2019.04.06 18:17:18 — OpenVPN > Route: Waiting for TUN/TAP interface to come up…
. 2019.04.06 18:17:18 — Eddie Windows Interface Hack executed (Ethernet 2)
. 2019.04.06 18:17:19 — OpenVPN > TEST ROUTES: 0/0 succeeded len=-1 ret=0 a=0 u/d=down
. 2019.04.06 18:17:19 — OpenVPN > Route: Waiting for TUN/TAP interface to come up…
. 2019.04.06 18:17:19 — Eddie Windows Interface Hack executed (Ethernet 2)
. 2019.04.06 18:17:20 — OpenVPN > TEST ROUTES: 0/0 succeeded len=-1 ret=0 a=0 u/d=down
. 2019.04.06 18:17:20 — OpenVPN > Route: Waiting for TUN/TAP interface to come up…
. 2019.04.06 18:17:20 — Eddie Windows Interface Hack executed (Ethernet 2)
. 2019.04.06 18:17:21 — OpenVPN > TEST ROUTES: 0/0 succeeded len=-1 ret=0 a=0 u/d=down
. 2019.04.06 18:17:21 — OpenVPN > Route: Waiting for TUN/TAP interface to come up…
. 2019.04.06 18:17:21 — Eddie Windows Interface Hack executed (Ethernet 2)
. 2019.04.06 18:17:22 — OpenVPN > TEST ROUTES: 0/0 succeeded len=-1 ret=0 a=0 u/d=down
. 2019.04.06 18:17:22 — OpenVPN > Route: Waiting for TUN/TAP interface to come up…
. 2019.04.06 18:17:22 — Eddie Windows Interface Hack executed (Ethernet 2)
. 2019.04.06 18:17:23 — OpenVPN > TEST ROUTES: 0/0 succeeded len=-1 ret=0 a=0 u/d=down
. 2019.04.06 18:17:23 — OpenVPN > Route: Waiting for TUN/TAP interface to come up…
. 2019.04.06 18:17:23 — Eddie Windows Interface Hack executed (Ethernet 2)
. 2019.04.06 18:17:24 — OpenVPN > TEST ROUTES: 0/0 succeeded len=-1 ret=0 a=0 u/d=down
. 2019.04.06 18:17:24 — OpenVPN > Route: Waiting for TUN/TAP interface to come up…
. 2019.04.06 18:17:24 — Eddie Windows Interface Hack executed (Ethernet 2)
. 2019.04.06 18:17:25 — OpenVPN > TEST ROUTES: 0/0 succeeded len=-1 ret=0 a=0 u/d=down
. 2019.04.06 18:17:25 — OpenVPN > C:\WINDOWS\system32\route.exe ADD 184.75.223.229 MASK 255.255.255.255 192.168.0.1
. 2019.04.06 18:17:25 — OpenVPN > ROUTE: CreateIpForwardEntry succeeded with dwForwardMetric1=25 and dwForwardType=4
. 2019.04.06 18:17:25 — OpenVPN > Route addition via IPAPI succeeded [adaptive]
. 2019.04.06 18:17:25 — OpenVPN > C:\WINDOWS\system32\route.exe ADD 0.0.0.0 MASK 128.0.0.0 10.28.250.1
W 2019.04.06 18:17:25 — OpenVPN > Warning: route gateway is not reachable on any active network adapters: 10.28.250.1
. 2019.04.06 18:17:25 — OpenVPN > Route addition via IPAPI failed [adaptive]
. 2019.04.06 18:17:25 — OpenVPN > Route addition fallback to route.exe
. 2019.04.06 18:17:25 — OpenVPN > env_block: add PATH=C:\WINDOWS\System32;C:\WINDOWS;C:\WINDOWS\System32\Wbem
. 2019.04.06 18:17:25 — OpenVPN > C:\WINDOWS\system32\route.exe ADD 128.0.0.0 MASK 128.0.0.0 10.28.250.1
W 2019.04.06 18:17:25 — OpenVPN > Warning: route gateway is not reachable on any active network adapters: 10.28.250.1
. 2019.04.06 18:17:25 — OpenVPN > Route addition via IPAPI failed [adaptive]
. 2019.04.06 18:17:25 — OpenVPN > Route addition fallback to route.exe
. 2019.04.06 18:17:25 — OpenVPN > env_block: add PATH=C:\WINDOWS\System32;C:\WINDOWS;C:\WINDOWS\System32\Wbem
. 2019.04.06 18:17:25 — OpenVPN > add_route_ipv6(::/3 -> fde6:7a:7d20:18fa::1 metric -1) dev Ethernet 2
. 2019.04.06 18:17:25 — OpenVPN > C:\WINDOWS\system32\netsh.exe interface ipv6 add route ::/3 interface=2 fe80::8 store=active
. 2019.04.06 18:17:25 — OpenVPN > env_block: add PATH=C:\WINDOWS\System32;C:\WINDOWS;C:\WINDOWS\System32\Wbem
. 2019.04.06 18:17:25 — OpenVPN > add_route_ipv6(2000::/4 -> fde6:7a:7d20:18fa::1 metric -1) dev Ethernet 2
. 2019.04.06 18:17:25 — OpenVPN > C:\WINDOWS\system32\netsh.exe interface ipv6 add route 2000::/4 interface=2 fe80::8 store=active
. 2019.04.06 18:17:25 — OpenVPN > env_block: add PATH=C:\WINDOWS\System32;C:\WINDOWS;C:\WINDOWS\System32\Wbem
. 2019.04.06 18:17:25 — OpenVPN > add_route_ipv6(3000::/4 -> fde6:7a:7d20:18fa::1 metric -1) dev Ethernet 2
. 2019.04.06 18:17:25 — OpenVPN > C:\WINDOWS\system32\netsh.exe interface ipv6 add route 3000::/4 interface=2 fe80::8 store=active
. 2019.04.06 18:17:25 — OpenVPN > env_block: add PATH=C:\WINDOWS\System32;C:\WINDOWS;C:\WINDOWS\System32\Wbem
. 2019.04.06 18:17:25 — OpenVPN > add_route_ipv6(fc00::/7 -> fde6:7a:7d20:18fa::1 metric -1) dev Ethernet 2
. 2019.04.06 18:17:25 — OpenVPN > C:\WINDOWS\system32\netsh.exe interface ipv6 add route fc00::/7 interface=2 fe80::8 store=active
. 2019.04.06 18:17:25 — OpenVPN > env_block: add PATH=C:\WINDOWS\System32;C:\WINDOWS;C:\WINDOWS\System32\Wbem
. 2019.04.06 18:17:25 — OpenVPN > SYSTEM ROUTING TABLE
. 2019.04.06 18:17:25 — OpenVPN > 0.0.0.0 0.0.0.0 192.168.0.1 p=0 i=13 t=4 pr=3 a=3938 h=0 m=25/0/0/0/0
. 2019.04.06 18:17:25 — OpenVPN > 0.0.0.0 128.0.0.0 10.28.250.1 p=0 i=13 t=4 pr=3 a=0 h=0 m=26/0/0/0/0
. 2019.04.06 18:17:25 — OpenVPN > 127.0.0.0 255.0.0.0 127.0.0.1 p=0 i=1 t=3 pr=2 a=3974 h=0 m=331/0/0/0/0
. 2019.04.06 18:17:25 — OpenVPN > 127.0.0.1 255.255.255.255 127.0.0.1 p=0 i=1 t=3 pr=2 a=3974 h=0 m=331/0/0/0/0
. 2019.04.06 18:17:25 — OpenVPN > 127.255.255.255 255.255.255.255 127.0.0.1 p=0 i=1 t=3 pr=2 a=3974 h=0 m=331/0/0/0/0
. 2019.04.06 18:17:25 — OpenVPN > 128.0.0.0 128.0.0.0 10.28.250.1 p=0 i=13 t=4 pr=3 a=0 h=0 m=26/0/0/0/0
. 2019.04.06 18:17:25 — OpenVPN > 169.254.0.0 255.255.0.0 169.254.126.104 p=0 i=2 t=3 pr=2 a=27 h=0 m=291/0/0/0/0
. 2019.04.06 18:17:25 — OpenVPN > 169.254.126.104 255.255.255.255 169.254.126.104 p=0 i=2 t=3 pr=2 a=27 h=0 m=291/0/0/0/0
. 2019.04.06 18:17:25 — OpenVPN > 169.254.255.255 255.255.255.255 169.254.126.104 p=0 i=2 t=3 pr=2 a=27 h=0 m=291/0/0/0/0
. 2019.04.06 18:17:25 — OpenVPN > 184.75.223.229 255.255.255.255 192.168.0.1 p=0 i=13 t=4 pr=3 a=0 h=0 m=25/0/0/0/0
. 2019.04.06 18:17:25 — OpenVPN > 192.168.0.0 255.255.255.0 192.168.0.3 p=0 i=13 t=3 pr=2 a=3938 h=0 m=281/0/0/0/0
. 2019.04.06 18:17:25 — OpenVPN > 192.168.0.3 255.255.255.255 192.168.0.3 p=0 i=13 t=3 pr=2 a=3938 h=0 m=281/0/0/0/0
. 2019.04.06 18:17:25 — OpenVPN > 192.168.0.255 255.255.255.255 192.168.0.3 p=0 i=13 t=3 pr=2 a=3938 h=0 m=281/0/0/0/0
. 2019.04.06 18:17:25 — OpenVPN > 224.0.0.0 240.0.0.0 127.0.0.1 p=0 i=1 t=3 pr=2 a=3974 h=0 m=331/0/0/0/0
. 2019.04.06 18:17:25 — OpenVPN > 224.0.0.0 240.0.0.0 192.168.0.3 p=0 i=13 t=3 pr=2 a=3965 h=0 m=281/0/0/0/0
. 2019.04.06 18:17:25 — OpenVPN > 224.0.0.0 240.0.0.0 169.254.126.104 p=0 i=2 t=3 pr=2 a=42 h=0 m=291/0/0/0/0
. 2019.04.06 18:17:25 — OpenVPN > 255.255.255.255 255.255.255.255 127.0.0.1 p=0 i=1 t=3 pr=2 a=3974 h=0 m=331/0/0/0/0
. 2019.04.06 18:17:25 — OpenVPN > 255.255.255.255 255.255.255.255 192.168.0.3 p=0 i=13 t=3 pr=2 a=3965 h=0 m=281/0/0/0/0
. 2019.04.06 18:17:25 — OpenVPN > 255.255.255.255 255.255.255.255 169.254.126.104 p=0 i=2 t=3 pr=2 a=42 h=0 m=291/0/0/0/0
. 2019.04.06 18:17:25 — OpenVPN > SYSTEM ADAPTER LIST
. 2019.04.06 18:17:25 — OpenVPN > Intel® 82579LM Gigabit Network Connection
. 2019.04.06 18:17:25 — OpenVPN > Index = 13
. 2019.04.06 18:17:25 — OpenVPN > GUID = {9F88DA24-A3A0-451D-BABB-347F27563B6F}
. 2019.04.06 18:17:25 — OpenVPN > IP = 192.168.0.3/255.255.255.0
. 2019.04.06 18:17:25 — OpenVPN > MAC = 5c:f9:dd:78:0e:aa
. 2019.04.06 18:17:25 — OpenVPN > GATEWAY = 192.168.0.1/255.255.255.255
. 2019.04.06 18:17:25 — OpenVPN > DHCP SERV = 192.168.0.1/255.255.255.255
. 2019.04.06 18:17:25 — OpenVPN > DHCP LEASE OBTAINED = Sat Apr 06 18:11:49 2019
. 2019.04.06 18:17:25 — OpenVPN > DHCP LEASE EXPIRES = Sat Apr 06 19:11:49 2019
. 2019.04.06 18:17:25 — OpenVPN > DNS SERV = 75.75.75.75/255.255.255.255 75.75.76.76/255.255.255.255
. 2019.04.06 18:17:25 — OpenVPN > TAP-Windows Adapter V9
. 2019.04.06 18:17:25 — OpenVPN > Index = 2
. 2019.04.06 18:17:25 — OpenVPN > GUID = {0ABEC94F-76D1-4CE9-89E7-E1810E356D0E}
. 2019.04.06 18:17:25 — OpenVPN > IP = 169.254.126.104/255.255.0.0
. 2019.04.06 18:17:25 — OpenVPN > MAC = 00:ff:0a:be:c9:4f
. 2019.04.06 18:17:25 — OpenVPN > GATEWAY = 0.0.0.0/255.255.255.255
. 2019.04.06 18:17:25 — OpenVPN > DHCP SERV = 0.0.0.0/255.255.255.255
. 2019.04.06 18:17:25 — OpenVPN > DHCP LEASE OBTAINED = Sat Apr 06 18:17:25 2019
. 2019.04.06 18:17:25 — OpenVPN > DHCP LEASE EXPIRES = Sat Apr 06 18:17:25 2019
. 2019.04.06 18:17:25 — OpenVPN > DNS SERV =
. 2019.04.06 18:17:25 — Interface Ethernet 2 metric changed from Automatic to 3, layer IPv4
. 2019.04.06 18:17:25 — Interface Ethernet 2 metric changed from Automatic to 3, layer IPv6
. 2019.04.06 18:17:25 — DNS leak protection with packet filtering enabled.
. 2019.04.06 18:17:25 — DNS IPv4 of a network adapter forced (Ethernet 2, from automatic to 10.28.250.1)
. 2019.04.06 18:17:26 — DNS IPv6 of a network adapter forced (Ethernet 2, from automatic to fde6:7a:7d20:18fa::1)
. 2019.04.06 18:17:26 — Routes, added a new route, 184.75.223.227 for gateway 10.28.250.1
. 2019.04.06 18:17:26 — Routes, added a new route, 2606:6080:1002:8:3285:30e:de43:8809 for gateway fde6:7a:7d20:18fa::1
. 2019.04.06 18:17:26 — Flushing DNS
. 2019.04.06 18:17:29 — OpenVPN > Initialization Sequence Completed With Errors ( see http://openvpn.net/faq.html#dhcpclientserv )
! 2019.04.06 18:17:29 — Disconnecting
. 2019.04.06 18:17:29 — Routes, removed a route previously added, 184.75.223.227 for gateway 10.28.250.1
. 2019.04.06 18:17:29 — Routes, removed a route previously added, 2606:6080:1002:8:3285:30e:de43:8809 for gateway fde6:7a:7d20:18fa::1
. 2019.04.06 18:17:29 — Sending management termination signal
. 2019.04.06 18:17:29 — Management — Send ‘signal SIGTERM’
. 2019.04.06 18:17:29 — OpenVPN > MANAGEMENT: CMD ‘fa6411d08179b2cebc78131df3991136752ecf242f836fcbdb2110ec6288bb0a’
. 2019.04.06 18:17:39 — Sending management termination signal
. 2019.04.06 18:17:39 — Management — Send ‘signal SIGTERM’
. 2019.04.06 18:17:39 — OpenVPN > MANAGEMENT: CMD ‘signal SIGTERM’
. 2019.04.06 18:17:39 — OpenVPN > SIGTERM received, sending exit notification to peer
. 2019.04.06 18:17:44 — OpenVPN > C:\WINDOWS\system32\route.exe DELETE 184.75.223.229 MASK 255.255.255.255 192.168.0.1
. 2019.04.06 18:17:44 — OpenVPN > Route deletion via IPAPI succeeded [adaptive]
. 2019.04.06 18:17:44 — OpenVPN > C:\WINDOWS\system32\route.exe DELETE 0.0.0.0 MASK 128.0.0.0 10.28.250.1
W 2019.04.06 18:17:44 — OpenVPN > Warning: route gateway is not reachable on any active network adapters: 10.28.250.1
. 2019.04.06 18:17:44 — OpenVPN > Route deletion via IPAPI failed [adaptive]
. 2019.04.06 18:17:44 — OpenVPN > Route deletion fallback to route.exe
. 2019.04.06 18:17:44 — OpenVPN > env_block: add PATH=C:\WINDOWS\System32;C:\WINDOWS;C:\WINDOWS\System32\Wbem
. 2019.04.06 18:17:44 — OpenVPN > C:\WINDOWS\system32\route.exe DELETE 128.0.0.0 MASK 128.0.0.0 10.28.250.1
W 2019.04.06 18:17:44 — OpenVPN > Warning: route gateway is not reachable on any active network adapters: 10.28.250.1
. 2019.04.06 18:17:44 — OpenVPN > Route deletion via IPAPI failed [adaptive]
. 2019.04.06 18:17:44 — OpenVPN > Route deletion fallback to route.exe
. 2019.04.06 18:17:44 — OpenVPN > env_block: add PATH=C:\WINDOWS\System32;C:\WINDOWS;C:\WINDOWS\System32\Wbem
. 2019.04.06 18:17:44 — OpenVPN > delete_route_ipv6(::/3)
. 2019.04.06 18:17:44 — OpenVPN > C:\WINDOWS\system32\netsh.exe interface ipv6 delete route ::/3 interface=2 fe80::8 store=active
. 2019.04.06 18:17:44 — OpenVPN > env_block: add PATH=C:\WINDOWS\System32;C:\WINDOWS;C:\WINDOWS\System32\Wbem
. 2019.04.06 18:17:44 — OpenVPN > delete_route_ipv6(2000::/4)
. 2019.04.06 18:17:44 — OpenVPN > C:\WINDOWS\system32\netsh.exe interface ipv6 delete route 2000::/4 interface=2 fe80::8 store=active
. 2019.04.06 18:17:44 — OpenVPN > env_block: add PATH=C:\WINDOWS\System32;C:\WINDOWS;C:\WINDOWS\System32\Wbem
. 2019.04.06 18:17:44 — OpenVPN > delete_route_ipv6(3000::/4)
. 2019.04.06 18:17:44 — OpenVPN > C:\WINDOWS\system32\netsh.exe interface ipv6 delete route 3000::/4 interface=2 fe80::8 store=active
. 2019.04.06 18:17:44 — OpenVPN > env_block: add PATH=C:\WINDOWS\System32;C:\WINDOWS;C:\WINDOWS\System32\Wbem
. 2019.04.06 18:17:44 — OpenVPN > delete_route_ipv6(fc00::/7)
. 2019.04.06 18:17:44 — OpenVPN > C:\WINDOWS\system32\netsh.exe interface ipv6 delete route fc00::/7 interface=2 fe80::8 store=active
. 2019.04.06 18:17:44 — OpenVPN > env_block: add PATH=C:\WINDOWS\System32;C:\WINDOWS;C:\WINDOWS\System32\Wbem
. 2019.04.06 18:17:44 — OpenVPN > Closing TUN/TAP interface
. 2019.04.06 18:17:44 — OpenVPN > delete_route_ipv6(fde6:7a:7d20:18fa::/64)
. 2019.04.06 18:17:44 — OpenVPN > C:\WINDOWS\system32\netsh.exe interface ipv6 delete route fde6:7a:7d20:18fa::/64 interface=2 fe80::8 store=active
. 2019.04.06 18:17:44 — OpenVPN > NETSH: C:\WINDOWS\system32\netsh.exe interface ipv6 delete address Ethernet 2 fde6:7a:7d20:18fa::10a9 store=active
. 2019.04.06 18:17:44 — OpenVPN > NETSH: C:\WINDOWS\system32\netsh.exe interface ipv6 delete dns Ethernet 2 all
. 2019.04.06 18:17:44 — OpenVPN > NOTE: Release of DHCP-assigned IP address lease on TAP-Windows adapter failed: An address has not yet been associated with the network endpoint. (code=1228)
. 2019.04.06 18:17:44 — OpenVPN > SIGTERM[soft,exit-with-notification] received, process exiting
. 2019.04.06 18:17:44 — Connection terminated.
. 2019.04.06 18:17:45 — DNS IPv4 of a network adapter restored to original settings (Ethernet 2, to automatic)
. 2019.04.06 18:17:45 — DNS IPv6 of a network adapter restored to original settings (Ethernet 2, to automatic)
. 2019.04.06 18:17:45 — DNS leak protection with packet filtering disabled.
. 2019.04.06 18:17:45 — Interface Ethernet 2 metric restored from 3 to Automatic, layer IPv4
. 2019.04.06 18:17:45 — Interface Ethernet 2 metric restored from 3 to Automatic, layer IPv6
I 2019.04.06 18:17:48 — Checking authorization …
! 2019.04.06 18:17:48 — Connecting to Sadalbari (Canada, Toronto, Ontario)
. 2019.04.06 18:17:48 — OpenVPN > OpenVPN 2.4.6 x86_64-w64-mingw32 [sSL (OpenSSL)] [LZO] [LZ4] [PKCS11] [AEAD] built on Apr 27 2018
. 2019.04.06 18:17:48 — OpenVPN > Windows version 6.2 (Windows 8 or greater) 64bit
. 2019.04.06 18:17:48 — OpenVPN > library versions: OpenSSL 1.1.0h 27 Mar 2018, LZO 2.10
. 2019.04.06 18:17:48 — Connection to OpenVPN Management Interface
. 2019.04.06 18:17:48 — OpenVPN > MANAGEMENT: TCP Socket listening on [AF_INET]127.0.0.1:3100
. 2019.04.06 18:17:48 — OpenVPN > Outgoing Control Channel Encryption: Cipher ‘AES-256-CTR’ initialized with 256 bit key
. 2019.04.06 18:17:48 — OpenVPN > Outgoing Control Channel Encryption: Using 256 bit message hash ‘SHA256’ for HMAC authentication
. 2019.04.06 18:17:48 — OpenVPN > Incoming Control Channel Encryption: Cipher ‘AES-256-CTR’ initialized with 256 bit key
. 2019.04.06 18:17:48 — OpenVPN > Incoming Control Channel Encryption: Using 256 bit message hash ‘SHA256’ for HMAC authentication
. 2019.04.06 18:17:48 — OpenVPN > TCP/UDP: Preserving recently used remote address: [AF_INET]184.75.221.181:443
. 2019.04.06 18:17:48 — OpenVPN > Socket Buffers: R=[65536->262144] S=[65536->262144]
. 2019.04.06 18:17:48 — OpenVPN > UDP link local: (not bound)
. 2019.04.06 18:17:48 — OpenVPN > UDP link remote: [AF_INET]184.75.221.181:443
. 2019.04.06 18:17:48 — OpenVPN > TLS: Initial packet from [AF_INET]184.75.221.181:443, sid=df11e269 e1efbc9a
. 2019.04.06 18:17:48 — OpenVPN > MANAGEMENT: Client connected from [AF_INET]127.0.0.1:3100
. 2019.04.06 18:17:48 — OpenVPN > VERIFY OK: depth=1, C=IT, ST=IT, L=Perugia, O=airvpn.org, CN=airvpn.org CA, emailAddress=info@airvpn.org
. 2019.04.06 18:17:48 — OpenVPN > VERIFY KU OK
. 2019.04.06 18:17:48 — OpenVPN > Validating certificate extended key usage
. 2019.04.06 18:17:48 — OpenVPN > ++ Certificate has EKU (str) TLS Web Server Authentication, expects TLS Web Server Authentication
. 2019.04.06 18:17:48 — OpenVPN > VERIFY EKU OK
. 2019.04.06 18:17:48 — OpenVPN > VERIFY OK: depth=0, C=IT, ST=IT, L=Perugia, O=airvpn.org, CN=server, emailAddress=info@airvpn.org
. 2019.04.06 18:17:49 — OpenVPN > Control Channel: TLSv1.2, cipher TLSv1.2 DHE-RSA-AES256-GCM-SHA384, 4096 bit RSA
. 2019.04.06 18:17:49 — OpenVPN > [server] Peer Connection Initiated with [AF_INET]184.75.221.181:443
. 2019.04.06 18:17:50 — OpenVPN > SENT CONTROL [server]: ‘PUSH_REQUEST’ (status=1)
. 2019.04.06 18:17:50 — OpenVPN > PUSH: Received control message: ‘PUSH_REPLY,comp-lzo no,redirect-gateway ipv6 def1 bypass-dhcp,dhcp-option DNS 10.28.186.1,dhcp-option DNS6 fde6:7a:7d20:18ba::1,tun-ipv6,route-gateway 10.28.186.1,topology subnet,ping 10,ping-restart 60,ifconfig-ipv6 fde6:7a:7d20:18ba::105a/64 fde6:7a:7d20:18ba::1,ifconfig 10.28.186.92 255.255.255.0,peer-id 5,cipher AES-256-GCM’
. 2019.04.06 18:17:50 — OpenVPN > Pushed option removed by filter: ‘redirect-gateway ipv6 def1 bypass-dhcp’
. 2019.04.06 18:17:50 — OpenVPN > OPTIONS IMPORT: timers and/or timeouts modified
. 2019.04.06 18:17:50 — OpenVPN > OPTIONS IMPORT: compression parms modified
. 2019.04.06 18:17:50 — OpenVPN > OPTIONS IMPORT: —ifconfig/up options modified
. 2019.04.06 18:17:50 — OpenVPN > OPTIONS IMPORT: route-related options modified
. 2019.04.06 18:17:50 — OpenVPN > OPTIONS IMPORT: —ip-win32 and/or —dhcp-option options modified
. 2019.04.06 18:17:50 — OpenVPN > OPTIONS IMPORT: peer-id set
. 2019.04.06 18:17:50 — OpenVPN > OPTIONS IMPORT: adjusting link_mtu to 1625
. 2019.04.06 18:17:50 — OpenVPN > OPTIONS IMPORT: data channel crypto options modified
. 2019.04.06 18:17:50 — OpenVPN > Data Channel: using negotiated cipher ‘AES-256-GCM’
. 2019.04.06 18:17:50 — OpenVPN > Outgoing Data Channel: Cipher ‘AES-256-GCM’ initialized with 256 bit key
. 2019.04.06 18:17:50 — OpenVPN > Incoming Data Channel: Cipher ‘AES-256-GCM’ initialized with 256 bit key
. 2019.04.06 18:17:50 — OpenVPN > interactive service msg_channel=0
. 2019.04.06 18:17:50 — OpenVPN > ROUTE_GATEWAY 192.168.0.1/255.255.255.0 I=13 HWADDR=5c:f9:dd:78:0e:aa
. 2019.04.06 18:17:50 — OpenVPN > GDG6: remote_host_ipv6=n/a
. 2019.04.06 18:17:50 — OpenVPN > GetBestInterfaceEx() returned if=13
. 2019.04.06 18:17:50 — OpenVPN > GDG6: II=13 DP=::/0 NH=fe80::d604:cdff:fe87:a51f
. 2019.04.06 18:17:50 — OpenVPN > GDG6: Metric=256, Loopback=0, AA=1, I=0
. 2019.04.06 18:17:50 — OpenVPN > ROUTE6_GATEWAY fe80::d604:cdff:fe87:a51f I=13
. 2019.04.06 18:17:50 — OpenVPN > open_tun
. 2019.04.06 18:17:50 — OpenVPN > TAP-WIN32 device [Ethernet 2] opened: \\.\Global\{0ABEC94F-76D1-4CE9-89E7-E1810E356D0E}.tap
. 2019.04.06 18:17:50 — OpenVPN > TAP-Windows Driver Version 9.21
. 2019.04.06 18:17:50 — OpenVPN > Set TAP-Windows TUN subnet mode network/local/netmask = 10.28.186.0/10.28.186.92/255.255.255.0 [sUCCEEDED]
. 2019.04.06 18:17:50 — OpenVPN > Notified TAP-Windows driver to set a DHCP IP/netmask of 10.28.186.92/255.255.255.0 on interface {0ABEC94F-76D1-4CE9-89E7-E1810E356D0E} [DHCP-serv: 10.28.186.254, lease-time: 31536000]
. 2019.04.06 18:17:50 — OpenVPN > Successful ARP Flush on interface [2] {0ABEC94F-76D1-4CE9-89E7-E1810E356D0E}
. 2019.04.06 18:17:50 — OpenVPN > do_ifconfig, tt->did_ifconfig_ipv6_setup=1
. 2019.04.06 18:17:51 — OpenVPN > NETSH: C:\WINDOWS\system32\netsh.exe interface ipv6 set address interface=2 fde6:7a:7d20:18ba::105a store=active
. 2019.04.06 18:17:52 — OpenVPN > NETSH: C:\WINDOWS\system32\netsh.exe interface ipv6 set dns Ethernet 2 static fde6:7a:7d20:18ba::1 validate=no
. 2019.04.06 18:17:52 — OpenVPN > add_route_ipv6(fde6:7a:7d20:18ba::/64 -> fde6:7a:7d20:18ba::105a metric 0) dev Ethernet 2
. 2019.04.06 18:17:52 — OpenVPN > C:\WINDOWS\system32\netsh.exe interface ipv6 add route fde6:7a:7d20:18ba::/64 interface=2 fe80::8 store=active
. 2019.04.06 18:17:52 — OpenVPN > env_block: add PATH=C:\WINDOWS\System32;C:\WINDOWS;C:\WINDOWS\System32\Wbem
! 2019.04.06 18:17:57 — Disconnecting
. 2019.04.06 18:17:57 — Sending management termination signal
. 2019.04.06 18:17:57 — Management — Send ‘signal SIGTERM’
. 2019.04.06 18:17:57 — OpenVPN > MANAGEMENT: CMD ‘289abc3f33a87142b314a320cce6f8e4a7fadc6ac4448c994f05769a634d00c2’
. 2019.04.06 18:17:57 — OpenVPN > TEST ROUTES: 0/0 succeeded len=-1 ret=0 a=0 u/d=down
. 2019.04.06 18:17:57 — OpenVPN > Route: Waiting for TUN/TAP interface to come up…
. 2019.04.06 18:17:57 — Eddie Windows Interface Hack executed (Ethernet 2)
. 2019.04.06 18:18:03 — OpenVPN > TEST ROUTES: 0/0 succeeded len=-1 ret=0 a=0 u/d=down
. 2019.04.06 18:18:03 — OpenVPN > Route: Waiting for TUN/TAP interface to come up…
. 2019.04.06 18:18:03 — Eddie Windows Interface Hack executed (Ethernet 2)
. 2019.04.06 18:18:03 — OpenVPN > TEST ROUTES: 0/0 succeeded len=-1 ret=0 a=0 u/d=down
. 2019.04.06 18:18:03 — OpenVPN > Route: Waiting for TUN/TAP interface to come up…
. 2019.04.06 18:18:03 — Eddie Windows Interface Hack executed (Ethernet 2)
. 2019.04.06 18:18:04 — OpenVPN > TEST ROUTES: 0/0 succeeded len=-1 ret=0 a=0 u/d=down
. 2019.04.06 18:18:04 — OpenVPN > Route: Waiting for TUN/TAP interface to come up…
. 2019.04.06 18:18:04 — Eddie Windows Interface Hack executed (Ethernet 2)
. 2019.04.06 18:18:05 — OpenVPN > TEST ROUTES: 0/0 succeeded len=-1 ret=0 a=0 u/d=down
. 2019.04.06 18:18:05 — OpenVPN > Route: Waiting for TUN/TAP interface to come up…
. 2019.04.06 18:18:05 — Eddie Windows Interface Hack executed (Ethernet 2)
. 2019.04.06 18:18:06 — OpenVPN > TEST ROUTES: 0/0 succeeded len=-1 ret=0 a=0 u/d=down
. 2019.04.06 18:18:06 — OpenVPN > Route: Waiting for TUN/TAP interface to come up…
. 2019.04.06 18:18:06 — Eddie Windows Interface Hack executed (Ethernet 2)
. 2019.04.06 18:18:06 — Sending management termination signal
. 2019.04.06 18:18:06 — Management — Send ‘signal SIGTERM’
. 2019.04.06 18:18:06 — OpenVPN > MANAGEMENT: CMD ‘signal SIGTERM’
. 2019.04.06 18:18:06 — OpenVPN > SIGTERM received, sending exit notification to peer
. 2019.04.06 18:18:07 — OpenVPN > TEST ROUTES: 0/0 succeeded len=-1 ret=0 a=0 u/d=down
. 2019.04.06 18:18:07 — OpenVPN > Route: Waiting for TUN/TAP interface to come up…
. 2019.04.06 18:18:07 — Eddie Windows Interface Hack executed (Ethernet 2)
. 2019.04.06 18:18:08 — OpenVPN > TEST ROUTES: 0/0 succeeded len=-1 ret=0 a=0 u/d=down
. 2019.04.06 18:18:08 — OpenVPN > Route: Waiting for TUN/TAP interface to come up…
. 2019.04.06 18:18:08 — Eddie Windows Interface Hack executed (Ethernet 2)
. 2019.04.06 18:18:09 — OpenVPN > TEST ROUTES: 0/0 succeeded len=-1 ret=0 a=0 u/d=down
. 2019.04.06 18:18:09 — OpenVPN > Route: Waiting for TUN/TAP interface to come up…
. 2019.04.06 18:18:09 — Eddie Windows Interface Hack executed (Ethernet 2)
. 2019.04.06 18:18:11 — OpenVPN > TEST ROUTES: 0/0 succeeded len=-1 ret=0 a=0 u/d=down
. 2019.04.06 18:18:11 — OpenVPN > Route: Waiting for TUN/TAP interface to come up…
. 2019.04.06 18:18:11 — Eddie Windows Interface Hack executed (Ethernet 2)
. 2019.04.06 18:18:11 — OpenVPN > Closing TUN/TAP interface
. 2019.04.06 18:18:11 — OpenVPN > delete_route_ipv6(fde6:7a:7d20:18ba::/64)
. 2019.04.06 18:18:11 — OpenVPN > C:\WINDOWS\system32\netsh.exe interface ipv6 delete route fde6:7a:7d20:18ba::/64 interface=2 fe80::8 store=active
. 2019.04.06 18:18:11 — Connection terminated.
. 2019.04.06 18:18:11 — OpenVPN > NETSH: C:\WINDOWS\system32\netsh.exe interface ipv6 delete address Ethernet 2 fde6:7a:7d20:18ba::105a store=active
. 2019.04.06 18:18:11 — OpenVPN > NETSH: C:\WINDOWS\system32\netsh.exe interface ipv6 delete dns Ethernet 2 all
. 2019.04.06 18:18:11 — OpenVPN > NOTE: Release of DHCP-assigned IP address lease on TAP-Windows adapter failed: An address has not yet been associated with the network endpoint. (code=1228)
. 2019.04.06 18:18:11 — OpenVPN > SIGTERM[soft,exit-with-notification] received, process exiting
I 2019.04.06 18:18:11 — Cancel requested.
! 2019.04.06 18:18:11 — Session terminated.

Источник