The local subnet is 192.168.119.0/24 and my Internet Asus Router has UDP ports 1198 and 1199 forwarded to the RPi3.
All seems to work well so I am ready to move the RPi3 to the target network.
So today I have moved it to the target network which operates on 10.0.0.0/24 with a Fortigate router, also set to forward UDP ports 1198-1199 to the RPI3. Due to the network layout I have had to configure the RPi3 with a fixed address of 10.0.0.235, which is outside the DHCP range of addresses.
With this in place I was able to perform an OpenVPN connect from my phone operating on the external mobile network. The phone is an Android Samsung Galaxy S7 using the OpenVPN-Connect app fully updated.
But even though there was no connection exception or error reported I am unable to connect anywhere with the phone....
Accesses to the Internet fail to pass through and accesses to internal servers also fail to complete.
I am at a loss as to what may cause this behaviour so I am asking for some troubleshooting help.
Here is my client config in the OVPN file:
remote vpn.xxxxx.com 1199
-----BEGIN RSA PRIVATE KEY-----
-----END RSA PRIVATE KEY-----
# 2048 bit OpenVPN static key
-----BEGIN OpenVPN Static key V1-----
-----END OpenVPN Static key V1-----
And here is the config for the server running on port 1199:
# listen on? (optional)
# 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.
# TCP or UDP server?
# "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.
# 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.
# 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).
key /etc/openvpn/easy-rsa/keys/AGIVPN.key # This file should be kept secret
# Diffie hellman parameters.
# Generate your own with:
# openssl dhparam -out dh2048.pem 2048
# 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)
# 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.
# 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.
# 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"
#Bosse home local network
;push "route 192.168.119.0 255.255.255.0"
#AGI local network
push "route 10.0.0.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:
;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:
;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.
# 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:
# The addresses below refer to the public
# DNS servers provided by opendns.com.
;push "dhcp-option DNS 22.214.171.124"
;push "dhcp-option DNS 126.96.36.199"
# 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.
# 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
# IF YOU HAVE NOT GENERATED INDIVIDUAL
# CERTIFICATE/KEY PAIRS FOR EACH CLIENT,
# EACH HAVING ITS OWN UNIQUE "COMMON NAME",
# UNCOMMENT THIS LINE OUT.
# 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 --secret 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 /etc/openvpn/easy-rsa/keys/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 2.4 client/server will automatically
# negotiate AES-256-GCM in TLS mode.
# See also the ncp-cipher option in the manpage
# Enable compression on the VPN link and push the
# option to the client (2.4+ only, for earlier
# versions see below)
;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.
# The maximum number of concurrently connected
# clients we want to allow.
# It's a good idea to reduce the OpenVPN
# daemon's privileges after initialization.
# You can uncomment this out on
# non-Windows systems.
# The persist options will try to avoid
# accessing certain resources on restart
# that may no longer be accessible because
# of the privilege downgrade.
# Output a short status file showing
# current connections, truncated
# and rewritten every minute.
# 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).
# 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
# Silence repeating messages. At most 20
# sequential messages of the same message
# category will be output to the log.
# Notify the client that when the server restarts so it
# can automatically reconnect.
I have looked at the logfiles and the openvpn.log file contains this after a connect is done:
Code: Select all
Fri Nov 3 16:31:34 2017 us=215893 OpenVPN 2.4.0 arm-unknown-linux-gnueabihf [SSL (OpenSSL)] [LZO] [LZ4] [EPOLL] [PKCS11] [MH/PKTINFO] [AEAD] built on Jul 18 2017 Fri Nov 3 16:31:34 2017 us=215986 library versions: OpenSSL 1.0.2l 25 May 2017, LZO 2.08 Fri Nov 3 16:31:34 2017 us=222921 Diffie-Hellman initialized with 2048 bit key Fri Nov 3 16:31:34 2017 us=227064 Outgoing Control Channel Authentication: Using 160 bit message hash 'SHA1' for HMAC authentication Fri Nov 3 16:31:34 2017 us=227170 Incoming Control Channel Authentication: Using 160 bit message hash 'SHA1' for HMAC authentication Fri Nov 3 16:31:34 2017 us=227310 TLS-Auth MTU parms [ L:1622 D:1184 EF:66 EB:0 ET:0 EL:3 ] Fri Nov 3 16:31:34 2017 us=231091 TUN/TAP device tun0 opened Fri Nov 3 16:31:34 2017 us=231314 TUN/TAP TX queue length set to 100 Fri Nov 3 16:31:34 2017 us=231469 do_ifconfig, tt->did_ifconfig_ipv6_setup=0 Fri Nov 3 16:31:34 2017 us=231620 /sbin/ip link set dev tun0 up mtu 1500 Fri Nov 3 16:31:34 2017 us=242506 /sbin/ip addr add dev tun0 10.8.0.1/24 broadcast 10.8.0.255 Fri Nov 3 16:31:34 2017 us=256783 Data Channel MTU parms [ L:1622 D:1450 EF:122 EB:406 ET:0 EL:3 ] Fri Nov 3 16:31:34 2017 us=259744 Could not determine IPv4/IPv6 protocol. Using AF_INET Fri Nov 3 16:31:34 2017 us=259944 Socket Buffers: R=[163840->163840] S=[163840->163840] Fri Nov 3 16:31:34 2017 us=260054 UDPv4 link local (bound): [AF_INET][undef]:1199 Fri Nov 3 16:31:34 2017 us=260125 UDPv4 link remote: [AF_UNSPEC] Fri Nov 3 16:31:34 2017 us=260206 GID set to nogroup Fri Nov 3 16:31:34 2017 us=260288 UID set to openvpn Fri Nov 3 16:31:34 2017 us=260410 MULTI: multi_init called, r=256 v=256 Fri Nov 3 16:31:34 2017 us=260629 IFCONFIG POOL: base=10.8.0.2 size=252, ipv6=0 Fri Nov 3 16:31:34 2017 us=260757 ifconfig_pool_read(), in='BosseB_AGI,10.8.0.2', TODO: IPv6 Fri Nov 3 16:31:34 2017 us=261204 succeeded -> ifconfig_pool_set() Fri Nov 3 16:31:34 2017 us=261335 IFCONFIG POOL LIST Fri Nov 3 16:31:34 2017 us=261434 BosseB_AGI,10.8.0.2 Fri Nov 3 16:31:34 2017 us=261883 Initialization Sequence Completed Fri Nov 3 16:31:38 2017 us=673946 MULTI: multi_create_instance called Fri Nov 3 16:31:38 2017 us=674155 188.8.131.52:37846 Re-using SSL/TLS context Fri Nov 3 16:31:38 2017 us=674263 184.108.40.206:37846 LZO compression initializing Fri Nov 3 16:31:38 2017 us=674791 220.127.116.11:37846 Control Channel MTU parms [ L:1622 D:1184 EF:66 EB:0 ET:0 EL:3 ] Fri Nov 3 16:31:38 2017 us=674875 18.104.22.168:37846 Data Channel MTU parms [ L:1622 D:1450 EF:122 EB:406 ET:0 EL:3 ] Fri Nov 3 16:31:38 2017 us=675080 22.214.171.124:37846 Local Options String (VER=V4): 'V4,dev-type tun,link-mtu 1558,tun-mtu 1500,proto UDPv4,comp-lzo,keydir 0,cipher AES-256-CBC,auth SHA1,keysize 256,tls-auth,key-method 2,tls-server' Fri Nov 3 16:31:38 2017 us=675148 126.96.36.199:37846 Expected Remote Options String (VER=V4): 'V4,dev-type tun,link-mtu 1558,tun-mtu 1500,proto UDPv4,comp-lzo,keydir 1,cipher AES-256-CBC,auth SHA1,keysize 256,tls-auth,key-method 2,tls-client' Fri Nov 3 16:31:38 2017 us=675323 188.8.131.52:37846 TLS: Initial packet from [AF_INET]184.108.40.206:37846, sid=dc614257 afa08ab9 Fri Nov 3 16:31:39 2017 us=3313 220.127.116.11:37846 VERIFY OK: depth=1, C=US, ST=TX, L=Austin, O=AdvancedGeosciences, OU=IT, CN=rpi3-agivpn, name=rpi3-agivpn, emailAddressfirstname.lastname@example.org Fri Nov 3 16:31:39 2017 us=4608 18.104.22.168:37846 VERIFY OK: depth=0, C=US, ST=TX, L=Austin, O=AdvancedGeosciences, OU=IT, CN=BosseB_AGI, name=BosseB_AGI, emailAddressemail@example.com Fri Nov 3 16:31:39 2017 us=80270 22.214.171.124:37846 peer info: IV_GUI_VER=net.openvpn.connect.android_1.1.17-76 Fri Nov 3 16:31:39 2017 us=80394 126.96.36.199:37846 peer info: IV_VER=3.0.12 Fri Nov 3 16:31:39 2017 us=80431 188.8.131.52:37846 peer info: IV_PLAT=android Fri Nov 3 16:31:39 2017 us=80465 184.108.40.206:37846 peer info: IV_NCP=2 Fri Nov 3 16:31:39 2017 us=80499 220.127.116.11:37846 peer info: IV_TCPNL=1 Fri Nov 3 16:31:39 2017 us=80533 18.104.22.168:37846 peer info: IV_PROTO=2 Fri Nov 3 16:31:39 2017 us=80566 22.214.171.124:37846 peer info: IV_LZO=1 Fri Nov 3 16:31:39 2017 us=134285 126.96.36.199:37846 Control Channel: TLSv1.2, cipher TLSv1/SSLv3 ECDHE-RSA-AES256-GCM-SHA384, 2048 bit RSA Fri Nov 3 16:31:39 2017 us=134370 188.8.131.52:37846 [BosseB_AGI] Peer Connection Initiated with [AF_INET]184.108.40.206:37846 Fri Nov 3 16:31:39 2017 us=134450 BosseB_AGI/220.127.116.11:37846 MULTI_sva: pool returned IPv4=10.8.0.2, IPv6=(Not enabled) Fri Nov 3 16:31:39 2017 us=134601 BosseB_AGI/18.104.22.168:37846 MULTI: Learn: 10.8.0.2 -> BosseB_AGI/22.214.171.124:37846 Fri Nov 3 16:31:39 2017 us=134678 BosseB_AGI/126.96.36.199:37846 MULTI: primary virtual IP for BosseB_AGI/188.8.131.52:37846: 10.8.0.2 Fri Nov 3 16:31:39 2017 us=134774 BosseB_AGI/184.108.40.206:37846 PUSH: Received control message: 'PUSH_REQUEST' Fri Nov 3 16:31:39 2017 us=134887 BosseB_AGI/220.127.116.11:37846 SENT CONTROL [BosseB_AGI]: 'PUSH_REPLY,route 10.0.0.0 255.255.255.0,redirect-gateway def1 bypass-dhcp,route-gateway 10.8.0.1,topology subnet,ping 10,ping-restart 120,ifconfig 10.8.0.2 255.255.255.0,peer-id 0,cipher AES-256-GCM' (status=1) Fri Nov 3 16:31:39 2017 us=134947 BosseB_AGI/18.104.22.168:37846 Data Channel MTU parms [ L:1550 D:1450 EF:50 EB:406 ET:0 EL:3 ] Fri Nov 3 16:31:39 2017 us=135304 BosseB_AGI/22.214.171.124:37846 Data Channel Encrypt: Cipher 'AES-256-GCM' initialized with 256 bit key Fri Nov 3 16:31:39 2017 us=135347 BosseB_AGI/126.96.36.199:37846 Data Channel Decrypt: Cipher 'AES-256-GCM' initialized with 256 bit key Fri Nov 3 16:50:14 2017 us=920821 BosseB_AGI/188.8.131.52:37846 SIGTERM[soft,remote-exit] received, client-instance exiting
And there is exactly nothing written into the openvpn.log file.
At 16:50:14 I disconnected the tunnel from the client (the phone).
The Linux firewall on the RPi3 is set up as shown by this sudo iptables-save command as adviced on this webpage :
Code: Select all
# Generated by iptables-save v1.6.0 on Fri Nov 3 23:12:12 2017 *filter :INPUT ACCEPT [0:0] :FORWARD ACCEPT [0:0] :OUTPUT ACCEPT [0:0] -A INPUT -i lo -j ACCEPT -A INPUT -s 127.0.0.0/8 ! -i lo -j REJECT --reject-with icmp-port-unreachable -A INPUT -p icmp -m state --state NEW -m icmp --icmp-type 8 -j ACCEPT -A INPUT -p icmp -m state --state RELATED,ESTABLISHED -j ACCEPT -A INPUT -i eth0 -p tcp -m state --state NEW,ESTABLISHED -m tcp --dport 22 -j ACCEPT -A INPUT -i eth0 -p udp -m state --state NEW,ESTABLISHED -m udp --dport 1199 -j ACCEPT -A INPUT -i eth0 -p udp -m state --state ESTABLISHED -m udp --sport 53 -j ACCEPT -A INPUT -i eth0 -p tcp -m state --state ESTABLISHED -m tcp --sport 53 -j ACCEPT -A INPUT -i eth0 -p tcp -m state --state ESTABLISHED -m tcp --sport 80 -j ACCEPT -A INPUT -i eth0 -p tcp -m state --state ESTABLISHED -m tcp --sport 443 -j ACCEPT -A INPUT -i eth0 -p udp -m state --state ESTABLISHED -m udp --sport 123 -j ACCEPT -A INPUT -i tun0 -j ACCEPT -A INPUT -m limit --limit 3/min -j LOG --log-prefix "iptables_INPUT_denied: " -A INPUT -j REJECT --reject-with icmp-port-unreachable -A FORWARD -i tun0 -j ACCEPT -A FORWARD -m limit --limit 3/min -j LOG --log-prefix "iptables_FORWARD_denied: " -A FORWARD -j REJECT --reject-with icmp-port-unreachable -A OUTPUT -o lo -j ACCEPT -A OUTPUT -p icmp -j ACCEPT -A OUTPUT -o eth0 -p tcp -m state --state ESTABLISHED -m tcp --sport 22 -j ACCEPT -A OUTPUT -o eth0 -p udp -m state --state ESTABLISHED -m udp --sport 1199 -j ACCEPT -A OUTPUT -o eth0 -p udp -m state --state NEW,ESTABLISHED -m udp --dport 53 -j ACCEPT -A OUTPUT -o eth0 -p tcp -m state --state NEW,ESTABLISHED -m tcp --dport 53 -j ACCEPT -A OUTPUT -o eth0 -p tcp -m state --state NEW,ESTABLISHED -m tcp --dport 80 -j ACCEPT -A OUTPUT -o eth0 -p tcp -m state --state NEW,ESTABLISHED -m tcp --dport 443 -j ACCEPT -A OUTPUT -o eth0 -p udp -m state --state NEW,ESTABLISHED -m udp --dport 123 -j ACCEPT -A OUTPUT -o tun0 -j ACCEPT -A OUTPUT -m limit --limit 3/min -j LOG --log-prefix "iptables_OUTPUT_denied: " -A OUTPUT -j REJECT --reject-with icmp-port-unreachable COMMIT # Completed on Fri Nov 3 23:12:12 2017 # Generated by iptables-save v1.6.0 on Fri Nov 3 23:12:12 2017 *nat :PREROUTING ACCEPT [40874:6577179] :INPUT ACCEPT [24:1500] :OUTPUT ACCEPT [35:2791] :POSTROUTING ACCEPT [27:2015] -A POSTROUTING -s 10.8.0.0/24 -o eth0 -j MASQUERADE COMMIT # Completed on Fri Nov 3 23:12:12 2017