歡迎您光臨本站 註冊首頁

Openvpn中兩內網網段主機間的訪問問題(已解決,非常感謝congli)

網路拓撲如下:



目的是讓兩端的內網之間的主機間能夠互相訪問。具體到拓撲圖上來說就是host1與host2之間能互訪。
現在從opnvpn client此主機可以訪問server端的內網的主機(10.0.10.0/24),但是host2無法訪問。
server上的配置為:
# 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 tap" if you are ethernet bridging.
# 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 serversz.crt
key serversz.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 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 10.0.10.0 255.255.0.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
# 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"

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

# Silence repeating messages.  At most 20
# sequential messages of the same message
# category will be output to the log.
;mute 20
參照http://bbs.chinaunix.net/viewthread.php?tid=830695&extra=page%3D1%26amp%3Bfilter%3Ddigest&page=1的操作,如果要使HOST2與host1之間能互相訪問,我需要做的操作有:
在server.ovpn中添加host2網段的路由「route 192.168.0.0 255.255.255.0",,啟用client-config-dir ccd然後在.../openvpn下新建立一個目錄client1,在裡面添加iroute 192.168.0.0 255.255.255.0
這樣為什麼還不行?誰能指點下?謝謝!

[ 本帖最後由 coldface 於 2007-11-29 11:07 編輯 ]
《解決方案》

在 server.ovpn中添加host2網段的路由「route 192.168.0.0 255.255.255.0",,啟用client-config-dir ccd然後在.../openvpn下新建立一個目錄client1,在裡面添加iroute 192.168.0.0 255.255.255.0

應該建ccd目錄,在此目錄下,以"comman name"為文件名,裡面有iconfig-push及iroute.這樣才可以指定客戶端VPN虛擬網段IP及讓其他客戶端或服務端路由到該客戶端的區域網.

[ 本帖最後由 congli 於 2007-11-28 09:34 編輯 ]
《解決方案》

是的,我是建了此目錄,也是已comman name命名.也加了iroute,唯獨ifconfig-push沒加,因為有點不是很明白,ifconfig-push加的是local vpn ip和另已一個IP,我不知道另一個IP是不是指VPN SERVER的VPN IP.通過MAN手冊上看,應該是.
您看對么 ?
《解決方案》

在server.conf,
server 172.16.0.0 255.255.255.0
此網段是VPN之間通信的虛擬網段.
ifconfig-push設置的就是這個網段的IP.
《解決方案》

恩,我來先看看!等等有問題再跟您請教!
《解決方案》

現在還不行,加了后連vpnclient訪問server端的內網都不可以了.我操作是這樣的:server端的vpn ip是172.16.0.1(255.255.255.252),client端的VPN IP是172.16.0.6(255.255.255.252).我再openvpn目錄下建立一個ccd目錄,裡面建立一個名字與客戶端comman name一致的文件,文件的內容是ifconfig-push 172.16.0.6 172.16.0.1 和添加此網段的IP iroute 192.168.0.0 255.255.255.0 在server.ovpn里啟用ccd那命令,然後添加route 192.168.0.0 255.255.255.0
等這些操作完后,兩內網的主機不僅無法訪問,而且原來client本來可以訪問server端內網,現在也不可以了! 我看了下路由表,在客戶端的路由表中有172.16.0.0 192.168.0.0 218.85.158.0
在server端的路由表中有10.0.10.0 172.16.0.0 192.168.0.0 218.85.158.0
我在想是不是在VPNclient上也要啟用route and remote access服務?還是自己的配置有問題.問題最可能出在ifconfig-push裡面. 請幫助下,謝謝!
《解決方案》

ifconfig-push 172.16.0.6 172.16.0.5
iroute 192.168.0.0 255.255.255.0
《解決方案》

是的! 我按照此方法后,兩網段還是不行.有沒有日誌記錄這?還又可能是別的原因么?有沒有可能是我伺服器端一直再修改導致文件讀的時候混亂?所以兩網段的內網主機無法訪問
《解決方案》

確實中間是我修改多次導致文件讀取命令的時候出現錯誤.我把系統還原了下,然後重新做了下! 結果還是不行,我從server上看其路由表,發現怎麼裡面沒有添加client的內網的網段?我再配置里加進去了的.請看
server.ovpn
port 1194

# TCP or UDP server?
;proto tcp
proto udp

;dev tap
dev tun

;dev-node MyTap

ca ca.crt
cert server001.crt
key server001.key  # This file should be kept secret

dh dh1024.pem

server 172.16.0.0 255.255.255.0

ifconfig-pool-persist ipp.txt


push "route 10.0.10.0 255.255.255.0"
;push "route 192.168.20.0 255.255.255.0"


;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

# 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 192.168.0.0 255.255.255.0
# Then add this line to ccd/Thelonious:
#   ifconfig-push 10.9.0.1 10.9.0.2


client-to-client

;duplicate-cn


# 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

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

# or the other (but not both).
;log         openvpn.log
;log-append  openvpn.log

verb 3

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


ccd中client1文件
ifconfig-push 172.16.0.6 172.16.0.5
iroute 192.168.0.0 255.255.255.0
還是不通,我把server端的路由表發下,還有那IP之間互通的關係

[ 本帖最後由 coldface 於 2007-11-28 20:53 編輯 ]
《解決方案》

補充點就是我的ccd目錄是放在programfile\openvpn\config下的,我看資料,在windows下是放置此位置下。還有我在openvpn client主機上也啟用了路由功能了。想想路由route 192.168.0.0 255.255.255.0已經加入,為什麼數據報還是會無法到達?
請指教 謝謝、

[火星人 ] Openvpn中兩內網網段主機間的訪問問題(已解決,非常感謝congli)已經有681次圍觀

http://coctec.com/docs/service/show-post-20371.html