I am new to openvpn and have tried several times over the past couple of years to get a functional openvpn server at home. i finally got the client to connect without cutting my internet connectivity. Now my issue is that i cannot ping the vpn server nor access or ping anything on my home lan. which makes the server completely useles....I am going nuts trying to figure out what i am doing wrong here. Hoping the forums will help me.
Here is my client.ovpn file code
##############################################
# Sample client-side OpenVPN 2.0 config file #
# for connecting to multi-client server. #
# #
# This configuration can be used by multiple #
# clients, however each client should have #
# its own cert and key files. #
# #
# On Windows, you might want to rename this #
# file so it has a .ovpn extension #
##############################################
route 0.0.0.0 192.168.0.0 net_gateway
# Specify that we are a client and that we
# will be pulling certain config file directives
# from the server.
client
# Use the same setting as you are using on
# the server.
# On most systems, the VPN will not function
# unless you partially or fully disable
# the firewall for the TUN/TAP interface.
;dev tap
dev tun
# Windows needs the TAP-Win32 adapter name
# from the Network Connections panel
# if you have more than one. On XP SP2,
# you may need to disable the firewall
# for the TAP adapter.
;dev-node MyTap
# Are we connecting to a TCP or
# UDP server? Use the same setting as
# on the server.
;proto tcp
proto udp
# The hostname/IP and port of the server.
# You can have multiple remote entries
# to load balance between the servers.
remote x.x.x.x 1194
;remote my-server-2 1194
# Choose a random host from the remote
# list for load-balancing. Otherwise
# try hosts in the order specified.
;remote-random
# Keep trying indefinitely to resolve the
# host name of the OpenVPN server. Very useful
# on machines which are not permanently connected
# to the internet such as laptops.
resolv-retry infinite
# Most clients don't need to bind to
# a specific local port number.
nobind
# Downgrade privileges after initialization (non-Windows only)
;user nobody
;group nogroup
# Try to preserve some state across restarts.
persist-key
persist-tun
# If you are connecting through an
# HTTP proxy to reach the actual OpenVPN
# server, put the proxy server/IP and
# port number here. See the man page
# if your proxy server requires
# authentication.
;http-proxy-retry # retry on connection failures
;http-proxy [proxy server] [proxy port #]
# Wireless networks often produce a lot
# of duplicate packets. Set this flag
# to silence duplicate packet warnings.
;mute-replay-warnings
# SSL/TLS parms.
# See the server config file for more
# description. It's best to use
# a separate .crt/.key file pair
# for each client. A single ca
# file can be used for all clients.
#ca ca.crt
#cert client.crt
#key client.key
# Verify server certificate by checking
# that the certicate has the nsCertType
# field set to "server". This is an
# important precaution to protect against
# a potential attack discussed here:
#
http://openvpn.net/howto.html#mitm
#
# To use this feature, you will need to generate
# your server certificates with the nsCertType
# field set to "server". The build-key-server
# script in the easy-rsa folder will do this.
ns-cert-type server
# If a tls-auth key is used on the server
# then every client must also have the key.
;tls-auth ta.key 1
# Select a cryptographic cipher.
# If the cipher option is used on the server
# then you must also specify it here.
;cipher x
# Enable compression on the VPN link.
# Don't enable this unless it is also
# enabled in the server config file.
comp-lzo
# Set log file verbosity.
verb 3
# Silence repeating messages
;mute 20
and my server.conf file
# Which local IP address should OpenVPN
# listen on? (optional)
;local a.b.c.d
# Which TCP/UDP port should OpenVPN listen on?
# If you want to run multiple OpenVPN instances
# on the same machine, use a different port
# number for each one. You will need to
# open up this port on your firewall.
port 1194
# TCP or UDP server?
;proto tcp
proto udp
# "dev tun" will create a routed IP tunnel,
# "dev tap" will create an ethernet tunnel.
# Use "dev tap0" if you are ethernet bridging
# and have precreated a tap0 virtual interface
# and bridged it with your ethernet interface.
# If you want to control access policies
# over the VPN, you must create firewall
# rules for the the TUN/TAP interface.
# On non-Windows systems, you can give
# an explicit unit number, such as tun0.
# On Windows, use "dev-node" for this.
# On most systems, the VPN will not function
# unless you partially or fully disable
# the firewall for the TUN/TAP interface.
;dev tap
dev tun
# Windows needs the TAP-Win32 adapter name
# from the Network Connections panel if you
# have more than one. On XP SP2 or higher,
# you may need to selectively disable the
# Windows firewall for the TAP adapter.
# Non-Windows systems usually don't need this.
;dev-node MyTap
# SSL/TLS root certificate (ca), certificate
# (cert), and private key (key). Each client
# and the server must have their own cert and
# key file. The server and all clients will
# use the same ca file.
#
# See the "easy-rsa" directory for a series
# of scripts for generating RSA certificates
# and private keys. Remember to use
# a unique Common Name for the server
# and each of the client certificates.
#
# Any X509 key management system can be used.
# OpenVPN can also use a PKCS #12 formatted key file
# (see "pkcs12" directive in man page).
ca ca.crt
cert server.crt
key server.key # This file should be kept secret
# Diffie hellman parameters.
# Generate your own with:
# openssl dhparam -out dh1024.pem 1024
# Substitute 2048 for 1024 if you are using
# 2048 bit keys.
dh dh2048.pem
# Configure server mode and supply a VPN subnet
# for OpenVPN to draw client addresses from.
# The server will take 10.8.0.1 for itself,
# the rest will be made available to clients.
# Each client will be able to reach the server
# on 10.8.0.1. Comment this line out if you are
# ethernet bridging. See the man page for more info.
server 10.8.0.0 255.255.255.0
# Maintain a record of client <-> virtual IP address
# associations in this file. If OpenVPN goes down or
# is restarted, reconnecting clients can be assigned
# the same virtual IP address from the pool that was
# previously assigned.
ifconfig-pool-persist ipp.txt
# Configure server mode for ethernet bridging.
# You must first use your OS's bridging capability
# to bridge the TAP interface with the ethernet
# NIC interface. Then you must manually set the
# IP/netmask on the bridge interface, here we
# assume 10.8.0.4/255.255.255.0. Finally we
# must set aside an IP range in this subnet
# (start=10.8.0.50 end=10.8.0.100) to allocate
# to connecting clients. Leave this line commented
out unless you are ethernet bridging.
;server-bridge 10.8.0.4 255.255.255.0 10.8.0.50 10.8.0.100
# Configure server mode for ethernet bridging
# using a DHCP-proxy, where clients talk
# to the OpenVPN server-side DHCP server
# to receive their IP address allocation
# and DNS server addresses. You must first use
# your OS's bridging capability to bridge the TAP
# interface with the ethernet NIC interface.
# Note: this mode only works on clients (such as
# Windows), where the client-side TAP adapter is
# bound to a DHCP client.
;server-bridge
# Push routes to the client to allow it
# to reach other private subnets behind
# the server. Remember that these
# private subnets will also need
# to know to route the OpenVPN client
# address pool (10.8.0.0/255.255.255.0)
# back to the OpenVPN server.
;push "route 192.168.10.0 255.255.255.0"
# To assign specific IP addresses to specific
# clients or if a connecting client has a private
# subnet behind it that should also have VPN access,
# use the subdirectory "ccd" for client-specific
# configuration files (see man page for more info).
# EXAMPLE: Suppose the client
# having the certificate common name "Thelonious"
# also has a small subnet behind his connecting
# machine, such as 192.168.40.128/255.255.255.248.
# First, uncomment out these lines:
;client-config-dir ccd
;route 192.168.40.128 255.255.255.248
# Then create a file ccd/Thelonious with this line:
# iroute 192.168.40.128 255.255.255.248
# This will allow Thelonious' private subnet to
# access the VPN. This example will only work
# if you are routing, not bridging, i.e. you are
# using "dev tun" and "server" directives.
# EXAMPLE: Suppose you want to give
# Thelonious a fixed VPN IP address of 10.9.0.1.
# First uncomment out these lines:
;client-config-dir ccd
;route 10.9.0.0 255.255.255.252
# Then add this line to ccd/Thelonious:
# ifconfig-push 10.9.0.1 10.9.0.2
# Suppose that you want to enable different
# firewall access policies for different groups
# of clients. There are two methods:
# (1) Run multiple OpenVPN daemons, one for each
# group, and firewall the TUN/TAP interface
# for each group/daemon appropriately.
# (2) (Advanced) Create a script to dynamically
# modify the firewall in response to access
# from different clients. See man
# page for more info on learn-address script.
;learn-address ./script
# If enabled, this directive will configure
# all clients to redirect their default
# network gateway through the VPN, causing
# all IP traffic such as web browsing and
# and DNS lookups to go through the VPN
# (The OpenVPN server machine may need to NAT
# or bridge the TUN/TAP interface to the internet
# in order for this to work properly).
#push "redirect-gateway def1 bypass-dhcp"
push "redirect-gateway local def1"
# Certain Windows-specific network settings
# can be pushed to clients, such as DNS
# or WINS server addresses. CAVEAT:
#
http://openvpn.net/faq.html#dhcpcaveats
# The addresses below refer to the public
# DNS servers provided by opendns.com.
push "dhcp-option DNS 8.8.8.8"
#push "dhcp-option DNS 208.67.220.220"
# Uncomment this directive to allow different
# clients to be able to "see" each other.
# By default, clients will only see the server.
# To force clients to only see the server, you
# will also need to appropriately firewall the
# server's TUN/TAP interface.
;client-to-client
# Uncomment this directive if multiple clients
# might connect with the same certificate/key
# files or common names. This is recommended
# only for testing purposes. For production use,
# each client should have its own certificate/key
# pair.
#
# IF YOU HAVE NOT GENERATED INDIVIDUAL
# CERTIFICATE/KEY PAIRS FOR EACH CLIENT,
# EACH HAVING ITS OWN UNIQUE "COMMON NAME",
# UNCOMMENT THIS LINE OUT.
;duplicate-cn
# The keepalive directive causes ping-like
# messages to be sent back and forth over
# the link so that each side knows when
# the other side has gone down.
# Ping every 10 seconds, assume that remote
# peer is down if no ping received during
# a 120 second time period.
keepalive 10 120
# For extra security beyond that provided
# by SSL/TLS, create an "HMAC firewall"
# to help block DoS attacks and UDP port flooding.
#
# Generate with:
# openvpn --genkey --secret ta.key
#
# The server and each client must have
# a copy of this key.
# The second parameter should be '0'
# on the server and '1' on the clients.
;tls-auth ta.key 0 # This file is secret
# Select a cryptographic cipher.
# This config item must be copied to
# the client config file as well.
;cipher BF-CBC # Blowfish (default)
;cipher AES-128-CBC # AES
;cipher DES-EDE3-CBC # Triple-DES
# Enable compression on the VPN link.
# If you enable it here, you must also
# enable it in the client config file.
comp-lzo
# The maximum number of concurrently connected
# clients we want to allow.
;max-clients 100
# It's a good idea to reduce the OpenVPN
# daemon's privileges after initialization.
#
# You can uncomment this out on
# non-Windows systems.
user nobody
group nogroup
# The persist options will try to avoid
# accessing certain resources on restart
# that may no longer be accessible because
# of the privilege downgrade.
persist-key
persist-tun
# Output a short status file showing
# current connections, truncated
# and rewritten every minute.
status openvpn-status.log
# By default, log messages will go to the syslog (or
# on Windows, if running as a service, they will go to
# the "\Program Files\OpenVPN\log" directory).
# Use log or log-append to override this default.
# "log" will truncate the log file on OpenVPN startup,
# while "log-append" will append to it. Use one
# or the other (but not both).
;log openvpn.log
;log-append openvpn.log
# Set the appropriate level of log
# file verbosity.
#
# 0 is silent, except for fatal errors
# 4 is reasonable for general usage
# 5 and 6 can help to debug connection problems
# 9 is extremely verbose
verb 3
# Silence repeating messages. At most 20
# sequential messages of the same message
# category will be output to the log.
;mute 20
here is the log file after i connected
Wed Aug 24 16:16:47 2016 WARNING: Endtag </key> missing
Wed Aug 24 16:16:47 2016 OpenVPN 2.3.11 x86_64-w64-mingw32 [SSL (OpenSSL)] [LZO] [PKCS11] [IPv6] built on May 10 2016
Wed Aug 24 16:16:47 2016 Windows version 6.1 (Windows 7) 64bit
Wed Aug 24 16:16:47 2016 library versions: OpenSSL 1.0.1t 3 May 2016, LZO 2.09
Enter Management Password:
Wed Aug 24 16:16:47 2016 MANAGEMENT: TCP Socket listening on [AF_INET]127.0.0.1:25340
Wed Aug 24 16:16:47 2016 Need hold release from management interface, waiting...
Wed Aug 24 16:16:48 2016 MANAGEMENT: Client connected from [AF_INET]127.0.0.1:25340
Wed Aug 24 16:16:48 2016 MANAGEMENT: CMD 'state on'
Wed Aug 24 16:16:48 2016 MANAGEMENT: CMD 'log all on'
Wed Aug 24 16:16:48 2016 MANAGEMENT: CMD 'hold off'
Wed Aug 24 16:16:48 2016 MANAGEMENT: CMD 'hold release'
Wed Aug 24 16:16:48 2016 Socket Buffers: R=[8192->8192] S=[64512->64512]
Wed Aug 24 16:16:48 2016 UDPv4 link local: [undef]
Wed Aug 24 16:16:48 2016 UDPv4 link remote: [AF_INET]x.x.x.x:1194
Wed Aug 24 16:16:48 2016 MANAGEMENT: >STATE:1472069808,WAIT,,,
Wed Aug 24 16:16:48 2016 MANAGEMENT: >STATE:1472069808,AUTH,,,
Wed Aug 24 16:16:48 2016 TLS: Initial packet from [AF_INET]x.x.x.x:1194, sid=172e0784 318048eb
Wed Aug 24 16:16:49 2016 VERIFY OK: depth=1, C=US, ST=NY, L=Lowville, O=ABC Company, OU=MyOrganizationalUnit, CN=ABC Company CA, name=server, emailAddress=ctabolt@gmail.com
Wed Aug 24 16:16:49 2016 VERIFY OK: nsCertType=SERVER
Wed Aug 24 16:16:49 2016 VERIFY OK: depth=0, C=US, ST=NY, L=Lowville, O=ABC Company, OU=MyOrganizationalUnit, CN=server, name=server, emailAddress=ctabolt@gmail.com
Wed Aug 24 16:16:49 2016 Data Channel Encrypt: Cipher 'BF-CBC' initialized with 128 bit key
Wed Aug 24 16:16:49 2016 Data Channel Encrypt: Using 160 bit message hash 'SHA1' for HMAC authentication
Wed Aug 24 16:16:49 2016 Data Channel Decrypt: Cipher 'BF-CBC' initialized with 128 bit key
Wed Aug 24 16:16:49 2016 Data Channel Decrypt: Using 160 bit message hash 'SHA1' for HMAC authentication
Wed Aug 24 16:16:49 2016 Control Channel: TLSv1, cipher TLSv1/SSLv3 DHE-RSA-AES256-SHA, 2048 bit RSA
Wed Aug 24 16:16:49 2016 [server] Peer Connection Initiated with [AF_INET]x.x.x.x:1194
Wed Aug 24 16:16:50 2016 MANAGEMENT: >STATE:1472069810,GET_CONFIG,,,
Wed Aug 24 16:16:51 2016 SENT CONTROL [server]: 'PUSH_REQUEST' (status=1)
Wed Aug 24 16:16:51 2016 PUSH: Received control message: 'PUSH_REPLY,route 192.168.1.0 255.255.255.0,route-gateway 10.8.0.1,dhcp-option DNS 208.67.222.222,dhcp-option DNS 208.67.220.220,route 10.8.0.1,topology net30,ping 10,ping-restart 120,ifconfig 10.8.0.6 10.8.0.5'
Wed Aug 24 16:16:51 2016 OPTIONS IMPORT: timers and/or timeouts modified
Wed Aug 24 16:16:51 2016 OPTIONS IMPORT: --ifconfig/up options modified
Wed Aug 24 16:16:51 2016 OPTIONS IMPORT: route options modified
Wed Aug 24 16:16:51 2016 OPTIONS IMPORT: route-related options modified
Wed Aug 24 16:16:51 2016 OPTIONS IMPORT: --ip-win32 and/or --dhcp-option options modified
Wed Aug 24 16:16:51 2016 ROUTE_GATEWAY 172.16.40.1/255.255.254.0 I=26 HWADDR=f4:06:69:76:ba:2e
Wed Aug 24 16:16:51 2016 do_ifconfig, tt->ipv6=0, tt->did_ifconfig_ipv6_setup=0
Wed Aug 24 16:16:51 2016 MANAGEMENT: >STATE:1472069811,ASSIGN_IP,,10.8.0.6,
Wed Aug 24 16:16:51 2016 open_tun, tt->ipv6=0
Wed Aug 24 16:16:51 2016 TAP-WIN32 device [Local Area Connection 5] opened: \\.\Global\{D3CE11DE-4C98-4251-AC60-C020D691B879}.tap
Wed Aug 24 16:16:51 2016 TAP-Windows Driver Version 9.21
Wed Aug 24 16:16:51 2016 Notified TAP-Windows driver to set a DHCP IP/netmask of 10.8.0.6/255.255.255.252 on interface {D3CE11DE-4C98-4251-AC60-C020D691B879} [DHCP-serv: 10.8.0.5, lease-time: 31536000]
Wed Aug 24 16:16:51 2016 Successful ARP Flush on interface [32] {D3CE11DE-4C98-4251-AC60-C020D691B879}
Wed Aug 24 16:16:57 2016 TEST ROUTES: 1/3 succeeded len=3 ret=0 a=0 u/d=up
Wed Aug 24 16:16:57 2016 Route: Waiting for TUN/TAP interface to come up...
Wed Aug 24 16:17:02 2016 TEST ROUTES: 1/3 succeeded len=3 ret=0 a=0 u/d=up
Wed Aug 24 16:17:02 2016 Route: Waiting for TUN/TAP interface to come up...
Wed Aug 24 16:17:03 2016 TEST ROUTES: 1/3 succeeded len=3 ret=0 a=0 u/d=up
Wed Aug 24 16:17:03 2016 Route: Waiting for TUN/TAP interface to come up...
Wed Aug 24 16:17:05 2016 TEST ROUTES: 1/3 succeeded len=3 ret=0 a=0 u/d=up
Wed Aug 24 16:17:05 2016 Route: Waiting for TUN/TAP interface to come up...
Wed Aug 24 16:17:06 2016 TEST ROUTES: 1/3 succeeded len=3 ret=0 a=0 u/d=up
Wed Aug 24 16:17:06 2016 Route: Waiting for TUN/TAP interface to come up...
Wed Aug 24 16:17:07 2016 TEST ROUTES: 1/3 succeeded len=3 ret=0 a=0 u/d=up
Wed Aug 24 16:17:07 2016 Route: Waiting for TUN/TAP interface to come up...
Wed Aug 24 16:17:08 2016 TEST ROUTES: 1/3 succeeded len=3 ret=0 a=0 u/d=up
Wed Aug 24 16:17:08 2016 Route: Waiting for TUN/TAP interface to come up...
Wed Aug 24 16:17:09 2016 TEST ROUTES: 1/3 succeeded len=3 ret=0 a=0 u/d=up
Wed Aug 24 16:17:09 2016 Route: Waiting for TUN/TAP interface to come up...
Wed Aug 24 16:17:10 2016 TEST ROUTES: 1/3 succeeded len=3 ret=0 a=0 u/d=up
Wed Aug 24 16:17:10 2016 Route: Waiting for TUN/TAP interface to come up...
Wed Aug 24 16:17:11 2016 TEST ROUTES: 1/3 succeeded len=3 ret=0 a=0 u/d=up
Wed Aug 24 16:17:11 2016 Route: Waiting for TUN/TAP interface to come up...
Wed Aug 24 16:17:12 2016 TEST ROUTES: 1/3 succeeded len=3 ret=0 a=0 u/d=up
Wed Aug 24 16:17:12 2016 Route: Waiting for TUN/TAP interface to come up...
Wed Aug 24 16:17:13 2016 TEST ROUTES: 1/3 succeeded len=3 ret=0 a=0 u/d=up
Wed Aug 24 16:17:13 2016 Route: Waiting for TUN/TAP interface to come up...
Wed Aug 24 16:17:14 2016 TEST ROUTES: 1/3 succeeded len=3 ret=0 a=0 u/d=up
Wed Aug 24 16:17:14 2016 Route: Waiting for TUN/TAP interface to come up...
Wed Aug 24 16:17:16 2016 TEST ROUTES: 1/3 succeeded len=3 ret=0 a=0 u/d=up
Wed Aug 24 16:17:16 2016 Route: Waiting for TUN/TAP interface to come up...
Wed Aug 24 16:17:17 2016 TEST ROUTES: 1/3 succeeded len=3 ret=0 a=0 u/d=up
Wed Aug 24 16:17:17 2016 Route: Waiting for TUN/TAP interface to come up...
Wed Aug 24 16:17:18 2016 TEST ROUTES: 1/3 succeeded len=3 ret=0 a=0 u/d=up
Wed Aug 24 16:17:18 2016 Route: Waiting for TUN/TAP interface to come up...
Wed Aug 24 16:17:19 2016 TEST ROUTES: 1/3 succeeded len=3 ret=0 a=0 u/d=up
Wed Aug 24 16:17:19 2016 Route: Waiting for TUN/TAP interface to come up...
Wed Aug 24 16:17:20 2016 TEST ROUTES: 1/3 succeeded len=3 ret=0 a=0 u/d=up
Wed Aug 24 16:17:20 2016 Route: Waiting for TUN/TAP interface to come up...
Wed Aug 24 16:17:21 2016 TEST ROUTES: 1/3 succeeded len=3 ret=0 a=0 u/d=up
Wed Aug 24 16:17:21 2016 Route: Waiting for TUN/TAP interface to come up...
Wed Aug 24 16:17:22 2016 TEST ROUTES: 1/3 succeeded len=3 ret=0 a=0 u/d=up
Wed Aug 24 16:17:22 2016 Route: Waiting for TUN/TAP interface to come up...
Wed Aug 24 16:17:23 2016 TEST ROUTES: 1/3 succeeded len=3 ret=0 a=0 u/d=up
Wed Aug 24 16:17:23 2016 Route: Waiting for TUN/TAP interface to come up...
Wed Aug 24 16:17:24 2016 TEST ROUTES: 1/3 succeeded len=3 ret=0 a=0 u/d=up
Wed Aug 24 16:17:24 2016 Route: Waiting for TUN/TAP interface to come up...
Wed Aug 24 16:17:25 2016 TEST ROUTES: 1/3 succeeded len=3 ret=0 a=0 u/d=up
Wed Aug 24 16:17:25 2016 Route: Waiting for TUN/TAP interface to come up...
Wed Aug 24 16:17:26 2016 TEST ROUTES: 1/3 succeeded len=3 ret=0 a=0 u/d=up
Wed Aug 24 16:17:26 2016 MANAGEMENT: >STATE:1472069846,ADD_ROUTES,,,
Wed Aug 24 16:17:26 2016 C:\Windows\system32\route.exe ADD 0.0.0.0 MASK 192.168.0.0 172.16.40.1
Wed Aug 24 16:17:26 2016 ROUTE: route addition failed using CreateIpForwardEntry: The parameter is incorrect. [status=87 if_index=26]
Wed Aug 24 16:17:26 2016 Route addition via IPAPI failed [adaptive]
Wed Aug 24 16:17:26 2016 Route addition fallback to route.exe
Wed Aug 24 16:17:26 2016 env_block: add PATH=C:\Windows\System32;C:\Windows;C:\Windows\System32\Wbem
Wed Aug 24 16:17:26 2016 C:\Windows\system32\route.exe ADD 192.168.1.0 MASK 255.255.255.0 10.8.0.1
Wed Aug 24 16:17:26 2016 Warning: route gateway is not reachable on any active network adapters: 10.8.0.1
Wed Aug 24 16:17:26 2016 Route addition via IPAPI failed [adaptive]
Wed Aug 24 16:17:26 2016 Route addition fallback to route.exe
Wed Aug 24 16:17:26 2016 env_block: add PATH=C:\Windows\System32;C:\Windows;C:\Windows\System32\Wbem
Wed Aug 24 16:17:26 2016 C:\Windows\system32\route.exe ADD 10.8.0.1 MASK 255.255.255.255 10.8.0.1
Wed Aug 24 16:17:26 2016 Warning: route gateway is not reachable on any active network adapters: 10.8.0.1
Wed Aug 24 16:17:26 2016 Route addition via IPAPI failed [adaptive]
Wed Aug 24 16:17:26 2016 Route addition fallback to route.exe
Wed Aug 24 16:17:26 2016 env_block: add PATH=C:\Windows\System32;C:\Windows;C:\Windows\System32\Wbem
SYSTEM ROUTING TABLE
0.0.0.0 0.0.0.0 172.16.40.1 p=0 i=26 t=4 pr=3 a=5258 h=0 m=26/0/0/0/0
10.8.0.1 255.255.255.255 10.8.0.1 p=0 i=26 t=4 pr=3 a=0 h=0 m=26/0/0/0/0
10.8.0.4 255.255.255.252 10.8.0.6 p=0 i=32 t=3 pr=3 a=34 h=0 m=276/0/0/0/0
10.8.0.6 255.255.255.255 10.8.0.6 p=0 i=32 t=3 pr=3 a=34 h=0 m=276/0/0/0/0
10.8.0.7 255.255.255.255 10.8.0.6 p=0 i=32 t=3 pr=3 a=34 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=5375 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=5375 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=5375 h=0 m=306/0/0/0/0
169.254.0.0 255.255.0.0 169.254.222.218 p=0 i=19 t=3 pr=3 a=5275 h=0 m=266/0/0/0/0
169.254.222.218 255.255.255.255 169.254.222.218 p=0 i=19 t=3 pr=3 a=5275 h=0 m=266/0/0/0/0
169.254.255.255 255.255.255.255 169.254.222.218 p=0 i=19 t=3 pr=3 a=5275 h=0 m=266/0/0/0/0
172.16.40.0 255.255.254.0 172.16.41.118 p=0 i=26 t=3 pr=3 a=5258 h=0 m=281/0/0/0/0
172.16.41.118 255.255.255.255 172.16.41.118 p=0 i=26 t=3 pr=3 a=5258 h=0 m=281/0/0/0/0
172.16.41.255 255.255.255.255 172.16.41.118 p=0 i=26 t=3 pr=3 a=5258 h=0 m=281/0/0/0/0
192.168.1.0 255.255.255.0 10.8.0.1 p=0 i=26 t=4 pr=3 a=0 h=0 m=26/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=5375 h=0 m=306/0/0/0/0
224.0.0.0 240.0.0.0 10.8.0.6 p=0 i=32 t=3 pr=3 a=5288 h=0 m=276/0/0/0/0
224.0.0.0 240.0.0.0 169.254.222.218 p=0 i=19 t=3 pr=3 a=5285 h=0 m=266/0/0/0/0
224.0.0.0 240.0.0.0 172.16.41.118 p=0 i=26 t=3 pr=3 a=5262 h=0 m=281/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=5375 h=0 m=306/0/0/0/0
255.255.255.255 255.255.255.255 10.8.0.6 p=0 i=32 t=3 pr=3 a=5288 h=0 m=276/0/0/0/0
255.255.255.255 255.255.255.255 169.254.222.218 p=0 i=19 t=3 pr=3 a=5285 h=0 m=266/0/0/0/0
255.255.255.255 255.255.255.255 172.16.41.118 p=0 i=26 t=3 pr=3 a=5262 h=0 m=281/0/0/0/0
SYSTEM ADAPTER LIST
TAP-Windows Adapter V9
Index = 32
GUID = {D3CE11DE-4C98-4251-AC60-C020D691B879}
IP = 10.8.0.6/255.255.255.252
MAC = 00:ff:d3:ce:11:de
GATEWAY = 0.0.0.0/255.255.255.255
DHCP SERV = 10.8.0.5/255.255.255.255
DHCP LEASE OBTAINED = Wed Aug 24 16:16:52 2016
DHCP LEASE EXPIRES = Thu Aug 24 16:16:52 2017
DNS SERV = 208.67.222.222/255.255.255.255 208.67.220.220/255.255.255.255
DisplayLink Network Adapter NCM #3
Index = 28
GUID = {7F4159AA-B939-408C-9CEF-1360D5C52DE6}
IP = 0.0.0.0/0.0.0.0
MAC = 00:1f:b5:25:3a:1e
GATEWAY = 0.0.0.0/255.255.255.255
DHCP SERV =
DHCP LEASE OBTAINED = Wed Aug 24 16:17:26 2016
DHCP LEASE EXPIRES = Wed Aug 24 16:17:26 2016
DNS SERV =
Intel(R) Dual Band Wireless-AC 3160
Index = 26
GUID = {403EDCFD-8F2B-4B7A-89D9-CA9B0DAA4D8B}
IP = 172.16.41.118/255.255.254.0
MAC = f4:06:69:76:ba:2e
GATEWAY = 172.16.40.1/255.255.255.255
DHCP SERV = 172.16.40.242/255.255.255.255
DHCP LEASE OBTAINED = Wed Aug 24 14:50:27 2016
DHCP LEASE EXPIRES = Thu Aug 25 02:50:27 2016
PRI WINS = 172.16.40.252/255.255.255.255
SEC WINS =
DNS SERV = 172.16.40.253/255.255.255.255 172.16.40.242/255.255.255.255
Bluetooth Device (Personal Area Network) #2
Index = 25
GUID = {84CFF7ED-05A5-41E3-9C58-337E5DB01969}
IP = 0.0.0.0/0.0.0.0
MAC = f4:06:69:76:ba:32
GATEWAY = 0.0.0.0/255.255.255.255
DHCP SERV =
DHCP LEASE OBTAINED = Wed Aug 24 16:17:26 2016
DHCP LEASE EXPIRES = Wed Aug 24 16:17:26 2016
DNS SERV =
Realtek PCIe GBE Family Controller
Index = 11
GUID = {0035319F-C23C-45F7-AF23-27A2B3B98F78}
IP = 0.0.0.0/0.0.0.0
MAC = b4:b5:2f:93:a6:d1
GATEWAY = 0.0.0.0/255.255.255.255
DHCP SERV =
DHCP LEASE OBTAINED = Wed Aug 24 16:17:26 2016
DHCP LEASE EXPIRES = Wed Aug 24 16:17:26 2016
PRI WINS = 172.16.40.252/255.255.255.255
SEC WINS =
DNS SERV =
VirtualBox Host-Only Ethernet Adapter
Index = 19
GUID = {75C86AD7-D6A2-4E81-8721-46322C48591E}
IP = 169.254.222.218/255.255.0.0
MAC = 0a:00:27:00:00:13
GATEWAY = 0.0.0.0/255.255.255.255
DNS SERV = 8.8.8.8/255.255.255.255 8.8.4.4/255.255.255.255 4.2.2.1/255.255.255.255 4.2.2.2/255.255.255.255 208.67.222.222/255.255.255.255 208.67.220.220/255.255.255.255 8.26.56.26/255.255.255.255 8.20.247.20/255.255.255.255 156.154.70.1/255.255.255.255 156.154.71.1/
Wed Aug 24 16:17:26 2016 Initialization Sequence Completed With Errors ( see http://openvpn.net/faq.html#dhcpclientserv )
Wed Aug 24 16:17:26 2016 MANAGEMENT: >STATE:1472069846,CONNECTED,ERROR,10.8.0.6,x.x.x.x
