It is currently 22.09.2017 04:25


All times are UTC




Post new topic Reply to topic  [ 11 posts ] 
Author Message
 Post subject: Can't ping local lan in bridge mode
PostPosted: 26.11.2009 08:50 
DES
DES

Joined: 26.11.2009 08:36
Posts: 4
Hi,

I installed Openvpn on CentoOS 5.4 in bridge mode. I am able to connect to my network but i am unable to ping aynthing on LAN, except the VPN server :(. I did enable ipv4 forward on centos and thats about it. Here are my configs. Any help?



server cfg:
Code:
# Which local IP address should OpenVPN
# listen on? (optional)
local 172.16.1.91

# 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 tap0
;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/keys/ca.crt
cert /etc/openvpn/keys/server.crt
key /etc/openvpn/keys/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 /etc/openvpn/keys/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-bridge 172.16.1.91 255.255.255.0 172.16.1.161 172.16.1.190

# 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 172.16.1.0 255.255.255.0"
;push "route 192.168.11.0 255.255.255.0"
;push "route 10.208.0.0 255.255.0.0"
;push "route 10.209.0.0 255.255.0.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 172.16.1.40"
;push "dhcp-option WINS 172.16.1.40"
push "dhcp-option DOMAIN swingint.hr"

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

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



user cfg:
Code:
##############################################
# 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 xxx.xxx.xxx 1194
;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 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 C:\\ProgramFiles\\OpenVPN\\config\\ca.crt
cert C:\\ProgramFiles\\OpenVPN\\config\\client1.crt
key C:\\ProgramFiles\\OpenVPN\\config\\client1.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


Config for bridge script
Code:
#!/bin/bash 
         # Create global variables   
         # Define Bridge Interface
         br="br0"
         # Define list of TAP interfaces to be bridged,
         # for example tap="tap0 tap1 tap2".
         tap="tap0"
         # Define physical ethernet interface to be bridged
         # with TAP interface(s) above.
         eth="eth0"
         eth_ip="172.16.1.91"
         eth_netmask="255.255.255.0"
         eth_broadcast="172.16.1.255"
         gw="172.16.1.253"   
         start_bridge () {   
         #################################   
         # Set up Ethernet bridge on Linux   
         # Requires: bridge-utils   
         #################################   
         for t in $tap; do
         openvpn --mktun --dev $t   
         done   
         for t in $tap; do
         ifconfig $t 0.0.0.0 promisc up   
         done
         ifconfig $eth 0.0.0.0 promisc up
         brctl addbr $br
         brctl addif $br $eth
         for t in $tap; do
         brctl addif $br $t   
         done   
         ifconfig $br $eth_ip netmask $eth_netmask broadcast $eth_broadcast up   
         route add default gw $gw $br
         }
         stop_bridge () {   
         ####################################   
         # Tear Down Ethernet bridge on Linux   
         ####################################   
         ifconfig $br down
         brctl delbr $br   
         for t in $tap; do
         openvpn --rmtun --dev $t   
         done   
         ifconfig $eth $eth_ip netmask $eth_netmask broadcast $eth_broadcast up   
         route add default gw $gw $eth
         } 
         case "$1" in
         start)   
         echo -n "Starting Bridge"   
         start_bridge   
         ;;
         stop)   
         echo -n "Stopping Bridge"   
         stop_bridge   
         ;;
         restart)   
         stop_bridge   
         sleep 2   
         start_bridge   
         ;;
         *)   
         echo "Usage: $0 {start|stop|restart}" >&2   
         exit 1   
         ;;
         esac 



Top
Offline Profile  
Reply with quote  
 Post subject: Re: Can't ping local lan in bridge mode
PostPosted: 26.11.2009 14:25 
openvpn.eu Admin
openvpn.eu Admin
User avatar

Joined: 23.01.2006 08:05
Posts: 3321
Location: near Vienna
Hello

Is your server a real machine or virtual ? Please be aware that wireless network cards can't be bridged.

_________________
regards,
note
Please take a look at our rules. Besucht mal unsere Wiki !


Top
Offline Profile  
Reply with quote  
 Post subject: Re: Can't ping local lan in bridge mode
PostPosted: 26.11.2009 15:08 
DES
DES

Joined: 26.11.2009 08:36
Posts: 4
My openvpn server is virtual machine.


Last edited by dreic on 11.11.2010 12:41, edited 1 time in total.

Top
Offline Profile  
Reply with quote  
 Post subject: Re: Can't ping local lan in bridge mode
PostPosted: 27.11.2009 07:48 
DES
DES

Joined: 26.11.2009 08:36
Posts: 4
If i add route for VPN clients on server whom i am pinging ping passes.

So in my firm i use 172.16.1.0/24 network, for clients i assigned 172.16.1.160/27. If i am using bridge why do i need to add route for vpn clients? Isn't the point of bridgin not to use routes?


Top
Offline Profile  
Reply with quote  
 Post subject: Re: Can't ping local lan in bridge mode
PostPosted: 09.11.2010 09:49 
DES
DES

Joined: 09.11.2010 09:47
Posts: 2
Hi, i have exactly the same problem. Did you find any resolution?


Top
Offline Profile  
Reply with quote  
 Post subject: Re: Can't ping local lan in bridge mode
PostPosted: 11.11.2010 10:40 
Profi
Profi

Joined: 23.10.2007 12:10
Posts: 2185
if you made a bridge, all IPs are reachable!
If not.. you did not make a bridge...(you call it only bridge).
and... no, i will never read configuration files with thousands of comment lines :)

F.


Top
Offline Profile  
Reply with quote  
 Post subject: Re: Can't ping local lan in bridge mode
PostPosted: 11.11.2010 12:39 
DES
DES

Joined: 26.11.2009 08:36
Posts: 4
I found the solution. SInce VPN server is on Vmware ESX host i had to enable promiscous mode under virtual switch and afterwards everything worked.


Top
Offline Profile  
Reply with quote  
 Post subject: Re: Can't ping local lan in bridge mode
PostPosted: 19.11.2010 10:47 
DES
DES

Joined: 09.11.2010 09:47
Posts: 2
Hi,

Great to hear that. In my physical environment the same configuration worked fine, and in virtual environment not. I made some investigation and found the same solution.

We use VMWare vSphere 4.1 with ESX server.

Regards!


Top
Offline Profile  
Reply with quote  
 Post subject: Re: Can't ping local lan in bridge mode
PostPosted: 05.12.2010 14:27 
DES
DES

Joined: 05.12.2010 14:18
Posts: 2
i have a problem :( can u please help me. :) :)


Top
Offline Profile  
Reply with quote  
 Post subject: Re: Can't ping local lan in bridge mode
PostPosted: 05.12.2010 14:32 
DES
DES

Joined: 05.12.2010 14:18
Posts: 2
i found the solution.:)
SInce VPN server is on Vmware ESX host i had to enable promiscous mode under virtual switch and afterwards everything worked.
:)
:)


Top
Offline Profile  
Reply with quote  
 Post subject: Cant ping local lan in bridge mode
PostPosted: 08.03.2016 23:40 
DES
DES
User avatar

Joined: 06.03.2016 06:21
Posts: 8
Location: Russia
ASA may be set to not respond to pings - try to ping from the ASA.

Also, the router isnt responding to ping - are all the switchports in the same VLAN?

___

XRumer 12.0.16 + SocPlugin: the BEST software for Facebook / VK / Forums / Blogs promotion!
Only TODAY: -30% DISCOUNT for XRumer!


Top
Offline Profile  
Reply with quote  
Display posts from previous:  Sort by  
Post new topic Reply to topic  [ 11 posts ]  Moderator: Moderators

All times are UTC


Who is online

Users browsing this forum: No registered users and 1 guest


You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot post attachments in this forum

Search for:
Jump to:  
Powered by phpBB © 2000, 2002, 2005, 2007 phpBB Group
Theme created StylerBB.net