Всем добрый день! Помогите разобраться пожалуйста.
Задача простая - выпустить клиента в Интернет через OpenVPN
Версия Ubuntu
Description: Ubuntu 22.04.5 LTS
Release: 22.04
Codename: jammy
Версия OpenVPN OpenVPN 2.5.11
Версия клиента Windows 11.49.00
Установил OpenVPN сервер, преднастроил из стандартных конфигурационных файлов.
Подключение осуществляется успешно, однако трафик умирает где-то внутри туннеля.
#################################################
# Sample OpenVPN 2.0 config file for #
# multi-client server. #
# #
# This file is for the server side #
# of a many-clients <-> one-server #
# OpenVPN configuration. #
# #
# OpenVPN also supports #
# single-machine <-> single-machine #
# configurations (See the Examples page #
# on the web site for more info). #
# #
# This config should work on Windows #
# or Linux/BSD systems. Remember on #
# Windows to quote pathnames and use #
# double backslashes, e.g.: #
# "C:\\Program Files\\OpenVPN\\config\\foo.key" #
# #
# Comments are preceded with '#' or ';' #
#################################################
# Which local IP address should OpenVPN
# listen on? (optional)
;local a.b.c.d
# Which TCP/UDP port should OpenVPN listen on?
# If you want to run multiple OpenVPN instances
# on the same machine, use a different port
# number for each one. You will need to
# open up this port on your firewall.
port 1194
# TCP or UDP server?
;proto tcp
proto udp
# "dev tun" will create a routed IP tunnel,
# "dev tap" will create an ethernet tunnel.
# Use "dev tap0" if you are ethernet bridging
# and have precreated a tap0 virtual interface
# and bridged it with your ethernet interface.
# If you want to control access policies
# over the VPN, you must create firewall
# rules for the the TUN/TAP interface.
# On non-Windows systems, you can give
# an explicit unit number, such as tun0.
# On Windows, use "dev-node" for this.
# On most systems, the VPN will not function
# unless you partially or fully disable
# the firewall for the TUN/TAP interface.
;dev tap
dev tun
# Windows needs the TAP-Win32 adapter name
# from the Network Connections panel if you
# have more than one. On XP SP2 or higher,
# you may need to selectively disable the
# Windows firewall for the TAP adapter.
# Non-Windows systems usually don't need this.
;dev-node MyTap
# SSL/TLS root certificate (ca), certificate
# (cert), and private key (key). Each client
# and the server must have their own cert and
# key file. The server and all clients will
# use the same ca file.
#
# See the "easy-rsa" directory for a series
# of scripts for generating RSA certificates
# and private keys. Remember to use
# a unique Common Name for the server
# and each of the client certificates.
#
# Any X509 key management system can be used.
# OpenVPN can also use a PKCS #12 formatted key file
# (see "pkcs12" directive in man page).
ca ca.crt
cert server.vpn.crt
key server.vpn.key # This file should be kept secret
# Diffie hellman parameters.
# Generate your own with:
# openssl dhparam -out dh2048.pem 2048
dh dh.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 /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
# 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-128-CBC
cipher AES-256-GCM
# 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 1
Конфиг клиента
##############################################
# 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 ХХХ.ХХХ.ХХХ.ХХХ 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
#local 192.168.88.240
# 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
#push "redirect-gateway def1 bypass-dhcp"
# SSL/TLS parms.
# See the server config file for more
# description. It's best to use
# a separate .crt/.key file pair
# for each client. A single ca
# file can be used for all clients.
ca "C:\\Program Files\\OpenVPN\\config\\Zab\\ca.crt"
cert "C:\\Program Files\\OpenVPN\\config\\Zab\\MkrT_A.crt"
key "C:\\Program Files\\OpenVPN\\config\\Zab\\MkrT_A.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
tun-mtu 1500
mssfix 1400
# If a tls-auth key is used on the server
# then every client must also have the key.
tls-auth "C:\\Program Files\\OpenVPN\\config\\Zab\\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-GCM
#cipher AES-128-CBC
# Enable compression on the VPN link.
# Don't enable this unless it is also
# enabled in the server config file.
# comp-lzo no
# Set log file verbosity.
verb 4
# Silence repeating messages
;mute 20
Интерфейс туннеля
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: ens3: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000
link/ether 52:54:00:4b:29:cb brd ff:ff:ff:ff:ff:ff
altname enp0s3
inet ХХХ.ХХХ.ХХХ.ХХХ/24 brd 185.112.249.255 scope global ens3
valid_lft forever preferred_lft forever
inet6 fe80::5054:ff:fe4b:29cb/64 scope link
valid_lft forever preferred_lft forever
3: ztcfwt3d5l: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 2800 qdisc fq_codel state UNKNOWN group default qlen 1000
link/ether a6:04:52:c0:2b:dd brd ff:ff:ff:ff:ff:ff
inet 192.168.193.50/24 brd 192.168.193.255 scope global ztcfwt3d5l
valid_lft forever preferred_lft forever
inet6 fe80::60be:5cff:fe2f:3d38/64 scope link
valid_lft forever preferred_lft forever
119: tun0: <POINTOPOINT,MULTICAST,NOARP,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UNKNOWN group default qlen 500
link/none
inet 10.8.0.1 peer 10.8.0.2/32 scope global tun0
valid_lft forever preferred_lft forever
inet6 fe80::d9c8:542c:dfe6:d0a7/64 scope link stable-privacy
valid_lft forever preferred_lft forever
Вывод route с Windows машины
===========================================================================
Список интерфейсов
11...60 63 4c b0 80 d0 ......Realtek PCIe GbE Family Controller
16...........................Wintun Userspace Tunnel
9...00 ff 43 4f 82 e9 ......TAP-Windows Adapter V9
5...a4 34 d9 d5 e4 cd ......Microsoft Wi-Fi Direct Virtual Adapter
12...a6 34 d9 d5 e4 cc ......Microsoft Wi-Fi Direct Virtual Adapter #2
17...a6 b2 59 b5 6b 04 ......ZeroTier Virtual Port
19...a4 34 d9 d5 e4 cc ......Intel(R) Dual Band Wireless-AC 8260
1...........................Software Loopback Interface 1
===========================================================================
IPv4 таблица маршрута
===========================================================================
Активные маршруты:
Сетевой адрес Маска сети Адрес шлюза Интерфейс Метрика
0.0.0.0 0.0.0.0 192.168.88.1 192.168.88.240 40
0.0.0.0 0.0.0.0 25.255.255.254 192.168.193.227 10034
0.0.0.0 128.0.0.0 10.8.0.5 10.8.0.6 281
10.8.0.1 255.255.255.255 10.8.0.5 10.8.0.6 281
10.8.0.4 255.255.255.252 On-link 10.8.0.6 281
10.8.0.6 255.255.255.255 On-link 10.8.0.6 281
10.8.0.7 255.255.255.255 On-link 10.8.0.6 281
10.10.44.0 255.255.255.0 192.168.193.146 192.168.193.227 291
127.0.0.0 255.0.0.0 On-link 127.0.0.1 331
127.0.0.1 255.255.255.255 On-link 127.0.0.1 331
127.255.255.255 255.255.255.255 On-link 127.0.0.1 331
128.0.0.0 128.0.0.0 10.8.0.5 10.8.0.6 281
ХХХ.ХХХ.ХХХ.ХХХ 255.255.255.255 192.168.88.1 192.168.88.240 296
192.168.88.0 255.255.255.0 On-link 192.168.88.240 296
192.168.88.0 255.255.255.0 192.168.193.138 192.168.193.227 291
192.168.88.240 255.255.255.255 On-link 192.168.88.240 296
192.168.88.255 255.255.255.255 On-link 192.168.88.240 296
192.168.193.0 255.255.255.0 On-link 192.168.193.227 291
192.168.193.227 255.255.255.255 On-link 192.168.193.227 291
192.168.193.255 255.255.255.255 On-link 192.168.193.227 291
224.0.0.0 240.0.0.0 On-link 127.0.0.1 331
224.0.0.0 240.0.0.0 On-link 10.8.0.6 281
224.0.0.0 240.0.0.0 On-link 192.168.88.240 296
224.0.0.0 240.0.0.0 On-link 192.168.193.227 291
255.255.255.255 255.255.255.255 On-link 127.0.0.1 331
255.255.255.255 255.255.255.255 On-link 10.8.0.6 281
255.255.255.255 255.255.255.255 On-link 192.168.88.240 296
255.255.255.255 255.255.255.255 On-link 192.168.193.227 291
===========================================================================
Постоянные маршруты:
Отсутствует
IPv6 таблица маршрута
===========================================================================
Активные маршруты:
Метрика Сетевой адрес Шлюз
1 331 ::1/128 On-link
9 281 fe80::/64 On-link
17 291 fe80::/64 On-link
17 291 fe80::3cfc:345c:4ec9:a47a/128
On-link
9 281 fe80::c3cd:d107:ab6:c915/128
On-link
1 331 ff00::/8 On-link
9 281 ff00::/8 On-link
17 291 ff00::/8 On-link
===========================================================================
Постоянные маршруты:
Отсутствует
Вывод log OpenVPN
024-11-16 11:48:39 45.94.119.215:9459 Outgoing Control Channel Authentication: Using 160 bit message hash 'SHA1' for HMAC authentication
2024-11-16 11:48:39 45.94.119.215:9459 Incoming Control Channel Authentication: Using 160 bit message hash 'SHA1' for HMAC authentication
2024-11-16 11:48:39 45.94.119.215:9459 TLS: Initial packet from [AF_INET]45.94.119.215:9459, sid=03984b17 13dcf8eb
2024-11-16 11:48:39 45.94.119.215:9459 VERIFY OK: depth=1, CN=server.vpn
2024-11-16 11:48:39 45.94.119.215:9459 VERIFY OK: depth=0, CN=MkrT_A
2024-11-16 11:48:39 45.94.119.215:9459 peer info: IV_VER=2.6.11
2024-11-16 11:48:39 45.94.119.215:9459 peer info: IV_PLAT=win
2024-11-16 11:48:39 45.94.119.215:9459 peer info: IV_TCPNL=1
2024-11-16 11:48:39 45.94.119.215:9459 peer info: IV_MTU=1600
2024-11-16 11:48:39 45.94.119.215:9459 peer info: IV_NCP=2
2024-11-16 11:48:39 45.94.119.215:9459 peer info: IV_CIPHERS=AES-256-GCM:AES-128-GCM
2024-11-16 11:48:39 45.94.119.215:9459 peer info: IV_PROTO=990
2024-11-16 11:48:39 45.94.119.215:9459 peer info: IV_LZO_STUB=1
2024-11-16 11:48:39 45.94.119.215:9459 peer info: IV_COMP_STUB=1
2024-11-16 11:48:39 45.94.119.215:9459 peer info: IV_COMP_STUBv2=1
2024-11-16 11:48:39 45.94.119.215:9459 peer info: IV_GUI_VER=OpenVPN_GUI_11.49.0.0
2024-11-16 11:48:39 45.94.119.215:9459 peer info: IV_SSO=openurl,webauth,crtext
2024-11-16 11:48:39 45.94.119.215:9459 Control Channel: TLSv1.3, cipher TLSv1.3 TLS_AES_256_GCM_SHA384, peer certificate: 2048 bit RSA, signature: RSA-SHA256
2024-11-16 11:48:39 45.94.119.215:9459 [MkrT_A] Peer Connection Initiated with [AF_INET]45.94.119.215:9459
2024-11-16 11:48:39 MkrT_A/45.94.119.215:9459 MULTI_sva: pool returned IPv4=10.8.0.6, IPv6=(Not enabled)
2024-11-16 11:48:39 MkrT_A/45.94.119.215:9459 MULTI: Learn: 10.8.0.6 -> MkrT_A/45.94.119.215:9459
2024-11-16 11:48:39 MkrT_A/45.94.119.215:9459 MULTI: primary virtual IP for MkrT_A/45.94.119.215:9459: 10.8.0.6
2024-11-16 11:48:39 MkrT_A/45.94.119.215:9459 Outgoing Data Channel: Cipher 'AES-256-GCM' initialized with 256 bit key
2024-11-16 11:48:39 MkrT_A/45.94.119.215:9459 Incoming Data Channel: Cipher 'AES-256-GCM' initialized with 256 bit key
2024-11-16 11:48:39 MkrT_A/45.94.119.215:9459 SENT CONTROL [MkrT_A]: 'PUSH_REPLY,redirect-gateway def1 bypass-dhcp,route 10.8.0.1,topology net30,ping 10,ping-restart 120,ifconfig 10.8.0.6 10.8.0.5,peer-id 0,cipher AES-256-GCM' (status=1)
2024-11-16 11:52:40 MkrT_A/45.94.119.215:9459 [MkrT_A] Inactivity timeout (--ping-restart), restarting
2024-11-16 11:52:40 MkrT_A/45.94.119.215:9459 SIGUSR1[soft,ping-restart] received, client-instance restarting
В iptables правило добавил
iptables -t nat -A POSTROUTING -s 10.8.0.0/24 -o ens3 -j MASQUERADE
--------------
правила пустые
Chain INPUT (policy ACCEPT)
target prot opt source destination
Chain FORWARD (policy ACCEPT)
target prot opt source destination
Chain OUTPUT (policy ACCEPT)
target prot opt source destination
tshark не видит пакеты с клиентского IP 10.8.0.6
вывод ip route c сервера
ip route
default via 185.112.249.1 dev ens3 onlink
10.8.0.0/24 via 10.8.0.2 dev tun0
10.8.0.2 dev tun0 proto kernel scope link src 10.8.0.1
10.10.44.0/24 via 192.168.193.146 dev ztcfwt3d5l proto static metric 5000
ХХХ.ХХХ.ХХХ.0/24 dev ens3 proto kernel scope link src ХХХ.ХХХ.ХХХ.ХХХ
192.168.88.0/24 via 192.168.193.138 dev ztcfwt3d5l proto static metric 5000
192.168.193.0/24 dev ztcfwt3d5l proto kernel scope link src 192.168.193.50
т.е. подключение есть, маршруты есть, nat есть.
Где я накосячил???
Тема: OpenVPN не уходят пакеты (Прочитано 1135 раз)
