[SOLVED] HELP: vpn cients can not ping advertised network after reboot

[pete83]

I had a fine working vpn.
This morning I had to reboot our zentyal server, after the system came up again the vpn client could connect but they can't ping any systems in our advertised network.

Can someone please help me, here are my config files. Please let me know if more info is needed.

/etc/openvpn/openvpn.conf

Code: [Select]

# EBox OpenVPN 2.0 config file for  server zentyal01

# Which local IP address should OpenVPN
# listen on? (optional)

local 192.168.100.19

# Which TCP/UDP port should OpenVPN listen on?

port 1194

# TCP or UDP server?

proto udp

# virtual device

dev tap0

# SSL/TLS root certificate (ca), certificate

# (cert), and private key (key).

ca '/var/lib/ebox/CA/cacert.pem'

cert '/var/lib/ebox/CA/certs/D35979196B6CBFF6.pem'

key '/var/lib/ebox/CA/private/zentyal01.pem'
 # This file should be kept secret

# check peer certificate against certificate revokation list

crl-verify /var/lib/ebox/CA/crl/latest.pem


# 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/dh1024.pem

dh /etc/openvpn/ebox-dh1024.pem


# Configure server mode and supply a VPN subnet
# for OpenVPN to draw client addresses from.
server 10.10.0.0 255.255.255.0

# Maintain a record of client <-> virtual IP address
# associations in this file.
ifconfig-pool-persist '/etc/openvpn/zentyal01-ipp.txt'


# If enabled, this directive will configure
# all clients to redirect their default
# network gateway through the VPN
;push "redirect-gateway"

# Uncomment this directive to allow different
# clients to be able to "see" each other.

client-to-client


# The keepalive directive causes ping-like
# messages to be sent back and forth over
keepalive 10 120


# client certificate common name authentication



# For extra security beyond that provided
# by SSL/TLS, create an "HMAC firewall"
# to help block DoS attacks and UDP port flooding.
;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

# 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

# group and user for the OpenVPN
# daemon's privileges after initialization.

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 '/var/log/ebox/openvpn/status-zentyal01.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-append  '/var/log/ebox/openvpn/zentyal01.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 5

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

   push "route 192.168.0.0 255.255.0.0"

client.conf

Code: [Select]

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

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

# Are we connecting to a TCP or
# UDP server?  Use the same setting as
# on the server.
proto udp

# The hostname/IP and port of the server.
# You can have multiple remote entries
# to load balance between the servers.
remote  195.XX.XX.XX 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


# Comment out user and group if you wish to increase security. Be advised you
# can experience some issues when reconnecting
# user nobody
# the group option may be wrong for some distributions
# normally distributions use wether 'nobody' (Fedora) or 'nogroup'
# for the no-priviligies group name
# 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   "XXXX.pem"
cert "XXXXXXX.pem"
key  "XXXXXX.pem"

# Verify server certificate by common name
tls-remote zentyal01


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

# 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

# Explicitly notify disconnections
explicit-exit-notify 3

# Silence repeating messages
;mute 20

ip route:

[pete83]

The arp table doesn't look good:

Code: [Select]

$ arp -a
? (10.10.0.1) at <incomplete> on tap0
With tcpdump I see this messages come along:

Code: [Select]

ARP, Request who-has 10.10.0.1 tell laptop.local, length 28

[pete83]

Bump   

When I ping from the zentyal server to clients it get an answer but the other way round I get Destination Host Unreachable:

server:

Code: [Select]

ping -Itap0 10.10.0.2
PING 10.10.0.2 (10.10.0.2) from 10.10.0.1 tap0: 56(84) bytes of data.
64 bytes from 10.10.0.2: icmp_seq=1 ttl=64 time=11.4 ms
64 bytes from 10.10.0.2: icmp_seq=2 ttl=64 time=0.214 ms
64 bytes from 10.10.0.2: icmp_seq=3 ttl=64 time=0.275 ms
client:

Code: [Select]

ping -Itap0 10.10.0.1
PING 10.10.0.1 (10.10.0.1) from 10.10.0.2 tap0: 56(84) bytes of data.
From 10.10.0.2 icmp_seq=1 Destination Host Unreachable
From 10.10.0.2 icmp_seq=2 Destination Host Unreachable
From 10.10.0.2 icmp_seq=3 Destination Host Unreachable

[pete83]

In the log file for VPN I also see these messages:

Code: [Select]

Mon May 14 11:32:16 2012 us=396178 read UDPv4 [CMSG=8|ECONNREFUSED]: Connection refused (code=111)
Mon May 14 11:32:24 2012 us=626561 CLIENT/XX.XX.XX.XX:40800 [CLIENT] Inactivity timeout (--ping-restart), restarting
Mon May 14 11:32:24 2012 us=626633 CLIENT/XX.XX.XX.XX:40800 SIGUSR1[soft,ping-restart] received, client-instance restarting

[pete83]

  wrong routing table after reboot. Deleted the route and everything works again. Still don't get it but happy that it works!!

[aguerra]

How did you solve this??