Openvpn dns leakeage

devheitor · 2022-04-08 19:39:10

I'm relatively new to linux network configuration but I have configured a VPN server on a personal computer running in a trusted network and a VPN client in other personal computer that could access the internet via an untrusted network safely routing the internet traffic through VPN. The general idea, of course, is the entire internet traffic getting encrypted, so no one can intercept it via public Wi-Fi as well as send all DNS queries to go through the VPN.

For that I thoroughly researched the related Arch Linux Wiki documentation pages for installing and configuring an openvpn server and client.

Briefly speaking, I followed the steps on
https://wiki.archlinux.org/title/OpenVP … the_server

adding to server.conf:

push "redirect-gateway def1 bypass-dhcp ipv6"

as well as to client.conf:

push "redirect-gateway def1 bypass-dhcp"

Configured Firewall on my openvpn server with

sudo sysctl -w net.ipv4.ip_forward=1
iptables -t nat -A POSTROUTING -s 10.8.0.0/24 -o wlp2s0 -j MASQUERADE

For DNS matter I followed the steps on
https://wiki.archlinux.org/title/OpenVPN#DNS

using the update-systemd-resolved custom script installed and configured via
https://github.com/jonathanio/update-sy … ns-leakage

made sure that systemd-resolved is enabled and running and follow the exactly steps for NSS and nssswitch.conf as well as Stub Resolver

I, as well, added a PolicyKit as described on arch linux documentation page to allow OpenVPN systemd units to call DBus with SetLinkDNS

/etc/polkit-1/rules.d/00-openvpn-resolved.rules

polkit.addRule(function(action, subject) {
    if (action.id == 'org.freedesktop.resolve1.set-dns-servers' ||
        action.id == 'org.freedesktop.resolve1.set-domains' ||
        action.id == 'org.freedesktop.resolve1.set-dnssec') {
        if (subject.user == 'openvpn') {
            return polkit.Result.YES;
        }
    }
});

Unfortunatelly after all, I accessed https://dnsleaktest.com to test if I'm connect to internet through vpn and if I'm facing any DNS leakeage.
In fact, I'm succesfully connected through VPN, but unsuccesfully having DNS leakeage issues. When I run the test, the hostname and ISP listed are still from the untrusted network.

openvpn server.conf

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

# 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 home-server.crt
key home-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
ecdh-curve secp521r1

# Network topology
# Should be subnet (addressing via IP)
# unless Windows clients v2.0.9 and lower have to
# be supported (then net30, i.e. a /30 per client)
# Defaults to net30 (not recommended)
;topology subnet

# Configure server mode and supply a VPN subnet
# for OpenVPN to draw client addresses from.
# The server will take 10.8.0.1 for itself,
# the rest will be made available to clients.
# Each client will be able to reach the server
# on 10.8.0.1. Comment this line out if you are
# ethernet bridging. See the man page for more info.
server 10.8.0.0 255.255.255.0

# Maintain a record of client <-> virtual IP address
# associations in this file.  If OpenVPN goes down or
# is restarted, reconnecting clients can be assigned
# the same virtual IP address from the pool that was
# previously assigned.
ifconfig-pool-persist ipp.txt

# Configure server mode for ethernet bridging.
# You must first use your OS's bridging capability
# to bridge the TAP interface with the ethernet
# NIC interface.  Then you must manually set the
# IP/netmask on the bridge interface, here we
# assume 10.8.0.4/255.255.255.0.  Finally we
# must set aside an IP range in this subnet
# (start=10.8.0.50 end=10.8.0.100) to allocate
# to connecting clients.  Leave this line commented
# out unless you are ethernet bridging.
;server-bridge 10.8.0.4 255.255.255.0 10.8.0.50 10.8.0.100

# Configure server mode for ethernet bridging
# using a DHCP-proxy, where clients talk
# to the OpenVPN server-side DHCP server
# to receive their IP address allocation
# and DNS server addresses.  You must first use
# your OS's bridging capability to bridge the TAP
# interface with the ethernet NIC interface.
# Note: this mode only works on clients (such as
# Windows), where the client-side TAP adapter is
# bound to a DHCP client.
;server-bridge

# Push routes to the client to allow it
# to reach other private subnets behind
# the server.  Remember that these
# private subnets will also need
# to know to route the OpenVPN client
# address pool (10.8.0.0/255.255.255.0)
# back to the OpenVPN server.
;push "route 192.168.10.0 255.255.255.0"
;push "route 192.168.20.0 255.255.255.0"

# To assign specific IP addresses to specific
# clients or if a connecting client has a private
# subnet behind it that should also have VPN access,
# use the subdirectory "ccd" for client-specific
# configuration files (see man page for more info).

# EXAMPLE: Suppose the client
# having the certificate common name "Thelonious"
# also has a small subnet behind his connecting
# machine, such as 192.168.40.128/255.255.255.248.
# First, uncomment out these lines:
;client-config-dir ccd
;route 192.168.40.128 255.255.255.248
# Then create a file ccd/Thelonious with this line:
#   iroute 192.168.40.128 255.255.255.248
# This will allow Thelonious' private subnet to
# access the VPN.  This example will only work
# if you are routing, not bridging, i.e. you are
# using "dev tun" and "server" directives.

# EXAMPLE: Suppose you want to give
# Thelonious a fixed VPN IP address of 10.9.0.1.
# First uncomment out these lines:
;client-config-dir ccd
;route 10.9.0.0 255.255.255.252
# Then add this line to ccd/Thelonious:
#   ifconfig-push 10.9.0.1 10.9.0.2

# Suppose that you want to enable different
# firewall access policies for different groups
# of clients.  There are two methods:
# (1) Run multiple OpenVPN daemons, one for each
#     group, and firewall the TUN/TAP interface
#     for each group/daemon appropriately.
# (2) (Advanced) Create a script to dynamically
#     modify the firewall in response to access
#     from different clients.  See man
#     page for more info on learn-address script.
;learn-address ./script

# If enabled, this directive will configure
# all clients to redirect their default
# network gateway through the VPN, causing
# all IP traffic such as web browsing and
# and DNS lookups to go through the VPN
# (The OpenVPN server machine may need to NAT
# or bridge the TUN/TAP interface to the internet
# in order for this to work properly).
#push "redirect-gateway def1 bypass-dhcp ipv6"
push "redirect-gateway def1 bypass-dhcp"
#push "dhcp-option DOMAIN-ROUTE ."

# 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 # Replaces tls-auth ta.key 0

# 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

openvpn client.conf

##############################################
# 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 xxx.xx.xx.xxx 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 cert.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
tls-crypt ta.key # Replaces 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

# 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

redirect-gateway def1 bypass-dhcp ipv6

dhcp-option DOMAIN-ROUTE .

script-security 2
up /usr/bin/update-systemd-resolved
up-restart
down /usr/bin/update-systemd-resolved
down-pre

Any hint what might be happening? Please let me know if I missed any specification of my systems, I'll be prompt to answer.
I have been researching a lot but I'm facing not knowing where to go, or what to check now.

I appreciate any considerations.

Strike0 · 2022-04-08 21:40:33

Hi & welcome to the forum,

The following needs changing in your config:
Since openvpn 2.5.0 the user/group nobody should not be used anymore. (The wiki apparently is not uptodate)

Have a look at the logging for the services. Do you see errors?

devheitor · 2022-04-08 21:56:49

Hi Strike0, thank you very much.

What services should I look?
I have looked the logs for

journalctl -u systemd-resolved.service

Apr 08 18:47:04 home-server systemd-resolved[1141]: Flushed all caches.
Apr 08 18:49:42 home-server systemd-resolved[1141]: Flushed all caches.
Apr 08 18:49:50 home-server systemd-resolved[1141]: tun0: Bus client set search domain list to: ~.
Apr 08 18:49:50 home-server systemd-resolved[1141]: Flushed all caches.
Apr 08 18:50:40 home-server systemd-resolved[1141]: Using degraded feature set UDP instead of UDP+EDNS0 for DNS server 143.107.45.11.

And I don't see any error...
I'm also not using the user/group nobody anymore, but no help in DNS leakeage issue..

# Downgrade privileges after initialization (non-Windows only)
#user nobody
#group nobody

Last edited by devheitor (2022-04-08 21:59:16)

Strike0 · 2022-04-09 06:21:52

The services you start for the VPN on the machine where you experience the leaks, i.e. the client machine. For your setup you can also directly check which DNS is active via systemd-resolve --status
Also, have a look at this post from the issue tracker of the script you use: https://github.com/jonathanio/update-sy … -803477296

devheitor · 2022-04-17 15:53:25

HI Strike0, thanks again for the help.

I take some days to read the post you mentioned, and it was very elucidating, specially deeper in the issue mentioned by piotr-dobrogost commented on Mar 20, 2021:
https://github.com/systemd/systemd/issues/6076

The matter is:
before running openvpn client.conf

> systemd-resolve --status             
Global
           Protocols: +LLMNR +mDNS -DNSOverTLS DNSSEC=no/unsupported
    resolv.conf mode: stub
Fallback DNS Servers: 9.9.9.9#dns.quad9.net 8.8.8.8#dns.google
                      2620:fe::9#dns.quad9.net 2001:4860:4860::8888#dns.google

Link 2 (enp2s0)
Current Scopes: none
     Protocols: -DefaultRoute +LLMNR -mDNS -DNSOverTLS DNSSEC=no/unsupported

Link 3 (wlo1)
    Current Scopes: DNS LLMNR/IPv4 LLMNR/IPv6
         Protocols: +DefaultRoute +LLMNR -mDNS -DNSOverTLS DNSSEC=no/unsupported
Current DNS Server: 2804:214:8000:ffff::88
       DNS Servers: 192.168.43.1 2804:214:8000:ffff::88
                    fe80::a8c:2cff:fead:ff71%32682

after running openvpn client.conf, vpn starts succesfully, update-systemd-resolved script is executed and have updated systemd-resolve service as expected, creating a new link - Link 15 (tun0)

> systemd-resolve --status
Global
           Protocols: +LLMNR +mDNS -DNSOverTLS DNSSEC=no/unsupported
    resolv.conf mode: stub
Fallback DNS Servers: 9.9.9.9#dns.quad9.net 8.8.8.8#dns.google
                      2620:fe::9#dns.quad9.net 2001:4860:4860::8888#dns.google

Link 2 (enp2s0)
Current Scopes: none
     Protocols: -DefaultRoute +LLMNR -mDNS -DNSOverTLS DNSSEC=no/unsupported

Link 3 (wlo1)
    Current Scopes: DNS LLMNR/IPv4 LLMNR/IPv6
         Protocols: +DefaultRoute +LLMNR -mDNS -DNSOverTLS DNSSEC=no/unsupported
Current DNS Server: fe80::a8c:2cff:fead:ff71%32765
       DNS Servers: 192.168.43.1 2804:214:8000:ffff::88
                    fe80::a8c:2cff:fead:ff71%32564

Link 15 (tun0)
Current Scopes: LLMNR/IPv4 LLMNR/IPv6
     Protocols: -DefaultRoute +LLMNR -mDNS -DNSOverTLS DNSSEC=no/unsupported
    DNS Domain: ~.

yet, as it can be seen, there is no difference for Link 3 (wl01) emphasised here:

Link 3 (wlo1)
    Current Scopes: DNS LLMNR/IPv4 LLMNR/IPv6
         Protocols: +DefaultRoute +LLMNR -mDNS -DNSOverTLS DNSSEC=no/unsupported
Current DNS Server: fe80::a8c:2cff:fead:ff71%32765
       DNS Servers: 192.168.43.1 2804:214:8000:ffff::88
                    fe80::a8c:2cff:fead:ff71%32564

The dns server listed is the one that seems to use the Internet Service Provider dns lookup.
As I told, I'm new to linux networking, but it seems to me that even when on vpn, openvpn is using the DNS Servers configured for Link 3 (wl01)

Researching on the issue I mentioned, I could figured out an workaround.
First option following the steps shared by snabb commented on Oct 29, 2017

snabb commented on Oct 29, 2017 wrote:

My current workaround is to do the following tricks every time I start my workplace VPN:
Find out the link number (a.k.a. interface index) of the ISP interface: systemd-resolve --status or ip l.
Connect the VPN.
Remove DNS settings from the ISP interface (using the link number from step 1) by sending a D-Bus command to systemd-resolved. This is an example using link number 2: sudo busctl call org.freedesktop.resolve1 /org/freedesktop/resolve1 org.freedesktop.resolve1.Manager SetLinkDNS 'ia(iay)' 2 0
Inspect with systemd-resolve --status to ensure that only the correct DNS servers are there.
Apparently there isn't any simple cli tool for managing systemd-resolved's settings. That busctl command isn't very user-friendly.

The other option would be just run the systemd-resolve command for the interface that is connecting to the internet and configured with the wrong DNS Servers with --revert flag:

sudo systemd-resolve -i wlo1 --revert

The result is

> systemd-resolve --status             
Global
           Protocols: +LLMNR +mDNS -DNSOverTLS DNSSEC=no/unsupported
    resolv.conf mode: stub
  Current DNS Server: 9.9.9.9#dns.quad9.net
Fallback DNS Servers: 9.9.9.9#dns.quad9.net 8.8.8.8#dns.google
                      2620:fe::9#dns.quad9.net 2001:4860:4860::8888#dns.google

Link 2 (enp2s0)
Current Scopes: none
     Protocols: -DefaultRoute +LLMNR -mDNS -DNSOverTLS DNSSEC=no/unsupported

Link 3 (wlo1)
Current Scopes: LLMNR/IPv4 LLMNR/IPv6
     Protocols: -DefaultRoute +LLMNR -mDNS -DNSOverTLS DNSSEC=no/unsupported

Link 15 (tun0)
Current Scopes: LLMNR/IPv4 LLMNR/IPv6
     Protocols: -DefaultRoute +LLMNR -mDNS -DNSOverTLS DNSSEC=no/unsupported
    DNS Domain: ~.

and now I don't see the hostname and ISP from the untrusted network listed in https://www.dnsleaktest.com/results.html , but just Google and WoodyNet, probably due to the configuration in

Global
           Protocols: +LLMNR +mDNS -DNSOverTLS DNSSEC=no/unsupported
    resolv.conf mode: stub
  Current DNS Server: 9.9.9.9#dns.quad9.net
Fallback DNS Servers: 9.9.9.9#dns.quad9.net 8.8.8.8#dns.google
                      2620:fe::9#dns.quad9.net 2001:4860:4860::8888#dns.google

Unfurtunatelly, honestly, I'm not totally sure if that is the best workaround or the best way to solve the matter. But here it is the way I have evolved from that.

Again, thanks for the help till now, and I would definitely appreciate more considerations from the community, if there are any.

Last edited by devheitor (2022-04-17 21:30:12)

Strike0 · 2022-04-19 15:03:43

Hi, great that you appear to have you found a work-around. Reading DNS leakage: If you want the client to resolve via a dns service like quad9 or google, regardless of whether it is connected to VPN or not - it should be possible to achieve that, with a simple static resolve configuration, disabling the automatism (incl systemd-resolve) you struggle with. That's basically what you achieve with your work-around now. The only thing that may break with such a static config are some public portals using redirects upon first connect.

Aside from the static client resolv.conf, change your client's vpn "dhcp-option DOMAIN-ROUTE" to "dhcp-option DNS 9.9.9.9". The client.conf should also use the "pull" option. If you want the client to use a specific dns upon vpn-connection, your vpn-server should first have specify one, e.g. 'push "dhcp-option DNS 9.9.9.9"' in the config.
Regarding leakage, check whether the route (ip route) upon connection to the vpn shows a catch all (0.0.0.0/1 via .... dev tun0) as first route. That's my 2c.

Perhaps somebody else indeed spots something else to help you with it.

progandy · 2022-04-19 15:23:56

To me it looks like the biggest problem is that openvpn does not set a DNS server for tun0. If there was a DNS server set for tun0, I believe the systemd-resolved configuration should work even with the non-vpn servers set to wl01.

Arch Linux

#1 2022-04-08 19:39:10

Openvpn dns leakeage

#2 2022-04-08 21:40:33

Re: Openvpn dns leakeage

#3 2022-04-08 21:56:49

Re: Openvpn dns leakeage

#4 2022-04-09 06:21:52

Re: Openvpn dns leakeage

#5 2022-04-17 15:53:25

Re: Openvpn dns leakeage

#6 2022-04-19 15:03:43

Re: Openvpn dns leakeage

#7 2022-04-19 15:23:56

Re: Openvpn dns leakeage

Board footer