I'm having an issue. Basically I have two devices, both with the MPTCP linux kernel installed and need to get a TCP VPN tunnel going through them. What's happening is it connects just fine and I can browse a few web pages but then it'll disconnect (process expedited by any "pressure testing" eg. speed test).
Here's my server config:
port 443
proto tcp-server
#proto udp
dev tun
#dev tap
#tcp-queue-limit 256
#tun-mtu 9000
ca ca.crt
cert server.crt
key server.key # This file should be kept secret
dh dh2048.pem
server 10.8.0.0 255.255.255.0
push "redirect-gateway def1 bypass-dhcp"
#push "redirect-gateway"
#push "dhcp-option DNS 8.8.8.8"
#push "dhcp-option DNS 8.8.4.4"
#tcp-queue-limit 256
cipher camellia-128-cbc
auth sha1
ifconfig-pool-persist ipp.txt
keepalive 10 20
comp-lzo
persist-key
persist-tun
status openvpn-status.log
verb 4
Here's my client config
##############################################
# 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
#tcp-queue-limit 256
#tun-mtu 9000
# 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
;dev-node OpenVPN
# Are we connecting to a TCP or
# UDP server? Use the same setting as
# on the server.
proto tcp-client
#proto udp
# The hostname/IP and port of the server.
# You can have multiple remote entries
# to load balance between the servers.
;remote my-server-2 1194
remote x.x.x.x 443
# 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 client1.crt
key client1.key # This file should be kept secret
# Verify server certificate by checking
# that the certicate has the nsCertType
# field set to "server". 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 nsCertType
# field set to "server". The build-key-server
# script in the easy-rsa folder will do this.
;ns-cert-type 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.
cipher camellia-128-cbc
auth sha1
# 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 4
# Silence repeating messages
;mute 20
# WINDOWS 7: Cannot ping server without these statements
# WINDOWS XP: not needed
#route-method exe
#route-delay 2
Here's a gist of what the server is spitting out
Fri Dec 1 17:54:32 2017 us=934796 client1/172.56.13.178:31252 PUSH: Received control message: 'PUSH_REQUEST'
Fri Dec 1 17:54:32 2017 us=934921 client1/172.56.13.178:31252 send_push_reply(): safe_cap=940
Fri Dec 1 17:54:32 2017 us=934996 client1/172.56.13.178:31252 SENT CONTROL [client1]: 'PUSH_REPLY,redirect-gateway def1 bypass-dhcp,route 10.8.0.1,topology net30,ping 10,ping-restart 20,ifconfig 10.8.0.6 10.8.0.5' (status=1)
Fri Dec 1 17:54:33 2017 us=286700 client1/172.56.13.178:31252 MULTI: bad source address from client [fe80::44d0:f566:adfd:36f8], packet dropped
Fri Dec 1 17:54:37 2017 us=126889 client1/172.56.13.178:31252 MULTI: bad source address from client [fe80::44d0:f566:adfd:36f8], packet dropped
Fri Dec 1 17:54:45 2017 us=165820 client1/172.56.13.178:31252 MULTI: bad source address from client [fe80::44d0:f566:adfd:36f8], packet dropped
Fri Dec 1 17:54:45 2017 us=165958 client1/172.56.13.178:31252 MULTI: bad source address from client [192.168.8.111], packet dropped
Fri Dec 1 17:54:59 2017 us=461689 client1/172.56.13.178:31252 MULTI: bad source address from client [fe80::44d0:f566:adfd:36f8], packet dropped
Fri Dec 1 17:55:37 2017 us=247809 MULTI: multi_create_instance called
Fri Dec 1 17:55:37 2017 us=247851 Re-using SSL/TLS context
Fri Dec 1 17:55:37 2017 us=247869 LZO compression initialized
Here's what the client is spitting out
Fri Dec 1 12:54:33 2017 us=147036 Initialization Sequence Completed
Fri Dec 1 12:55:32 2017 us=145661 [server] Inactivity timeout (--ping-restart), restarting
Fri Dec 1 12:55:32 2017 us=146096 TCP/UDP: Closing socket
Fri Dec 1 12:55:32 2017 us=146243 SIGUSR1[soft,ping-restart] received, process restarting
Fri Dec 1 12:55:32 2017 us=146285 Restart pause, 5 second(s)
Any help would be much appreciated, especially if you have any experience with MPTCP!!
