#1  
Old 3rd July 2010, 22:46
RoMiONeT RoMiONeT is offline
Junior Member
 
Join Date: Apr 2009
Location: Egypt
Posts: 9
Thanks: 0
Thanked 0 Times in 0 Posts
Default Can't Ping over VPN

Hello,

I have just installed openvpn on my server
i followed this tutorial to install http://www.howtoforge.com/openvpn-server-on-centos-5.2

it is installed proberly and i can connect to the openvpn server and it appears assigned ip in openvpn-client-gui program

but i can't ping any ip over the network as well as i can't ping the main openvpn ip & i can't ping any client ip from the openvpn server

this is the server.conf
#################################################
# 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 1723

# 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 dh1024.pem 1024
# Substitute 2048 for 1024 if you are using
# 2048 bit keys.
dh 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
server 172.16.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

# 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"
push "route 192.168.168.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
# the TUN/TAP interface to the internet in
# order for this to work properly).
# CAVEAT: May break client's network config if
# client's local DHCP server packets get routed
# through the tunnel. Solution: make sure
# client's local DHCP server is reachable via
# a more specific route than the default route
# of 0.0.0.0/0.0.0.0.
;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
;push "dhcp-option DNS 10.8.0.1"
;push "dhcp-option WINS 10.8.0.1"
push "dhcp-option DNS 192.168.168.1"
push "dhcp-option DNS 168.210.2.2"

# 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

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

# 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


the client.ovpn

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

# The hostname/IP and port of the server.
# You can have multiple remote entries
# to load balance between the servers.
remote myopenvpnserverip 1723
;remote my-server-2 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 users

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

# 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

# Silence repeating messages
;mute 20

aslo i have stoped all firewalls and iptables

and this is what appeard when i connect via openvpn-gui software

Sat Jul 03 17:31:50 2010 NOTE: --user option is not implemented on Windows
Sat Jul 03 17:31:50 2010 NOTE: --group option is not implemented on Windows
Sat Jul 03 17:31:50 2010 OpenVPN 2.0.9 Win32-MinGW [SSL] [LZO] built on Oct 1 2006
Sat Jul 03 17:31:50 2010 IMPORTANT: OpenVPN's default port number is now 1194, based on an official port number assignment by IANA. OpenVPN 2.0-beta16 and earlier used 5000 as the default port.
Sat Jul 03 17:31:50 2010 WARNING: No server certificate verification method has been enabled. See http://openvpn.net/howto.html#mitm for more info.
Sat Jul 03 17:31:50 2010 LZO compression initialized
Sat Jul 03 17:31:50 2010 Control Channel MTU parms [ L:1544 D:140 EF:40 EB:0 ET:0 EL:0 ]
Sat Jul 03 17:31:50 2010 Data Channel MTU parms [ L:1544 D:1450 EF:44 EB:135 ET:0 EL:0 AF:3/1 ]
Sat Jul 03 17:31:50 2010 Local Options hash (VER=V4): '69109d17'
Sat Jul 03 17:31:50 2010 Expected Remote Options hash (VER=V4): 'c0103fa8'
Sat Jul 03 17:31:50 2010 Attempting to establish TCP connection with 69.162.85.178:1723
Sat Jul 03 17:31:51 2010 TCP connection established with 69.162.85.178:1723
Sat Jul 03 17:31:51 2010 TCPv4_CLIENT link local: [undef]
Sat Jul 03 17:31:51 2010 TCPv4_CLIENT link remote: 69.162.85.178:1723
Sat Jul 03 17:31:51 2010 TLS: Initial packet from 69.162.85.178:1723, sid=f84d0f1e 766a3571
Sat Jul 03 17:31:53 2010 VERIFY OK: depth=1, /C=SA/ST=SA/L=RI/O=3JENAN/OU=3JENAN-NETWORK/CN=Ramy/emailAddress=dnx@hotmail.com
Sat Jul 03 17:31:53 2010 VERIFY OK: depth=0, /C=SA/ST=SA/L=RI/O=3JENAN/OU=3JENAN-NETWORK/CN=Ramy/emailAddress=dnx@hotmail.com
Sat Jul 03 17:31:58 2010 Data Channel Encrypt: Cipher 'BF-CBC' initialized with 128 bit key
Sat Jul 03 17:31:58 2010 Data Channel Encrypt: Using 160 bit message hash 'SHA1' for HMAC authentication
Sat Jul 03 17:31:58 2010 Data Channel Decrypt: Cipher 'BF-CBC' initialized with 128 bit key
Sat Jul 03 17:31:58 2010 Data Channel Decrypt: Using 160 bit message hash 'SHA1' for HMAC authentication
Sat Jul 03 17:31:58 2010 Control Channel: TLSv1, cipher TLSv1/SSLv3 DHE-RSA-AES256-SHA, 1024 bit RSA
Sat Jul 03 17:31:58 2010 [Ramy] Peer Connection Initiated with 69.162.85.178:1723
Sat Jul 03 17:31:59 2010 SENT CONTROL [Ramy]: 'PUSH_REQUEST' (status=1)
Sat Jul 03 17:32:00 2010 PUSH: Received control message: 'PUSH_REPLY,route 192.168.168.0 255.255.255.0,dhcp-option DNS 192.168.168.1,dhcp-option DNS 168.210.2.2,route 172.16.0.0 255.255.255.0,ping 10,ping-restart 120,ifconfig 172.16.0.6 172.16.0.5'
Sat Jul 03 17:32:00 2010 OPTIONS IMPORT: timers and/or timeouts modified
Sat Jul 03 17:32:00 2010 OPTIONS IMPORT: --ifconfig/up options modified
Sat Jul 03 17:32:00 2010 OPTIONS IMPORT: route options modified
Sat Jul 03 17:32:00 2010 OPTIONS IMPORT: --ip-win32 and/or --dhcp-option options modified
Sat Jul 03 17:32:00 2010 TAP-WIN32 device [Local Area Connection 2] opened: \\.\Global\{2BECA3FA-8526-4DBD-A11E-6076B68A8472}.tap
Sat Jul 03 17:32:00 2010 TAP-Win32 Driver Version 8.4
Sat Jul 03 17:32:00 2010 TAP-Win32 MTU=1500
Sat Jul 03 17:32:00 2010 Notified TAP-Win32 driver to set a DHCP IP/netmask of 172.16.0.6/255.255.255.252 on interface {2BECA3FA-8526-4DBD-A11E-6076B68A8472} [DHCP-serv: 172.16.0.5, lease-time: 31536000]
Sat Jul 03 17:32:00 2010 Successful ARP Flush on interface [17] {2BECA3FA-8526-4DBD-A11E-6076B68A8472}
Sat Jul 03 17:32:00 2010 TEST ROUTES: 0/0 succeeded len=2 ret=0 a=0 u/d=down
Sat Jul 03 17:32:00 2010 Route: Waiting for TUN/TAP interface to come up...
Sat Jul 03 17:32:01 2010 TEST ROUTES: 2/2 succeeded len=2 ret=1 a=0 u/d=up
Sat Jul 03 17:32:01 2010 route ADD 192.168.168.0 MASK 255.255.255.0 172.16.0.5
Sat Jul 03 17:32:01 2010 ROUTE: route addition failed using CreateIpForwardEntry: One or more arguments are not correct. [if_index=17]
Sat Jul 03 17:32:01 2010 Route addition via IPAPI failed
Sat Jul 03 17:32:01 2010 route ADD 172.16.0.0 MASK 255.255.255.0 172.16.0.5
Sat Jul 03 17:32:01 2010 ROUTE: route addition failed using CreateIpForwardEntry: One or more arguments are not correct. [if_index=17]
Sat Jul 03 17:32:01 2010 Route addition via IPAPI failed
Sat Jul 03 17:32:01 2010 Initialization Sequence Completed

Could you please help me about that ?

Thanks alot
__________________
My Lord IS Enough 4 Me .. Glory 2 Be Allah
Reply With Quote
Sponsored Links
  #2  
Old 3rd July 2010, 23:44
damir damir is offline
Senior Member
 
Join Date: Jun 2006
Posts: 375
Thanks: 11
Thanked 51 Times in 42 Posts
Default

Is the VPN LAN on the same subnet as your LAN?
Reply With Quote
  #3  
Old 4th July 2010, 00:19
RoMiONeT RoMiONeT is offline
Junior Member
 
Join Date: Apr 2009
Location: Egypt
Posts: 9
Thanks: 0
Thanked 0 Times in 0 Posts
 
Default

Quote:
Originally Posted by damir View Post
Is the VPN LAN on the same subnet as your LAN?
Hello,

No ..
ifconfig from openvpn server
tun0 Link encap:UNSPEC HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00
inet addr:172.16.0.1 P-t-P:172.16.0.2 Mask:255.255.255.255
UP POINTOPOINT RUNNING NOARP MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:8 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:100
RX bytes:0 (0.0 b) TX bytes:672 (672.0 b)


from vpn client
ip : 10.0.0.10
Subnet mask : 255.255.255.0


i can ping 172.16.0.1 from my pc ( vpn client ) also i can't ping any other ip over the network & i can't ping any vpn client from the vpn server
__________________
My Lord IS Enough 4 Me .. Glory 2 Be Allah

Last edited by RoMiONeT; 4th July 2010 at 00:21.
Reply With Quote
Reply

Bookmarks

Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump

Similar Threads
Thread Thread Starter Forum Replies Last Post
VPN Server Problem pinguingilo Installation/Configuration 3 15th January 2014 23:00
openvpn I cant ping or get connection to the internet through vpn Deficit Server Operation 1 11th November 2009 10:04
Vista not able to ping office network through vpn pawan_lal Server Operation 1 29th June 2009 12:34
not able to ping office lan from vpn pawan_lal Server Operation 0 18th June 2009 11:41
power failure caused ISPConfig to start up with a weird problem FOBioPatel Installation/Configuration 10 23rd August 2008 01:58


All times are GMT +2. The time now is 14:47.


Powered by vBulletin® Version 3.8.7
Copyright ©2000 - 2014, vBulletin Solutions, Inc.