OpemVPN on Windows 2016 server standard

Need help configuring your VPN? Just post here and you'll get that help.

Moderators: TinCanTech, TinCanTech, TinCanTech, TinCanTech, TinCanTech, TinCanTech

Forum rules
Please use the [oconf] BB tag for openvpn Configurations. See viewtopic.php?f=30&t=21589 for an example.
Post Reply
mrdebug
OpenVpn Newbie
Posts: 11
Joined: Thu Apr 25, 2013 9:54 am

OpemVPN on Windows 2016 server standard

Post by mrdebug » Sat Feb 27, 2021 11:24 am

Hi, I have a problem with OpenVPN on a Windows 2016 server.
After the server restart OpenVPN does not work. A client can connect, can obtain a valid address but the server is not available. In the server side I see that the tap in terface has got a wrong address: 169.254.66.230 insterad of 10.8.0.1.
In order to resolve the problem (till the next server restart) I have to stop the OpenVPN service, disable the tap interface, reenable the tap interface, restart the OpenVPN service.
Now a client can connect to the server and the tap interface has got the right ip address.
The OpenVPN is the latest stable release.
How can I resolve?

TinCanTech
OpenVPN Protagonist
Posts: 11137
Joined: Fri Jun 03, 2016 1:17 pm

Re: OpemVPN on Windows 2016 server standard

Post by TinCanTech » Sat Feb 27, 2021 3:30 pm

Start the Windows DHCP Client Service

mrdebug
OpenVpn Newbie
Posts: 11
Joined: Thu Apr 25, 2013 9:54 am

Re: OpemVPN on Windows 2016 server standard

Post by mrdebug » Sat Feb 27, 2021 3:39 pm

The dhcp client service in already started in automatic mode at startup.
The OpenVPN service in already in delayed startup mode and it already has got the dhcp client service as dependency.

TinCanTech
OpenVPN Protagonist
Posts: 11137
Joined: Fri Jun 03, 2016 1:17 pm

Re: OpemVPN on Windows 2016 server standard

Post by TinCanTech » Sat Feb 27, 2021 3:41 pm

See your log file for errors

mrdebug
OpenVpn Newbie
Posts: 11
Joined: Thu Apr 25, 2013 9:54 am

Re: OpemVPN on Windows 2016 server standard

Post by mrdebug » Sun Feb 28, 2021 7:16 am

Hi, have a look at the attached log. This is relative at OpenVPN after the server reboot. During this session a client has connected to the server but the server was not avaible because the server address was wrong.

Code: Select all

2021-02-28 08:00:26 WARNING: --topology net30 support for server configs with IPv4 pools will be removed in a future release. Please migrate to --topology subnet as soon as possible.
2021-02-28 08:00:26 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.
2021-02-28 08:00:26 OpenVPN 2.5.0 x86_64-w64-mingw32 [SSL (OpenSSL)] [LZO] [LZ4] [PKCS11] [AEAD] built on Oct 28 2020
2021-02-28 08:00:26 Windows version 10.0 (Windows 10 or greater) 64bit
2021-02-28 08:00:26 library versions: OpenSSL 1.1.1h  22 Sep 2020, LZO 2.10
2021-02-28 08:00:26 NOTE: your local LAN uses the extremely common subnet address 192.168.0.x or 192.168.1.x.  Be aware that this might create routing conflicts if you connect to the VPN server from public locations such as internet cafes that use the same subnet.
2021-02-28 08:00:26 Diffie-Hellman initialized with 2048 bit key
2021-02-28 08:00:26 Outgoing Control Channel Authentication: Using 160 bit message hash 'SHA1' for HMAC authentication
2021-02-28 08:00:26 Incoming Control Channel Authentication: Using 160 bit message hash 'SHA1' for HMAC authentication
2021-02-28 08:00:26 interactive service msg_channel=0
2021-02-28 08:00:26 ROUTE_GATEWAY 192.168.0.254/255.255.255.0 I=11 HWADDR=dc:f4:01:e4:f4:10
2021-02-28 08:00:26 open_tun
2021-02-28 08:00:26 tap-windows6 device [OpenVPN TAP-Windows6] opened
2021-02-28 08:00:26 TAP-Windows Driver Version 9.24 
2021-02-28 08:00:26 Notified TAP-Windows driver to set a DHCP IP/netmask of 10.8.0.1/255.255.255.252 on interface {27C77640-C538-4BDA-A9ED-B7A480CAF22D} [DHCP-serv: 10.8.0.2, lease-time: 31536000]
2021-02-28 08:00:26 Sleeping for 10 seconds...
2021-02-28 08:00:36 Successful ARP Flush on interface [4] {27C77640-C538-4BDA-A9ED-B7A480CAF22D}
2021-02-28 08:00:36 IPv4 MTU set to 1500 on interface 4 using SetIpInterfaceEntry()
2021-02-28 08:00:36 C:\Windows\system32\route.exe ADD 10.8.0.0 MASK 255.255.255.0 10.8.0.2
2021-02-28 08:00:36 Warning: route gateway is not reachable on any active network adapters: 10.8.0.2
2021-02-28 08:00:36 Route addition via IPAPI failed [adaptive]
2021-02-28 08:00:36 Route addition fallback to route.exe
2021-02-28 08:00:36 env_block: add PATH=C:\Windows\System32;C:\Windows;C:\Windows\System32\Wbem
2021-02-28 08:00:36 Could not determine IPv4/IPv6 protocol. Using AF_INET6
2021-02-28 08:00:36 Socket Buffers: R=[65536->65536] S=[65536->65536]
2021-02-28 08:00:36 setsockopt(IPV6_V6ONLY=0)
2021-02-28 08:00:36 UDPv6 link local (bound): [AF_INET6][undef]:1194
2021-02-28 08:00:36 UDPv6 link remote: [AF_UNSPEC]
2021-02-28 08:00:36 MULTI: multi_init called, r=256 v=256
2021-02-28 08:00:36 IFCONFIG POOL IPv4: base=10.8.0.4 size=62
2021-02-28 08:00:36 ifconfig_pool_read(), in='home.denis,10.8.0.4,'
2021-02-28 08:00:36 succeeded -> ifconfig_pool_set(hand=0)
2021-02-28 08:00:36 ifconfig_pool_read(), in='pc09,10.8.0.8,'
2021-02-28 08:00:36 succeeded -> ifconfig_pool_set(hand=1)
2021-02-28 08:00:36 ifconfig_pool_read(), in='home.laura,10.8.0.12,'
2021-02-28 08:00:36 succeeded -> ifconfig_pool_set(hand=2)
2021-02-28 08:00:36 IFCONFIG POOL LIST
2021-02-28 08:00:36 home.denis,10.8.0.4,
2021-02-28 08:00:36 pc09,10.8.0.8,
2021-02-28 08:00:36 home.laura,10.8.0.12,
2021-02-28 08:00:36 Initialization Sequence Completed
2021-02-28 08:04:57 87.8.176.74:63047 Outgoing Control Channel Authentication: Using 160 bit message hash 'SHA1' for HMAC authentication
2021-02-28 08:04:57 87.8.176.74:63047 Incoming Control Channel Authentication: Using 160 bit message hash 'SHA1' for HMAC authentication
2021-02-28 08:04:57 87.8.176.74:63047 TLS: Initial packet from [AF_INET6]::ffff:87.8.176.74:63047, sid=14469f2d d03a95b8
2021-02-28 08:04:57 87.8.176.74:63047 VERIFY OK: depth=0, C=IT, ST=PD, L=XXXXXX, O=XXXXXXXX, OU=changeme, CN=home.denis, name=changeme, emailAddress=XXXXXXXXXXXXXXXXXXXXXXXXX
2021-02-28 08:04:57 87.8.176.74:63047 peer info: IV_VER=2.4.9
2021-02-28 08:04:57 87.8.176.74:63047 peer info: IV_PLAT=win
2021-02-28 08:04:57 87.8.176.74:63047 peer info: IV_PROTO=2
2021-02-28 08:04:57 87.8.176.74:63047 peer info: IV_NCP=2
2021-02-28 08:04:57 87.8.176.74:63047 peer info: IV_LZ4=1
2021-02-28 08:04:57 87.8.176.74:63047 peer info: IV_LZ4v2=1
2021-02-28 08:04:57 87.8.176.74:63047 peer info: IV_LZO=1
2021-02-28 08:04:57 87.8.176.74:63047 peer info: IV_COMP_STUB=1
2021-02-28 08:04:57 87.8.176.74:63047 peer info: IV_COMP_STUBv2=1
2021-02-28 08:04:57 87.8.176.74:63047 peer info: IV_TCPNL=1
2021-02-28 08:04:57 87.8.176.74:63047 peer info: IV_GUI_VER=OpenVPN_GUI_11
2021-02-28 08:04:57 87.8.176.74:63047 Control Channel: TLSv1.3, cipher TLSv1.3 TLS_AES_256_GCM_SHA384, 4096 bit RSA
2021-02-28 08:04:57 87.8.176.74:63047 [home.denis] Peer Connection Initiated with [AF_INET6]::ffff:87.8.176.74:63047
2021-02-28 08:04:57 home.denis/87.8.176.74:63047 MULTI_sva: pool returned IPv4=10.8.0.6, IPv6=(Not enabled)
2021-02-28 08:04:57 home.denis/87.8.176.74:63047 MULTI: Learn: 10.8.0.6 -> home.denis/87.8.176.74:63047
2021-02-28 08:04:57 home.denis/87.8.176.74:63047 MULTI: primary virtual IP for home.denis/87.8.176.74:63047: 10.8.0.6
2021-02-28 08:04:57 home.denis/87.8.176.74:63047 Data Channel: using negotiated cipher 'AES-256-GCM'
2021-02-28 08:04:57 home.denis/87.8.176.74:63047 Outgoing Data Channel: Cipher 'AES-256-GCM' initialized with 256 bit key
2021-02-28 08:04:57 home.denis/87.8.176.74:63047 Incoming Data Channel: Cipher 'AES-256-GCM' initialized with 256 bit key
2021-02-28 08:04:58 home.denis/87.8.176.74:63047 PUSH: Received control message: 'PUSH_REQUEST'
2021-02-28 08:04:58 home.denis/87.8.176.74:63047 SENT CONTROL [home.denis]: 'PUSH_REPLY,route 10.8.0.1,topology net30,ping 10,ping-restart 120,ifconfig 10.8.0.6 10.8.0.5,peer-id 0,cipher AES-256-GCM' (status=1)
2021-02-28 08:06:47 SENT CONTROL [home.denis]: 'RESTART' (status=1)
2021-02-28 08:06:47 C:\Windows\system32\route.exe DELETE 10.8.0.0 MASK 255.255.255.0 10.8.0.2
2021-02-28 08:06:47 ROUTE: route deletion failed using DeleteIpForwardEntry: Impossibile trovare elemento.  
2021-02-28 08:06:47 Route deletion via IPAPI failed [adaptive]
2021-02-28 08:06:47 Route deletion fallback to route.exe
2021-02-28 08:06:47 env_block: add PATH=C:\Windows\System32;C:\Windows;C:\Windows\System32\Wbem
2021-02-28 08:06:47 Closing TUN/TAP interface
2021-02-28 08:06:48 TAP: DHCP address released
2021-02-28 08:06:48 SIGTERM[hard,] received, process exiting
Last edited by Pippin on Sun Feb 28, 2021 11:55 am, edited 1 time in total.
Reason: Formatting

TinCanTech
OpenVPN Protagonist
Posts: 11137
Joined: Fri Jun 03, 2016 1:17 pm

Re: OpemVPN on Windows 2016 server standard

Post by TinCanTech » Sun Feb 28, 2021 4:21 pm

Please post your server config file.

mrdebug
OpenVpn Newbie
Posts: 11
Joined: Thu Apr 25, 2013 9:54 am

Re: OpemVPN on Windows 2016 server standard

Post by mrdebug » Mon Mar 01, 2021 8:07 pm

#################################################
# 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\\easy-rsa\\keys\\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"

# 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 208.67.222.222"
;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.
# 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
Last edited by Pippin on Wed Mar 03, 2021 1:42 pm, edited 2 times in total.
Reason: Undo formatting

TinCanTech
OpenVPN Protagonist
Posts: 11137
Joined: Fri Jun 03, 2016 1:17 pm

Re: OpemVPN on Windows 2016 server standard

Post by TinCanTech » Mon Mar 01, 2021 9:15 pm

Replace "proto udp" with "proto udp4"

TinCanTech
OpenVPN Protagonist
Posts: 11137
Joined: Fri Jun 03, 2016 1:17 pm

Re: OpemVPN on Windows 2016 server standard

Post by TinCanTech » Tue Mar 02, 2021 3:43 pm

@ mrdebug - What is the result of the change ?

@ Pippin - By editing the users post you have lost the essential nature of the config.
It is no longer obvious that the user is using the sample server.conf file ...
I have made this point before, by editing all the user posts you loose some information.
I appreciate you enclosing logs in <code> braces but the constant yse of <oconf> is not so helpful.

mrdebug
OpenVpn Newbie
Posts: 11
Joined: Thu Apr 25, 2013 9:54 am

Re: OpenVPN on Windows 2016 server standard

Post by mrdebug » Fri Mar 05, 2021 8:25 pm

Sorry but does not resolve.

TinCanTech
OpenVPN Protagonist
Posts: 11137
Joined: Fri Jun 03, 2016 1:17 pm

Re: OpemVPN on Windows 2016 server standard

Post by TinCanTech » Fri Mar 05, 2021 8:56 pm

Can you post your log file ?

mrdebug
OpenVpn Newbie
Posts: 11
Joined: Thu Apr 25, 2013 9:54 am

Re: OpemVPN on Windows 2016 server standard

Post by mrdebug » Sat Mar 06, 2021 7:50 am

2021-03-05 21:18:51 WARNING: --topology net30 support for server configs with IPv4 pools will be removed in a future release. Please migrate to --topology subnet as soon as possible.
2021-03-05 21:18:51 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.
2021-03-05 21:18:51 OpenVPN 2.5.0 x86_64-w64-mingw32 [SSL (OpenSSL)] [LZO] [LZ4] [PKCS11] [AEAD] built on Oct 28 2020
2021-03-05 21:18:51 Windows version 10.0 (Windows 10 or greater) 64bit
2021-03-05 21:18:51 library versions: OpenSSL 1.1.1h 22 Sep 2020, LZO 2.10
2021-03-05 21:18:51 NOTE: your local LAN uses the extremely common subnet address 192.168.0.x or 192.168.1.x. Be aware that this might create routing conflicts if you connect to the VPN server from public locations such as internet cafes that use the same subnet.
2021-03-05 21:18:51 Diffie-Hellman initialized with 2048 bit key
2021-03-05 21:18:51 Outgoing Control Channel Authentication: Using 160 bit message hash 'SHA1' for HMAC authentication
2021-03-05 21:18:51 Incoming Control Channel Authentication: Using 160 bit message hash 'SHA1' for HMAC authentication
2021-03-05 21:18:51 interactive service msg_channel=0
2021-03-05 21:18:51 ROUTE_GATEWAY 192.168.0.254/255.255.255.0 I=11 HWADDR=dc:f4:01:e4:f4:10
2021-03-05 21:18:51 open_tun
2021-03-05 21:18:51 tap-windows6 device [OpenVPN TAP-Windows6] opened
2021-03-05 21:18:51 TAP-Windows Driver Version 9.24
2021-03-05 21:18:51 Notified TAP-Windows driver to set a DHCP IP/netmask of 10.8.0.1/255.255.255.252 on interface {27C77640-C538-4BDA-A9ED-B7A480CAF22D} [DHCP-serv: 10.8.0.2, lease-time: 31536000]
2021-03-05 21:18:51 Sleeping for 10 seconds...
2021-03-05 21:19:01 Successful ARP Flush on interface [4] {27C77640-C538-4BDA-A9ED-B7A480CAF22D}
2021-03-05 21:19:01 IPv4 MTU set to 1500 on interface 4 using SetIpInterfaceEntry()
2021-03-05 21:19:01 C:\Windows\system32\route.exe ADD 10.8.0.0 MASK 255.255.255.0 10.8.0.2
2021-03-05 21:19:01 ROUTE: CreateIpForwardEntry succeeded with dwForwardMetric1=25 and dwForwardType=4
2021-03-05 21:19:01 Route addition via IPAPI succeeded [adaptive]
2021-03-05 21:19:01 Could not determine IPv4/IPv6 protocol. Using AF_INET6
2021-03-05 21:19:01 Socket Buffers: R=[65536->65536] S=[65536->65536]
2021-03-05 21:19:01 setsockopt(IPV6_V6ONLY=0)
2021-03-05 21:19:01 UDPv6 link local (bound): [AF_INET6][undef]:1194
2021-03-05 21:19:01 UDPv6 link remote: [AF_UNSPEC]
2021-03-05 21:19:01 MULTI: multi_init called, r=256 v=256
2021-03-05 21:19:01 IFCONFIG POOL IPv4: base=10.8.0.4 size=62
2021-03-05 21:19:01 ifconfig_pool_read(), in='home.denis,10.8.0.4,'
2021-03-05 21:19:01 succeeded -> ifconfig_pool_set(hand=0)
2021-03-05 21:19:01 ifconfig_pool_read(), in='pc09,10.8.0.8,'
2021-03-05 21:19:01 succeeded -> ifconfig_pool_set(hand=1)
2021-03-05 21:19:01 ifconfig_pool_read(), in='home.laura,10.8.0.12,'
2021-03-05 21:19:01 succeeded -> ifconfig_pool_set(hand=2)
2021-03-05 21:19:01 ifconfig_pool_read(), in='pc05,10.8.0.16,'
2021-03-05 21:19:01 succeeded -> ifconfig_pool_set(hand=3)
2021-03-05 21:19:01 IFCONFIG POOL LIST
2021-03-05 21:19:01 home.denis,10.8.0.4,
2021-03-05 21:19:01 pc09,10.8.0.8,
2021-03-05 21:19:01 home.laura,10.8.0.12,
2021-03-05 21:19:01 pc05,10.8.0.16,
2021-03-05 21:19:01 Initialization Sequence Completed
2021-03-05 21:19:09 87.8.176.74:49235 Outgoing Control Channel Authentication: Using 160 bit message hash 'SHA1' for HMAC authentication
2021-03-05 21:19:09 87.8.176.74:49235 Incoming Control Channel Authentication: Using 160 bit message hash 'SHA1' for HMAC authentication
2021-03-05 21:19:09 87.8.176.74:49235 TLS: Initial packet from [AF_INET6]::ffff:87.8.176.74:49235, sid=e228661b bcd52745
2021-03-05 21:19:09 87.8.176.74:49235 VERIFY OK: depth=0, C=IT, ST=PD, L=XXXXXXXXXXXXXXX, O=XXXXXXX, OU=changeme, CN=home.denis, name=changeme, emailAddress=XXXXXXXXXXXXXXXX
2021-03-05 21:19:09 87.8.176.74:49235 peer info: IV_VER=2.4.9
2021-03-05 21:19:09 87.8.176.74:49235 peer info: IV_PLAT=win
2021-03-05 21:19:09 87.8.176.74:49235 peer info: IV_PROTO=2
2021-03-05 21:19:09 87.8.176.74:49235 peer info: IV_NCP=2
2021-03-05 21:19:09 87.8.176.74:49235 peer info: IV_LZ4=1
2021-03-05 21:19:09 87.8.176.74:49235 peer info: IV_LZ4v2=1
2021-03-05 21:19:09 87.8.176.74:49235 peer info: IV_LZO=1
2021-03-05 21:19:09 87.8.176.74:49235 peer info: IV_COMP_STUB=1
2021-03-05 21:19:09 87.8.176.74:49235 peer info: IV_COMP_STUBv2=1
2021-03-05 21:19:09 87.8.176.74:49235 peer info: IV_TCPNL=1
2021-03-05 21:19:09 87.8.176.74:49235 peer info: IV_GUI_VER=OpenVPN_GUI_11
2021-03-05 21:19:09 87.8.176.74:49235 Control Channel: TLSv1.3, cipher TLSv1.3 TLS_AES_256_GCM_SHA384, 4096 bit RSA
2021-03-05 21:19:09 87.8.176.74:49235 [home.denis] Peer Connection Initiated with [AF_INET6]::ffff:87.8.176.74:49235
2021-03-05 21:19:09 home.denis/87.8.176.74:49235 MULTI_sva: pool returned IPv4=10.8.0.6, IPv6=(Not enabled)
2021-03-05 21:19:09 home.denis/87.8.176.74:49235 MULTI: Learn: 10.8.0.6 -> home.denis/87.8.176.74:49235
2021-03-05 21:19:09 home.denis/87.8.176.74:49235 MULTI: primary virtual IP for home.denis/87.8.176.74:49235: 10.8.0.6
2021-03-05 21:19:09 home.denis/87.8.176.74:49235 Data Channel: using negotiated cipher 'AES-256-GCM'
2021-03-05 21:19:09 home.denis/87.8.176.74:49235 Outgoing Data Channel: Cipher 'AES-256-GCM' initialized with 256 bit key
2021-03-05 21:19:09 home.denis/87.8.176.74:49235 Incoming Data Channel: Cipher 'AES-256-GCM' initialized with 256 bit key
2021-03-05 21:19:11 home.denis/87.8.176.74:49235 PUSH: Received control message: 'PUSH_REQUEST'
2021-03-05 21:19:11 home.denis/87.8.176.74:49235 SENT CONTROL [home.denis]: 'PUSH_REPLY,route 10.8.0.1,topology net30,ping 10,ping-restart 120,ifconfig 10.8.0.6 10.8.0.5,peer-id 0,cipher AES-256-GCM' (status=1)
2021-03-05 21:25:37 home.denis/87.8.176.74:49235 [home.denis] Inactivity timeout (--ping-restart), restarting
2021-03-05 21:25:37 home.denis/87.8.176.74:49235 SIGUSR1[soft,ping-restart] received, client-instance restarting
2021-03-05 21:54:03 TLS Error: cannot locate HMAC in incoming packet from [AF_INET6]::ffff:185.200.118.84:53974
2021-03-05 23:21:19 TLS Error: cannot locate HMAC in incoming packet from [AF_INET6]::ffff:209.141.47.222:41048
2021-03-06 04:17:38 TLS Error: cannot locate HMAC in incoming packet from [AF_INET6]::ffff:146.88.240.4:45663

TinCanTech
OpenVPN Protagonist
Posts: 11137
Joined: Fri Jun 03, 2016 1:17 pm

Re: OpemVPN on Windows 2016 server standard

Post by TinCanTech » Sat Mar 06, 2021 2:13 pm

mrdebug wrote:
Sun Feb 28, 2021 7:16 am
2021-02-28 08:00:36 C:\Windows\system32\route.exe ADD 10.8.0.0 MASK 255.255.255.0 10.8.0.2
2021-02-28 08:00:36 Warning: route gateway is not reachable on any active network adapters: 10.8.0.2
2021-02-28 08:00:36 Route addition via IPAPI failed [adaptive]
1st log.

mrdebug wrote:
Sat Mar 06, 2021 7:50 am
2021-03-05 21:19:01 C:\Windows\system32\route.exe ADD 10.8.0.0 MASK 255.255.255.0 10.8.0.2
2021-03-05 21:19:01 ROUTE: CreateIpForwardEntry succeeded with dwForwardMetric1=25 and dwForwardType=4
2021-03-05 21:19:01 Route addition via IPAPI succeeded [adaptive]
2nd log.

LGTM

mrdebug
OpenVpn Newbie
Posts: 11
Joined: Thu Apr 25, 2013 9:54 am

Re: OpemVPN on Windows 2016 server standard

Post by mrdebug » Sat Mar 06, 2021 3:26 pm

As explained above, after the server reboot the first connection goes to failure. (first log). So I have to stop the OpenVPN service, disable the interface, enable the interface, start the openVPN service.
After that the connections end correctly (second log).

TinCanTech
OpenVPN Protagonist
Posts: 11137
Joined: Fri Jun 03, 2016 1:17 pm

Re: OpemVPN on Windows 2016 server standard

Post by TinCanTech » Sat Mar 06, 2021 4:15 pm

OK.

Try adding this to your server config:

Code: Select all

dhcp-renew

300000
OpenVPN Expert
Posts: 685
Joined: Tue May 01, 2012 9:30 pm

Re: OpemVPN on Windows 2016 server standard

Post by 300000 » Sat Mar 06, 2021 5:52 pm

cipher AES-128-CBC
auth SHA256

check the line here to see if your client have it or not. something wrong with certificate not windows dhcp, in your client should have that line to make it works.

TLS Error: cannot locate HMAC in incoming packet from [AF_INET6]::ffff:146.88.240.4:45663

mrdebug
OpenVpn Newbie
Posts: 11
Joined: Thu Apr 25, 2013 9:54 am

Re: OpemVPN on Windows 2016 server standard

Post by mrdebug » Sat Mar 06, 2021 5:52 pm

Seems to be solved

TinCanTech
OpenVPN Protagonist
Posts: 11137
Joined: Fri Jun 03, 2016 1:17 pm

Re: OpemVPN on Windows 2016 server standard

Post by TinCanTech » Sat Mar 06, 2021 7:32 pm

300000 wrote:
Sat Mar 06, 2021 5:52 pm
cipher AES-128-CBC
auth SHA256

check the line here to see if your client have it or not. something wrong with certificate not windows dhcp, in your client should have that line to make it works.
If this were true then the client would simply fail to connect, Always.
300000 wrote:
Sat Mar 06, 2021 5:52 pm
TLS Error: cannot locate HMAC in incoming packet from [AF_INET6]::ffff:146.88.240.4:45663
Because the client has already timed out due to:
mrdebug wrote:
Sat Mar 06, 2021 7:50 am
2021-03-05 21:25:37 home.denis/87.8.176.74:49235 [home.denis] Inactivity timeout (--ping-restart), restarting
2021-03-05 21:25:37 home.denis/87.8.176.74:49235 SIGUSR1[soft,ping-restart] received, client-instance restarting

300000
OpenVPN Expert
Posts: 685
Joined: Tue May 01, 2012 9:30 pm

Re: OpemVPN on Windows 2016 server standard

Post by 300000 » Sat Mar 06, 2021 7:45 pm

mrdebug wrote:
Sat Mar 06, 2021 5:52 pm
Seems to be solved
It works now simple that is all

Post Reply