Windows 10 Client / Server / pfSense

bimmerdriver

I'm trying to get a windows 10 openvpn client / server working. I'm trying to get openvpn configured so the client pc can connect to the internet through the server pc, in order to test "Problems with Browser Default Protocol and Fallback" which I posted here: https://forums.openvpn.net/viewtopic.php?f=4&t=22420. It's doing something, just not working.

The configuration is the following:

Windows 2012R2 hyper-v server
virtual switch
pfsense 2.4 guest
windows 10 client pc guest 192.168.1.107
windows 10 server pc guest 192.168.1.108
openvpn-install-2.3.12-I601-x86_64
EasyRSA-3.0.0-rc2

The router is connected to a bridged port on the modem and is providing native ipv4 / ipv6. Both pcs also have native ipv4 / ipv6.

I used EasyRSA-3.0.0-rc2 to create the pki and dh parameters. When I initially started the openvpn server, it complained that the dh parameters file was missing. It was looking for dh2048.pem. Easyrsa generated dh.pem. I renamed the file to dh2048.pem. Is that okay?

I created a port forwarding rule on the router. I used the WAN ipv4 address for the server. There was no sign that the client was talking to the server, even with firewall on the server disabled. Not sure why that was happenign so I then tried to connect the client to the server over the lan, not going through pfSense. There was a connection, but internet access from the client was broken. There was no ipv4 connectivity, but ipv6 was working, just not through the vpn. I observed that both using a browser to ipv6-test.com and test-ipv6.com, as well as ping. When I pinged yahoo.com, it was using ipv6. When I used tracert, the client appeared to be going directly to pfSense, not through the server.

The client and server config files and logs from the "lan" connection are below. I started from the example howto files. I would appreciate suggestions to get it working. This is my first attempt to set up openvpn so please excuse any noob mistakes.

Here is the client config file and log:
##############################################
# 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.1.108 1194
;remote a.c.b.d 1194

# Choose a random host from the remote
# list for load-balancing. Otherwise
# try hosts in the order specified.
;remote-random

# Keep trying indefinitely to resolve the
# host name of the OpenVPN server. Very useful
# on machines which are not permanently connected
# to the internet such as laptops.
resolv-retry infinite

# Most clients don't need to bind to
# a specific local port number.
nobind

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

# Try to preserve some state across restarts.
persist-key
persist-tun

# If you are connecting through an
# HTTP proxy to reach the actual OpenVPN
# server, put the proxy server/IP and
# port number here. See the man page
# if your proxy server requires
# authentication.
;http-proxy-retry # retry on connection failures
;http-proxy [proxy server] [proxy port #]

# Wireless networks often produce a lot
# of duplicate packets. Set this flag
# to silence duplicate packet warnings.
;mute-replay-warnings

# SSL/TLS parms.
# See the server config file for more
# description. It's best to use
# a separate .crt/.key file pair
# for each client. A single ca
# file can be used for all clients.
ca ca.crt
cert client.crt
key client.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.
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

# Tunnel IPv6 traffic as well as IPv4
tun-ipv6

Tue Sep 20 16:28:51 2016 OpenVPN 2.3.12 x86_64-w64-mingw32 [SSL (OpenSSL)] [LZO] [PKCS11] [IPv6] built on Aug 23 2016
Tue Sep 20 16:28:51 2016 Windows version 6.2 (Windows 8 or greater) 64bit
Tue Sep 20 16:28:51 2016 library versions: OpenSSL 1.0.1t  3 May 2016, LZO 2.09
Enter Management Password:
Tue Sep 20 16:28:51 2016 MANAGEMENT: TCP Socket listening on [AF_INET]127.0.0.1:25340
Tue Sep 20 16:28:51 2016 Need hold release from management interface, waiting...
Tue Sep 20 16:28:51 2016 MANAGEMENT: Client connected from [AF_INET]127.0.0.1:25340
Tue Sep 20 16:28:51 2016 MANAGEMENT: CMD 'state on'
Tue Sep 20 16:28:51 2016 MANAGEMENT: CMD 'log all on'
Tue Sep 20 16:28:51 2016 MANAGEMENT: CMD 'hold off'
Tue Sep 20 16:28:51 2016 MANAGEMENT: CMD 'hold release'
Tue Sep 20 16:29:01 2016 MANAGEMENT: CMD 'password [...]'
Tue Sep 20 16:29:01 2016 WARNING: this configuration may cache passwords in memory -- use the auth-nocache option to prevent this
Tue Sep 20 16:29:01 2016 Socket Buffers: R=[65536->65536] S=[65536->65536]
Tue Sep 20 16:29:01 2016 UDPv4 link local: [undef]
Tue Sep 20 16:29:01 2016 UDPv4 link remote: [AF_INET]192.168.1.108:1194
Tue Sep 20 16:29:01 2016 MANAGEMENT: >STATE:1474414141,WAIT,,,
Tue Sep 20 16:29:01 2016 MANAGEMENT: >STATE:1474414141,AUTH,,,
Tue Sep 20 16:29:01 2016 TLS: Initial packet from [AF_INET]192.168.1.108:1194, sid=dfa69c96 c9de04e5
Tue Sep 20 16:29:01 2016 VERIFY OK: depth=1, CN=Easy-RSA CA
Tue Sep 20 16:29:01 2016 Validating certificate key usage
Tue Sep 20 16:29:01 2016 ++ Certificate has key usage  00a0, expects 00a0
Tue Sep 20 16:29:01 2016 VERIFY KU OK
Tue Sep 20 16:29:01 2016 Validating certificate extended key usage
Tue Sep 20 16:29:01 2016 ++ Certificate has EKU (str) TLS Web Server Authentication, expects TLS Web Server Authentication
Tue Sep 20 16:29:01 2016 VERIFY EKU OK
Tue Sep 20 16:29:01 2016 VERIFY OK: depth=0, CN=SERVER
Tue Sep 20 16:29:01 2016 Data Channel Encrypt: Cipher 'AES-256-CBC' initialized with 256 bit key
Tue Sep 20 16:29:01 2016 Data Channel Encrypt: Using 160 bit message hash 'SHA1' for HMAC authentication
Tue Sep 20 16:29:01 2016 Data Channel Decrypt: Cipher 'AES-256-CBC' initialized with 256 bit key
Tue Sep 20 16:29:01 2016 Data Channel Decrypt: Using 160 bit message hash 'SHA1' for HMAC authentication
Tue Sep 20 16:29:01 2016 Control Channel: TLSv1.2, cipher TLSv1/SSLv3 DHE-RSA-AES256-GCM-SHA384, 2048 bit RSA
Tue Sep 20 16:29:01 2016 [SERVER] Peer Connection Initiated with [AF_INET]192.168.1.108:1194
Tue Sep 20 16:29:02 2016 MANAGEMENT: >STATE:1474414142,GET_CONFIG,,,
Tue Sep 20 16:29:03 2016 SENT CONTROL [SERVER]: 'PUSH_REQUEST' (status=1)
Tue Sep 20 16:29:03 2016 PUSH: Received control message: 'PUSH_REPLY,redirect-gateway,route 10.8.0.1,topology net30,ping 10,ping-restart 120,ifconfig 10.8.0.6 10.8.0.5'
Tue Sep 20 16:29:03 2016 OPTIONS IMPORT: timers and/or timeouts modified
Tue Sep 20 16:29:03 2016 OPTIONS IMPORT: --ifconfig/up options modified
Tue Sep 20 16:29:03 2016 OPTIONS IMPORT: route options modified
Tue Sep 20 16:29:03 2016 ROUTE_GATEWAY 192.168.1.1/255.255.255.0 I=2 HWADDR=00:15:5d:5c:e2:11
Tue Sep 20 16:29:03 2016 do_ifconfig, tt->ipv6=1, tt->did_ifconfig_ipv6_setup=0
Tue Sep 20 16:29:03 2016 MANAGEMENT: >STATE:1474414143,ASSIGN_IP,,10.8.0.6,
Tue Sep 20 16:29:03 2016 open_tun, tt->ipv6=1
Tue Sep 20 16:29:03 2016 TAP-WIN32 device [Ethernet 2] opened: \\.\Global\{2C29AFC7-5413-4B4B-872D-291C0BF8AB61}.tap
Tue Sep 20 16:29:03 2016 TAP-Windows Driver Version 9.21 
Tue Sep 20 16:29:03 2016 Notified TAP-Windows driver to set a DHCP IP/netmask of 10.8.0.6/255.255.255.252 on interface {2C29AFC7-5413-4B4B-872D-291C0BF8AB61} [DHCP-serv: 10.8.0.5, lease-time: 31536000]
Tue Sep 20 16:29:03 2016 Successful ARP Flush on interface [7] {2C29AFC7-5413-4B4B-872D-291C0BF8AB61}
Tue Sep 20 16:29:08 2016 TEST ROUTES: 2/2 succeeded len=1 ret=1 a=0 u/d=up
Tue Sep 20 16:29:08 2016 C:\WINDOWS\system32\route.exe ADD 192.168.1.108 MASK 255.255.255.255 192.168.1.1 IF 2
Tue Sep 20 16:29:08 2016 ROUTE: CreateIpForwardEntry succeeded with dwForwardMetric1=15 and dwForwardType=4
Tue Sep 20 16:29:08 2016 Route addition via IPAPI succeeded [adaptive]
Tue Sep 20 16:29:08 2016 C:\WINDOWS\system32\route.exe DELETE 0.0.0.0 MASK 0.0.0.0 192.168.1.1
Tue Sep 20 16:29:08 2016 Route deletion via IPAPI succeeded [adaptive]
Tue Sep 20 16:29:08 2016 C:\WINDOWS\system32\route.exe ADD 0.0.0.0 MASK 0.0.0.0 10.8.0.5
Tue Sep 20 16:29:08 2016 ROUTE: CreateIpForwardEntry succeeded with dwForwardMetric1=35 and dwForwardType=4
Tue Sep 20 16:29:08 2016 Route addition via IPAPI succeeded [adaptive]
Tue Sep 20 16:29:08 2016 MANAGEMENT: >STATE:1474414148,ADD_ROUTES,,,
Tue Sep 20 16:29:08 2016 C:\WINDOWS\system32\route.exe ADD 10.8.0.1 MASK 255.255.255.255 10.8.0.5
Tue Sep 20 16:29:08 2016 ROUTE: CreateIpForwardEntry succeeded with dwForwardMetric1=35 and dwForwardType=4
Tue Sep 20 16:29:08 2016 Route addition via IPAPI succeeded [adaptive]
Tue Sep 20 16:29:08 2016 Initialization Sequence Completed
Tue Sep 20 16:29:08 2016 MANAGEMENT: >STATE:1474414148,CONNECTED,SUCCESS,10.8.0.6,192.168.1.108

Here is the server config file and log:
#################################################
# 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 192.168.1.108

# 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 ca.crt
cert server.crt
key server.key # This file should be kept secret

# Diffie hellman parameters.
# Generate your own with:
# openssl dhparam -out dh2048.pem 2048
dh dh2048.pem

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

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

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

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

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

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

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

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

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

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

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

# Certain Windows-specific network settings
# can be pushed to clients, such as DNS
# or WINS server addresses. CAVEAT:
# http://openvpn.net/faq.html#dhcpcaveats
# The addresses below refer to the public
# DNS servers provided by opendns.com.
;push "dhcp-option DNS 208.67.222.222"
;push "dhcp-option DNS 208.67.220.220"

# Uncomment this directive to allow different
# clients to be able to "see" each other.
# By default, clients will only see the server.
# To force clients to only see the server, you
# will also need to appropriately firewall the
# server's TUN/TAP interface.
;client-to-client

# Uncomment this directive if multiple clients
# might connect with the same certificate/key
# files or common names. This is recommended
# only for testing purposes. For production use,
# each client should have its own certificate/key
# pair.
#
# IF YOU HAVE NOT GENERATED INDIVIDUAL
# CERTIFICATE/KEY PAIRS FOR EACH CLIENT,
# EACH HAVING ITS OWN UNIQUE "COMMON NAME",
# UNCOMMENT THIS LINE OUT.
;duplicate-cn

# The keepalive directive causes ping-like
# messages to be sent back and forth over
# the link so that each side knows when
# the other side has gone down.
# Ping every 10 seconds, assume that remote
# peer is down if no ping received during
# a 120 second time period.
keepalive 10 120

# For extra security beyond that provided
# by SSL/TLS, create an "HMAC firewall"
# to help block DoS attacks and UDP port flooding.
#
# Generate with:
# openvpn --genkey --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 ta.key 0 # This file is secret

# 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
cipher AES-256-CBC

# 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 nobody

# The persist options will try to avoid
# accessing certain resources on restart
# that may no longer be accessible because
# of the privilege downgrade.
persist-key
persist-tun

# Output a short status file showing
# current connections, truncated
# and rewritten every minute.
status openvpn-status.log

# By default, log messages will go to the syslog (or
# on Windows, if running as a service, they will go to
# the "\Program Files\OpenVPN\log" directory).
# Use log or log-append to override this default.
# "log" will truncate the log file on OpenVPN startup,
# while "log-append" will append to it. Use one
# or the other (but not both).
;log openvpn.log
;log-append openvpn.log

# Set the appropriate level of log
# file verbosity.
#
# 0 is silent, except for fatal errors
# 4 is reasonable for general usage
# 5 and 6 can help to debug connection problems
# 9 is extremely verbose
verb 3

# Silence repeating messages. At most 20
# sequential messages of the same message
# category will be output to the log.
;mute 20

# Tunnel IPv6 traffic as well as IPv4
tun-ipv6

Tue Sep 20 16:28:37 2016 OpenVPN 2.3.12 x86_64-w64-mingw32 [SSL (OpenSSL)] [LZO] [PKCS11] [IPv6] built on Aug 23 2016
Tue Sep 20 16:28:37 2016 Windows version 6.2 (Windows 8 or greater) 64bit
Tue Sep 20 16:28:37 2016 library versions: OpenSSL 1.0.1t  3 May 2016, LZO 2.09
Enter Management Password:
Tue Sep 20 16:28:37 2016 MANAGEMENT: TCP Socket listening on [AF_INET]127.0.0.1:25340
Tue Sep 20 16:28:37 2016 Need hold release from management interface, waiting...
Tue Sep 20 16:28:38 2016 MANAGEMENT: Client connected from [AF_INET]127.0.0.1:25340
Tue Sep 20 16:28:38 2016 MANAGEMENT: CMD 'state on'
Tue Sep 20 16:28:38 2016 MANAGEMENT: CMD 'log all on'
Tue Sep 20 16:28:38 2016 MANAGEMENT: CMD 'hold off'
Tue Sep 20 16:28:38 2016 MANAGEMENT: CMD 'hold release'
Tue Sep 20 16:28:38 2016 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.
Tue Sep 20 16:28:38 2016 Diffie-Hellman initialized with 2048 bit key
Tue Sep 20 16:28:38 2016 Socket Buffers: R=[65536->65536] S=[65536->65536]
Tue Sep 20 16:28:38 2016 ROUTE_GATEWAY 192.168.1.1/255.255.255.0 I=5 HWADDR=00:15:5d:5c:e2:12
Tue Sep 20 16:28:38 2016 do_ifconfig, tt->ipv6=1, tt->did_ifconfig_ipv6_setup=0
Tue Sep 20 16:28:38 2016 MANAGEMENT: >STATE:1474414118,ASSIGN_IP,,10.8.0.1,
Tue Sep 20 16:28:38 2016 open_tun, tt->ipv6=1
Tue Sep 20 16:28:38 2016 TAP-WIN32 device [Ethernet 2] opened: \\.\Global\{99CC5C53-98D4-4786-8CB3-7272DB92E990}.tap
Tue Sep 20 16:28:38 2016 TAP-Windows Driver Version 9.21 
Tue Sep 20 16:28:38 2016 Notified TAP-Windows driver to set a DHCP IP/netmask of 10.8.0.1/255.255.255.252 on interface {99CC5C53-98D4-4786-8CB3-7272DB92E990} [DHCP-serv: 10.8.0.2, lease-time: 31536000]
Tue Sep 20 16:28:38 2016 Sleeping for 10 seconds...
Tue Sep 20 16:28:48 2016 Successful ARP Flush on interface [2] {99CC5C53-98D4-4786-8CB3-7272DB92E990}
Tue Sep 20 16:28:48 2016 MANAGEMENT: >STATE:1474414128,ADD_ROUTES,,,
Tue Sep 20 16:28:48 2016 C:\WINDOWS\system32\route.exe ADD 10.8.0.0 MASK 255.255.255.0 10.8.0.2
Tue Sep 20 16:28:48 2016 ROUTE: CreateIpForwardEntry succeeded with dwForwardMetric1=35 and dwForwardType=4
Tue Sep 20 16:28:48 2016 Route addition via IPAPI succeeded [adaptive]
Tue Sep 20 16:28:48 2016 UDPv4 link local (bound): [undef]
Tue Sep 20 16:28:48 2016 UDPv4 link remote: [undef]
Tue Sep 20 16:28:48 2016 MULTI: multi_init called, r=256 v=256
Tue Sep 20 16:28:48 2016 IFCONFIG POOL: base=10.8.0.4 size=62, ipv6=0
Tue Sep 20 16:28:48 2016 Initialization Sequence Completed
Tue Sep 20 16:28:48 2016 MANAGEMENT: >STATE:1474414128,CONNECTED,SUCCESS,10.8.0.1,
Tue Sep 20 16:29:01 2016 192.168.1.107:58462 TLS: Initial packet from [AF_INET]192.168.1.107:58462, sid=3d17a837 8e1af151
Tue Sep 20 16:29:01 2016 192.168.1.107:58462 VERIFY OK: depth=1, CN=Easy-RSA CA
Tue Sep 20 16:29:01 2016 192.168.1.107:58462 VERIFY OK: depth=0, CN=CLIENT
Tue Sep 20 16:29:01 2016 192.168.1.107:58462 Data Channel Encrypt: Cipher 'AES-256-CBC' initialized with 256 bit key
Tue Sep 20 16:29:01 2016 192.168.1.107:58462 Data Channel Encrypt: Using 160 bit message hash 'SHA1' for HMAC authentication
Tue Sep 20 16:29:01 2016 192.168.1.107:58462 Data Channel Decrypt: Cipher 'AES-256-CBC' initialized with 256 bit key
Tue Sep 20 16:29:01 2016 192.168.1.107:58462 Data Channel Decrypt: Using 160 bit message hash 'SHA1' for HMAC authentication
Tue Sep 20 16:29:01 2016 192.168.1.107:58462 Control Channel: TLSv1.2, cipher TLSv1/SSLv3 DHE-RSA-AES256-GCM-SHA384, 2048 bit RSA
Tue Sep 20 16:29:01 2016 192.168.1.107:58462 [CLIENT] Peer Connection Initiated with [AF_INET]192.168.1.107:58462
Tue Sep 20 16:29:01 2016 CLIENT/192.168.1.107:58462 MULTI_sva: pool returned IPv4=10.8.0.6, IPv6=(Not enabled)
Tue Sep 20 16:29:01 2016 CLIENT/192.168.1.107:58462 MULTI: Learn: 10.8.0.6 -> CLIENT/192.168.1.107:58462
Tue Sep 20 16:29:01 2016 CLIENT/192.168.1.107:58462 MULTI: primary virtual IP for CLIENT/192.168.1.107:58462: 10.8.0.6
Tue Sep 20 16:29:03 2016 CLIENT/192.168.1.107:58462 PUSH: Received control message: 'PUSH_REQUEST'
Tue Sep 20 16:29:03 2016 CLIENT/192.168.1.107:58462 send_push_reply(): safe_cap=940
Tue Sep 20 16:29:03 2016 CLIENT/192.168.1.107:58462 SENT CONTROL [CLIENT]: 'PUSH_REPLY,redirect-gateway,route 10.8.0.1,topology net30,ping 10,ping-restart 120,ifconfig 10.8.0.6 10.8.0.5' (status=1)

TinCanTech

According to your logs, your client is successfully connected to your server.

You will need:

push "redirect-gateway def1"

when you try this from a remote location.

bimmerdriver

TinCanTech wroteAccording to your logs, your client is successfully connected to your server.

You will need:

push "redirect-gateway def1"

when you try this from a remote location.

Thanks for the reply. I didn't originally add the def1 part because I got the impression from the man page that it was the default. I tried it and it made no difference. Using the direct connection on the LAN, ipv4 is not working (based on http, ping and tracert) and ipv6 is working, but it's not going through the vpn.

I found this in the howto:

Pushing the redirect-gateway option to clients will cause all IP network traffic originating on client machines to pass through the OpenVPN server. The server will need to be configured to deal with this traffic somehow, such as by NATing it to the internet, or routing it through the server site's HTTP proxy.

On Linux, you could use a command such as this to NAT the VPN client traffic to the internet:

iptables -t nat -A POSTROUTING -s 10.8.0.0/24 -o eth0 -j MASQUERADE
This command assumes that the VPN subnet is 10.8.0.0/24 (taken from the server directive in the OpenVPN server configuration) and that the local ethernet interface is eth0.

When redirect-gateway is used, OpenVPN clients will route DNS queries through the VPN, and the VPN server will need handle them. This can be accomplished by pushing a DNS server address to connecting clients which will replace their normal DNS server settings during the time that the VPN is active. For example:

push "dhcp-option DNS 10.8.0.1"
will configure Windows clients (or non-Windows clients with some extra server-side scripting) to use 10.8.0.1 as their DNS server. Any address which is reachable from clients may be used as the DNS server address.

bimmerdriver

I accidentally hit submit instead of preview and it won't let me edit the post for some reason, so I have some things to add.

After I found that it wasn't working with the client and server on the same LAN, I moved the client to another LAN (I have two pfsense guests with their own WAN connections. I configured a port forwarding rule to forward WAN:1194 to LAN:1194. The incoming requests from the client were getting blocked by the firewall because they were using random port numbers. Why is that happening? Is there a way to get the client to use 1194? I can't forward a random port number.

Regarding the section of the howto about server routing, the example is for linux. Is there a windows example?

Thanks again for the help.

TinCanTech

bimmerdriver wroteIs there a way to get the client to use 1194?

See --nobind & --lport in The Manual v23x .. Read it carefully.

bimmerdriver

TinCanTech wrote
bimmerdriver wroteIs there a way to get the client to use 1194?
See --nobind & --lport in The Manual v23x .. Read it carefully.

I tried lport 1194 and rport 1194. Neither caused the outgoing port to be 1194. Is that even supported from the config file? The client tries for a couple of minutes with an arbitrary port number, then it changes to another port number.

bimmerdriver

I also tried port 1194. Nothing made any difference in the outgoing port number.

TinCanTech

TinCanTech wrote
bimmerdriver wroteIs there a way to get the client to use 1194?
See --nobind & --lport in The Manual v23x .. Read carefully.

bimmerdriver

TinCanTech wrote
TinCanTech wrote
bimmerdriver wroteIs there a way to get the client to use 1194?
See --nobind & --lport in The Manual v23x .. Read carefully.

Are you purposely trying to be obtuse? I read the man pages several times. nobind cannot be used with lport. The default is bind, which what I assume is required, but it doesn't seem to do anything. My firewall is logging the blocked incoming connection attempts. The client uses a random port number until it times out, then it switches to another random port number. How can I get the client to use a fixed port number (e.g., 1194) so I can get port forwarding to work?

TinCanTech

bimmerdriver wrotenobind cannot be used with lport

Exactly .. and you want to bind to a specific local port.

bimmerdriver

TinCanTech wrote
bimmerdriver wrotenobind cannot be used with lport
Exactly .. and you want to bind to a specific local port.

Are you suggesting that I'm trying to use unbind? If so, I'm not. I commented it out and I've tried using port, lport and rport, with and without bind before and after. In all cases it had no effect on what's happening. Unless I'm missing something, this appears to be a bug.

TinCanTech

bimmerdriver wroteAre you suggesting that I'm trying to use unbind? If so, I'm not.

I think your paranoia has over come you .. there is no such option as unbind

--lport works perfectly for me, even on wind-blows eleven and a bit less .. :mrgreen:

bimmerdriver

TinCanTech wrote
bimmerdriver wroteAre you suggesting that I'm trying to use unbind? If so, I'm not.
I think your paranoia has over come you .. there is no such option as unbind

--lport works perfectly for me, even on wind-blows eleven and a bit less .. :mrgreen:

Obviously I meant nobind.

TinCanTech

bimmerdriver wroteAre you suggesting that I'm trying to use unbind?

TinCanTech wroteI think your paranoia has over come you .. there is no such option as unbind

bimmerdriver wroteObviously I meant nobind

Obviously, that was not obvious.

Have you figured it out yet :?:

bimmerdriver

It was a typo, and no, it's not working. No matter what I've tried, the client keeps using a random outbound port.

TinCanTech

Please post your current client config .....

bimmerdriver

The client config is below. As I said before, I've tried using port, lport, rport, bind (before and after) and also <connection> / </connection>. No matter what I've tried, I can see on the firewall that the incoming port is a random number, never 1194. I am exiting the client between changes.
##############################################
# 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.

<connection>
bind
;remote 192.168.1.108 1194
remote do.not.post.public-ip 1194
lport 1194
</connection>

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

# Tunnel IPv6 traffic as well as IPv4
tun-ipv6

TinCanTech

bimmerdriver wroteI can see on the firewall that the incoming port is a random number, never 1194

Check on the client which port it actually uses ..

> netstat anop udp

bimmerdriver

Well, the output from netstat is interesting.

Here it is:

Proto Local Address Foreign Address
UDP 0.0.0.0:1194 *:*

The output port is correct, but it's interesting that the address is 0.0.0.0, also that the foreign address is not being shown.

bimmerdriver

bimmerdriver wroteIt was a typo, and no, it's not working. No matter what I've tried, the client keeps using a random outbound port.

Problem solved. The port number was being changed by the router. I now have router set up to pass the connection through the firewall and redirect it to the server.

Openvpn is still not working. Initially, it was doing the same thing as when the client and server were on the same lan. There was no ipv4 connection and ipv6 was sort of working, but it was bypassing openvpn and using the local ipv6 connection on the client, which is a hurricane electric tunnel. I added block-outside-dns to the client and with that enabled, there is no ipv4 or ipv6 connectivity when the client is connected to the server. I uncommented the command to push the "openvpn.com" dns, but that made no difference. Do routes need to be pushed?

I'll post the config files and logs.