Форум русскоязычного сообщества Ubuntu


Считаете, что Ubuntu недостаточно дружелюбна к новичкам?
Помогите создать новое Руководство для новичков!

Автор Тема: Ubuntu 20.04+OpenVPN не хочет подключатся (VPN серв. работает, порт слушает)  (Прочитано 2280 раз)

0 Пользователей и 1 Гость просматривают эту тему.

Оффлайн TATOSHCKA_2022

  • Автор темы
  • Новичок
  • *
  • Сообщений: 5
    • Просмотр профиля
Всем, добрый день.

Поднял я OpenVPN.
Сервер работает.

sudo systemctl status openvpn-server@server.service
* openvpn-server@server.service - OpenVPN service for server
     Loaded: loaded (/lib/systemd/system/openvpn-server@.service; enabled; vendor preset: enabled)
     Active: active (running) since Sat 2022-03-19 19:26:21 MSK; 17min ago
       Docs: man:openvpn(8)
             https://community.openvpn.net/openvpn/wiki/Openvpn24ManPage
             https://community.openvpn.net/openvpn/wiki/HOWTO
   Main PID: 444 (openvpn)
     Status: "Initialization Sequence Completed"
      Tasks: 1 (limit: 499)
     Memory: 3.7M
     CGroup: /system.slice/system-openvpn\x2dserver.slice/openvpn-server@server.service
             `-444 /usr/sbin/openvpn --status /run/openvpn-server/status-server.log --status-version 2 --suppress-timestamps --config server.conf

Mar 19 19:26:21 vds2219655.my-ihor.ru openvpn[444]: MULTI: TCP INIT maxclients=1024 maxevents=1028
Mar 19 19:26:21 vds2219655.my-ihor.ru openvpn[444]: Initialization Sequence Completed
Mar 19 19:38:58 vds2219655.my-ihor.ru openvpn[444]: Outgoing Control Channel Encryption: Cipher 'AES-256-CTR' initialized with 256 bit key
Mar 19 19:38:58 vds2219655.my-ihor.ru openvpn[444]: Outgoing Control Channel Encryption: Using 256 bit message hash 'SHA256' for HMAC authentication
Mar 19 19:38:58 vds2219655.my-ihor.ru openvpn[444]: Incoming Control Channel Encryption: Cipher 'AES-256-CTR' initialized with 256 bit key
Mar 19 19:38:58 vds2219655.my-ihor.ru openvpn[444]: Incoming Control Channel Encryption: Using 256 bit message hash 'SHA256' for HMAC authentication
Mar 19 19:38:58 vds2219655.my-ihor.ru openvpn[444]: TCP connection established with [AF_INET]103.121.89.201:50296
Mar 19 19:38:58 vds2219655.my-ihor.ru openvpn[444]: 103.121.89.201:50296 WARNING: Bad encapsulated packet length from peer (18245), which must be > 0 and <= 1626 -- please ensure that --tun-mtu or --link-mtu is equal on both peers -- th>
Mar 19 19:38:58 vds2219655.my-ihor.ru openvpn[444]: 103.121.89.201:50296 Connection reset, restarting [0]
Mar 19 19:38:58 vds2219655.my-ihor.ru openvpn[444]: 103.121.89.201:50296 SIGUSR1[soft,connection-reset] received, client-instance restarting

В конфиге прописан tcp 81 порт. (Пробывал разные upd, tcp).

Порт слушает:

stebus@vds2219655:~$ netstat -ntlp | grep LISTEN
(Not all processes could be identified, non-owned process info
 will not be shown, you would have to be root to see it all.)
tcp        0      0 0.0.0.0:80              0.0.0.0:*               LISTEN      -
tcp        0      0 0.0.0.0:81              0.0.0.0:*               LISTEN      -
tcp        0      0 127.0.0.53:53           0.0.0.0:*               LISTEN      -
tcp        0      0 0.0.0.0:22              0.0.0.0:*               LISTEN      -
tcp6       0      0 :::22                   :::*                    LISTEN      -

Через иптаблс я разрешил на порт трафику приходить
Правила файрвола
(Нажмите, чтобы показать/скрыть)

Но клиент на другой машине, все равно говорит что не могу подключится по данному адресу. Ошибка возникает сразу, и лог указывает на строчку с адресом сервера.
Помогите понять, почему клиент ни в какую не видит на этом адресе с портом сервер ВПН.


Оффлайн AlexDem

  • Активист
  • *
  • Сообщений: 696
    • Просмотр профиля
Ошибка возникает сразу, и лог указывает на строчку с адресом сервера.
Покажи, что клиент говорит?

Оффлайн TATOSHCKA_2022

  • Автор темы
  • Новичок
  • *
  • Сообщений: 5
    • Просмотр профиля
Конфиг сервера
#################################################
# 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 81

# 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

multihome

# 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 dh2048.pem 2048
;dh dh2048.pem
dh none

# 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 /var/log/openvpn/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 tls-auth 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
tls-crypt ta.key

# 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
cipher AES-256-GCM
auth SHA256

# 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 /var/log/openvpn/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         /var/log/openvpn/openvpn.log
;log-append  /var/log/openvpn/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 0

Конфиг клиента (Ключи убраны но в оригинале они есть)
##############################################
# 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.
95.214.8.219 81
;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 ca.crt
#cert client.crt
#key client.key

# Verify server certificate by checking that the
# certificate 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 data-ciphers option in the manpage
cipher AES-256-CBC
auth SHA256

# 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

key-direction 1

# script-security 2
# up /etc/openvpn/update-resolv-conf
# down /etc/openvpn/update-resolv-conf
<ca>
-----BEGIN CERTIFICATE-----

-----END CERTIFICATE-----
</ca>
<cert>
Certificate:
    Data:
        Version: 3 (0x2)
        Serial Number:
           
        Signature Algorithm: ecdsa-with-SHA512
        Issuer: CN=Easy-RSA CA
        Validity
            Not Before: Mar 19 11:27:11 2022 GMT
            Not After : Mar  3 11:27:11 2025 GMT
        Subject: CN=stebus
        Subject Public Key Info:
            Public Key Algorithm: id-ecPublicKey
                Public-Key: (384 bit)
                pub:
                 
                ASN1 OID: secp384r1
                NIST CURVE: P-384
        X509v3 extensions:
            X509v3 Basic Constraints:
                CA:FALSE
            X509v3 Subject Key Identifier:
               
            X509v3 Authority Key Identifier:
                keyid:
                DirName:/CN=Easy-RSA CA
                serial:

            X509v3 Extended Key Usage:
                TLS Web Client Authentication
            X509v3 Key Usage:
                Digital Signature
    Signature Algorithm: ecdsa-with-SHA512
         
-----BEGIN CERTIFICATE-----

-----END CERTIFICATE-----
</cert>
<key>
-----BEGIN PRIVATE KEY-----

-----END PRIVATE KEY-----
</key>
<tls-auth>
#
# 2048 bit OpenVPN static key
#
-----BEGIN OpenVPN Static key V1-----

-----END OpenVPN Static key V1-----
</tls-auth>

Лог клиента:

Options error: Unrecognized option or missing or extra parameter(s) in stebus.ovpn:42 95.214.8.219 (2.4.9)
Use --help for more information.

А 42 строка это:

95.214.8.219 81

Оффлайн MooSE

  • Старожил
  • *
  • Сообщений: 1123
    • Просмотр профиля

Оффлайн AlexDem

  • Активист
  • *
  • Сообщений: 696
    • Просмотр профиля
Тебе там ранее верно сказали, ошибка в конфиге
В конфиге прям написано, как надо писать


;remote my-server-2 1194

А у тебя просто

95.214.8.219 81

добавь ключ remote

Еще вопрос - а для чего выбран нестандартный порт?

Оффлайн TATOSHCKA_2022

  • Автор темы
  • Новичок
  • *
  • Сообщений: 5
    • Просмотр профиля
Ну не работал у меня с 1194 удп.

Поменял сейчас порт на 1194.

Sun Mar 20 16:00:05 2022 NOTE: --user option is not implemented on Windows
Sun Mar 20 16:00:05 2022 NOTE: --group option is not implemented on Windows
Sun Mar 20 16:00:05 2022 OpenVPN 2.4.9 x86_64-w64-mingw32 [SSL (OpenSSL)] [LZO] [LZ4] [PKCS11] [AEAD] built on Apr 16 2020
Sun Mar 20 16:00:05 2022 Windows version 6.2 (Windows 8 or greater) 64bit
Sun Mar 20 16:00:05 2022 library versions: OpenSSL 1.1.1f  31 Mar 2020, LZO 2.10
Enter Management Password:
Sun Mar 20 16:00:05 2022 MANAGEMENT: TCP Socket listening on [AF_INET]127.0.0.1:25340
Sun Mar 20 16:00:05 2022 Need hold release from management interface, waiting...
Sun Mar 20 16:00:06 2022 MANAGEMENT: Client connected from [AF_INET]127.0.0.1:25340
Sun Mar 20 16:00:06 2022 MANAGEMENT: CMD 'state on'
Sun Mar 20 16:00:06 2022 MANAGEMENT: CMD 'log all on'
Sun Mar 20 16:00:06 2022 MANAGEMENT: CMD 'echo all on'
Sun Mar 20 16:00:06 2022 MANAGEMENT: CMD 'bytecount 5'
Sun Mar 20 16:00:06 2022 MANAGEMENT: CMD 'hold off'
Sun Mar 20 16:00:06 2022 MANAGEMENT: CMD 'hold release'
Sun Mar 20 16:00:06 2022 Outgoing Control Channel Authentication: Using 256 bit message hash 'SHA256' for HMAC authentication
Sun Mar 20 16:00:06 2022 Incoming Control Channel Authentication: Using 256 bit message hash 'SHA256' for HMAC authentication
Sun Mar 20 16:00:06 2022 TCP/UDP: Preserving recently used remote address: [AF_INET]95.214.8.219:1194
Sun Mar 20 16:00:06 2022 Socket Buffers: R=[65536->65536] S=[65536->65536]
Sun Mar 20 16:00:06 2022 UDP link local: (not bound)
Sun Mar 20 16:00:06 2022 UDP link remote: [AF_INET]95.214.8.219:1194
Sun Mar 20 16:00:06 2022 MANAGEMENT: >STATE:1647766806,WAIT,,,,,,
Sun Mar 20 16:01:06 2022 TLS Error: TLS key negotiation failed to occur within 60 seconds (check your network connectivity)
Sun Mar 20 16:01:06 2022 TLS Error: TLS handshake failed
Sun Mar 20 16:01:06 2022 SIGUSR1[soft,tls-error] received, process restarting
Sun Mar 20 16:01:06 2022 MANAGEMENT: >STATE:1647766866,RECONNECTING,tls-error,,,,,
Sun Mar 20 16:01:06 2022 Restart pause, 5 second(s)
Sun Mar 20 16:01:11 2022 TCP/UDP: Preserving recently used remote address: [AF_INET]95.214.8.219:1194
Sun Mar 20 16:01:11 2022 Socket Buffers: R=[65536->65536] S=[65536->65536]
Sun Mar 20 16:01:11 2022 UDP link local: (not bound)
Sun Mar 20 16:01:11 2022 UDP link remote: [AF_INET]95.214.8.219:1194
Sun Mar 20 16:01:11 2022 MANAGEMENT: >STATE:1647766871,WAIT,,,,,,
Sun Mar 20 16:02:11 2022 TLS Error: TLS key negotiation failed to occur within 60 seconds (check your network connectivity)
Sun Mar 20 16:02:11 2022 TLS Error: TLS handshake failed
Sun Mar 20 16:02:11 2022 SIGUSR1[soft,tls-error] received, process restarting
Sun Mar 20 16:02:11 2022 MANAGEMENT: >STATE:1647766931,RECONNECTING,tls-error,,,,,
Sun Mar 20 16:02:11 2022 Restart pause, 5 second(s)
Sun Mar 20 16:02:16 2022 TCP/UDP: Preserving recently used remote address: [AF_INET]95.214.8.219:1194
Sun Mar 20 16:02:16 2022 Socket Buffers: R=[65536->65536] S=[65536->65536]
Sun Mar 20 16:02:16 2022 UDP link local: (not bound)
Sun Mar 20 16:02:16 2022 UDP link remote: [AF_INET]95.214.8.219:1194
Sun Mar 20 16:02:16 2022 MANAGEMENT: >STATE:1647766936,WAIT,,,,,,
Sun Mar 20 16:03:16 2022 TLS Error: TLS key negotiation failed to occur within 60 seconds (check your network connectivity)
Sun Mar 20 16:03:16 2022 TLS Error: TLS handshake failed
Sun Mar 20 16:03:16 2022 SIGUSR1[soft,tls-error] received, process restarting
Sun Mar 20 16:03:16 2022 MANAGEMENT: >STATE:1647766996,RECONNECTING,tls-error,,,,,
Sun Mar 20 16:03:16 2022 Restart pause, 5 second(s)
Sun Mar 20 16:03:21 2022 TCP/UDP: Preserving recently used remote address: [AF_INET]95.214.8.219:1194
Sun Mar 20 16:03:21 2022 Socket Buffers: R=[65536->65536] S=[65536->65536]
Sun Mar 20 16:03:21 2022 UDP link local: (not bound)
Sun Mar 20 16:03:21 2022 UDP link remote: [AF_INET]95.214.8.219:1194
Sun Mar 20 16:03:21 2022 MANAGEMENT: >STATE:1647767001,WAIT,,,,,,
Sun Mar 20 16:04:22 2022 TLS Error: TLS key negotiation failed to occur within 60 seconds (check your network connectivity)
Sun Mar 20 16:04:22 2022 TLS Error: TLS handshake failed
Sun Mar 20 16:04:22 2022 SIGUSR1[soft,tls-error] received, process restarting
Sun Mar 20 16:04:22 2022 MANAGEMENT: >STATE:1647767062,RECONNECTING,tls-error,,,,,
Sun Mar 20 16:04:22 2022 Restart pause, 5 second(s)
Sun Mar 20 16:04:27 2022 TCP/UDP: Preserving recently used remote address: [AF_INET]95.214.8.219:1194
Sun Mar 20 16:04:27 2022 Socket Buffers: R=[65536->65536] S=[65536->65536]
Sun Mar 20 16:04:27 2022 UDP link local: (not bound)
Sun Mar 20 16:04:27 2022 UDP link remote: [AF_INET]95.214.8.219:1194
Sun Mar 20 16:04:27 2022 MANAGEMENT: >STATE:1647767067,WAIT,,,,,,
Sun Mar 20 16:05:27 2022 TLS Error: TLS key negotiation failed to occur within 60 seconds (check your network connectivity)
Sun Mar 20 16:05:27 2022 TLS Error: TLS handshake failed
Sun Mar 20 16:05:27 2022 SIGUSR1[soft,tls-error] received, process restarting
Sun Mar 20 16:05:27 2022 MANAGEMENT: >STATE:1647767127,RECONNECTING,tls-error,,,,,
Sun Mar 20 16:05:27 2022 Restart pause, 10 second(s)
Sun Mar 20 16:05:37 2022 TCP/UDP: Preserving recently used remote address: [AF_INET]95.214.8.219:1194
Sun Mar 20 16:05:37 2022 Socket Buffers: R=[65536->65536] S=[65536->65536]
Sun Mar 20 16:05:37 2022 UDP link local: (not bound)
Sun Mar 20 16:05:37 2022 UDP link remote: [AF_INET]95.214.8.219:1194
Sun Mar 20 16:05:37 2022 MANAGEMENT: >STATE:1647767137,WAIT,,,,,,
Sun Mar 20 16:06:37 2022 TLS Error: TLS key negotiation failed to occur within 60 seconds (check your network connectivity)
Sun Mar 20 16:06:37 2022 TLS Error: TLS handshake failed
Sun Mar 20 16:06:37 2022 SIGUSR1[soft,tls-error] received, process restarting
Sun Mar 20 16:06:37 2022 MANAGEMENT: >STATE:1647767197,RECONNECTING,tls-error,,,,,
Sun Mar 20 16:06:37 2022 Restart pause, 20 second(s)
Sun Mar 20 16:06:57 2022 TCP/UDP: Preserving recently used remote address: [AF_INET]95.214.8.219:1194
Sun Mar 20 16:06:57 2022 Socket Buffers: R=[65536->65536] S=[65536->65536]
Sun Mar 20 16:06:57 2022 UDP link local: (not bound)
Sun Mar 20 16:06:57 2022 UDP link remote: [AF_INET]95.214.8.219:1194
Sun Mar 20 16:06:57 2022 MANAGEMENT: >STATE:1647767217,WAIT,,,,,,
Sun Mar 20 16:07:57 2022 TLS Error: TLS key negotiation failed to occur within 60 seconds (check your network connectivity)
Sun Mar 20 16:07:57 2022 TLS Error: TLS handshake failed
Sun Mar 20 16:07:57 2022 SIGUSR1[soft,tls-error] received, process restarting
Sun Mar 20 16:07:57 2022 MANAGEMENT: >STATE:1647767277,RECONNECTING,tls-error,,,,,
Sun Mar 20 16:07:57 2022 Restart pause, 40 second(s)
Sun Mar 20 16:08:37 2022 TCP/UDP: Preserving recently used remote address: [AF_INET]95.214.8.219:1194
Sun Mar 20 16:08:37 2022 Socket Buffers: R=[65536->65536] S=[65536->65536]
Sun Mar 20 16:08:37 2022 UDP link local: (not bound)
Sun Mar 20 16:08:37 2022 UDP link remote: [AF_INET]95.214.8.219:1194
Sun Mar 20 16:08:37 2022 MANAGEMENT: >STATE:1647767317,WAIT,,,,,,
Sun Mar 20 16:09:37 2022 TLS Error: TLS key negotiation failed to occur within 60 seconds (check your network connectivity)
Sun Mar 20 16:09:37 2022 TLS Error: TLS handshake failed
Sun Mar 20 16:09:37 2022 SIGUSR1[soft,tls-error] received, process restarting
Sun Mar 20 16:09:37 2022 MANAGEMENT: >STATE:1647767377,RECONNECTING,tls-error,,,,,
Sun Mar 20 16:09:37 2022 Restart pause, 80 second(s)
Sun Mar 20 16:10:57 2022 TCP/UDP: Preserving recently used remote address: [AF_INET]95.214.8.219:1194
Sun Mar 20 16:10:57 2022 Socket Buffers: R=[65536->65536] S=[65536->65536]
Sun Mar 20 16:10:57 2022 UDP link local: (not bound)
Sun Mar 20 16:10:57 2022 UDP link remote: [AF_INET]95.214.8.219:1194
Sun Mar 20 16:10:57 2022 MANAGEMENT: >STATE:1647767457,WAIT,,,,,,
Sun Mar 20 16:11:57 2022 TLS Error: TLS key negotiation failed to occur within 60 seconds (check your network connectivity)
Sun Mar 20 16:11:57 2022 TLS Error: TLS handshake failed
Sun Mar 20 16:11:57 2022 SIGUSR1[soft,tls-error] received, process restarting
Sun Mar 20 16:11:57 2022 MANAGEMENT: >STATE:1647767517,RECONNECTING,tls-error,,,,,
Sun Mar 20 16:11:57 2022 Restart pause, 160 second(s)
Sun Mar 20 16:14:37 2022 TCP/UDP: Preserving recently used remote address: [AF_INET]95.214.8.219:1194
Sun Mar 20 16:14:37 2022 Socket Buffers: R=[65536->65536] S=[65536->65536]
Sun Mar 20 16:14:37 2022 UDP link local: (not bound)
Sun Mar 20 16:14:37 2022 UDP link remote: [AF_INET]95.214.8.219:1194
Sun Mar 20 16:14:37 2022 MANAGEMENT: >STATE:1647767677,WAIT,,,,,,
Sun Mar 20 16:15:37 2022 TLS Error: TLS key negotiation failed to occur within 60 seconds (check your network connectivity)
Sun Mar 20 16:15:37 2022 TLS Error: TLS handshake failed
Sun Mar 20 16:15:37 2022 SIGUSR1[soft,tls-error] received, process restarting
Sun Mar 20 16:15:37 2022 MANAGEMENT: >STATE:1647767737,RECONNECTING,tls-error,,,,,
Sun Mar 20 16:15:37 2022 Restart pause, 300 second(s)
Sun Mar 20 16:20:37 2022 TCP/UDP: Preserving recently used remote address: [AF_INET]95.214.8.219:1194
Sun Mar 20 16:20:37 2022 Socket Buffers: R=[65536->65536] S=[65536->65536]
Sun Mar 20 16:20:37 2022 UDP link local: (not bound)
Sun Mar 20 16:20:37 2022 UDP link remote: [AF_INET]95.214.8.219:1194
Sun Mar 20 16:20:37 2022 MANAGEMENT: >STATE:1647768037,WAIT,,,,,,
Sun Mar 20 16:21:38 2022 TLS Error: TLS key negotiation failed to occur within 60 seconds (check your network connectivity)
Sun Mar 20 16:21:38 2022 TLS Error: TLS handshake failed
Sun Mar 20 16:21:38 2022 SIGUSR1[soft,tls-error] received, process restarting
Sun Mar 20 16:21:38 2022 MANAGEMENT: >STATE:1647768098,RECONNECTING,tls-error,,,,,
Sun Mar 20 16:21:38 2022 Restart pause, 300 second(s)
Sun Mar 20 16:26:38 2022 TCP/UDP: Preserving recently used remote address: [AF_INET]95.214.8.219:1194
Sun Mar 20 16:26:38 2022 Socket Buffers: R=[65536->65536] S=[65536->65536]
Sun Mar 20 16:26:38 2022 UDP link local: (not bound)
Sun Mar 20 16:26:38 2022 UDP link remote: [AF_INET]95.214.8.219:1194
Sun Mar 20 16:26:38 2022 MANAGEMENT: >STATE:1647768398,WAIT,,,,,,
Sun Mar 20 16:27:38 2022 TLS Error: TLS key negotiation failed to occur within 60 seconds (check your network connectivity)
Sun Mar 20 16:27:38 2022 TLS Error: TLS handshake failed
Sun Mar 20 16:27:38 2022 SIGUSR1[soft,tls-error] received, process restarting
Sun Mar 20 16:27:38 2022 MANAGEMENT: >STATE:1647768458,RECONNECTING,tls-error,,,,,
Sun Mar 20 16:27:38 2022 Restart pause, 300 second(s)
Sun Mar 20 16:32:21 2022 MANAGEMENT: CMD 'signal SIGHUP'
Sun Mar 20 16:32:21 2022 SIGHUP[hard,init_instance] received, process restarting
Sun Mar 20 16:32:21 2022 MANAGEMENT: >STATE:1647768741,RECONNECTING,init_instance,,,,,
Sun Mar 20 16:32:21 2022 NOTE: --user option is not implemented on Windows
Sun Mar 20 16:32:21 2022 NOTE: --group option is not implemented on Windows
Sun Mar 20 16:32:21 2022 OpenVPN 2.4.9 x86_64-w64-mingw32 [SSL (OpenSSL)] [LZO] [LZ4] [PKCS11] [AEAD] built on Apr 16 2020
Sun Mar 20 16:32:21 2022 Windows version 6.2 (Windows 8 or greater) 64bit
Sun Mar 20 16:32:21 2022 library versions: OpenSSL 1.1.1f  31 Mar 2020, LZO 2.10
Sun Mar 20 16:32:21 2022 Restart pause, 5 second(s)
Sun Mar 20 16:32:26 2022 Outgoing Control Channel Authentication: Using 256 bit message hash 'SHA256' for HMAC authentication
Sun Mar 20 16:32:26 2022 Incoming Control Channel Authentication: Using 256 bit message hash 'SHA256' for HMAC authentication
Sun Mar 20 16:32:26 2022 TCP/UDP: Preserving recently used remote address: [AF_INET]95.214.8.219:1194
Sun Mar 20 16:32:26 2022 Socket Buffers: R=[65536->65536] S=[65536->65536]
Sun Mar 20 16:32:26 2022 UDP link local: (not bound)
Sun Mar 20 16:32:26 2022 UDP link remote: [AF_INET]95.214.8.219:1194
Sun Mar 20 16:32:26 2022 MANAGEMENT: >STATE:1647768746,WAIT,,,,,,
Sun Mar 20 16:33:27 2022 TLS Error: TLS key negotiation failed to occur within 60 seconds (check your network connectivity)
Sun Mar 20 16:33:27 2022 TLS Error: TLS handshake failed
Sun Mar 20 16:33:27 2022 SIGUSR1[soft,tls-error] received, process restarting
Sun Mar 20 16:33:27 2022 MANAGEMENT: >STATE:1647768807,RECONNECTING,tls-error,,,,,
Sun Mar 20 16:33:27 2022 Restart pause, 5 second(s)
Sun Mar 20 16:33:32 2022 TCP/UDP: Preserving recently used remote address: [AF_INET]95.214.8.219:1194
Sun Mar 20 16:33:32 2022 Socket Buffers: R=[65536->65536] S=[65536->65536]
Sun Mar 20 16:33:32 2022 UDP link local: (not bound)
Sun Mar 20 16:33:32 2022 UDP link remote: [AF_INET]95.214.8.219:1194
Sun Mar 20 16:33:32 2022 MANAGEMENT: >STATE:1647768812,WAIT,,,,,,

Порт я открыл

sudo iptables -I INPUT -p udp --dport 1194 -j ACCEPT
Тоесть передаёт информацию, но не получает. Конфиг сервера я поменял.

Сервер:

#################################################
# 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

multihome

# 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 dh2048.pem 2048
;dh dh2048.pem
dh none

# 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 /var/log/openvpn/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 tls-auth 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
tls-crypt ta.key

# 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
cipher AES-256-GCM
auth SHA256

# 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 /var/log/openvpn/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         /var/log/openvpn/openvpn.log
;log-append  /var/log/openvpn/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 0

Клиент:

##############################################
# 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 95.214.8.219 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 ca.crt
#cert client.crt
#key client.key

# Verify server certificate by checking that the
# certificate 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 data-ciphers option in the manpage
cipher AES-256-CBC
auth SHA256

# 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

key-direction 1

# script-security 2
# up /etc/openvpn/update-resolv-conf
# down /etc/openvpn/update-resolv-conf
<cert>
Certificate:
    Data:
        Version: 3 (0x2)
        Serial Number:
            3e:fa:78:61:b2:f4:79:17:0a:3f:0a:cf:be:4f:42:63
        Signature Algorithm: ecdsa-with-SHA512
        Issuer: CN=Easy-RSA CA
        Validity
            Not Before: Mar 19 11:27:11 2022 GMT
            Not After : Mar  3 11:27:11 2025 GMT
        Subject: CN=stebus
        Subject Public Key Info:
            Public Key Algorithm: id-ecPublicKey
                Public-Key: (384 bit)
                pub:
                    04:d2:7e:02:9e:a7:60:0f:d6:bf:46:3b:54:d4:48:
                    b6:e7:44:3b:78:d2:f8:92:29:07:40:c9:54:90:79:
                    0e:f7:e2:3a:31:ef:53:58:8d:b5:26:73:79:f2:12:
                    7d:0e:b1:16:20:66:b8:67:11:e2:8c:ce:ff:53:b1:
                    7d:f7:c6:d8:18:5f:89:74:01:30:6c:1e:7e:62:2c:
                    83:45:cb:8e:81:a2:a3:14:73:20:aa:5c:86:55:43:
                    9a:a9:14:7e:15:27:fb
                ASN1 OID: secp384r1
                NIST CURVE: P-384
        X509v3 extensions:
            X509v3 Basic Constraints:
                CA:FALSE
                X509v3 Extended Key Usage:
                TLS Web Client Authentication
            X509v3 Key Usage:
                Digital Signature
    Signature Algorithm: ecdsa-with-SHA512
       

-----BEGIN CERTIFICATE-----

-----END CERTIFICATE-----
</cert>
<key>
-----BEGIN PRIVATE KEY-----

-----END PRIVATE KEY-----
</key>
<tls-auth>
#
# 2048 bit OpenVPN static key
#
-----BEGIN OpenVPN Static key V1-----

-----END OpenVPN Static key V1-----
</tls-auth>

Оффлайн ALiEN

  • Администратор
  • Старожил
  • *
  • Сообщений: 6861
  • Luck Tales
    • Просмотр профиля
Сервер -
tls-auth ta.key 0 # поставить
tls-crypt ta.key # убрать
« Последнее редактирование: 20 Марта 2022, 16:22:18 от ALiEN175 »
🖥 AsRock B550M Pro4 :: AMD Ryzen 5 3600 :: 16 GB DDR4 :: AMD Radeon RX 6600 :: XFCE
💻 ACER 5750G :: Intel Core i5-2450M :: 6 GB DDR3 :: GeForce GT 630M :: XFCE

Оффлайн TATOSHCKA_2022

  • Автор темы
  • Новичок
  • *
  • Сообщений: 5
    • Просмотр профиля
Поправил я конфиг сервера:

#################################################
# 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

multihome

# 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 dh2048.pem 2048
;dh dh2048.pem
dh none

# 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 /var/log/openvpn/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 tls-auth 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
;tls-crypt ta.key

# 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
cipher AES-256-GCM
auth SHA256

# 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 /var/log/openvpn/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         /var/log/openvpn/openvpn.log
;log-append  /var/log/openvpn/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 0

Все равно не подключается:

Sun Mar 20 20:36:42 2022 NOTE: --user option is not implemented on Windows
Sun Mar 20 20:36:42 2022 NOTE: --group option is not implemented on Windows
Sun Mar 20 20:36:42 2022 OpenVPN 2.4.9 x86_64-w64-mingw32 [SSL (OpenSSL)] [LZO] [LZ4] [PKCS11] [AEAD] built on Apr 16 2020
Sun Mar 20 20:36:42 2022 Windows version 6.2 (Windows 8 or greater) 64bit
Sun Mar 20 20:36:42 2022 library versions: OpenSSL 1.1.1f  31 Mar 2020, LZO 2.10
Enter Management Password:
Sun Mar 20 20:36:42 2022 MANAGEMENT: TCP Socket listening on [AF_INET]127.0.0.1:25340
Sun Mar 20 20:36:42 2022 Need hold release from management interface, waiting...
Sun Mar 20 20:36:42 2022 MANAGEMENT: Client connected from [AF_INET]127.0.0.1:25340
Sun Mar 20 20:36:43 2022 MANAGEMENT: CMD 'state on'
Sun Mar 20 20:36:43 2022 MANAGEMENT: CMD 'log all on'
Sun Mar 20 20:36:43 2022 MANAGEMENT: CMD 'echo all on'
Sun Mar 20 20:36:43 2022 MANAGEMENT: CMD 'bytecount 5'
Sun Mar 20 20:36:43 2022 MANAGEMENT: CMD 'hold off'
Sun Mar 20 20:36:43 2022 MANAGEMENT: CMD 'hold release'
Sun Mar 20 20:36:43 2022 Outgoing Control Channel Authentication: Using 256 bit message hash 'SHA256' for HMAC authentication
Sun Mar 20 20:36:43 2022 Incoming Control Channel Authentication: Using 256 bit message hash 'SHA256' for HMAC authentication
Sun Mar 20 20:36:43 2022 TCP/UDP: Preserving recently used remote address: [AF_INET]95.214.8.219:1194
Sun Mar 20 20:36:43 2022 Socket Buffers: R=[65536->65536] S=[65536->65536]
Sun Mar 20 20:36:43 2022 UDP link local: (not bound)
Sun Mar 20 20:36:43 2022 UDP link remote: [AF_INET]95.214.8.219:1194
Sun Mar 20 20:36:43 2022 MANAGEMENT: >STATE:1647783403,WAIT,,,,,,
Sun Mar 20 20:37:43 2022 TLS Error: TLS key negotiation failed to occur within 60 seconds (check your network connectivity)
Sun Mar 20 20:37:43 2022 TLS Error: TLS handshake failed
Sun Mar 20 20:37:43 2022 SIGUSR1[soft,tls-error] received, process restarting
Sun Mar 20 20:37:43 2022 MANAGEMENT: >STATE:1647783463,RECONNECTING,tls-error,,,,,
Sun Mar 20 20:37:43 2022 Restart pause, 5 second(s)
Sun Mar 20 20:37:48 2022 TCP/UDP: Preserving recently used remote address: [AF_INET]95.214.8.219:1194
Sun Mar 20 20:37:48 2022 Socket Buffers: R=[65536->65536] S=[65536->65536]
Sun Mar 20 20:37:48 2022 UDP link local: (not bound)
Sun Mar 20 20:37:48 2022 UDP link remote: [AF_INET]95.214.8.219:1194
Sun Mar 20 20:37:48 2022 MANAGEMENT: >STATE:1647783468,WAIT,,,,,,
Sun Mar 20 20:38:48 2022 TLS Error: TLS key negotiation failed to occur within 60 seconds (check your network connectivity)
Sun Mar 20 20:38:48 2022 TLS Error: TLS handshake failed
Sun Mar 20 20:38:48 2022 SIGUSR1[soft,tls-error] received, process restarting
Sun Mar 20 20:38:48 2022 MANAGEMENT: >STATE:1647783528,RECONNECTING,tls-error,,,,,
Sun Mar 20 20:38:48 2022 Restart pause, 5 second(s)
Sun Mar 20 20:38:53 2022 TCP/UDP: Preserving recently used remote address: [AF_INET]95.214.8.219:1194
Sun Mar 20 20:38:53 2022 Socket Buffers: R=[65536->65536] S=[65536->65536]
Sun Mar 20 20:38:53 2022 UDP link local: (not bound)
Sun Mar 20 20:38:53 2022 UDP link remote: [AF_INET]95.214.8.219:1194
Sun Mar 20 20:38:53 2022 MANAGEMENT: >STATE:1647783533,WAIT,,,,,,
Sun Mar 20 20:39:54 2022 TLS Error: TLS key negotiation failed to occur within 60 seconds (check your network connectivity)
Sun Mar 20 20:39:54 2022 TLS Error: TLS handshake failed
Sun Mar 20 20:39:54 2022 SIGUSR1[soft,tls-error] received, process restarting
Sun Mar 20 20:39:54 2022 MANAGEMENT: >STATE:1647783594,RECONNECTING,tls-error,,,,,
Sun Mar 20 20:39:54 2022 Restart pause, 5 second(s)
Sun Mar 20 20:39:59 2022 TCP/UDP: Preserving recently used remote address: [AF_INET]95.214.8.219:1194
Sun Mar 20 20:39:59 2022 Socket Buffers: R=[65536->65536] S=[65536->65536]
Sun Mar 20 20:39:59 2022 UDP link local: (not bound)
Sun Mar 20 20:39:59 2022 UDP link remote: [AF_INET]95.214.8.219:1194
Sun Mar 20 20:39:59 2022 MANAGEMENT: >STATE:1647783599,WAIT,,,,,,
Sun Mar 20 20:40:59 2022 TLS Error: TLS key negotiation failed to occur within 60 seconds (check your network connectivity)
Sun Mar 20 20:40:59 2022 TLS Error: TLS handshake failed
Sun Mar 20 20:40:59 2022 SIGUSR1[soft,tls-error] received, process restarting
Sun Mar 20 20:40:59 2022 MANAGEMENT: >STATE:1647783659,RECONNECTING,tls-error,,,,,
Sun Mar 20 20:40:59 2022 Restart pause, 5 second(s)
Sun Mar 20 20:41:04 2022 TCP/UDP: Preserving recently used remote address: [AF_INET]95.214.8.219:1194
Sun Mar 20 20:41:04 2022 Socket Buffers: R=[65536->65536] S=[65536->65536]
Sun Mar 20 20:41:04 2022 UDP link local: (not bound)
Sun Mar 20 20:41:04 2022 UDP link remote: [AF_INET]95.214.8.219:1194
Sun Mar 20 20:41:04 2022 MANAGEMENT: >STATE:1647783664,WAIT,,,,,,
Sun Mar 20 20:42:04 2022 TLS Error: TLS key negotiation failed to occur within 60 seconds (check your network connectivity)
Sun Mar 20 20:42:04 2022 TLS Error: TLS handshake failed
Sun Mar 20 20:42:04 2022 SIGUSR1[soft,tls-error] received, process restarting
Sun Mar 20 20:42:04 2022 MANAGEMENT: >STATE:1647783724,RECONNECTING,tls-error,,,,,
Sun Mar 20 20:42:04 2022 Restart pause, 10 second(s)
Sun Mar 20 20:42:14 2022 TCP/UDP: Preserving recently used remote address: [AF_INET]95.214.8.219:1194
Sun Mar 20 20:42:14 2022 Socket Buffers: R=[65536->65536] S=[65536->65536]
Sun Mar 20 20:42:14 2022 UDP link local: (not bound)
Sun Mar 20 20:42:14 2022 UDP link remote: [AF_INET]95.214.8.219:1194
Sun Mar 20 20:42:14 2022 MANAGEMENT: >STATE:1647783734,WAIT,,,,,,
Sun Mar 20 20:43:14 2022 TLS Error: TLS key negotiation failed to occur within 60 seconds (check your network connectivity)
Sun Mar 20 20:43:14 2022 TLS Error: TLS handshake failed
Sun Mar 20 20:43:14 2022 SIGUSR1[soft,tls-error] received, process restarting
Sun Mar 20 20:43:14 2022 MANAGEMENT: >STATE:1647783794,RECONNECTING,tls-error,,,,,
Sun Mar 20 20:43:14 2022 Restart pause, 20 second(s)
Sun Mar 20 20:43:34 2022 TCP/UDP: Preserving recently used remote address: [AF_INET]95.214.8.219:1194
Sun Mar 20 20:43:34 2022 Socket Buffers: R=[65536->65536] S=[65536->65536]
Sun Mar 20 20:43:34 2022 UDP link local: (not bound)
Sun Mar 20 20:43:34 2022 UDP link remote: [AF_INET]95.214.8.219:1194
Sun Mar 20 20:43:34 2022 MANAGEMENT: >STATE:1647783814,WAIT,,,,,,
Sun Mar 20 20:44:34 2022 TLS Error: TLS key negotiation failed to occur within 60 seconds (check your network connectivity)
Sun Mar 20 20:44:34 2022 TLS Error: TLS handshake failed
Sun Mar 20 20:44:34 2022 SIGUSR1[soft,tls-error] received, process restarting
Sun Mar 20 20:44:34 2022 MANAGEMENT: >STATE:1647783874,RECONNECTING,tls-error,,,,,
Sun Mar 20 20:44:34 2022 Restart pause, 40 second(s)
Sun Mar 20 20:44:45 2022 SIGTERM[hard,init_instance] received, process exiting
Sun Mar 20 20:44:45 2022 MANAGEMENT: >STATE:1647783885,EXITING,init_instance,,,,,

Даже пытался опцию в конфиге клиента менять (разкоментировал, коментировал) эффект тот же.

tls-auth ta.key 1

Оффлайн AlexDem

  • Активист
  • *
  • Сообщений: 696
    • Просмотр профиля
Sun Mar 20 20:43:34 2022 UDP link local: (not bound)
Sun Mar 20 20:43:34 2022 UDP link remote: [AF_INET]95.214.8.219:1194
Sun Mar 20 20:43:34 2022 MANAGEMENT: >STATE:1647783814,WAIT,,,,,,
Sun Mar 20 20:44:34 2022 TLS Error: TLS key negotiation failed to occur within 60 seconds (check your network connectivity)
Sun Mar 20 20:44:34 2022 TLS Error: TLS handshake failed
Тут вопрос не в сертификатах.
Нет подключения, поэтому и проверка сертификатов не проходит...
Возможно где то не установлены правили маршрутизации, или iptables неверно настроены.
Вот тебе рабочий мануал, проверенный, проверь, все ли у тебя настроено как надо:
https://www.digitalocean.com/community/tutorials/how-to-set-up-an-openvpn-server-on-ubuntu-18-04-ru
Особое внимание обрати на раздел 6.
Также покажи
sudo netstat -tulpn | grep LISTENи
netstat -n --udp --listenна сервере.



Оффлайн TATOSHCKA_2022

  • Автор темы
  • Новичок
  • *
  • Сообщений: 5
    • Просмотр профиля
Всем спасибо за помощь!

Дело оказалось, что я забыл в конфиге поправить сеть с server 10.8.0.0 255.255.255.0 на server 10.8.1.0 255.255.255.0.

Правила NAT я прописал для 10.8.1.0.

Всем огромное спасибо.

 

Страница сгенерирована за 0.064 секунд. Запросов: 25.