I have quite typical configuration meaning I would like to access Windows Server and other computers mostly with Windows 7 and Windows 10 located in company from my private computer.
In order to secure connectivity I decided to use OpenVPN as a tool to setup secured tunnel.
In fact after reading very good tutorial I manage to get connection from client to server but still I cannot access any of devices from LAN network including OpenVPN server.
Both server and Client are on Windows Environment.
Configuration for Server (Windows Server 2012):
# Sample OpenVPN 2.0 config file for #
# multi-client server. #
# #
# This file is for the server side #
# of a many-clients <-> one-server #
# OpenVPN configuration. #
# #
# OpenVPN also supports #
# single-machine <-> single-machine #
# configurations (See the Examples page #
# on the web site for more info). #
# #
# This config should work on Windows #
# or Linux/BSD systems. Remember on #
# Windows to quote pathnames and use #
# double backslashes, e.g.: #
# "C:\\Program Files\\OpenVPN\\config\\foo.key" #
# #
# Comments are preceded with '#' or ';' #
#################################################
# 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 "C:\\Program Files\\OpenVPN\\config\\ca.crt"
cert "C:\\Program Files\\OpenVPN\\config\\server.crt"
key "C:\\Program Files\\OpenVPN\\config\\server.key"
# Diffie hellman parameters.
# Generate your own with:
# openssl dhparam -out dh2048.pem 2048
dh "C:\\Program Files\\OpenVPN\\config\\dh2048.pem"
# Network topology
# Should be subnet (addressing via IP)
# unless Windows clients v2.0.9 and lower have to
# be supported (then net30, i.e. a /30 per client)
# Defaults to net30 (not recommended)
;topology subnet
# 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"
;push "route 192.168.20.0 255.255.255.0"
push "route 192.168.0.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"
# 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 192.168.0.1"
push "dhcp-option DNS 8.8.8.8"
# 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.
# Note that v2.4 client/server will automatically
# negotiate AES-256-GCM in TLS mode.
# See also the ncp-cipher option in the manpage
cipher AES-256-CBC
# Enable compression on the VPN link and push the
# option to the client (v2.4+ only, for earlier
# versions see below)
;compress lz4-v2
;push "compress lz4-v2"
# For compression compatible with older clients use comp-lzo
# 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 nobody
# 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
# Notify the client that when the server restarts so it
# can automatically reconnect.
explicit-exit-notify 1
Here is the configuration of Client:
# 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 #
##############################################
# 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 82.160.124.120 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 nobody
# 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 "C:\\Program Files\\OpenVPN\\config\\ca.crt"
cert "C:\\Program Files\\OpenVPN\\config\\lukasz-laptop.crt"
key "C:\\Program Files\\OpenVPN\\config\\lukasz-laptop.key"
# Verify server certificate by checking that the
# certicate has the correct key usage set.
# 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 keyUsage set to
# digitalSignature, keyEncipherment
# and the extendedKeyUsage to
# serverAuth
# EasyRSA can do this for you.
remote-cert-tls server
# If a tls-auth key is used on the server
# then every client must also have the key.
tls-auth "C:\\Program Files\\OpenVPN\\config\\ta.key" 1
# Select a cryptographic cipher.
# If the cipher option is used on the server
# then you must also specify it here.
# Note that v2.4 client/server will automatically
# negotiate AES-256-GCM in TLS mode.
# See also the ncp-cipher option in the manpage
cipher AES-256-CBC
# 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
Here is the log from the client site while login in:
Code: Select all
Wed Nov 27 01:30:22 2019 OpenVPN 2.4.8 x86_64-w64-mingw32 [SSL (OpenSSL)] [LZO] [LZ4] [PKCS11] [AEAD] built on Oct 31 2019
Wed Nov 27 01:30:22 2019 Windows version 6.2 (Windows 8 or greater) 64bit
Wed Nov 27 01:30:22 2019 library versions: OpenSSL 1.1.0l 10 Sep 2019, LZO 2.10
Wed Nov 27 01:30:22 2019 MANAGEMENT: TCP Socket listening on [AF_INET]127.0.0.1:25340
Wed Nov 27 01:30:22 2019 Need hold release from management interface, waiting...
Wed Nov 27 01:30:22 2019 MANAGEMENT: Client connected from [AF_INET]127.0.0.1:25340
Wed Nov 27 01:30:22 2019 MANAGEMENT: CMD 'state on'
Wed Nov 27 01:30:22 2019 MANAGEMENT: CMD 'log all on'
Wed Nov 27 01:30:22 2019 MANAGEMENT: CMD 'echo all on'
Wed Nov 27 01:30:22 2019 MANAGEMENT: CMD 'bytecount 5'
Wed Nov 27 01:30:22 2019 MANAGEMENT: CMD 'hold off'
Wed Nov 27 01:30:22 2019 MANAGEMENT: CMD 'hold release'
Wed Nov 27 01:30:22 2019 Outgoing Control Channel Authentication: Using 160 bit message hash 'SHA1' for HMAC authentication
Wed Nov 27 01:30:22 2019 Incoming Control Channel Authentication: Using 160 bit message hash 'SHA1' for HMAC authentication
Wed Nov 27 01:30:22 2019 TCP/UDP: Preserving recently used remote address: [AF_INET]82.160.124.120:1194
Wed Nov 27 01:30:22 2019 Socket Buffers: R=[65536->65536] S=[65536->65536]
Wed Nov 27 01:30:22 2019 UDP link local: (not bound)
Wed Nov 27 01:30:22 2019 UDP link remote: [AF_INET]82.160.124.120:1194
Wed Nov 27 01:30:22 2019 MANAGEMENT: >STATE:1574814622,WAIT,,,,,,
Wed Nov 27 01:30:23 2019 MANAGEMENT: >STATE:1574814623,AUTH,,,,,,
Wed Nov 27 01:30:23 2019 TLS: Initial packet from [AF_INET]82.160.124.120:1194, sid=996680fe 9ee7fbd5
Wed Nov 27 01:30:23 2019 VERIFY OK: depth=1, C=PL, ST=Mazowieckie, L=Zyrardow, O=DPSSosabowski, OU=changeme, CN=OpenVPNCA-DPS, name=OpenVPNCA-DPS, emailAddress=it@dpssosabowski.pl
Wed Nov 27 01:30:23 2019 VERIFY KU OK
Wed Nov 27 01:30:23 2019 Validating certificate extended key usage
Wed Nov 27 01:30:23 2019 ++ Certificate has EKU (str) TLS Web Server Authentication, expects TLS Web Server Authentication
Wed Nov 27 01:30:23 2019 VERIFY EKU OK
Wed Nov 27 01:30:23 2019 VERIFY OK: depth=0, C=PL, ST=PL, L=Zyrardow, O=DPS, OU=changeme, CN=changeme, name=changeme, emailAddress=it@dpssosabowski.pl
Wed Nov 27 01:30:23 2019 Control Channel: TLSv1.2, cipher TLSv1.2 ECDHE-RSA-AES256-GCM-SHA384, 4096 bit RSA
Wed Nov 27 01:30:23 2019 [changeme] Peer Connection Initiated with [AF_INET]82.160.124.120:1194
Wed Nov 27 01:30:24 2019 MANAGEMENT: >STATE:1574814624,GET_CONFIG,,,,,,
Wed Nov 27 01:30:24 2019 SENT CONTROL [changeme]: 'PUSH_REQUEST' (status=1)
Wed Nov 27 01:30:24 2019 PUSH: Received control message: 'PUSH_REPLY,route 192.168.0.0 255.255.255.0,dhcp-option DNS 192.168.0.1,dhcp-option DNS 8.8.8.8,route 10.8.0.0 255.255.255.0,topology net30,ping 10,ping-restart 120,ifconfig 10.8.0.6 10.8.0.5,peer-id 0,cipher AES-256-GCM'
Wed Nov 27 01:30:24 2019 OPTIONS IMPORT: timers and/or timeouts modified
Wed Nov 27 01:30:24 2019 OPTIONS IMPORT: --ifconfig/up options modified
Wed Nov 27 01:30:24 2019 OPTIONS IMPORT: route options modified
Wed Nov 27 01:30:24 2019 OPTIONS IMPORT: --ip-win32 and/or --dhcp-option options modified
Wed Nov 27 01:30:24 2019 OPTIONS IMPORT: peer-id set
Wed Nov 27 01:30:24 2019 OPTIONS IMPORT: adjusting link_mtu to 1624
Wed Nov 27 01:30:24 2019 OPTIONS IMPORT: data channel crypto options modified
Wed Nov 27 01:30:24 2019 Data Channel: using negotiated cipher 'AES-256-GCM'
Wed Nov 27 01:30:24 2019 Outgoing Data Channel: Cipher 'AES-256-GCM' initialized with 256 bit key
Wed Nov 27 01:30:24 2019 Incoming Data Channel: Cipher 'AES-256-GCM' initialized with 256 bit key
Wed Nov 27 01:30:24 2019 interactive service msg_channel=724
Wed Nov 27 01:30:24 2019 ROUTE_GATEWAY 10.5.236.254/255.255.255.0 I=11 HWADDR=fc:aa:14:72:82:8b
Wed Nov 27 01:30:24 2019 open_tun
Wed Nov 27 01:30:24 2019 TAP-WIN32 device [Połączenie lokalne 2] opened: \\.\Global\{96555132-7F8B-41CC-A182-0D3E9D962F01}.tap
Wed Nov 27 01:30:24 2019 TAP-Windows Driver Version 9.24
Wed Nov 27 01:30:24 2019 Notified TAP-Windows driver to set a DHCP IP/netmask of 10.8.0.6/255.255.255.252 on interface {96555132-7F8B-41CC-A182-0D3E9D962F01} [DHCP-serv: 10.8.0.5, lease-time: 31536000]
Wed Nov 27 01:30:24 2019 Successful ARP Flush on interface [28] {96555132-7F8B-41CC-A182-0D3E9D962F01}
Wed Nov 27 01:30:24 2019 MANAGEMENT: >STATE:1574814624,ASSIGN_IP,,10.8.0.6,,,,
Wed Nov 27 01:30:29 2019 TEST ROUTES: 2/2 succeeded len=2 ret=1 a=0 u/d=up
Wed Nov 27 01:30:29 2019 MANAGEMENT: >STATE:1574814629,ADD_ROUTES,,,,,,
Wed Nov 27 01:30:29 2019 C:\WINDOWS\system32\route.exe ADD 192.168.0.0 MASK 255.255.255.0 10.8.0.5
Wed Nov 27 01:30:29 2019 Route addition via service succeeded
Wed Nov 27 01:30:29 2019 C:\WINDOWS\system32\route.exe ADD 10.8.0.0 MASK 255.255.255.0 10.8.0.5
Wed Nov 27 01:30:29 2019 Route addition via service succeeded
Wed Nov 27 01:30:29 2019 WARNING: this configuration may cache passwords in memory -- use the auth-nocache option to prevent this
Wed Nov 27 01:30:29 2019 Initialization Sequence Completed
Wed Nov 27 01:30:29 2019 MANAGEMENT: >STATE:1574814629,CONNECTED,SUCCESS,10.8.0.6,82.160.124.120,1194,,
Here are the ipconfing configuration from the server:
Code: Select all
Unknown adapter Połączenie lokalne:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : TAP-Windows Adapter V9
Physical Address. . . . . . . . . : 00-FF-B1-A5-15-F3
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
Link-local IPv6 Address . . . . . : fe80::c147:aad3:642a:7760%17(Preferred)
IPv4 Address. . . . . . . . . . . : 10.8.0.1(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.252
Lease Obtained. . . . . . . . . . : 27 listopada 2019 01:49:14
Lease Expires . . . . . . . . . . : 26 listopada 2020 01:49:14
Default Gateway . . . . . . . . . :
DHCP Server . . . . . . . . . . . : 10.8.0.2
DHCPv6 IAID . . . . . . . . . . . : 520159153
DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-19-B8-66-B8-A0-1D-48-97-EB-90
DNS Servers . . . . . . . . . . . : 192.168.0.1
NetBIOS over Tcpip. . . . . . . . : Enabled
Ethernet adapter Ethernet:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : HP Ethernet 1Gb 2-port 332i Adapter
Physical Address. . . . . . . . . : A0-1D-48-97-EB-90
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
Link-local IPv6 Address . . . . . : fe80::41b2:d1a:7452:8c11%12(Preferred)
IPv4 Address. . . . . . . . . . . : 192.168.0.180(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.0.1
DHCPv6 IAID . . . . . . . . . . . : 262151496
DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-19-B8-66-B8-A0-1D-48-97-EB-
DNS Servers . . . . . . . . . . . : ::1
192.168.0.1
8.8.8.8
NetBIOS over Tcpip. . . . . . . . : Enabled
Code: Select all
Ethernet adapter Połączenie lokalne:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Realtek PCIe GbE Family Controller
Physical Address. . . . . . . . . : FC-AA-14-72-82-8B
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
Link-local IPv6 Address . . . . . : fe80::ddbf:3626:51ef:d326%11(Preferred)
IPv4 Address. . . . . . . . . . . : 10.5.236.108(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Lease Obtained. . . . . . . . . . : 26 listopada 2019 20:30:08
Lease Expires . . . . . . . . . . : 27 listopada 2019 20:30:06
Default Gateway . . . . . . . . . : 10.5.236.254
DHCP Server . . . . . . . . . . . : 10.5.236.254
DHCPv6 IAID . . . . . . . . . . . : 251439636
DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-1E-14-D2-60-FC-AA-14-72-82-8B
DNS Servers . . . . . . . . . . . : 10.5.236.254
NetBIOS over Tcpip. . . . . . . . : Enabled
Unknown adapter Połączenie lokalne 2:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : TAP-Windows Adapter V9
Physical Address. . . . . . . . . : 00-FF-96-55-51-32
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
Link-local IPv6 Address . . . . . : fe80::65b5:b350:4514:9da1%28(Preferred)
IPv4 Address. . . . . . . . . . . : 10.8.0.6(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.252
Lease Obtained. . . . . . . . . . : 27 listopada 2019 01:50:47
Lease Expires . . . . . . . . . . : 26 listopada 2020 01:50:47
Default Gateway . . . . . . . . . :
DHCP Server . . . . . . . . . . . : 10.8.0.5
DHCPv6 IAID . . . . . . . . . . . : 469827478
DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-1E-14-D2-60-FC-AA-14-72-82-8B
DNS Servers . . . . . . . . . . . : 192.168.0.1
8.8.8.8
NetBIOS over Tcpip. . . . . . . . : Enabled
Code: Select all
C:\Users\Luk>ping 10.8.0.1
Pinging 10.8.0.1 with 32 bytes of data:
Control-C
^C
C:\Users\Luk>ping 192.168.0.180
Pinging 192.168.0.180 with 32 bytes of data:
Control-C
^C
C:\Users\Luk>
Best regards,
Lukasz