TLS Error

anthomedal

Hello,

I have a server with debian 9 connected with ethernet to my box and I try to connect on of my Pc connected with ethernet to the same box with openvpn. For the moment I try local connection with local IP on my network. My server configuration file :

# Port protocole et interface
port 1194
proto udp
dev tun

# Chemin vers les fichiers ssl
ca keys/ca.crt
cert keys/server.crt
key keys/server.key
dh keys/dh2048.pem

# IP désirée pour le serveur
server 10.8.0.0 255.255.255.0
ifconfig-pool-persist ipp.txt
keepalive 10 120
comp-lzo
user nobody
group nogroup
persist-key
persist-tun
status openvpn-status.log
verb 3

# On définit le serveur VPN comme passerelle par défaut pour les clients.
push "redirect-gateway def1"
push "route 10.9.8.0 255.255.252.0"
# On définit le serveur VPN comme DNS par défaut
push "dhcp-option DNS 10.8.0.1"
persist-tun

My client configuration file :

##############################################
# 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 192.168.0.10
;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 nogroup

# 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 client1.crt
key client1.key

# Verify server certificate by checking that the
# certicate has the correct key usage set.
# This is an important precaution to protect against
# a potential attack discussed here:
#  http://openvpn.net/howto.html#mitm
#
# To use this feature, you will need to generate
# your server certificates with the keyUsage set to
#   digitalSignature, keyEncipherment
# and the extendedKeyUsage to
#   serverAuth
# EasyRSA can do this for you.
remote-cert-tls server

# If a tls-auth key is used on the server
# then every client must also have the key.
;tls-auth ta.key 1

# Select a cryptographic cipher.
# If the cipher option is used on the server
# then you must also specify it here.
# Note that 2.4 client/server will automatically
# negotiate AES-256-GCM in TLS mode.
# See also the ncp-cipher option in the manpage
cipher AES-256-CBC

# Enable compression on the VPN link.
# Don't enable this unless it is also
# enabled in the server config file.
#comp-lzo

# Set log file verbosity.
verb 3

# Silence repeating messages
;mute 20

But when I connect (over windows or ubuntu) I have this error :

TLS Error: TLS key negotiation failed to occur within 60 seconds (check your network connectivity)

And with OpenVPN GUI I can see :

Bytes in : 0 B

during all operation.

The full log during connection :

Wed Jul 25 19:28:47 2018 NOTE: --user option is not implemented on Windows
Wed Jul 25 19:28:47 2018 NOTE: --group option is not implemented on Windows
Wed Jul 25 19:28:47 2018 OpenVPN 2.4.6 x86_64-w64-mingw32 [SSL (OpenSSL)] [LZO] [LZ4] [PKCS11] [AEAD] built on Apr 26 2018
Wed Jul 25 19:28:47 2018 Windows version 6.1 (Windows 7) 64bit
Wed Jul 25 19:28:47 2018 library versions: OpenSSL 1.1.0h  27 Mar 2018, LZO 2.10
Wed Jul 25 19:28:47 2018 MANAGEMENT: TCP Socket listening on [AF_INET]127.0.0.1:25340
Wed Jul 25 19:28:47 2018 Need hold release from management interface, waiting...
Wed Jul 25 19:28:47 2018 MANAGEMENT: Client connected from [AF_INET]127.0.0.1:25340
Wed Jul 25 19:28:47 2018 MANAGEMENT: CMD 'state on'
Wed Jul 25 19:28:47 2018 MANAGEMENT: CMD 'log all on'
Wed Jul 25 19:28:47 2018 MANAGEMENT: CMD 'echo all on'
Wed Jul 25 19:28:47 2018 MANAGEMENT: CMD 'bytecount 5'
Wed Jul 25 19:28:47 2018 MANAGEMENT: CMD 'hold off'
Wed Jul 25 19:28:47 2018 MANAGEMENT: CMD 'hold release'
Wed Jul 25 19:28:47 2018 TCP/UDP: Preserving recently used remote address: [AF_INET]192.168.0.10:1194
Wed Jul 25 19:28:47 2018 Socket Buffers: R=[8192->8192] S=[8192->8192]
Wed Jul 25 19:28:47 2018 UDP link local: (not bound)
Wed Jul 25 19:28:47 2018 UDP link remote: [AF_INET]192.168.0.10:1194
Wed Jul 25 19:28:47 2018 MANAGEMENT: >STATE:1532539727,WAIT,,,,,,
Wed Jul 25 19:29:48 2018 TLS Error: TLS key negotiation failed to occur within 60 seconds (check your network connectivity)
Wed Jul 25 19:29:48 2018 TLS Error: TLS handshake failed
Wed Jul 25 19:29:48 2018 SIGUSR1[soft,tls-error] received, process restarting
Wed Jul 25 19:29:48 2018 MANAGEMENT: >STATE:1532539788,RECONNECTING,tls-error,,,,,
Wed Jul 25 19:29:48 2018 Restart pause, 5 second(s)

I already read this : https://openvpn.net/index.php/open-source/faq/79-client/253-tls-error-tls-key-negotiation-failed-to-occur-within-60-seconds-check-your-network-connectivity.html but I did't manage.

Have you an idea ?

Thank you !

TinCanTech

And your server log .. ?

Use --verb 4

Here is an example:
HOWTO: Request Help ! {2}

anthomedal

Hello,

I try to configure a debian server with openvpn. First that's what I can do actually :
Connect to server with client with any internet connection.

But when I connect, I can't use the web.

My server's file config :

local 192.168.0.10

port 1194

proto udp

dev tun

ca keys/ca.crt
cert keys/server.crt
key keys/server.key  # This file should be kept secret
dh keys/dh2048.pem

server 10.8.0.0 255.255.255.0

ifconfig-pool-persist ipp.txt

push "route 10.8.0.1 255.255.255.255"
push "route 10.8.0.0 255.255.255.0"
push "route 192.168.0.0 255.255.255.0"

;push "redirect-gateway def1 bypass-dhcp"
push "redirect-gateway def1"

;push "dhcp-option DNS 208.67.222.222"
;push "dhcp-option DNS 208.67.220.220"
# 8.8.8.8 is public IP of a Google DNS 
push "dhcp-option DNS 8.8.8.8"
;push "dhcp-option DNS 217.237.150.188"
# 192.168.0.1 is the local IP of my box 
push "dhcp-option DNS 192.168.0.1"

client-to-client

keepalive 10 120

user nobody
group nogroup

persist-key
persist-tun

status openvpn-status.log

verb 3

explicit-exit-notify 1

My client's file config :

client

dev tun

proto udp

remote my.ip 1194

resolv-retry infinite

nobind

user nobody
group nogroup

persist-key
persist-tun

mute-replay-warnings

ca ca.crt
cert client1.crt
key client1.key

verb 3

When I run the server I run this commands :

iptables -A INPUT -i tun+ -j ACCEPT
iptables -A FORWARD -i tun+ -j ACCEPT
iptables -A FORWARD -m state --state ESTABLISHED,RELATED -j ACCEPT
iptables -t nat -F POSTROUTING
iptables -t nat -A POSTROUTING -s 10.8.0.0/24 -o eth0 -j MASQUERADE
iptables -t nat -A INPUT -i eth0 -p udp -m udp --dport 1194 -j ACCEPT
iptables -t nat -A POSTROUTING -s 10.8.0.0/24 -o eth0 -j SNAT --to-source 192.168.0.10
service openvpn restart
service openvpn status

192.168.0.10 is local IP of server.

Must I run this command on server ? (many tutorials don't do that, but how server can know the server.config file ?)

service openvpn stop
openvpn server.conf

When I run it, it print that :

Fri Jul 27 14:42:34 2018 OpenVPN 2.4.0 i686-pc-linux-gnu [SSL (OpenSSL)] [LZO] [LZ4] [EPOLL] [PKCS11] [MH/PKTINFO] [AEAD] built on Jul 18 2017
Fri Jul 27 14:42:34 2018 library versions: OpenSSL 1.0.2l  25 May 2017, LZO 2.08
Fri Jul 27 14:42:34 2018 NOTE: your local LAN uses the extremely common subnet address 192.168.0.x or 192.168.1.x.  Be aware that this might create 

routing conflicts if you connect to the VPN server from public locations such as internet cafes that use the same subnet.
Fri Jul 27 14:42:34 2018 Diffie-Hellman initialized with 2048 bit key
Fri Jul 27 14:42:34 2018 ROUTE_GATEWAY 192.168.0.1/255.255.255.0 IFACE=enp1s0 HWADDR=00:04:e2:2a:a6:dc
Fri Jul 27 14:42:34 2018 TUN/TAP device tun0 opened
Fri Jul 27 14:42:34 2018 TUN/TAP TX queue length set to 100
Fri Jul 27 14:42:34 2018 do_ifconfig, tt->did_ifconfig_ipv6_setup=0
Fri Jul 27 14:42:34 2018 /sbin/ip link set dev tun0 up mtu 1500
Fri Jul 27 14:42:34 2018 /sbin/ip addr add dev tun0 local 10.8.0.1 peer 10.8.0.2
Fri Jul 27 14:42:34 2018 /sbin/ip route add 10.8.0.0/24 via 10.8.0.2
Fri Jul 27 14:42:34 2018 Could not determine IPv4/IPv6 protocol. Using AF_INET
Fri Jul 27 14:42:34 2018 Socket Buffers: R=[163840->163840] S=[163840->163840]
Fri Jul 27 14:42:34 2018 UDPv4 link local (bound): [AF_INET]192.168.0.10:1194
Fri Jul 27 14:42:34 2018 UDPv4 link remote: [AF_UNSPEC]
Fri Jul 27 14:42:34 2018 GID set to nogroup
Fri Jul 27 14:42:34 2018 UID set to nobody
Fri Jul 27 14:42:34 2018 MULTI: multi_init called, r=256 v=256
Fri Jul 27 14:42:34 2018 IFCONFIG POOL: base=10.8.0.4 size=62, ipv6=0
Fri Jul 27 14:42:34 2018 ifconfig_pool_read(), in='client1,10.8.0.4', TODO: IPv6
Fri Jul 27 14:42:34 2018 succeeded -> ifconfig_pool_set()
Fri Jul 27 14:42:34 2018 IFCONFIG POOL LIST
Fri Jul 27 14:42:34 2018 client1,10.8.0.4
Fri Jul 27 14:42:34 2018 Initialization Sequence Completed

After, I run client (windows), It print that :

Fri Jul 27 12:45:50 2018 NOTE: --user option is not implemented on Windows
Fri Jul 27 12:45:50 2018 NOTE: --group option is not implemented on Windows
Fri Jul 27 12:45:50 2018 OpenVPN 2.4.6 x86_64-w64-mingw32 [SSL (OpenSSL)] [LZO] [LZ4] [PKCS11] [AEAD] built on Apr 26 2018
Fri Jul 27 12:45:50 2018 Windows version 6.1 (Windows 7) 64bit
Fri Jul 27 12:45:50 2018 library versions: OpenSSL 1.1.0h  27 Mar 2018, LZO 2.10
Fri Jul 27 12:45:50 2018 MANAGEMENT: TCP Socket listening on [AF_INET]127.0.0.1:25340
Fri Jul 27 12:45:50 2018 Need hold release from management interface, waiting...
Fri Jul 27 12:45:50 2018 MANAGEMENT: Client connected from [AF_INET]127.0.0.1:25340
Fri Jul 27 12:45:50 2018 MANAGEMENT: CMD 'state on'
Fri Jul 27 12:45:50 2018 MANAGEMENT: CMD 'log all on'
Fri Jul 27 12:45:50 2018 MANAGEMENT: CMD 'echo all on'
Fri Jul 27 12:45:50 2018 MANAGEMENT: CMD 'bytecount 5'
Fri Jul 27 12:45:50 2018 MANAGEMENT: CMD 'hold off'
Fri Jul 27 12:45:50 2018 MANAGEMENT: CMD 'hold release'
Fri Jul 27 12:45:50 2018 WARNING: No server certificate verification method has been enabled.  See http://openvpn.net/howto.html#mitm for more info.
Fri Jul 27 12:45:50 2018 TCP/UDP: Preserving recently used remote address: [AF_INET]my.ip:1194
Fri Jul 27 12:45:50 2018 Socket Buffers: R=[8192->8192] S=[8192->8192]
Fri Jul 27 12:45:50 2018 UDP link local: (not bound)
Fri Jul 27 12:45:50 2018 UDP link remote: [AF_INET]my.ip:1194
Fri Jul 27 12:45:50 2018 MANAGEMENT: >STATE:1532688350,WAIT,,,,,,
Fri Jul 27 12:45:50 2018 MANAGEMENT: >STATE:1532688350,AUTH,,,,,,
Fri Jul 27 12:45:50 2018 TLS: Initial packet from [AF_INET]my.ip:1194, sid=d3653085 56ea18db
Fri Jul 27 12:45:50 2018 VERIFY OK: depth=1, C=FR, ST=GEST, L=Argancy, O=serveur.domaine.org, OU=MyOrganizationalUnit, CN=serveur.domaine.org CA, 

name=EasyRSA, emailAddress=admin@domaine.org
Fri Jul 27 12:45:50 2018 VERIFY OK: depth=0, C=FR, ST=GEST, L=Argancy, O=serveur.domaine.org, OU=MyOrganizationalUnit, CN=server, name=EasyRSA, 

emailAddress=admin@domaine.org
Fri Jul 27 12:45:50 2018 Control Channel: TLSv1.2, cipher TLSv1.2 ECDHE-RSA-AES256-GCM-SHA384, 2048 bit RSA
Fri Jul 27 12:45:50 2018 [server] Peer Connection Initiated with [AF_INET]78.24.242.43:1194
Fri Jul 27 12:45:51 2018 MANAGEMENT: >STATE:1532688351,GET_CONFIG,,,,,,
Fri Jul 27 12:45:51 2018 SENT CONTROL [server]: 'PUSH_REQUEST' (status=1)
Fri Jul 27 12:45:51 2018 PUSH: Received control message: 'PUSH_REPLY,route 10.8.0.1 255.255.255.255,route 10.8.0.0 255.255.255.0,route 192.168.0.0 

255.255.255.0,redirect-gateway def1,dhcp-option DNS 8.8.8.8,dhcp-option DNS 192.168.0.1,route 10.8.0.0 255.255.255.0,topology net30,ping 10,ping-restart 

120,ifconfig 10.8.0.6 10.8.0.5,peer-id 0,cipher AES-256-GCM'
Fri Jul 27 12:45:51 2018 OPTIONS IMPORT: timers and/or timeouts modified
Fri Jul 27 12:45:51 2018 OPTIONS IMPORT: --ifconfig/up options modified
Fri Jul 27 12:45:51 2018 OPTIONS IMPORT: route options modified
Fri Jul 27 12:45:51 2018 OPTIONS IMPORT: --ip-win32 and/or --dhcp-option options modified
Fri Jul 27 12:45:51 2018 OPTIONS IMPORT: peer-id set
Fri Jul 27 12:45:51 2018 OPTIONS IMPORT: adjusting link_mtu to 1624
Fri Jul 27 12:45:51 2018 OPTIONS IMPORT: data channel crypto options modified
Fri Jul 27 12:45:51 2018 Data Channel: using negotiated cipher 'AES-256-GCM'
Fri Jul 27 12:45:51 2018 Outgoing Data Channel: Cipher 'AES-256-GCM' initialized with 256 bit key
Fri Jul 27 12:45:51 2018 Incoming Data Channel: Cipher 'AES-256-GCM' initialized with 256 bit key
Fri Jul 27 12:45:51 2018 interactive service msg_channel=0
Fri Jul 27 12:45:51 2018 ROUTE_GATEWAY 192.168.0.1/255.255.255.0 I=24 HWADDR=e8:40:f2:68:84:d8
Fri Jul 27 12:45:51 2018 open_tun
Fri Jul 27 12:45:51 2018 TAP-WIN32 device [Connexion au réseau local 2] opened: \\.\Global\{139B9445-1A29-457C-988D-BD4B74DE8C0C}.tap
Fri Jul 27 12:45:51 2018 TAP-Windows Driver Version 9.21 
Fri Jul 27 12:45:51 2018 Notified TAP-Windows driver to set a DHCP IP/netmask of 10.8.0.6/255.255.255.252 on interface {139B9445-1A29-457C-988D-

BD4B74DE8C0C} [DHCP-serv: 10.8.0.5, lease-time: 31536000]
Fri Jul 27 12:45:51 2018 Successful ARP Flush on interface [28] {139B9445-1A29-457C-988D-BD4B74DE8C0C}
Fri Jul 27 12:45:51 2018 do_ifconfig, tt->did_ifconfig_ipv6_setup=0
Fri Jul 27 12:45:51 2018 MANAGEMENT: >STATE:1532688351,ASSIGN_IP,,10.8.0.6,,,,
Fri Jul 27 12:45:56 2018 TEST ROUTES: 5/5 succeeded len=4 ret=1 a=0 u/d=up
Fri Jul 27 12:45:56 2018 C:\Windows\system32\route.exe ADD 78.24.242.43 MASK 255.255.255.255 192.168.0.1
Fri Jul 27 12:45:56 2018 ROUTE: CreateIpForwardEntry succeeded with dwForwardMetric1=10 and dwForwardType=4
Fri Jul 27 12:45:56 2018 Route addition via IPAPI succeeded [adaptive]
Fri Jul 27 12:45:56 2018 C:\Windows\system32\route.exe ADD 0.0.0.0 MASK 128.0.0.0 10.8.0.5
Fri Jul 27 12:45:56 2018 ROUTE: CreateIpForwardEntry succeeded with dwForwardMetric1=20 and dwForwardType=4
Fri Jul 27 12:45:56 2018 Route addition via IPAPI succeeded [adaptive]
Fri Jul 27 12:45:56 2018 C:\Windows\system32\route.exe ADD 128.0.0.0 MASK 128.0.0.0 10.8.0.5
Fri Jul 27 12:45:56 2018 ROUTE: CreateIpForwardEntry succeeded with dwForwardMetric1=20 and dwForwardType=4
Fri Jul 27 12:45:56 2018 Route addition via IPAPI succeeded [adaptive]
Fri Jul 27 12:45:56 2018 MANAGEMENT: >STATE:1532688356,ADD_ROUTES,,,,,,
Fri Jul 27 12:45:56 2018 C:\Windows\system32\route.exe ADD 10.8.0.1 MASK 255.255.255.255 10.8.0.5
Fri Jul 27 12:45:56 2018 ROUTE: CreateIpForwardEntry succeeded with dwForwardMetric1=20 and dwForwardType=4
Fri Jul 27 12:45:56 2018 Route addition via IPAPI succeeded [adaptive]
Fri Jul 27 12:45:56 2018 C:\Windows\system32\route.exe ADD 10.8.0.0 MASK 255.255.255.0 10.8.0.5
Fri Jul 27 12:45:56 2018 ROUTE: CreateIpForwardEntry succeeded with dwForwardMetric1=20 and dwForwardType=4
Fri Jul 27 12:45:56 2018 Route addition via IPAPI succeeded [adaptive]
Fri Jul 27 12:45:56 2018 C:\Windows\system32\route.exe ADD 192.168.0.0 MASK 255.255.255.0 10.8.0.5
Fri Jul 27 12:45:56 2018 ROUTE: CreateIpForwardEntry succeeded with dwForwardMetric1=20 and dwForwardType=4
Fri Jul 27 12:45:56 2018 Route addition via IPAPI succeeded [adaptive]
Fri Jul 27 12:45:56 2018 C:\Windows\system32\route.exe ADD 10.8.0.0 MASK 255.255.255.0 10.8.0.5
Fri Jul 27 12:45:56 2018 ROUTE: route addition failed using CreateIpForwardEntry: Lobjet existe déjà.   [status=5010 if_index=28]
Fri Jul 27 12:45:56 2018 Route addition via IPAPI failed [adaptive]
Fri Jul 27 12:45:56 2018 Route addition fallback to route.exe
Fri Jul 27 12:45:56 2018 env_block: add PATH=C:\Windows\System32;C:\Windows;C:\Windows\System32\Wbem
Fri Jul 27 12:45:56 2018 WARNING: this configuration may cache passwords in memory -- use the auth-nocache option to prevent this
Fri Jul 27 12:45:56 2018 Initialization Sequence Completed
Fri Jul 27 12:45:56 2018 MANAGEMENT: >STATE:1532688356,CONNECTED,SUCCESS,10.8.0.6,78.24.242.43,1194,,

And server print that :

Fri Jul 27 14:45:50 2018 78.24.242.43:52593 TLS: Initial packet from [AF_INET]78                                                                         

                                                                            .24.242.43:52593, sid=08fe3551 3cb27c1b
Fri Jul 27 14:45:50 2018 78.24.242.43:52593 VERIFY OK: depth=1, C=FR, ST=GEST, L=Argancy, O=serveur.domaine.org, OU=MyOrganizationalUnit, 
CN=serveur.domaine.org                                                                                                                                   
CA, name=EasyRSA, emailAddress=admin@domaine.org
Fri Jul 27 14:45:50 2018 78.24.242.43:52593 VERIFY OK: depth=0, C=FR, ST=GEST, L =Argancy, O=serveur.domaine.org, OU=MyOrganizationalUnit, CN=client1, 
name=EasyRSA, emailAddress=admin@domaine.org
Fri Jul 27 14:45:50 2018 78.24.242.43:52593 peer info: IV_VER=2.4.6
Fri Jul 27 14:45:50 2018 78.24.242.43:52593 peer info: IV_PLAT=win
Fri Jul 27 14:45:50 2018 78.24.242.43:52593 peer info: IV_PROTO=2
Fri Jul 27 14:45:50 2018 78.24.242.43:52593 peer info: IV_NCP=2
Fri Jul 27 14:45:50 2018 78.24.242.43:52593 peer info: IV_LZ4=1
Fri Jul 27 14:45:50 2018 78.24.242.43:52593 peer info: IV_LZ4v2=1
Fri Jul 27 14:45:50 2018 78.24.242.43:52593 peer info: IV_LZO=1
Fri Jul 27 14:45:50 2018 78.24.242.43:52593 peer info: IV_COMP_STUB=1
Fri Jul 27 14:45:50 2018 78.24.242.43:52593 peer info: IV_COMP_STUBv2=1
Fri Jul 27 14:45:50 2018 78.24.242.43:52593 peer info: IV_TCPNL=1
Fri Jul 27 14:45:50 2018 78.24.242.43:52593 peer info: IV_GUI_VER=OpenVPN_GUI_11
Fri Jul 27 14:45:50 2018 78.24.242.43:52593 Control Channel: TLSv1.2, cipher TLS                                                                         

                                                                            v1/SSLv3 ECDHE-RSA-AES256-GCM-SHA384, 2048 bit RSA
Fri Jul 27 14:45:50 2018 78.24.242.43:52593 [client1] Peer Connection Initiated                                                                          

                                                                            with [AF_INET]78.24.242.43:52593
Fri Jul 27 14:45:50 2018 client1/78.24.242.43:52593 MULTI_sva: pool returned IPv                                                                         

                                                                            4=10.8.0.6, IPv6=(Not enabled)
Fri Jul 27 14:45:50 2018 client1/78.24.242.43:52593 MULTI: Learn: 10.8.0.6 -> cl                                                                         

                                                                            ient1/my.ip:52593
Fri Jul 27 14:45:50 2018 client1/78.24.242.43:52593 MULTI: primary virtual IP fo                                                                         

                                                                            r client1/my.ip:52593: 10.8.0.6
Fri Jul 27 14:45:51 2018 client1/78.24.242.43:52593 PUSH: Received control messa                                                                         

                                                                            ge: 'PUSH_REQUEST'
Fri Jul 27 14:45:51 2018 client1/78.24.242.43:52593 SENT CONTROL [client1]: 'PUS                                                                         

                                                                            H_REPLY,route 10.8.0.1 255.255.255.255,route 10.8.0.0 255.255.255.0,route 

192.16                                                                                                                                                   

  8.0.0 255.255.255.0,redirect-gateway def1,dhcp-option DNS 8.8.8.8,dhcp-option DN                                                                       

                                                                              S 192.168.0.1,route 10.8.0.0 255.255.255.0,topology net30,ping 10,ping-

restart 1                                                                                                                                                

     20,ifconfig 10.8.0.6 10.8.0.5,peer-id 0,cipher AES-256-GCM' (status=1)
Fri Jul 27 14:45:51 2018 client1/78.24.242.43:52593 Data Channel Encrypt: Cipher                                                                         

                                                                             'AES-256-GCM' initialized with 256 bit key
Fri Jul 27 14:45:51 2018 client1/78.24.242.43:52593 Data Channel Decrypt: Cipher                                                                         

                                                                             'AES-256-GCM' initialized with 256 bit key

Then I quit this on server (CTRL+C) :

^CFri Jul 27 14:46:59 2018 event_wait : Interrupted system call (code=4)
Fri Jul 27 14:46:59 2018 SENT CONTROL [client1]: 'RESTART' (status=1)
Fri Jul 27 14:47:01 2018 /sbin/ip route del 10.8.0.0/24
RTNETLINK answers: Operation not permitted
Fri Jul 27 14:47:01 2018 ERROR: Linux route delete command failed: external program exited with error status: 2
Fri Jul 27 14:47:01 2018 Closing TUN/TAP interface
Fri Jul 27 14:47:01 2018 /sbin/ip addr del dev tun0 local 10.8.0.1 peer 10.8.0.2
RTNETLINK answers: Operation not permitted
Fri Jul 27 14:47:01 2018 Linux ip addr del failed: external program exited with error status: 2
Fri Jul 27 14:47:01 2018 SIGINT[hard,] received, process exiting

I start openvpn

service openvpn start

And on client I have no internet, and I can't ping client with server...

Have an Idea please ?

Thank you !

anthomedal

Sorry that solved 😉

TinCanTech

anthomedal wrote First that's what I can do actually :
Connect to server with client with any internet connection.

But when I connect, I can't use the web.

Your client log shows you are successfully connected:

anthomedal wrote Fri Jul 27 12:45:56 2018 Initialization Sequence Completed

anthomedal wrote When I run the server I run this commands :

iptables -A INPUT -i tun+ -j ACCEPT
iptables -A FORWARD -i tun+ -j ACCEPT
iptables -A FORWARD -m state --state ESTABLISHED,RELATED -j ACCEPT
iptables -t nat -F POSTROUTING
iptables -t nat -A POSTROUTING -s 10.8.0.0/24 -o eth0 -j MASQUERADE
iptables -t nat -A INPUT -i eth0 -p udp -m udp --dport 1194 -j ACCEPT
iptables -t nat -A POSTROUTING -s 10.8.0.0/24 -o eth0 -j SNAT --to-source 192.168.0.10
service openvpn restart
service openvpn status

192.168.0.10 is local IP of server.

The only rule you need is:

iptables -t nat -A POSTROUTING -s 10.8.0.0/24 -o eth0 -j MASQUERADE

Do not do this:

anthomedal wrote

# server config
# 192.168.0.1 is the local IP of my box 
push "dhcp-option DNS 192.168.0.1"

This is the correct tutorial:
HOWTO: Routing all client traffic (including web-traffic) through the VPN

anthomedal

Thank you TinCanTech, I will look that.

I precise, the first topic is solved, not the second, don't close the topic please

anthomedal

I tried with the rule and this config :

local 192.168.0.10

port 1194

proto udp

dev tun

ca keys/ca.crt
cert keys/server.crt
key keys/server.key  # This file should be kept secret
dh keys/dh2048.pem

server 10.8.0.0 255.255.255.0

ifconfig-pool-persist ipp.txt

push "route 10.8.0.1 255.255.255.255"
push "route 10.8.0.0 255.255.255.0"
push "route 192.168.0.0 255.255.255.0"

;push "redirect-gateway def1 bypass-dhcp"
push "redirect-gateway def1"

push "dhcp-option DNS 10.8.0.1"

client-to-client

keepalive 10 120

user nobody
group nogroup

persist-key
persist-tun

status openvpn-status.log

verb 3

explicit-exit-notify 1

And that don't work (no web connection)... Anyone has an idea ?

Thank you !

TinCanTech

Make sure your iptables is using the correct rule. (See above)

anthomedal

The commands that I run after server booting :

iptables -t nat -A POSTROUTING -s 10.8.0.0/24 -o eth0 -j MASQUERADE
service openvpn restart
service openvpn status
service openvpn stop
service openvpn status

I copied your command :/

TinCanTech

Can you ping 8.8.8.8 from both the server and the client when the client is connected to the VPN ?

anthomedal

I can ping 8.8.8.8 from the server but can't with the client. (when the client is connected to the vpn)

TinCanTech

Make sure you have the correct iptables rules. (Try iptables-save)

anthomedal

I did that :

root@Serveur:/home/anthony# iptables -t nat -A POSTROUTING -s 10.8.0.0/24 -o eth0 -j MASQUERADE
root@Serveur:/home/anthony# iptables-save
# Generated by iptables-save v1.6.0 on Sat Jul 28 16:17:50 2018
*nat
:PREROUTING ACCEPT [1:78]
:INPUT ACCEPT [1:78]
:OUTPUT ACCEPT [1:120]
:POSTROUTING ACCEPT [1:120]
-A POSTROUTING -s 10.8.0.0/24 -o eth0 -j MASQUERADE
COMMIT
# Completed on Sat Jul 28 16:17:50 2018

I restarted, and after connection I have always the same problem : can't ping 8.8.8.8 and no web connection when client connect to server.

TinCanTech

Please post the output from:

root@Serveur:/home/anthony$ ip l

anthomedal

Without client connection :

root@Serveur:/home/anthony# ip l
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT                                                                                                                                                      group default qlen 1
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: enp1s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UNK                                                                                                                                                     NOWN mode DEFAULT group default qlen 1000
    link/ether 00:04:e2:2a:a6:dc brd ff:ff:ff:ff:ff:ff
3: tun0: <POINTOPOINT,MULTICAST,NOARP,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast sta                                                                                                                                                     te UNKNOWN mode DEFAULT group default qlen 100
    link/none

And if client connection is the same.

TinCanTech

anthomedal wrote2: enp1s0

This is your device name.

So this is the iptables rule:

iptables -t nat -A POSTROUTING -s 10.8.0.0/24 -o enp1s0 -j MASQUERADE

Note: -o enp1s0

anthomedal

I see what you want to say, but that don't work... If that can help I repost my server config file :

local 192.168.0.10

port 1194

proto udp

dev tun

ca keys/ca.crt
cert keys/server.crt
key keys/server.key  # This file should be kept secret
dh keys/dh2048.pem

server 10.8.0.0 255.255.255.0

ifconfig-pool-persist ipp.txt

push "route 10.8.0.1 255.255.255.255"
push "route 10.8.0.0 255.255.255.0"
push "route 192.168.0.0 255.255.255.0"

;push "redirect-gateway def1 bypass-dhcp"
push "redirect-gateway local def1"

push "dhcp-option DNS 10.8.0.0"

client-to-client

keepalive 10 120

user nobody
group nogroup

persist-key
persist-tun

status openvpn-status.log

verb 3

explicit-exit-notify 1

And the client file :

client

dev tun

proto udp

remote 78.24.242.43 1194

resolv-retry infinite

nobind

user nobody
group nogroup

persist-key
persist-tun

mute-replay-warnings

ca ca.crt
cert client1.crt
key client1.key

verb 3

If you have another idea. Thank you !

TinCanTech

anthomedal wrote I see what you want to say, but that don't work

It does not matter if it works or not .. That *is* the correct setting .. If you do not use it then your server will not masquerade your client packets and your VPN will not be able to send your client packets to the internet.

All I can suggest you do is to try again ..

You can also use tcpdump to see the packets in flight, on your server do:

root@Serveur:/home/anthony$ sudo tcpdump -ni enp1s0

and post the output.

anthomedal

The output :

root@Serveur:/home/anthony# tcpdump -ni enp1s0 > output
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on enp1s0, link-type EN10MB (Ethernet), capture size 262144 bytes

17:56:33.840300 IP 192.168.0.10.22 > 192.168.0.13.50160: Flags [P.], seq 2175532249:2175532377, ack 471080143, win 1211, length 128
17:56:33.840700 IP 192.168.0.10.22 > 192.168.0.13.50160: Flags [P.], seq 128:192, ack 1, win 1211, length 64
17:56:33.841018 IP 192.168.0.10.22 > 192.168.0.13.50160: Flags [P.], seq 192:320, ack 1, win 1211, length 128
17:56:33.841385 IP 192.168.0.10.22 > 192.168.0.13.50160: Flags [P.], seq 320:384, ack 1, win 1211, length 64
17:56:33.841629 IP 192.168.0.13.50160 > 192.168.0.10.22: Flags [.], ack 320, win 16105, length 0
17:56:34.043575 IP 192.168.0.13.50160 > 192.168.0.10.22: Flags [.], ack 384, win 16089, length 0
17:56:35.013927 IP6 fe80::59b:6699:bf51:7cf1.54442 > ff02::c.1900: UDP, length 146
17:56:38.014738 IP6 fe80::59b:6699:bf51:7cf1.54442 > ff02::c.1900: UDP, length 146
17:56:41.014707 IP6 fe80::59b:6699:bf51:7cf1.54442 > ff02::c.1900: UDP, length 146
17:56:44.537924 IP 78.24.242.43.65429 > 192.168.0.10.1194: UDP, length 14
17:56:44.542107 IP 192.168.0.10.1194 > 78.24.242.43.65429: UDP, length 26
17:56:44.542942 IP 78.24.242.43.65429 > 192.168.0.10.1194: UDP, length 22
17:56:44.543050 IP 78.24.242.43.65429 > 192.168.0.10.1194: UDP, length 174
17:56:44.597607 IP 192.168.0.10.1194 > 78.24.242.43.65429: UDP, length 1200
17:56:44.597796 IP 192.168.0.10.1194 > 78.24.242.43.65429: UDP, length 1188
17:56:44.597870 IP 192.168.0.10.1194 > 78.24.242.43.65429: UDP, length 1095
17:56:44.598628 IP 78.24.242.43.65429 > 192.168.0.10.1194: UDP, length 22
17:56:44.598715 IP 78.24.242.43.65429 > 192.168.0.10.1194: UDP, length 22
17:56:44.604696 IP 78.24.242.43.65429 > 192.168.0.10.1194: UDP, length 1200
17:56:44.604775 IP 78.24.242.43.65429 > 192.168.0.10.1194: UDP, length 1188
17:56:44.604841 IP 78.24.242.43.65429 > 192.168.0.10.1194: UDP, length 818
17:56:44.605035 IP 192.168.0.10.1194 > 78.24.242.43.65429: UDP, length 22
17:56:44.605253 IP 192.168.0.10.1194 > 78.24.242.43.65429: UDP, length 22
17:56:44.623176 IP 192.168.0.10.1194 > 78.24.242.43.65429: UDP, length 77
17:56:44.623965 IP 78.24.242.43.65429 > 192.168.0.10.1194: UDP, length 439
17:56:44.632124 IP 192.168.0.10.1194 > 78.24.242.43.65429: UDP, length 247
17:56:44.632925 IP 78.24.242.43.65429 > 192.168.0.10.1194: UDP, length 22
17:56:45.015906 IP6 fe80::59b:6699:bf51:7cf1.54442 > ff02::c.1900: UDP, length 146
17:56:45.836030 IP 78.24.242.43.65429 > 192.168.0.10.1194: UDP, length 56
17:56:45.837359 IP 192.168.0.10.1194 > 78.24.242.43.65429: UDP, length 22
17:56:45.837525 IP 192.168.0.10.1194 > 78.24.242.43.65429: UDP, length 324
17:56:45.861231 IP6 fe80::59b:6699:bf51:7cf1.63344 > ff02::1:3.5355: UDP, length 24
17:56:45.865739 IP 78.24.242.43.65429 > 192.168.0.10.1194: UDP, length 22
17:56:45.876160 IP6 fe80::59b:6699:bf51:7cf1 > ff02::16: HBH ICMP6, multicast listener report v2, 1 group record(s), length 28
17:56:45.876183 IP 192.168.0.13 > 224.0.0.2: igmp leave 224.0.0.252
17:56:45.894020 ARP, Request who-has 192.168.0.1 tell 192.168.0.13, length 46
17:56:45.895544 IP 192.168.0.13.61890 > 239.255.255.250.3702: UDP, length 994
17:56:45.900190 IP6 fe80::59b:6699:bf51:7cf1.61891 > ff02::c.3702: UDP, length 994
17:56:45.902919 ARP, Request who-has 192.168.0.1 tell 192.168.0.13, length 46
17:56:45.903369 IP6 fe80::59b:6699:bf51:7cf1 > ff02::16: HBH ICMP6, multicast listener report v2, 1 group record(s), length 28
17:56:45.903723 IP6 fe80::59b:6699:bf51:7cf1 > ff02::16: HBH ICMP6, multicast listener report v2, 1 group record(s), length 28
17:56:45.903749 IP 192.168.0.13 > 224.0.0.2: igmp leave 224.0.0.252
17:56:45.903888 IP6 fe80::59b:6699:bf51:7cf1 > ff02::16: HBH ICMP6, multicast listener report v2, 1 group record(s), length 28
17:56:45.904547 IP6 fe80::59b:6699:bf51:7cf1.58087 > ff02::1:3.5355: UDP, length 28
17:56:45.912154 IP 78.24.242.43.65429 > 192.168.0.10.1194: UDP, length 100
17:56:45.919193 IP 78.24.242.43.65429 > 192.168.0.10.1194: UDP, length 100
17:56:45.919771 IP 78.24.242.43.65429 > 192.168.0.10.1194: UDP, length 100
17:56:45.928425 IP 78.24.242.43.65429 > 192.168.0.10.1194: UDP, length 100
17:56:45.929099 IP 78.24.242.43.65429 > 192.168.0.10.1194: UDP, length 100
17:56:45.929198 IP 78.24.242.43.65429 > 192.168.0.10.1194: UDP, length 162
17:56:45.946571 IP 192.168.0.13.53010 > 239.255.255.250.3702: UDP, length 656
17:56:45.946710 IP6 fe80::59b:6699:bf51:7cf1.53011 > ff02::c.3702: UDP, length 656
17:56:45.955626 IP6 fe80::59b:6699:bf51:7cf1.63344 > ff02::1:3.5355: UDP, length 24
17:56:45.955817 IP 192.168.0.13.1900 > 239.255.255.250.1900: UDP, length 514
17:56:45.955989 IP6 fe80::59b:6699:bf51:7cf1.1900 > ff02::c.1900: UDP, length 522
17:56:45.975797 IP6 fe80::59b:6699:bf51:7cf1.61891 > ff02::c.3702: UDP, length 994
17:56:45.995741 IP6 fe80::59b:6699:bf51:7cf1.58087 > ff02::1:3.5355: UDP, length 28
17:56:45.999839 IP 78.24.242.43.65429 > 192.168.0.10.1194: UDP, length 100
17:56:46.025810 IP 192.168.0.13.53010 > 239.255.255.250.3702: UDP, length 656
17:56:46.055739 IP6 fe80::59b:6699:bf51:7cf1 > ff02::16: HBH ICMP6, multicast listener report v2, 1 group record(s), length 28
17:56:46.061129 IP 78.24.242.43.65429 > 192.168.0.10.1194: UDP, length 88
17:56:46.061198 IP 78.24.242.43.65429 > 192.168.0.10.1194: UDP, length 80
17:56:46.061265 IP 78.24.242.43.65429 > 192.168.0.10.1194: UDP, length 140
17:56:46.065757 IP 192.168.0.13.61890 > 239.255.255.250.3702: UDP, length 994
17:56:46.105623 IP6 fe80::59b:6699:bf51:7cf1.53006 > ff02::c.1900: UDP, length 119
17:56:46.105803 IP 192.168.0.13.53008 > 239.255.255.250.1900: UDP, length 125
17:56:46.135581 IP6 fe80::59b:6699:bf51:7cf1.53006 > ff02::c.1900: UDP, length 117
17:56:46.135694 IP 192.168.0.13.53008 > 239.255.255.250.1900: UDP, length 123
17:56:46.135807 IP6 fe80::59b:6699:bf51:7cf1.53011 > ff02::c.3702: UDP, length 656
17:56:46.155935 IP 192.168.0.13.137 > 192.168.0.255.137: NBT UDP PACKET(137): QUERY; REQUEST; BROADCAST
17:56:46.157314 IP 192.168.0.13.53008 > 239.255.255.250.1900: UDP, length 133
17:56:46.165529 IP 192.168.0.13.53008 > 239.255.255.250.1900: UDP, length 133
17:56:46.245647 IP 192.168.0.13.1900 > 239.255.255.250.1900: UDP, length 500
17:56:46.245730 IP6 fe80::59b:6699:bf51:7cf1.1900 > ff02::c.1900: UDP, length 508
17:56:46.376738 IP 192.168.0.13.1900 > 239.255.255.250.1900: UDP, length 486
17:56:46.376926 IP6 fe80::59b:6699:bf51:7cf1.1900 > ff02::c.1900: UDP, length 494
17:56:46.377089 IP 192.168.0.13.1900 > 239.255.255.250.1900: UDP, length 498
17:56:46.377247 IP6 fe80::59b:6699:bf51:7cf1.1900 > ff02::c.1900: UDP, length 506
17:56:46.556971 IP 78.24.242.43.65429 > 192.168.0.10.1194: UDP, length 100
17:56:46.636700 IP 192.168.0.13.1900 > 239.255.255.250.1900: UDP, length 434
17:56:46.636840 IP6 fe80::59b:6699:bf51:7cf1.1900 > ff02::c.1900: UDP, length 442
17:56:46.906635 IP 192.168.0.13.137 > 192.168.0.255.137: NBT UDP PACKET(137): QUERY; REQUEST; BROADCAST
17:56:46.917952 IP 78.24.242.43.65429 > 192.168.0.10.1194: UDP, length 162
17:56:47.057899 IP 78.24.242.43.65429 > 192.168.0.10.1194: UDP, length 96
17:56:47.058151 IP 192.168.0.13.1900 > 239.255.255.250.1900: UDP, length 434
17:56:47.058259 IP6 fe80::59b:6699:bf51:7cf1.1900 > ff02::c.1900: UDP, length 442
17:56:47.059839 IP6 fe80::59b:6699:bf51:7cf1 > ff02::16: HBH ICMP6, multicast listener report v2, 1 group record(s), length 28
17:56:47.059850 IP 192.168.0.13 > 224.0.0.2: igmp leave 224.0.0.252
17:56:47.066016 IP 78.24.242.43.65429 > 192.168.0.10.1194: UDP, length 100
17:56:47.074638 ARP, Request who-has 192.168.0.1 tell 192.168.0.13, length 46
17:56:47.076117 IP6 fe80::59b:6699:bf51:7cf1 > ff02::16: HBH ICMP6, multicast listener report v2, 1 group record(s), length 28
17:56:47.076574 IP 78.24.242.43.65429 > 192.168.0.10.1194: UDP, length 100
17:56:47.077659 IP6 fe80::59b:6699:bf51:7cf1.50364 > ff02::1:3.5355: UDP, length 28
17:56:47.077842 IP 192.168.0.13.1900 > 239.255.255.250.1900: UDP, length 443
17:56:47.077986 IP6 fe80::59b:6699:bf51:7cf1.1900 > ff02::c.1900: UDP, length 451
17:56:47.084988 IP 78.24.242.43.65429 > 192.168.0.10.1194: UDP, length 100
17:56:47.177716 IP6 fe80::59b:6699:bf51:7cf1.50364 > ff02::1:3.5355: UDP, length 28
17:56:47.177873 IP 78.24.242.43.65429 > 192.168.0.10.1194: UDP, length 100
17:56:47.559606 IP6 fe80::59b:6699:bf51:7cf1 > ff02::16: HBH ICMP6, multicast listener report v2, 1 group record(s), length 28
17:56:47.564597 IP 78.24.242.43.65429 > 192.168.0.10.1194: UDP, length 100
17:56:47.659607 IP 192.168.0.13.137 > 192.168.0.255.137: NBT UDP PACKET(137): QUERY; REQUEST; BROADCAST
17:56:47.909506 IP 192.168.0.13 > 224.0.0.2: igmp leave 224.0.0.251
17:56:47.909547 IP6 fe80::59b:6699:bf51:7cf1 > ff02::16: HBH ICMP6, multicast listener report v2, 1 group record(s), length 28
17:56:47.922439 IP6 fe80::59b:6699:bf51:7cf1 > ff02::16: HBH ICMP6, multicast listener report v2, 1 group record(s), length 28
17:56:48.019680 IP6 fe80::59b:6699:bf51:7cf1.53006 > ff02::c.1900: UDP, length 146
17:56:48.059605 IP6 fe80::59b:6699:bf51:7cf1 > ff02::16: HBH ICMP6, multicast listener report v2, 1 group record(s), length 28
17:56:48.269841 IP 192.168.0.13.1900 > 239.255.255.250.1900: UDP, length 498
17:56:48.269926 IP6 fe80::59b:6699:bf51:7cf1.1900 > ff02::c.1900: UDP, length 506
17:56:48.389795 IP 192.168.0.13.1900 > 239.255.255.250.1900: UDP, length 514
17:56:48.389865 IP6 fe80::59b:6699:bf51:7cf1.1900 > ff02::c.1900: UDP, length 522
17:56:48.409726 IP 192.168.0.13.1900 > 239.255.255.250.1900: UDP, length 486
17:56:48.409777 IP6 fe80::59b:6699:bf51:7cf1.1900 > ff02::c.1900: UDP, length 494
17:56:48.411463 IP 78.24.242.43.65429 > 192.168.0.10.1194: UDP, length 96
17:56:48.411515 IP6 fe80::59b:6699:bf51:7cf1.63070 > ff02::1:3.5355: UDP, length 24
17:56:48.509708 IP6 fe80::59b:6699:bf51:7cf1.63070 > ff02::1:3.5355: UDP, length 24
17:56:48.509900 IP 78.24.242.43.65429 > 192.168.0.10.1194: UDP, length 96
17:56:48.619745 IP 192.168.0.13.1900 > 239.255.255.250.1900: UDP, length 443
17:56:48.619865 IP6 fe80::59b:6699:bf51:7cf1.1900 > ff02::c.1900: UDP, length 451
17:56:48.709923 IP 192.168.0.13.137 > 192.168.0.255.137: NBT UDP PACKET(137): QUERY; REQUEST; BROADCAST
17:56:48.869699 IP 192.168.0.13.1900 > 239.255.255.250.1900: UDP, length 500
17:56:48.869744 IP6 fe80::59b:6699:bf51:7cf1.1900 > ff02::c.1900: UDP, length 508
17:56:48.919909 IP 78.24.242.43.65429 > 192.168.0.10.1194: UDP, length 162
17:56:48.959767 IP 192.168.0.13.1900 > 239.255.255.250.1900: UDP, length 514
17:56:48.959880 IP6 fe80::59b:6699:bf51:7cf1.1900 > ff02::c.1900: UDP, length 522
17:56:49.065350 IP6 fe80::59b:6699:bf51:7cf1 > ff02::16: HBH ICMP6, multicast listener report v2, 1 group record(s), length 28
17:56:49.065404 IP 192.168.0.13 > 224.0.0.2: igmp leave 224.0.0.252
17:56:49.065526 IP 78.24.242.43.65429 > 192.168.0.10.1194: UDP, length 100
17:56:49.070922 ARP, Request who-has 192.168.0.1 tell 192.168.0.13, length 46
17:56:49.075798 IP6 fe80::59b:6699:bf51:7cf1 > ff02::16: HBH ICMP6, multicast listener report v2, 1 group record(s), length 28
17:56:49.076277 IP 78.24.242.43.65429 > 192.168.0.10.1194: UDP, length 100
17:56:49.077071 IP6 fe80::59b:6699:bf51:7cf1.55953 > ff02::1:3.5355: UDP, length 28
17:56:49.084790 IP 78.24.242.43.65429 > 192.168.0.10.1194: UDP, length 100
17:56:49.159699 IP 192.168.0.13.53008 > 239.255.255.250.1900: UDP, length 133
17:56:49.169607 IP6 fe80::59b:6699:bf51:7cf1.53006 > ff02::c.1900: UDP, length 119
17:56:49.169720 IP6 fe80::59b:6699:bf51:7cf1.55953 > ff02::1:3.5355: UDP, length 28
17:56:49.169740 IP 192.168.0.13.53008 > 239.255.255.250.1900: UDP, length 125
17:56:49.170112 IP 78.24.242.43.65429 > 192.168.0.10.1194: UDP, length 100
17:56:49.199627 IP6 fe80::59b:6699:bf51:7cf1.53006 > ff02::c.1900: UDP, length 117
17:56:49.199680 IP 192.168.0.13.53008 > 239.255.255.250.1900: UDP, length 123
17:56:49.229596 IP 192.168.0.13.53008 > 239.255.255.250.1900: UDP, length 133
17:56:49.249696 IP 192.168.0.13.1900 > 239.255.255.250.1900: UDP, length 500
17:56:49.249861 IP6 fe80::59b:6699:bf51:7cf1.1900 > ff02::c.1900: UDP, length 508
17:56:49.379767 IP 192.168.0.13.1900 > 239.255.255.250.1900: UDP, length 498
17:56:49.379818 IP6 fe80::59b:6699:bf51:7cf1.1900 > ff02::c.1900: UDP, length 506
17:56:49.379977 IP 192.168.0.13.1900 > 239.255.255.250.1900: UDP, length 486
17:56:49.380108 IP6 fe80::59b:6699:bf51:7cf1.1900 > ff02::c.1900: UDP, length 494
17:56:49.459537 IP 192.168.0.13.137 > 192.168.0.255.137: NBT UDP PACKET(137): QUERY; REQUEST; BROADCAST
17:56:49.559568 IP6 fe80::59b:6699:bf51:7cf1 > ff02::16: HBH ICMP6, multicast listener report v2, 1 group record(s), length 28
17:56:49.564636 IP 78.24.242.43.65429 > 192.168.0.10.1194: UDP, length 100
17:56:49.639720 IP 192.168.0.13.1900 > 239.255.255.250.1900: UDP, length 434
17:56:49.639862 IP6 fe80::59b:6699:bf51:7cf1.1900 > ff02::c.1900: UDP, length 442
17:56:49.741089 ARP, Request who-has 192.168.0.1 tell 192.168.0.10, length 28
17:56:49.741450 ARP, Reply 192.168.0.1 is-at 44:32:c8:3d:c3:29, length 46
17:56:50.059670 IP 192.168.0.13.1900 > 239.255.255.250.1900: UDP, length 434
17:56:50.059825 IP6 fe80::59b:6699:bf51:7cf1.1900 > ff02::c.1900: UDP, length 442
17:56:50.059846 IP 78.24.242.43.65429 > 192.168.0.10.1194: UDP, length 80
17:56:50.079678 IP 192.168.0.13.1900 > 239.255.255.250.1900: UDP, length 443
17:56:50.079788 IP6 fe80::59b:6699:bf51:7cf1.1900 > ff02::c.1900: UDP, length 451
17:56:50.209595 IP 192.168.0.13.137 > 192.168.0.255.137: NBT UDP PACKET(137): QUERY; REQUEST; BROADCAST
17:56:50.962064 IP6 fe80::59b:6699:bf51:7cf1.60775 > ff02::1:3.5355: UDP, length 24
17:56:51.019210 IP 192.168.0.13.61334 > 239.255.255.250.3702: UDP, length 624
17:56:51.019575 IP6 fe80::59b:6699:bf51:7cf1.61335 > ff02::c.3702: UDP, length 624
17:56:51.020572 IP6 fe80::59b:6699:bf51:7cf1.53006 > ff02::c.1900: UDP, length 146
17:56:51.060699 IP6 fe80::59b:6699:bf51:7cf1.60775 > ff02::1:3.5355: UDP, length 24
17:56:51.110780 IP6 fe80::59b:6699:bf51:7cf1.61335 > ff02::c.3702: UDP, length 624
17:56:51.120747 IP 192.168.0.13.61334 > 239.255.255.250.3702: UDP, length 624
17:56:51.260796 IP 192.168.0.13.137 > 192.168.0.255.137: NBT UDP PACKET(137): QUERY; REQUEST; BROADCAST
17:56:51.270668 IP 192.168.0.13.1900 > 239.255.255.250.1900: UDP, length 498
17:56:51.270748 IP6 fe80::59b:6699:bf51:7cf1.1900 > ff02::c.1900: UDP, length 506
17:56:51.391795 IP 192.168.0.13.1900 > 239.255.255.250.1900: UDP, length 514
17:56:51.391948 IP6 fe80::59b:6699:bf51:7cf1.1900 > ff02::c.1900: UDP, length 522
17:56:51.411671 IP 192.168.0.13.1900 > 239.255.255.250.1900: UDP, length 486
17:56:51.411715 IP6 fe80::59b:6699:bf51:7cf1.1900 > ff02::c.1900: UDP, length 494
17:56:51.621740 IP 192.168.0.13.1900 > 239.255.255.250.1900: UDP, length 443
17:56:51.621783 IP6 fe80::59b:6699:bf51:7cf1.1900 > ff02::c.1900: UDP, length 451
17:56:51.871751 IP 192.168.0.13.1900 > 239.255.255.250.1900: UDP, length 500
17:56:51.871817 IP6 fe80::59b:6699:bf51:7cf1.1900 > ff02::c.1900: UDP, length 508
17:56:51.961754 IP 192.168.0.13.1900 > 239.255.255.250.1900: UDP, length 514
17:56:51.961891 IP6 fe80::59b:6699:bf51:7cf1.1900 > ff02::c.1900: UDP, length 522
17:56:51.974018 IP 192.168.0.13.138 > 192.168.0.255.138: NBT UDP PACKET(138)
17:56:52.011542 IP 192.168.0.13.137 > 192.168.0.255.137: NBT UDP PACKET(137): QUERY; REQUEST; BROADCAST
17:56:52.161645 IP 192.168.0.13.53008 > 239.255.255.250.1900: UDP, length 133
17:56:52.251755 IP 192.168.0.13.1900 > 239.255.255.250.1900: UDP, length 500
17:56:52.251809 IP6 fe80::59b:6699:bf51:7cf1.1900 > ff02::c.1900: UDP, length 508
17:56:52.381764 IP 192.168.0.13.1900 > 239.255.255.250.1900: UDP, length 498
17:56:52.381920 IP6 fe80::59b:6699:bf51:7cf1.1900 > ff02::c.1900: UDP, length 506
17:56:52.381996 IP 192.168.0.13.1900 > 239.255.255.250.1900: UDP, length 486
17:56:52.382125 IP6 fe80::59b:6699:bf51:7cf1.1900 > ff02::c.1900: UDP, length 494
17:56:52.641706 IP 192.168.0.13.1900 > 239.255.255.250.1900: UDP, length 434
17:56:52.641838 IP6 fe80::59b:6699:bf51:7cf1.1900 > ff02::c.1900: UDP, length 442
17:56:52.761540 IP 192.168.0.13.137 > 192.168.0.255.137: NBT UDP PACKET(137): QUERY; REQUEST; BROADCAST
17:56:53.061803 IP 192.168.0.13.1900 > 239.255.255.250.1900: UDP, length 434
17:56:53.061858 IP6 fe80::59b:6699:bf51:7cf1.1900 > ff02::c.1900: UDP, length 442
17:56:53.081728 IP 192.168.0.13.1900 > 239.255.255.250.1900: UDP, length 443
17:56:53.081802 IP6 fe80::59b:6699:bf51:7cf1.1900 > ff02::c.1900: UDP, length 451
17:56:53.514079 IP6 fe80::59b:6699:bf51:7cf1.55335 > ff02::1:3.5355: UDP, length 24
17:56:53.527732 ARP, Request who-has 192.168.0.1 tell 192.168.0.13, length 46
17:56:53.536927 IP 192.168.0.13.61890 > 239.255.255.250.3702: UDP, length 994
17:56:53.537276 IP6 fe80::59b:6699:bf51:7cf1.61891 > ff02::c.3702: UDP, length 994
17:56:53.540107 ARP, Request who-has 192.168.0.1 tell 192.168.0.13, length 46
17:56:53.611699 IP6 fe80::59b:6699:bf51:7cf1.55335 > ff02::1:3.5355: UDP, length 24
17:56:53.761709 IP6 fe80::59b:6699:bf51:7cf1.61891 > ff02::c.3702: UDP, length 994
17:56:53.771667 IP 192.168.0.13.61890 > 239.255.255.250.3702: UDP, length 994
17:56:53.811889 IP 192.168.0.13.137 > 192.168.0.255.137: NBT UDP PACKET(137): QUERY; REQUEST; BROADCAST
17:56:54.013758 IP 192.168.0.13.58732 > 239.255.255.250.3702: UDP, length 656
17:56:54.014001 IP6 fe80::59b:6699:bf51:7cf1.58733 > ff02::c.3702: UDP, length 656
17:56:54.141753 IP 192.168.0.13.58732 > 239.255.255.250.3702: UDP, length 656
17:56:54.181844 IP6 fe80::59b:6699:bf51:7cf1.58733 > ff02::c.3702: UDP, length 656
17:56:54.271712 IP 192.168.0.13.1900 > 239.255.255.250.1900: UDP, length 498
17:56:54.271859 IP6 fe80::59b:6699:bf51:7cf1.1900 > ff02::c.1900: UDP, length 506
17:56:54.391728 IP 192.168.0.13.1900 > 239.255.255.250.1900: UDP, length 514
17:56:54.391862 IP6 fe80::59b:6699:bf51:7cf1.1900 > ff02::c.1900: UDP, length 522
17:56:54.411697 IP 192.168.0.13.1900 > 239.255.255.250.1900: UDP, length 486
17:56:54.411756 IP6 fe80::59b:6699:bf51:7cf1.1900 > ff02::c.1900: UDP, length 494
17:56:54.561570 IP 192.168.0.13.137 > 192.168.0.255.137: NBT UDP PACKET(137): QUERY; REQUEST; BROADCAST
17:56:54.621758 IP 192.168.0.13.1900 > 239.255.255.250.1900: UDP, length 443
17:56:54.621902 IP6 fe80::59b:6699:bf51:7cf1.1900 > ff02::c.1900: UDP, length 451
17:56:54.871729 IP 192.168.0.13.1900 > 239.255.255.250.1900: UDP, length 500
17:56:54.871822 IP6 fe80::59b:6699:bf51:7cf1.1900 > ff02::c.1900: UDP, length 508
17:56:55.021808 IP6 fe80::59b:6699:bf51:7cf1.53006 > ff02::c.1900: UDP, length 146
17:56:55.162131 IP 192.168.0.10.1194 > 78.24.242.43.65429: UDP, length 37
17:56:55.178922 IP 192.168.0.13.53008 > 239.255.255.250.1900: UDP, length 133
17:56:55.311563 IP 192.168.0.13.137 > 192.168.0.255.137: NBT UDP PACKET(137): QUERY; REQUEST; BROADCAST
17:56:56.062750 IP6 fe80::59b:6699:bf51:7cf1.58321 > ff02::1:3.5355: UDP, length 24
17:56:56.161741 IP6 fe80::59b:6699:bf51:7cf1.58321 > ff02::1:3.5355: UDP, length 24
17:56:56.361922 IP 192.168.0.13.137 > 192.168.0.255.137: NBT UDP PACKET(137): QUERY; REQUEST; BROADCAST
17:56:57.112531 IP 192.168.0.13.137 > 192.168.0.255.137: NBT UDP PACKET(137): QUERY; REQUEST; BROADCAST
17:56:57.862592 IP 192.168.0.13.137 > 192.168.0.255.137: NBT UDP PACKET(137): QUERY; REQUEST; BROADCAST
17:56:58.022665 IP6 fe80::59b:6699:bf51:7cf1.53006 > ff02::c.1900: UDP, length 146
17:56:58.172563 IP 192.168.0.13.53008 > 239.255.255.250.1900: UDP, length 133
17:56:58.613842 IP6 fe80::59b:6699:bf51:7cf1.58271 > ff02::1:3.5355: UDP, length 24
17:56:58.712630 IP6 fe80::59b:6699:bf51:7cf1.58271 > ff02::1:3.5355: UDP, length 24
17:56:58.912854 IP 192.168.0.13.137 > 192.168.0.255.137: NBT UDP PACKET(137): QUERY; REQUEST; BROADCAST
17:56:59.662573 IP 192.168.0.13.137 > 192.168.0.255.137: NBT UDP PACKET(137): QUERY; REQUEST; BROADCAST
17:57:00.412584 IP 192.168.0.13.137 > 192.168.0.255.137: NBT UDP PACKET(137): QUERY; REQUEST; BROADCAST
17:57:01.022651 IP6 fe80::59b:6699:bf51:7cf1.53006 > ff02::c.1900: UDP, length 146
17:57:01.163609 IP6 fe80::59b:6699:bf51:7cf1.57448 > ff02::1:3.5355: UDP, length 24
17:57:01.172605 IP 192.168.0.13.53008 > 239.255.255.250.1900: UDP, length 133
17:57:01.262688 IP6 fe80::59b:6699:bf51:7cf1.57448 > ff02::1:3.5355: UDP, length 24
17:57:01.463891 IP 192.168.0.13.137 > 192.168.0.255.137: NBT UDP PACKET(137): QUERY; REQUEST; BROADCAST
17:57:02.213563 IP 192.168.0.13.137 > 192.168.0.255.137: NBT UDP PACKET(137): QUERY; REQUEST; BROADCAST
17:57:02.963560 IP 192.168.0.13.137 > 192.168.0.255.137: NBT UDP PACKET(137): QUERY; REQUEST; BROADCAST
17:57:03.714848 IP6 fe80::59b:6699:bf51:7cf1.56903 > ff02::1:3.5355: UDP, length 24
17:57:03.813681 IP6 fe80::59b:6699:bf51:7cf1.56903 > ff02::1:3.5355: UDP, length 24
17:57:04.013880 IP 192.168.0.13.137 > 192.168.0.255.137: NBT UDP PACKET(137): QUERY; REQUEST; BROADCAST
17:57:04.763565 IP 192.168.0.13.137 > 192.168.0.255.137: NBT UDP PACKET(137): QUERY; REQUEST; BROADCAST
17:57:05.023820 IP6 fe80::59b:6699:bf51:7cf1.53006 > ff02::c.1900: UDP, length 146
17:57:05.379470 IP 192.168.0.10.1194 > 78.24.242.43.65429: UDP, length 37
17:57:05.513548 IP 192.168.0.13.137 > 192.168.0.255.137: NBT UDP PACKET(137): QUERY; REQUEST; BROADCAST
17:57:06.264645 IP6 fe80::59b:6699:bf51:7cf1.50320 > ff02::1:3.5355: UDP, length 24
17:57:06.363639 IP6 fe80::59b:6699:bf51:7cf1.50320 > ff02::1:3.5355: UDP, length 24
17:57:06.564849 IP 192.168.0.13.137 > 192.168.0.255.137: NBT UDP PACKET(137): QUERY; REQUEST; BROADCAST
17:57:07.314562 IP 192.168.0.13.137 > 192.168.0.255.137: NBT UDP PACKET(137): QUERY; REQUEST; BROADCAST
17:57:07.976859 IP 192.168.0.13.138 > 192.168.0.255.138: NBT UDP PACKET(138)
17:57:08.024620 IP6 fe80::59b:6699:bf51:7cf1.53006 > ff02::c.1900: UDP, length 146
17:57:08.064532 IP 192.168.0.13.137 > 192.168.0.255.137: NBT UDP PACKET(137): QUERY; REQUEST; BROADCAST
17:57:08.815711 IP6 fe80::59b:6699:bf51:7cf1.58735 > ff02::1:3.5355: UDP, length 24
17:57:08.914660 IP6 fe80::59b:6699:bf51:7cf1.58735 > ff02::1:3.5355: UDP, length 24
17:57:09.114858 IP 192.168.0.13.137 > 192.168.0.255.137: NBT UDP PACKET(137): QUERY; REQUEST; BROADCAST
17:57:09.864515 IP 192.168.0.13.137 > 192.168.0.255.137: NBT UDP PACKET(137): QUERY; REQUEST; BROADCAST
17:57:10.614503 IP 192.168.0.13.137 > 192.168.0.255.137: NBT UDP PACKET(137): QUERY; REQUEST; BROADCAST
17:57:11.024631 IP6 fe80::59b:6699:bf51:7cf1.53006 > ff02::c.1900: UDP, length 146
17:57:11.365694 IP6 fe80::59b:6699:bf51:7cf1.50269 > ff02::1:3.5355: UDP, length 24
17:57:11.465669 IP6 fe80::59b:6699:bf51:7cf1.50269 > ff02::1:3.5355: UDP, length 24
17:57:11.665889 IP 192.168.0.13.137 > 192.168.0.255.137: NBT UDP PACKET(137): QUERY; REQUEST; BROADCAST
17:57:12.415556 IP 192.168.0.13.137 > 192.168.0.255.137: NBT UDP PACKET(137): QUERY; REQUEST; BROADCAST
17:57:13.165578 IP 192.168.0.13.137 > 192.168.0.255.137: NBT UDP PACKET(137): QUERY; REQUEST; BROADCAST
17:57:13.916990 IP6 fe80::59b:6699:bf51:7cf1.57217 > ff02::1:3.5355: UDP, length 24
17:57:14.015663 IP6 fe80::59b:6699:bf51:7cf1.57217 > ff02::1:3.5355: UDP, length 24
17:57:14.215908 IP 192.168.0.13.137 > 192.168.0.255.137: NBT UDP PACKET(137): QUERY; REQUEST; BROADCAST
17:57:14.965551 IP 192.168.0.13.137 > 192.168.0.255.137: NBT UDP PACKET(137): QUERY; REQUEST; BROADCAST
17:57:15.025869 IP6 fe80::59b:6699:bf51:7cf1.53006 > ff02::c.1900: UDP, length 146
17:57:15.512600 IP 192.168.0.10.1194 > 78.24.242.43.65429: UDP, length 37
17:57:15.715570 IP 192.168.0.13.137 > 192.168.0.255.137: NBT UDP PACKET(137): QUERY; REQUEST; BROADCAST
17:57:16.467653 IP6 fe80::59b:6699:bf51:7cf1.55478 > ff02::1:3.5355: UDP, length 24
17:57:16.566694 IP6 fe80::59b:6699:bf51:7cf1.55478 > ff02::1:3.5355: UDP, length 24
17:57:16.766907 IP 192.168.0.13.137 > 192.168.0.255.137: NBT UDP PACKET(137): QUERY; REQUEST; BROADCAST
17:57:17.516546 IP 192.168.0.13.137 > 192.168.0.255.137: NBT UDP PACKET(137): QUERY; REQUEST; BROADCAST
17:57:18.026654 IP6 fe80::59b:6699:bf51:7cf1.53006 > ff02::c.1900: UDP, length 146
17:57:18.266565 IP 192.168.0.13.137 > 192.168.0.255.137: NBT UDP PACKET(137): QUERY; REQUEST; BROADCAST
17:57:19.017692 IP6 fe80::59b:6699:bf51:7cf1.63582 > ff02::1:3.5355: UDP, length 24
17:57:19.116653 IP6 fe80::59b:6699:bf51:7cf1.63582 > ff02::1:3.5355: UDP, length 24
17:57:19.316902 IP 192.168.0.13.137 > 192.168.0.255.137: NBT UDP PACKET(137): QUERY; REQUEST; BROADCAST
17:57:20.066496 IP 192.168.0.13.137 > 192.168.0.255.137: NBT UDP PACKET(137): QUERY; REQUEST; BROADCAST
17:57:20.816539 IP 192.168.0.13.137 > 192.168.0.255.137: NBT UDP PACKET(137): QUERY; REQUEST; BROADCAST
17:57:21.026651 IP6 fe80::59b:6699:bf51:7cf1.53006 > ff02::c.1900: UDP, length 146
17:57:21.567657 IP6 fe80::59b:6699:bf51:7cf1.52620 > ff02::1:3.5355: UDP, length 24
17:57:21.666663 IP6 fe80::59b:6699:bf51:7cf1.52620 > ff02::1:3.5355: UDP, length 24
17:57:21.866841 IP 192.168.0.13.137 > 192.168.0.255.137: NBT UDP PACKET(137): QUERY; REQUEST; BROADCAST
17:57:22.616537 IP 192.168.0.13.137 > 192.168.0.255.137: NBT UDP PACKET(137): QUERY; REQUEST; BROADCAST
17:57:23.366567 IP 192.168.0.13.137 > 192.168.0.255.137: NBT UDP PACKET(137): QUERY; REQUEST; BROADCAST
17:57:24.117750 IP6 fe80::59b:6699:bf51:7cf1.61641 > ff02::1:3.5355: UDP, length 24
17:57:24.216635 IP6 fe80::59b:6699:bf51:7cf1.61641 > ff02::1:3.5355: UDP, length 24
17:57:24.416865 IP 192.168.0.13.137 > 192.168.0.255.137: NBT UDP PACKET(137): QUERY; REQUEST; BROADCAST
17:57:25.026944 IP6 fe80::59b:6699:bf51:7cf1.53006 > ff02::c.1900: UDP, length 146
17:57:25.166518 IP 192.168.0.13.137 > 192.168.0.255.137: NBT UDP PACKET(137): QUERY; REQUEST; BROADCAST
17:57:25.623793 IP 192.168.0.10.1194 > 78.24.242.43.65429: UDP, length 37
17:57:25.916547 IP 192.168.0.13.137 > 192.168.0.255.137: NBT UDP PACKET(137): QUERY; REQUEST; BROADCAST
17:57:26.668627 IP6 fe80::59b:6699:bf51:7cf1.58963 > ff02::1:3.5355: UDP, length 24
17:57:26.767640 IP6 fe80::59b:6699:bf51:7cf1.58963 > ff02::1:3.5355: UDP, length 24
17:57:26.967883 IP 192.168.0.13.137 > 192.168.0.255.137: NBT UDP PACKET(137): QUERY; REQUEST; BROADCAST
17:57:27.717513 IP 192.168.0.13.137 > 192.168.0.255.137: NBT UDP PACKET(137): QUERY; REQUEST; BROADCAST
17:57:27.787891 IP 192.168.0.13.137 > 192.168.0.255.137: NBT UDP PACKET(137): QUERY; REQUEST; BROADCAST
17:57:28.027587 IP6 fe80::59b:6699:bf51:7cf1.53006 > ff02::c.1900: UDP, length 146
17:57:28.467509 IP 192.168.0.13.137 > 192.168.0.255.137: NBT UDP PACKET(137): QUERY; REQUEST; BROADCAST
17:57:28.537550 IP 192.168.0.13.137 > 192.168.0.255.137: NBT UDP PACKET(137): QUERY; REQUEST; BROADCAST
17:57:29.218742 IP6 fe80::59b:6699:bf51:7cf1.51796 > ff02::1:3.5355: UDP, length 24
17:57:29.287522 IP 192.168.0.13.137 > 192.168.0.255.137: NBT UDP PACKET(137): QUERY; REQUEST; BROADCAST
17:57:29.317626 IP6 fe80::59b:6699:bf51:7cf1.51796 > ff02::1:3.5355: UDP, length 24
17:57:29.517890 IP 192.168.0.13.137 > 192.168.0.255.137: NBT UDP PACKET(137): QUERY; REQUEST; BROADCAST
17:57:30.267521 IP 192.168.0.13.137 > 192.168.0.255.137: NBT UDP PACKET(137): QUERY; REQUEST; BROADCAST
17:57:31.017514 IP 192.168.0.13.137 > 192.168.0.255.137: NBT UDP PACKET(137): QUERY; REQUEST; BROADCAST
17:57:31.027603 IP6 fe80::59b:6699:bf51:7cf1.53006 > ff02::c.1900: UDP, length 146
17:57:31.769582 IP6 fe80::59b:6699:bf51:7cf1.63676 > ff02::1:3.5355: UDP, length 24
17:57:31.868648 IP6 fe80::59b:6699:bf51:7cf1.63676 > ff02::1:3.5355: UDP, length 24
17:57:32.068813 IP 192.168.0.13.137 > 192.168.0.255.137: NBT UDP PACKET(137): QUERY; REQUEST; BROADCAST
17:57:32.818504 IP 192.168.0.13.137 > 192.168.0.255.137: NBT UDP PACKET(137): QUERY; REQUEST; BROADCAST
17:57:33.568542 IP 192.168.0.13.137 > 192.168.0.255.137: NBT UDP PACKET(137): QUERY; REQUEST; BROADCAST
17:57:35.028797 IP6 fe80::59b:6699:bf51:7cf1.53006 > ff02::c.1900: UDP, length 146
17:57:35.727035 IP 192.168.0.10.1194 > 78.24.242.43.65429: UDP, length 37
17:57:38.029629 IP6 fe80::59b:6699:bf51:7cf1.53006 > ff02::c.1900: UDP, length 146
17:57:38.289694 ARP, Request who-has 192.168.0.10 tell 192.168.0.13, length 46
17:57:38.289756 ARP, Reply 192.168.0.10 is-at 00:04:e2:2a:a6:dc, length 28
17:57:38.290053 IP 192.168.0.13.50160 > 192.168.0.10.22: Flags [P.], seq 1:65, ack 384, win 16089, length 64
17:57:38.290666 IP 192.168.0.10.22 > 192.168.0.13.50160: Flags [P.], seq 384:448, ack 65, win 1211, length 64
17:57:38.499471 IP 192.168.0.13.50160 > 192.168.0.10.22: Flags [.], ack 448, win 16073, length 0
17:57:40.941094 ARP, Request who-has 192.168.0.1 tell 192.168.0.10, length 28
17:57:40.941743 ARP, Reply 192.168.0.1 is-at 44:32:c8:3d:c3:29, length 46
17:57:41.029604 IP6 fe80::59b:6699:bf51:7cf1.53006 > ff02::c.1900: UDP, length 146
329 packets captured
330 packets received by filter
0 packets dropped by kernel

I tried to connect the client and ping 8.8.8.8 and connect to https://ent.univ-lorraine.fr/f/u21l1s4/normal/render.uP

TinCanTech

Try enabling IP Forwarding.