[Resolved] Can't use internet via VPN connection.

doni49

FIRST: I DID use the troubleshooting guide here and didn't have any luck:
https://forums.openvpn.net/topic10923.html

I had OpenVPN working last spring -- I even took my laptop with me to a St Louis and used the hotel's WiFi to connect to my VPN when I wanted to check my bank info.

Then I moved and my ISP is now providing my router. The new router will not allow me to spec my own LAN IP address (my previous router had an internal address of 10.2.1.1). So I changed my RasPi to connect to the new router using the new ip address.

This caused OpenVPN to fail. So I updated my OpenVPN settings to use the new IP address. I'm at my aunt's house right now testing the connection and it fails. I'm able to connect to the server but internet traffic won't go through.

When I first opened the OpenVPN connection, I saw the following message:

Sun Nov 24 07:40:10 2013 OpenVPN 2.3.2 x86_64-w64-mingw32 [SSL (OpenSSL)] [LZO] [PKCS11] [eurephia] [IPv6] built on Jun 3 2013
Sun Nov 24 07:40:10 2013 MANAGEMENT: TCP Socket listening on [AF_INET]127.0.0.1:25340
Sun Nov 24 07:40:10 2013 Need hold release from management interface, waiting...
Sun Nov 24 07:40:10 2013 MANAGEMENT: Client connected from [AF_INET]127.0.0.1:25340
Sun Nov 24 07:40:10 2013 MANAGEMENT: CMD 'state on'
Sun Nov 24 07:40:10 2013 MANAGEMENT: CMD 'log all on'
Sun Nov 24 07:40:10 2013 MANAGEMENT: CMD 'hold off'
Sun Nov 24 07:40:10 2013 MANAGEMENT: CMD 'hold release'
Sun Nov 24 07:40:11 2013 Control Channel Authentication: using 'C:\Program Files\OpenVPN\config\RasPiHomeNAS-donireland.com\ta.key' as a OpenVPN static key file
Sun Nov 24 07:40:11 2013 Outgoing Control Channel Authentication: Using 160 bit message hash 'SHA1' for HMAC authentication
Sun Nov 24 07:40:11 2013 Incoming Control Channel Authentication: Using 160 bit message hash 'SHA1' for HMAC authentication
Sun Nov 24 07:40:11 2013 Socket Buffers: R=[8192->8192] S=[8192->8192]
Sun Nov 24 07:40:11 2013 MANAGEMENT: >STATE:1385300411,RESOLVE,,,
Sun Nov 24 07:40:11 2013 UDPv4 link local: [undef]
Sun Nov 24 07:40:11 2013 UDPv4 link remote: [AF_INET]173.25.128.52:1194
Sun Nov 24 07:40:11 2013 MANAGEMENT: >STATE:1385300411,WAIT,,,
Sun Nov 24 07:40:11 2013 MANAGEMENT: >STATE:1385300411,AUTH,,,
Sun Nov 24 07:40:11 2013 TLS: Initial packet from [AF_INET]173.25.128.52:1194, sid=7487ac13 20264e29
Sun Nov 24 07:40:12 2013 VERIFY OK: depth=1, C=US, ST=MO, L=Jefferson City, O=biapy, OU=changeme, CN=OpenVPNServer.domain.com, name=changeme, emailAddress=root@RasPiHomeNas
Sun Nov 24 07:40:12 2013 VERIFY OK: nsCertType=SERVER
Sun Nov 24 07:40:12 2013 VERIFY OK: depth=0, C=US, ST=MO, L=Jefferson City, O=biapy, OU=changeme, CN=OpenVPNServer.domain.com, name=changeme, emailAddress=root@RasPiHomeNas
Sun Nov 24 07:40:13 2013 Data Channel Encrypt: Cipher 'BF-CBC' initialized with 128 bit key
Sun Nov 24 07:40:13 2013 Data Channel Encrypt: Using 160 bit message hash 'SHA1' for HMAC authentication
Sun Nov 24 07:40:13 2013 Data Channel Decrypt: Cipher 'BF-CBC' initialized with 128 bit key
Sun Nov 24 07:40:13 2013 Data Channel Decrypt: Using 160 bit message hash 'SHA1' for HMAC authentication
Sun Nov 24 07:40:13 2013 Control Channel: TLSv1, cipher TLSv1/SSLv3 DHE-RSA-AES256-SHA, 1024 bit RSA
Sun Nov 24 07:40:13 2013 [OpenVPNServer.domain.com] Peer Connection Initiated with [AF_INET]173.25.128.52:1194
Sun Nov 24 07:40:14 2013 MANAGEMENT: >STATE:1385300414,GET_CONFIG,,,
Sun Nov 24 07:40:16 2013 SENT CONTROL [OpenVPNServer.domain.com]: 'PUSH_REQUEST' (status=1)
Sun Nov 24 07:40:16 2013 PUSH: Received control message: 'PUSH_REPLY,route 192.168.0.1 255.255.255.0,redirect-gateway def1 bypass-dhcp,dhcp-option DNS 208.67.220.220,dhcp-option DNS 208.67.222.222,route 10.8.0.1,topology net30,ping 10,ping-restart 120,ifconfig 10.8.0.6 10.8.0.5'
Sun Nov 24 07:40:16 2013 OPTIONS IMPORT: timers and/or timeouts modified
Sun Nov 24 07:40:16 2013 OPTIONS IMPORT: --ifconfig/up options modified
Sun Nov 24 07:40:16 2013 OPTIONS IMPORT: route options modified
Sun Nov 24 07:40:16 2013 OPTIONS IMPORT: --ip-win32 and/or --dhcp-option options modified
Sun Nov 24 07:40:16 2013 do_ifconfig, tt->ipv6=0, tt->did_ifconfig_ipv6_setup=0
Sun Nov 24 07:40:16 2013 MANAGEMENT: >STATE:1385300416,ASSIGN_IP,,10.8.0.6,
Sun Nov 24 07:40:16 2013 open_tun, tt->ipv6=0
Sun Nov 24 07:40:16 2013 TAP-WIN32 device [Local Area Connection 2] opened: \\.\Global\{AC8D916C-D035-4141-9441-027CA70E5C18}.tap
Sun Nov 24 07:40:16 2013 TAP-Windows Driver Version 9.9
Sun Nov 24 07:40:16 2013 Notified TAP-Windows driver to set a DHCP IP/netmask of 10.8.0.6/255.255.255.252 on interface {AC8D916C-D035-4141-9441-027CA70E5C18} [DHCP-serv: 10.8.0.5, lease-time: 31536000]
Sun Nov 24 07:40:16 2013 Successful ARP Flush on interface [19] {AC8D916C-D035-4141-9441-027CA70E5C18}
Sun Nov 24 07:40:21 2013 TEST ROUTES: 3/3 succeeded len=2 ret=1 a=0 u/d=up
Sun Nov 24 07:40:21 2013 C:\windows\system32\route.exe ADD 173.25.128.52 MASK 255.255.255.255 192.168.0.1
Sun Nov 24 07:40:21 2013 ROUTE: CreateIpForwardEntry succeeded with dwForwardMetric1=30 and dwForwardType=4
Sun Nov 24 07:40:21 2013 Route addition via IPAPI succeeded [adaptive]
Sun Nov 24 07:40:21 2013 C:\windows\system32\route.exe ADD 192.168.0.1 MASK 255.255.255.255 192.168.0.1 IF 12
Sun Nov 24 07:40:21 2013 ROUTE: CreateIpForwardEntry succeeded with dwForwardMetric1=30 and dwForwardType=4
Sun Nov 24 07:40:21 2013 Route addition via IPAPI succeeded [adaptive]
Sun Nov 24 07:40:21 2013 C:\windows\system32\route.exe ADD 0.0.0.0 MASK 128.0.0.0 10.8.0.5
Sun Nov 24 07:40:21 2013 ROUTE: CreateIpForwardEntry succeeded with dwForwardMetric1=30 and dwForwardType=4
Sun Nov 24 07:40:21 2013 Route addition via IPAPI succeeded [adaptive]
Sun Nov 24 07:40:21 2013 C:\windows\system32\route.exe ADD 128.0.0.0 MASK 128.0.0.0 10.8.0.5
Sun Nov 24 07:40:21 2013 ROUTE: CreateIpForwardEntry succeeded with dwForwardMetric1=30 and dwForwardType=4
Sun Nov 24 07:40:21 2013 Route addition via IPAPI succeeded [adaptive]
Sun Nov 24 07:40:21 2013 MANAGEMENT: >STATE:1385300421,ADD_ROUTES,,,
Sun Nov 24 07:40:21 2013 C:\windows\system32\route.exe ADD 192.168.0.1 MASK 255.255.255.0 10.8.0.5
Sun Nov 24 07:40:21 2013 Warning: address 192.168.0.1 is not a network address in relation to netmask 255.255.255.0
Sun Nov 24 07:40:21 2013 ROUTE: route addition failed using CreateIpForwardEntry: The parameter is incorrect. [status=87 if_index=19]
Sun Nov 24 07:40:21 2013 Route addition via IPAPI failed [adaptive]
Sun Nov 24 07:40:21 2013 Route addition fallback to route.exe
Sun Nov 24 07:40:21 2013 env_block: add PATH=C:\Windows\System32;C:\WINDOWS;C:\WINDOWS\System32\Wbem
Sun Nov 24 07:40:21 2013 C:\windows\system32\route.exe ADD 10.8.0.1 MASK 255.255.255.255 10.8.0.5
Sun Nov 24 07:40:21 2013 ROUTE: CreateIpForwardEntry succeeded with dwForwardMetric1=30 and dwForwardType=4
Sun Nov 24 07:40:21 2013 Route addition via IPAPI succeeded [adaptive]
Sun Nov 24 07:40:21 2013 Initialization Sequence Completed
Sun Nov 24 07:40:21 2013 MANAGEMENT: >STATE:1385300421,CONNECTED,SUCCESS,10.8.0.6,173.25.128.52

It LOOKS like it has a problem with the subnet masking. But that doesn't make any sense either. Following is from the RasPi's IFCONFIG:

pi@RasPiHomeNas ~ $ sudo su
root@RasPiHomeNas:/var/home/pi# ifconfig
eth0 Link encap:Ethernet HWaddr b8:27:eb:0c:91:85
inet addr:192.168.0.14 Bcast:192.168.0.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:184761 errors:0 dropped:89 overruns:0 frame:0
TX packets:51912 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:18921487 (18.0 MiB) TX bytes:8820113 (8.4 MiB)

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:2189 errors:0 dropped:0 overruns:0 frame:0
TX packets:2189 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:314169 (306.8 KiB) TX bytes:314169 (306.8 KiB)

tun0 Link encap:UNSPEC HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00
inet addr:10.8.0.1 P-t-P:10.8.0.2 Mask:255.255.255.255
UP POINTOPOINT RUNNING NOARP MULTICAST MTU:1500 Metric:1
RX packets:8370 errors:0 dropped:0 overruns:0 frame:0
TX packets:340 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:100
RX bytes:490842 (479.3 KiB) TX bytes:43744 (42.7 KiB)

root@RasPiHomeNas:/var/home/pi#

This is the snippet from my OpenVPN configuration that pushes the route:

push "route 192.168.0.0 255.255.255.0"
;push "route 192.168.20.1 255.255.255.0"  [color=#FF0000]<-- I've tried both lines and get the same results.[/color]

And lastly, here's the snippet from my OpenVPN configuration that creates the tun connection.

# 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

https://forums.openvpn.net/topic10923.html

doni49

debbie10t wrote
doni49 wrotethe snippet from my OpenVPN configuration
"Snippet" .. Crystal ball ..

Huh?

doni49

debbie10t wrote
doni49 wrotethe snippet from my OpenVPN configuration
"Snippet" .. Crystal ball ..

The only thing I can imagine that that comment is supposed to mean is you'd like to see the entire file. I didn't post the entire contents because I didn't think you'd want the entire thing.

But in case that's what you meant, it's below.

#################################################
# Sample OpenVPN 2.0 config file for            #
# multi-client server.                          #
#                                               #
# This file is for the server side              #
# of a many-clients <-> one-server              #
# OpenVPN configuration.                        #
#                                               #
# OpenVPN also supports                         #
# single-machine <-> single-machine             #
# configurations (See the Examples page         #
# on the web site for more info).               #
#                                               #
# This config should work on Windows            #
# or Linux/BSD systems.  Remember on            #
# Windows to quote pathnames and use            #
# double backslashes, e.g.:                     #
# "C:\\Program Files\\OpenVPN\\config\\foo.key" #
#                                               #
# Comments are preceded with '#' or ';'         #
#################################################

# Which local IP address should OpenVPN
# listen on? (optional)
;local a.b.c.d

# Which TCP/UDP port should OpenVPN listen on?
# If you want to run multiple OpenVPN instances
# on the same machine, use a different port
# number for each one.  You will need to
# open up this port on your firewall.
port 1194

# TCP or UDP server?
;proto tcp
proto udp

# "dev tun" will create a routed IP tunnel,
# "dev tap" will create an ethernet tunnel.
# Use "dev tap0" if you are ethernet bridging
# and have precreated a tap0 virtual interface
# and bridged it with your ethernet interface.
# If you want to control access policies
# over the VPN, you must create firewall
# rules for the the TUN/TAP interface.
# On non-Windows systems, you can give
# an explicit unit number, such as tun0.
# On Windows, use "dev-node" for this.
# On most systems, the VPN will not function
# unless you partially or fully disable
# the firewall for the TUN/TAP interface.
;dev tap
dev tun

# Windows needs the TAP-Win32 adapter name
# from the Network Connections panel if you
# have more than one.  On XP SP2 or higher,
# you may need to selectively disable the
# Windows firewall for the TAP adapter.
# Non-Windows systems usually don't need this.
;dev-node MyTap

# SSL/TLS root certificate (ca), certificate
# (cert), and private key (key).  Each client
# and the server must have their own cert and
# key file.  The server and all clients will
# use the same ca file.
#
# See the "easy-rsa" directory for a series
# of scripts for generating RSA certificates
# and private keys.  Remember to use
# a unique Common Name for the server
# and each of the client certificates.
#
# Any X509 key management system can be used.
# OpenVPN can also use a PKCS #12 formatted key file
# (see "pkcs12" directive in man page).
ca /etc/openvpn/config/RasPiHomeNAS-donireland.com/ca.crt
cert /etc/openvpn/config/RasPiHomeNAS-donireland.com/RasPiHomeNAS.donireland.com.crt
key /etc/openvpn/config/RasPiHomeNAS-donireland.com/RasPiHomeNAS.donireland.com.key

# Diffie hellman parameters.
# Generate your own with:
#   openssl dhparam -out dh1024.pem 1024
# Substitute 2048 for 1024 if you are using
# 2048 bit keys. 
dh /etc/openvpn/config/RasPiHomeNAS-donireland.com/dh1024.pem

# 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.0.0 255.255.255.0"
;push "route 192.168.20.0 255.255.255.0"
;push "route 10.2.1.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"
;push "redirect-gateway local def1 bypass-dhcp"
;push "redirect-gateway local def1"

# 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"
;push "dhcp-option DNS 10.8.8.8"
;push "dhcp-option DNS 10.8.8.4"
push "dhcp-option DNS 208.67.220.220"
push "dhcp-option DNS 208.67.222.222"


# 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 --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/config/RasPiHomeNAS-donireland.com/ta.key 0

# Select a cryptographic cipher.
# This config item must be copied to
# the client config file as well.
;cipher BF-CBC        # Blowfish (default)
;cipher AES-128-CBC   # AES
;cipher DES-EDE3-CBC  # Triple-DES

# Enable compression on the VPN link.
# 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 nogroup

# 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
# Revoked certificate list
crl-verify /etc/openvpn/config/RasPiHomeNAS-donireland.com/crl.pem

doni49

debbie10t wrote If your home network is 192.168.0.0/24 and your ISP Router will not allow you to change that you should probably make a strong complaint to your ISP.

If your client network (IE. Your aunt's house) also has a network number 192.168.0.0/24 you have a network conflict. The problem is OpenVPN does not know which side is which as both server and client network is 192.168.0.0 ..... If the above is true.

Thanks that was it. I thought I had checked that but I guess not. My uncle never changed from the default IP address.

I'll have to look at the alternatives you offered. My ultimate goal is to use the VPN while traveling and using public WiFi. I'm not concerned about using my aunt's WiFi.