Я пытаюсь настроить VPN с OpenVPN, используя Windows Server 2016 в качестве VPN-сервера.
Я могу успешно подключиться к VPN, но затем не могу связаться или пропинговать что-либо на стороне локальной сети, ни сервер, ни какое-либо устройство в локальной сети.
Я следовал этому руководству, чтобы настроить все статические маршруты и пересылку пакетов с обеих сторон, но это все равно не работает.
Это моя конфигурация сервера OpenVPN (Windows Server 2016):
#################################################
# 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 udp4
# "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" # This file should be kept secret
# 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.2.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"
push "dhcp-option DNS 192.168.2.117"
push "dhcp-option DOMAIN femarimpianti.local"
push "dhcp-option SEARCH femarimpianti.local"
# 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
И это моя конфигурация клиента Open VPN (Linux Debian, но я тоже пробовал Windows10):
##############################################
# 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 udp4
# The hostname/IP and port of the server.
# You can have multiple remote entries
# to load balance between the servers.
remote portale.femarimpianti.it 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 /etc/openvpn/client/femar-ca.crt
cert /etc/openvpn/client/StefanoCampanella.crt
key /etc/openvpn/client/StefanoCampanella.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 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
Когда я подключаюсь, это журнал моего сервера:
Sat Mar 02 13:17:25 2019 OpenVPN 2.4.6 x86_64-w64-mingw32 [SSL (OpenSSL)] [LZO] [LZ4] [PKCS11] [AEAD] built on Apr 26 2018
Sat Mar 02 13:17:25 2019 Windows version 6.2 (Windows 8 or greater) 64bit
Sat Mar 02 13:17:25 2019 library versions: OpenSSL 1.1.0h 27 Mar 2018, LZO 2.10
Sat Mar 02 13:17:25 2019 Diffie-Hellman initialized with 2048 bit key
Sat Mar 02 13:17:25 2019 interactive service msg_channel=0
Sat Mar 02 13:17:25 2019 open_tun
Sat Mar 02 13:17:25 2019 TAP-WIN32 device [Ethernet 2] opened: \\.\Global\{023A86A7-D4C0-408D-BCEF-7C63C4D61DB9}.tap
Sat Mar 02 13:17:25 2019 TAP-Windows Driver Version 9.21
Sat Mar 02 13:17:25 2019 Set TAP-Windows TUN subnet mode network/local/netmask = 10.8.0.0/10.8.0.1/255.255.255.0 [SUCCEEDED]
Sat Mar 02 13:17:25 2019 Notified TAP-Windows driver to set a DHCP IP/netmask of 10.8.0.1/255.255.255.0 on interface {023A86A7-D4C0-408D-BCEF-7C63C4D61DB9} [DHCP-serv: 10.8.0.254, lease-time: 31536000]
Sat Mar 02 13:17:25 2019 Sleeping for 10 seconds...
Sat Mar 02 13:17:35 2019 Successful ARP Flush on interface [2] {023A86A7-D4C0-408D-BCEF-7C63C4D61DB9}
Sat Mar 02 13:17:35 2019 do_ifconfig, tt->did_ifconfig_ipv6_setup=0
Sat Mar 02 13:17:35 2019 Socket Buffers: R=[65536->65536] S=[65536->65536]
Sat Mar 02 13:17:35 2019 UDPv4 link local (bound): [AF_INET][undef]:1194
Sat Mar 02 13:17:35 2019 UDPv4 link remote: [AF_UNSPEC]
Sat Mar 02 13:17:35 2019 MULTI: multi_init called, r=256 v=256
Sat Mar 02 13:17:35 2019 IFCONFIG POOL: base=10.8.0.2 size=252, ipv6=0
Sat Mar 02 13:17:35 2019 ifconfig_pool_read(), in='StefanoCampanella,10.8.0.4', TODO: IPv6
Sat Mar 02 13:17:35 2019 succeeded -> ifconfig_pool_set()
Sat Mar 02 13:17:35 2019 IFCONFIG POOL LIST
Sat Mar 02 13:17:35 2019 StefanoCampanella,10.8.0.4
Sat Mar 02 13:17:35 2019 Initialization Sequence Completed
Sat Mar 02 13:19:20 2019 151.36.250.252:41444 TLS: Initial packet from [AF_INET]151.36.250.252:41444, sid=620a3767 13d56a0f
Sat Mar 02 13:19:20 2019 151.36.250.252:41444 VERIFY OK: <CENSORED INFO>
Sat Mar 02 13:19:20 2019 151.36.250.252:41444 VERIFY OK: <CENSORED INFO>
Sat Mar 02 13:19:20 2019 151.36.250.252:41444 peer info: IV_VER=2.4.0
Sat Mar 02 13:19:20 2019 151.36.250.252:41444 peer info: IV_PLAT=linux
Sat Mar 02 13:19:20 2019 151.36.250.252:41444 peer info: IV_PROTO=2
Sat Mar 02 13:19:20 2019 151.36.250.252:41444 peer info: IV_NCP=2
Sat Mar 02 13:19:20 2019 151.36.250.252:41444 peer info: IV_LZ4=1
Sat Mar 02 13:19:20 2019 151.36.250.252:41444 peer info: IV_LZ4v2=1
Sat Mar 02 13:19:20 2019 151.36.250.252:41444 peer info: IV_LZO=1
Sat Mar 02 13:19:20 2019 151.36.250.252:41444 peer info: IV_COMP_STUB=1
Sat Mar 02 13:19:20 2019 151.36.250.252:41444 peer info: IV_COMP_STUBv2=1
Sat Mar 02 13:19:20 2019 151.36.250.252:41444 peer info: IV_TCPNL=1
Sat Mar 02 13:19:20 2019 151.36.250.252:41444 Control Channel: TLSv1.2, cipher TLSv1.2 ECDHE-RSA-AES256-GCM-SHA384, 4096 bit RSA
Sat Mar 02 13:19:20 2019 151.36.250.252:41444 [StefanoCampanella] Peer Connection Initiated with [AF_INET]151.36.250.252:41444
Sat Mar 02 13:19:20 2019 StefanoCampanella/151.36.250.252:41444 MULTI_sva: pool returned IPv4=10.8.0.4, IPv6=(Not enabled)
Sat Mar 02 13:19:20 2019 StefanoCampanella/151.36.250.252:41444 MULTI: Learn: 10.8.0.4 -> StefanoCampanella/151.36.250.252:41444
Sat Mar 02 13:19:20 2019 StefanoCampanella/151.36.250.252:41444 MULTI: primary virtual IP for StefanoCampanella/151.36.250.252:41444: 10.8.0.4
Sat Mar 02 13:19:21 2019 StefanoCampanella/151.36.250.252:41444 PUSH: Received control message: 'PUSH_REQUEST'
Sat Mar 02 13:19:21 2019 StefanoCampanella/151.36.250.252:41444 SENT CONTROL [StefanoCampanella]: 'PUSH_REPLY,route 192.168.2.0 255.255.255.0,dhcp-option DNS 192.168.2.117,dhcp-option DOMAIN femarimpianti.local,dhcp-option SEARCH femarimpianti.local,route-gateway 10.8.0.1,topology subnet,ping 10,ping-restart 120,ifconfig 10.8.0.4 255.255.255.0,peer-id 0,cipher AES-256-GCM' (status=1)
Sat Mar 02 13:19:21 2019 StefanoCampanella/151.36.250.252:41444 Data Channel: using negotiated cipher 'AES-256-GCM'
Sat Mar 02 13:19:21 2019 StefanoCampanella/151.36.250.252:41444 Outgoing Data Channel: Cipher 'AES-256-GCM' initialized with 256 bit key
Sat Mar 02 13:19:21 2019 StefanoCampanella/151.36.250.252:41444 Incoming Data Channel: Cipher 'AES-256-GCM' initialized with 256 bit key
Sat Mar 02 13:45:47 2019 StefanoCampanella/151.36.250.252:41444 [StefanoCampanella] Inactivity timeout (--ping-restart), restarting
Sat Mar 02 13:45:47 2019 StefanoCampanella/151.36.250.252:41444 SIGUSR1[soft,ping-restart] received, client-instance restarting
И это журнал моего клиента:
Sat Mar 2 13:19:19 2019 OpenVPN 2.4.0 x86_64-pc-linux-gnu [SSL (OpenSSL)] [LZO] [LZ4] [EPOLL] [PKCS11] [MH/PKTINFO] [AEAD] built on Oct 14 2018
Sat Mar 2 13:19:19 2019 library versions: OpenSSL 1.0.2q 20 Nov 2018, LZO 2.08
Sat Mar 2 13:19:20 2019 TCP/UDP: Preserving recently used remote address: [AF_INET]176.57.114.197:1194
Sat Mar 2 13:19:20 2019 Socket Buffers: R=[212992->212992] S=[212992->212992]
Sat Mar 2 13:19:20 2019 UDPv4 link local: (not bound)
Sat Mar 2 13:19:20 2019 UDPv4 link remote: [AF_INET]176.57.114.197:1194
Sat Mar 2 13:19:20 2019 TLS: Initial packet from [AF_INET]176.57.114.197:1194, sid=01759675 024829a8
Sat Mar 2 13:19:20 2019 VERIFY OK: depth=1, C=IT, ST=MI, L=Milan, O=FemarImpianti, OU=ICT, CN=Femar, name=Server, emailAddress=femar@femarimpianti.it
Sat Mar 2 13:19:20 2019 Validating certificate key usage
Sat Mar 2 13:19:20 2019 ++ Certificate has key usage 00a0, expects 00a0
Sat Mar 2 13:19:20 2019 VERIFY KU OK
Sat Mar 2 13:19:20 2019 Validating certificate extended key usage
Sat Mar 2 13:19:20 2019 ++ Certificate has EKU (str) TLS Web Server Authentication, expects TLS Web Server Authentication
Sat Mar 2 13:19:20 2019 VERIFY EKU OK
Sat Mar 2 13:19:20 2019 VERIFY OK: depth=0, C=IT, ST=MI, L=Milan, O=FemarImpianti, OU=ICT, CN=server, name=server, emailAddress=femar@femarimpianti.it
Sat Mar 2 13:19:20 2019 Control Channel: TLSv1.2, cipher TLSv1/SSLv3 ECDHE-RSA-AES256-GCM-SHA384, 4096 bit RSA
Sat Mar 2 13:19:20 2019 [server] Peer Connection Initiated with [AF_INET]176.57.114.197:1194
Sat Mar 2 13:19:21 2019 SENT CONTROL [server]: 'PUSH_REQUEST' (status=1)
Sat Mar 2 13:19:21 2019 PUSH: Received control message: 'PUSH_REPLY,route 192.168.2.0 255.255.255.0,dhcp-option DNS 192.168.2.117,dhcp-option DOMAIN femarimpianti.local,dhcp-option SEARCH femarimpianti.local,route-gateway 10.8.0.1,topology subnet,ping 10,ping-restart 120,ifconfig 10.8.0.4 255.255.255.0,peer-id 0,cipher AES-256-GCM'
Sat Mar 2 13:19:21 2019 OPTIONS IMPORT: timers and/or timeouts modified
Sat Mar 2 13:19:21 2019 OPTIONS IMPORT: --ifconfig/up options modified
Sat Mar 2 13:19:21 2019 OPTIONS IMPORT: route options modified
Sat Mar 2 13:19:21 2019 OPTIONS IMPORT: route-related options modified
Sat Mar 2 13:19:21 2019 OPTIONS IMPORT: --ip-win32 and/or --dhcp-option options modified
Sat Mar 2 13:19:21 2019 OPTIONS IMPORT: peer-id set
Sat Mar 2 13:19:21 2019 OPTIONS IMPORT: adjusting link_mtu to 1624
Sat Mar 2 13:19:21 2019 OPTIONS IMPORT: data channel crypto options modified
Sat Mar 2 13:19:21 2019 Data Channel Encrypt: Cipher 'AES-256-GCM' initialized with 256 bit key
Sat Mar 2 13:19:21 2019 Data Channel Decrypt: Cipher 'AES-256-GCM' initialized with 256 bit key
Sat Mar 2 13:19:21 2019 ROUTE_GATEWAY 192.168.43.1/255.255.255.0 IFACE=wlp3s0 HWADDR=f8:59:71:5a:55:8c
Sat Mar 2 13:19:21 2019 TUN/TAP device tun0 opened
Sat Mar 2 13:19:21 2019 TUN/TAP TX queue length set to 100
Sat Mar 2 13:19:21 2019 do_ifconfig, tt->did_ifconfig_ipv6_setup=0
Sat Mar 2 13:19:21 2019 /sbin/ip link set dev tun0 up mtu 1500
Sat Mar 2 13:19:21 2019 /sbin/ip addr add dev tun0 10.8.0.4/24 broadcast 10.8.0.255
Sat Mar 2 13:19:21 2019 /sbin/ip route add 192.168.2.0/24 via 10.8.0.1
Sat Mar 2 13:19:21 2019 Initialization Sequence Completed
Клиент сообщает эту таблицу маршрутизации:
default via 192.168.43.1 dev wlp3s0 proto static metric 600
10.8.0.0/24 dev tun0 proto kernel scope link src 10.8.0.4
169.254.0.0/16 dev wlp3s0 scope link metric 1000
192.168.2.0/24 via 10.8.0.1 dev tun0
192.168.43.0/24 dev wlp3s0 proto kernel scope link src 192.168.43.80 metric 600
И мне кажется правильным, трафик на адреса VPN перенаправляется на интерфейс настройки и трафик на LAN (192.168.2. *).
Таблица маршрутизации сервера печати не показывает никаких правил о сетях VPN (не так ли?) но другие устройства в локальной сети правильно имеют статическое правило для маршрутизации пакетов до 10.8.0. * на сервер VPN.
Теперь ... если я должен угадать, в чем проблема, я бы сказал, что это настройка маршрутизации / пересылки сервера или что-то связанное с брандмауэрами (брандмауэр Windows на сервере отключен), но я не знаю, чего не хватает