Linux 下 OpenVPN 安装和 Windows OpenVPN GUI 安装笔记

页: 1 2 [3] 4

kenny

2009-9-12 02:42

我的安装终于可以连接上了，但是连上去以后访问不了网站，我也输入了echo 1 > /proc/sys/net/ipv4/ip_forward，但就是死活访问不了，怎么回事啊？

XiaoHui

2009-9-12 07:21

<blockquote>引用 kenny 的贴子<hr size=1 noshadow>我的安装终于可以连接上了，但是连上去以后访问不了网站，我也输入了echo 1 > /proc/sys/net/ipv4/ip_forward，但就是死活访问不了，怎么回事啊？<hr size=1 noshadow></blockquote>用 sysctl -a | grep for 看一下 ipfoward 是否打开了。

藤苇	2009-9-27 10:40

你好我遇到一个问题我没法解决，想向你咨询下 
[root@localhost root]# /usr/local/sbin/openvpn --config /usr/local/etc/server.conf 
Sun Sep 27 17:41:12 2009 OpenVPN 2.0.9 i686-pc-linux [SSL] [LZO] built on Sep 27 2009 
Sun Sep 27 17:41:12 2009 Cannot open dh1024.pem for DH parameters:error:02001002:system library:fopen:NO such file or directory:error:2006D080:BIO routines:BIO_new_file:no such file 
Sun Sep 27 14:41:12 2009 Exiting 
这是怎么一回事呢？急急急！！！

XiaoHui

2009-9-27 12:44

<blockquote>引用藤苇的贴子<hr size=1 noshadow>你好我遇到一个问题我没法解决，想向你咨询下 
[root@localhost root]# /usr/local/sbin/openvpn --config /usr/local/etc/server.conf 
Sun Sep 27 17:41:12 2009 OpenVPN 2.0.9 i686-pc-linux [SSL] [LZO] built on Sep 27 2009 
Sun Sep 27 17:41:12 2009 Cannot open dh1024.pem for DH parameters:error:02001002:system library:fopen:NO such file or directory:error:2006D080:BIO routines:BIO_new_file:no such file 
Sun Sep 27 14:41:12 2009 Exiting 
这是怎么一回事呢？急急急！！！<hr size=1 noshadow></blockquote>没有 Diffie Hellman 参数或文件的位置没有设置正确。见第七步代码:

./build-dh

藤苇	2009-9-27 14:17

你好 
./build-dh 
这一步我做了都是按照你上面说的去做的 
export D=`pwd` 只是这一步没做。 
export KEY_CONFIG=root/openvpn-2.0.9/easy-rsa/openssl.cnf 
export KEY_DIR=root/openvpn-2.0.9/easy-rsa/keys

藤苇	2009-9-27 14:25

在root/openvpn-2.0.9/easy-rsa/keys下生成了这个文件dh1024.pem 。

藤苇	2009-9-27 14:28

D=`pwd` 是什么意思呢?

XiaoHui

2009-9-28 01:22

<blockquote>引用藤苇的贴子<hr size=1 noshadow>D=`pwd` 是什么意思呢?<hr size=1 noshadow></blockquote>pwd 表示当前工作目录

藤苇	2009-10-12 03:58

############################################## 
# 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 172.16.37.83 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 ca.crt 
cert client1.crt 
key 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 
服务器配置 
################################################# 
# 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 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 /root/openvpn-2.0.9/easy-rsa/keys/ca.crt 
cert /root/openvpn-2.0.9/easy-rsa/keys/server.crt 
key /root/openvpn-2.0.9/easy-rsa/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 /root/openvpn-2.0.9/easy-rsa/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.0.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 p10.8.0.1rivate 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.11.0 255.255.255.0" 
;push "route 192.168.13.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 /usr/local/etc/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 /usr/local/etc/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 /root/openvpn-2.0.9/easy-rsa/keys/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 FilesOpenVPNlog" 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/root/openvpn-2.0.9/easy-rsa/keys 
# 4 is reasonable for genera/root/openvpn-2.0.9/easy-rsa/keysl 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 
 
 
openvpn服务器是red hat Linux 
客户机是windows server 2000 两个网卡开起了rip协议 
server ip： 172.16.37.83 虚拟ip 10.0.0.1； 
client1 ip：172.16.37.110 192.168.11.1 虚拟IP 10.0.0.5； 
client2 ip： 172.16.19.22. 192.168.12.1 虚拟ip 10.0.0.13； 
在server中可ping通10.0.0.1 172.16.37.83 172.16.37.110 172.16.19.22 192.168.11.1 192.168.12.1 ping不通 10.0.0.5 10.0.0.13 
client1 中可ping通 172.16.37.83 172.16.37.110 172.16.19.22 192.168.11.1 192.168.12.1 10.0.0.5 10.0.0.13 ping不通 10.0.0.1 
 
client2中可ping通 172.16.37.83 172.16.37.110 172.16.19.22 192.168.11.1 192.168.12.1 10.0.0.5 10.0.0.13 ping不通 10.0.0.1 
楼主这是哪出现了问题呢？拜托拜托

XiaoHui

2009-10-12 09:47

<blockquote>引用藤苇的贴子<hr size=1 noshadow>############################################## 
# 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 172.16.37.83 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 ca.crt 
cert client1.crt 
key 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 
服务器配置 
################################################# 
# 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 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 /root/openvpn-2.0.9/easy-rsa/keys/ca.crt 
cert /root/openvpn-2.0.9/easy-rsa/keys/server.crt 
key /root/openvpn-2.0.9/easy-rsa/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 /root/openvpn-2.0.9/easy-rsa/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.0.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 p10.8.0.1rivate 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.11.0 255.255.255.0" 
;push "route 192.168.13.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 /usr/local/etc/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 /usr/local/etc/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 /root/openvpn-2.0.9/easy-rsa/keys/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 FilesOpenVPNlog" 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/root/openvpn-2.0.9/easy-rsa/keys 
# 4 is reasonable for genera/root/openvpn-2.0.9/easy-rsa/keysl 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 
 
 
openvpn服务器是red hat Linux 
客户机是windows server 2000 两个网卡开起了rip协议 
server ip： 172.16.37.83 虚拟ip 10.0.0.1； 
client1 ip：172.16.37.110 192.168.11.1 虚拟IP 10.0.0.5； 
client2 ip： 172.16.19.22. 192.168.12.1 虚拟ip 10.0.0.13； 
在server中可ping通10.0.0.1 172.16.37.83 172.16.37.110 172.16.19.22 192.168.11.1 192.168.12.1 ping不通 10.0.0.5 10.0.0.13 
client1 中可ping通 172.16.37.83 172.16.37.110 172.16.19.22 192.168.11.1 192.168.12.1 10.0.0.5 10.0.0.13 ping不通 10.0.0.1 
 
client2中可ping通 172.16.37.83 172.16.37.110 172.16.19.22 192.168.11.1 192.168.12.1 10.0.0.5 10.0.0.13 ping不通 10.0.0.1 
楼主这是哪出现了问题呢？拜托拜托<hr size=1 noshadow></blockquote>Tooooooo looooooooog, 看着头晕又不方便比较。能不能把 #的注释去掉再贴上来。

藤苇	2009-10-12 10:23

client 
dev tap 
;dev tun 
;dev-node MyTap 
proto tcp 
;proto udp 
remote 172.16.37.83 1194 
;remote my-server-2 1194 
;remote-random 
resolv-retry infinite 
nobind 
;user nobody 
;group nobody 
persist-key 
persist-tun 
;http-proxy-retry # retry on connection failures 
;http-proxy [proxy server] [proxy port #] 
;mute-replay-warnings 
ca ca.crt 
cert client1.crt 
key client1.key 
;ns-cert-type server 
;tls-auth ta.key 1 
;cipher x 
comp-lzo 
verb 3 
服务器配置 
;local a.b.c.d 
port 1194 
proto tcp 
;proto udp 
dev tap 
;dev tun 
;dev-node MyTap 
ca /root/openvpn-2.0.9/easy-rsa/keys/ca.crt 
cert /root/openvpn-2.0.9/easy-rsa/keys/server.crt 
key /root/openvpn-2.0.9/easy-rsa/keys/server.key # This file should be kept secret 
dh /root/openvpn-2.0.9/easy-rsa/keys/dh1024.pem 
server 10.0.0.0 255.255.255.0 
ifconfig-pool-persist ipp.txt 
;server-bridge 10.8.0.4 255.255.255.0 10.8.0.50 10.8.0.100 
;push "route 192.168.11.0 255.255.255.0" 
;push "route 192.168.13.0 255.255.255.0" 
client-config-dir /usr/local/etc/ccd 
;route 192.168.40.128 255.255.255.248 
client-config-dir /usr/local/etc/ccd 
;route 10.9.0.0 255.255.255.252 
;learn-address ./script 
;push "redirect-gateway" 
;push "dhcp-option DNS 10.8.0.1" 
;push "dhcp-option WINS 10.8.0.1" 
;duplicate-cn 
keepalive 10 120 
;tls-auth ta.key 0 # This file is secret 
;cipher BF-CBC # Blowfish (default) 
;cipher AES-128-CBC # AES 
;cipher DES-EDE3-CBC # Triple-DES 
comp-lzo 
;max-clients 100 
;user nobody 
;group nobody 
persist-key 
persist-tun 
status /root/openvpn-2.0.9/easy-rsa/keys/openvpn-status.log 
;log openvpn.log 
;log-append openvpn.log 
verb 3 
;mute 20 
 
 
openvpn服务器是red hat Linux 
客户机是windows server 2000 两个网卡开起了rip协议 
server ip： 172.16.37.83 虚拟ip 10.0.0.1； 
client1 ip：172.16.37.110 192.168.11.1 虚拟IP 10.0.0.5； 
client2 ip： 172.16.19.22. 192.168.12.1 虚拟ip 10.0.0.13； 
在server中可ping通10.0.0.1 172.16.37.83 172.16.37.110 172.16.19.22 192.168.11.1 192.168.12.1 ping不通 10.0.0.5 10.0.0.13 
client1 中可ping通 172.16.37.83 172.16.37.110 172.16.19.22 192.168.11.1 192.168.12.1 10.0.0.5 10.0.0.13 ping不通 10.0.0.1 
 
client2中可ping通 172.16.37.83 172.16.37.110 172.16.19.22 192.168.11.1 
192.168.12.1 10.0.0.5 10.0.0.13 ping不通 10.0.0.1 
楼主这是哪出现了问题呢？拜托拜托我的QQ是137294593加我谢谢

藤苇	2009-10-12 10:23

client 
dev tap 
;dev tun 
;dev-node MyTap 
proto tcp 
;proto udp 
remote 172.16.37.83 1194 
;remote my-server-2 1194 
;remote-random 
resolv-retry infinite 
nobind 
;user nobody 
;group nobody 
persist-key 
persist-tun 
;http-proxy-retry # retry on connection failures 
;http-proxy [proxy server] [proxy port #] 
;mute-replay-warnings 
ca ca.crt 
cert client1.crt 
key client1.key 
;ns-cert-type server 
;tls-auth ta.key 1 
;cipher x 
comp-lzo 
verb 3 
服务器配置 
;local a.b.c.d 
port 1194 
proto tcp 
;proto udp 
dev tap 
;dev tun 
;dev-node MyTap 
ca /root/openvpn-2.0.9/easy-rsa/keys/ca.crt 
cert /root/openvpn-2.0.9/easy-rsa/keys/server.crt 
key /root/openvpn-2.0.9/easy-rsa/keys/server.key # This file should be kept secret 
dh /root/openvpn-2.0.9/easy-rsa/keys/dh1024.pem 
server 10.0.0.0 255.255.255.0 
ifconfig-pool-persist ipp.txt 
;server-bridge 10.8.0.4 255.255.255.0 10.8.0.50 10.8.0.100 
;push "route 192.168.11.0 255.255.255.0" 
;push "route 192.168.13.0 255.255.255.0" 
client-config-dir /usr/local/etc/ccd 
;route 192.168.40.128 255.255.255.248 
client-config-dir /usr/local/etc/ccd 
;route 10.9.0.0 255.255.255.252 
;learn-address ./script 
;push "redirect-gateway" 
;push "dhcp-option DNS 10.8.0.1" 
;push "dhcp-option WINS 10.8.0.1" 
;duplicate-cn 
keepalive 10 120 
;tls-auth ta.key 0 # This file is secret 
;cipher BF-CBC # Blowfish (default) 
;cipher AES-128-CBC # AES 
;cipher DES-EDE3-CBC # Triple-DES 
comp-lzo 
;max-clients 100 
;user nobody 
;group nobody 
persist-key 
persist-tun 
status /root/openvpn-2.0.9/easy-rsa/keys/openvpn-status.log 
;log openvpn.log 
;log-append openvpn.log 
verb 3 
;mute 20 
 
 
openvpn服务器是red hat Linux 
客户机是windows server 2000 两个网卡开起了rip协议 
server ip： 172.16.37.83 虚拟ip 10.0.0.1； 
client1 ip：172.16.37.110 192.168.11.1 虚拟IP 10.0.0.5； 
client2 ip： 172.16.19.22. 192.168.12.1 虚拟ip 10.0.0.13； 
在server中可ping通10.0.0.1 172.16.37.83 172.16.37.110 172.16.19.22 192.168.11.1 192.168.12.1 ping不通 10.0.0.5 10.0.0.13 192.168.11.1 192.168.12.1
 
client1 中可ping通 172.16.37.83 172.16.37.110 172.16.19.22 192.168.11.1 192.168.12.1 10.0.0.5 10.0.0.13 ping不通 10.0.0.1 
 
client2中可ping通 172.16.37.83 172.16.37.110 172.16.19.22 192.168.11.1 
192.168.12.1 10.0.0.5 10.0.0.13 ping不通 10.0.0.1 
楼主这是哪出现了问题呢？拜托拜托我的QQ是137294593加我谢谢

藤苇	2009-10-12 11:07

在以上的“在server中可ping通10.0.0.1 172.16.37.83 172.16.37.110 172.16.19.22 192.168.11.1 192.168.12.1 ping不通 10.0.0.5 10.0.0.13”修改一下 
应该是在server中可ping通10.0.0.1 172.16.37.83 172.16.37.110 172.16.19.22 192.168.11.1 192.168.12.1 ping不通 10.0.0.5 10.0.0.13 192.168.11.1 192.168.12.1

XiaoHui

2009-10-12 12:27

<blockquote>引用藤苇的贴子<hr size=1 noshadow>在以上的“在server中可ping通10.0.0.1 172.16.37.83 172.16.37.110 172.16.19.22 192.168.11.1 192.168.12.1 ping不通 10.0.0.5 10.0.0.13”修改一下 
应该是在server中可ping通10.0.0.1 172.16.37.83 172.16.37.110 172.16.19.22 192.168.11.1 192.168.12.1 ping不通 10.0.0.5 10.0.0.13 192.168.11.1 192.168.12.1<hr size=1 noshadow></blockquote>看了一下，配置很正常。有几个参数我没有用过，如client-config-dir 等。你可以参考我文中第四小节的样例文件，先用最简单的配置搭建起来再说。 
如果能连接但 Ping 不通，要看看是不是配置了 iptables。可参见第五节。

藤苇	2009-10-12 12:45

可以连接但ping不通， 
red hat Linux 中的网络配置要怎么设置呢？

藤苇	2009-10-12 13:51

Microsoft Windows 2000 [Version 5.00.2195] 
(C) 版权所有 1985-1998 Microsoft Corp. 
 
C:Documents and SettingsAdministrator>ipconfig/all 
 
Windows 2000 IP Configuration 
 
 Host Name . . . . . . . . . . . . : 2000serv-qh80ma 
 Primary DNS Suffix . . . . . . . : 
 Node Type . . . . . . . . . . . . : Hybrid 
 IP Routing Enabled. . . . . . . . : Yes 
 WINS Proxy Enabled. . . . . . . . : No 
 
Ethernet adapter 本地连接 3: 
 
 Connection-specific DNS Suffix . : 
 Description . . . . . . . . . . . : TAP-Win32 Adapter V8 
 Physical Address. . . . . . . . . : 00-FF-C2-18-82-DA 
 DHCP Enabled. . . . . . . . . . . : Yes 
 Autoconfiguration Enabled . . . . : Yes 
 IP Address. . . . . . . . . . . . : 10.0.0.5 
 Subnet Mask . . . . . . . . . . . : 255.255.255.252 
 Default Gateway . . . . . . . . . : 
 DHCP Server . . . . . . . . . . . : 10.0.0.6 
 DNS Servers . . . . . . . . . . . : 10.0.0.1 
 70.88.98.10 
 70.88.99.11 
 Lease Obtained. . . . . . . . . . : 2009年10月12日 20:43:19 
 Lease Expires . . . . . . . . . . : 2010年10月12日 20:43:19 
 
Ethernet adapter 本地连接 2: 
 
 Connection-specific DNS Suffix . : 
 Description . . . . . . . . . . . : VMware Accelerated AMD PCNet Adapter 
 
 Physical Address. . . . . . . . . : 00-0C-29-2E-84-B5 
 DHCP Enabled. . . . . . . . . . . : No 
 IP Address. . . . . . . . . . . . : 192.168.11.1 
 Subnet Mask . . . . . . . . . . . : 255.255.255.0 
 Default Gateway . . . . . . . . . : 172.16.37.110 
 DNS Servers . . . . . . . . . . . : 218.30.19.40 
 61.134.1.4 
 
Ethernet adapter 本地连接: 
 
 Connection-specific DNS Suffix . : 
 Description . . . . . . . . . . . : VMware Accelerated AMD PCNet Adapter 
 
 Physical Address. . . . . . . . . : 00-0C-29-2E-84-AB 
 DHCP Enabled. . . . . . . . . . . : No 
 IP Address. . . . . . . . . . . . : 172.16.37.110 
 Subnet Mask . . . . . . . . . . . : 255.255.0.0 
 Default Gateway . . . . . . . . . : 192.168.11.1 
 DNS Servers . . . . . . . . . . . : 218.30.19.40 
 61.134.1.4 
 
C:Documents and SettingsAdministrator>ping 10.0.0.1 
 
Pinging 10.0.0.1 with 32 bytes of data: 
 
Reply from 172.16.37.110: TTL expired in transit. 
Reply from 172.16.37.110: TTL expired in transit. 
Reply from 172.16.37.110: TTL expired in transit. 
Reply from 172.16.37.110: TTL expired in transit. 
 
Ping statistics for 10.0.0.1: 
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), 
Approximate round trip times in milli-seconds: 
Minimum = 0ms, Maximum = 0ms, Average = 0ms 
 
C:Documents and SettingsAdministrator>ping 10.0.0.13 
 
Pinging 10.0.0.13 with 32 bytes of data: 
 
Reply from 10.0.0.13: bytes=32 time<10ms TTL=128 
Reply from 10.0.0.13: bytes=32 time<10ms TTL=128 
Reply from 10.0.0.13: bytes=32 time<10ms TTL=128 
Reply from 10.0.0.13: bytes=32 time<10ms TTL=128 
 
Ping statistics for 10.0.0.13: 
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), 
Approximate round trip times in milli-seconds: 
Minimum = 0ms, Maximum = 0ms, Average = 0ms 
C:Documents and SettingsAdministrator>ping 172.16.37.83 
 
Pinging 172.16.37.83 with 32 bytes of data: 
 
Reply from 172.16.37.83: bytes=32 time<10ms TTL=64 
Reply from 172.16.37.83: bytes=32 time<10ms TTL=64 
Reply from 172.16.37.83: bytes=32 time<10ms TTL=64 
Reply from 172.16.37.83: bytes=32 time<10ms TTL=64 
 
Ping statistics for 172.16.37.83: 
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), 
Approximate round trip times in milli-seconds: 
Minimum = 0ms, Maximum = 0ms, Average = 0ms 
Default Gateway 那里没ip。 
麻烦你在给我看看哪个地方出错了！！！

藤苇	2009-10-12 13:55

Mon Oct 12 20:43:17 2009 OpenVPN 2.0.9 Win32-MinGW [SSL] [LZO] built on Oct 1 2006 
Mon Oct 12 20:43:17 2009 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. 
Mon Oct 12 20:43:17 2009 WARNING: No server certificate verification method has been enabled. See http://openvpn.net/howto.html#mitm for more info. 
Mon Oct 12 20:43:17 2009 LZO compression initialized 
Mon Oct 12 20:43:17 2009 Control Channel MTU parms [ L:1544 D:140 EF:40 EB:0 ET:0 EL:0 ] 
Mon Oct 12 20:43:17 2009 Data Channel MTU parms [ L:1544 D:1450 EF:44 EB:135 ET:0 EL:0 AF:3/1 ] 
Mon Oct 12 20:43:17 2009 Local Options hash (VER=V4): '69109d17' 
Mon Oct 12 20:43:17 2009 Expected Remote Options hash (VER=V4): 'c0103fa8' 
Mon Oct 12 20:43:17 2009 Attempting to establish TCP connection with 172.16.37.83:1194 
Mon Oct 12 20:43:17 2009 TCP connection established with 172.16.37.83:1194 
Mon Oct 12 20:43:17 2009 TCPv4_CLIENT link local: [undef] 
Mon Oct 12 20:43:17 2009 TCPv4_CLIENT link remote: 172.16.37.83:1194 
Mon Oct 12 20:43:17 2009 TLS: Initial packet from 172.16.37.83:1194, sid=f570158c 99bbcc93 
Mon Oct 12 20:43:17 2009 VERIFY OK: depth=1, /C=CN/ST=GD/L=SZ/O=xiaohui.com/emailAddress=your-email__at__xiaohui.com 
Mon Oct 12 20:43:17 2009 VERIFY OK: depth=0, /C=CN/ST=GD/O=xiaohui.com/CN=server/emailAddress=your-email__at__xiaohui.com 
Mon Oct 12 20:43:17 2009 Data Channel Encrypt: Cipher 'BF-CBC' initialized with 128 bit key 
Mon Oct 12 20:43:17 2009 Data Channel Encrypt: Using 160 bit message hash 'SHA1' for HMAC authentication 
Mon Oct 12 20:43:17 2009 Data Channel Decrypt: Cipher 'BF-CBC' initialized with 128 bit key 
Mon Oct 12 20:43:17 2009 Data Channel Decrypt: Using 160 bit message hash 'SHA1' for HMAC authentication 
Mon Oct 12 20:43:17 2009 Control Channel: TLSv1, cipher TLSv1/SSLv3 DHE-RSA-AES256-SHA, 1024 bit RSA 
Mon Oct 12 20:43:17 2009 [server] Peer Connection Initiated with 172.16.37.83:1194 
Mon Oct 12 20:43:18 2009 SENT CONTROL [server]: 'PUSH_REQUEST' (status=1) 
Mon Oct 12 20:43:18 2009 PUSH: Received control message: 'PUSH_REPLY,route 192.168.10.0 255.255.255.0,route 192.168.13.0 255.255.255.0,dhcp-option DNS 10.0.0.1,dhcp-option DNS 70.88.98.10,dhcp-option DNS 70.88.99.11,route 10.0.0.0 255.255.255.0,ping 10,ping-restart 120,ifconfig 10.0.0.5 10.0.0.6' 
Mon Oct 12 20:43:18 2009 OPTIONS IMPORT: timers and/or timeouts modified 
Mon Oct 12 20:43:18 2009 OPTIONS IMPORT: --ifconfig/up options modified 
Mon Oct 12 20:43:18 2009 OPTIONS IMPORT: route options modified 
Mon Oct 12 20:43:18 2009 OPTIONS IMPORT: --ip-win32 and/or --dhcp-option options modified 
Mon Oct 12 20:43:18 2009 TAP-WIN32 device [本地连接 3] opened: \.Global{C21882DA-A40E-4842-8C84-E8ABD2B2938D}.tap 
Mon Oct 12 20:43:18 2009 TAP-Win32 Driver Version 8.4 
Mon Oct 12 20:43:18 2009 TAP-Win32 MTU=1500 
Mon Oct 12 20:43:18 2009 Notified TAP-Win32 driver to set a DHCP IP/netmask of 10.0.0.5/255.255.255.252 on interface {C21882DA-A40E-4842-8C84-E8ABD2B2938D} [DHCP-serv: 10.0.0.6, lease-time: 31536000] 
Mon Oct 12 20:43:18 2009 NOTE: FlushIpNetTable failed on interface [2] {C21882DA-A40E-4842-8C84-E8ABD2B2938D} (status=1413) : 无效索引。 
Mon Oct 12 20:43:19 2009 TEST ROUTES: 3/3 succeeded len=3 ret=1 a=0 u/d=up 
Mon Oct 12 20:43:19 2009 route ADD 192.168.10.0 MASK 255.255.255.0 10.0.0.6 
Mon Oct 12 20:43:19 2009 Route addition via IPAPI succeeded 
Mon Oct 12 20:43:19 2009 route ADD 192.168.13.0 MASK 255.255.255.0 10.0.0.6 
Mon Oct 12 20:43:19 2009 Route addition via IPAPI succeeded 
Mon Oct 12 20:43:19 2009 route ADD 10.0.0.0 MASK 255.255.255.0 10.0.0.6 
Mon Oct 12 20:43:19 2009 Route addition via IPAPI succeeded 
Mon Oct 12 20:43:19 2009 Initialization Sequence Completed

王菲菲	2009-11-11 11:16

我的VPN应该属于已经配置好了，但是我启用VPN以后，我的客户端能打开大智慧，MSN，但是不能打开网页还有QQ，请问是为什么？ 
谢谢！

王菲菲	2009-11-11 11:20

我的VPN通了，但是客户端能启动MSN和大智慧，但是不能打开网页和QQ，请问我还应该做什么？ 
还有sysctl -w net.ipv4.ip_forward=0.改好后不能保存，不知是不是我的系统有问题。 
 
谢谢！

ysbaggio

2009-11-13 15:07

很有帮助，谢谢小辉了，现在正在研究用密码用户名登陆。

ysbaggio

2009-11-13 15:10

回54楼 
你可以修改# vi /etc/sysctl.conf文件。net.ipv4.ip_forward = 0将0 改成1

王菲菲	2009-11-19 04:36

ysbaggio 
您好！ 
您用密码用户名登陆，怎么做的？ 
我可以问问您吗？ 
我的QQ是1050626886，请加我。

david

2009-11-26 08:30

我启动vpn服务器的时候,/usr/local/sbin/openvpn --config /usr/local/etc/server.conf 
然后最后一行报错 
Cannot load certificate file /home/zhangke/openvpn-2.0.5/easy-rsa/keys/server.crt: error:0906D06C:PEM routines:PEM_read_bio:no start line: error:140AD009:SSL routines:SSL_CTX_use_certificate_file:PEM lib 
请问该如何处理,server.crt就是在那个目录下,却无法加载

XiaoHui

2009-11-26 11:37

<blockquote>引用 david 的贴子<hr size=1 noshadow>我启动vpn服务器的时候,/usr/local/sbin/openvpn --config /usr/local/etc/server.conf 
然后最后一行报错 
Cannot load certificate file /home/zhangke/openvpn-2.0.5/easy-rsa/keys/server.crt: error:0906D06C:PEM routines:PEM_read_bio:no start line: error:140AD009:SSL routines:SSL_CTX_use_certificate_file:PEM lib 
请问该如何处理,server.crt就是在那个目录下,却无法加载<hr size=1 noshadow></blockquote>证书没有做正确。按第六步重做一下。

zhaoke

2009-11-28 16:18

如Tun设备已编到内核中, 可用下面办法: 
cat /proc/net/dev|grep tun 
 
如果上面无任何显示, 说明你的内核不支持TUN/TAP设备, 可通过重新编译内添加.

高	2010-5-28 09:35

OpenVPN 2.1 requires '--script-security 2' or higher to call user-defined scripts or executables 
 
为什么我装完会报这个错，我也不知道这是为什么，请各位老大帮帮我呀！

rogerer

2010-6-21 06:56

请教一下！ 
我的安装及配置状态情况是这样的： 
 OpenVPN Server在内网，通过Cisco网关端口映射到VPN服务器上，OpenVPN启动正常！ 
 server.conf: server 192.168.5.0 255.255.255.0 
 两个客户端，一个在外网，一个在内网，连接状态正常。 
 我的网关上已经具备了从5网段跨到2、1的能力，同时网关设置为192.168.5.1. 
问题：两个客户端均能够ping 192.168.5.1,但是无法ping通192.168.5.*（除1而外）、192.168.2.1、192.168.1.1，即无法访问vpn网段的客户端和其他网段。 
这可能是什么原因呢？

XiaoHui

2010-6-21 11:34

<blockquote>引用 rogerer 的贴子<hr size=1 noshadow>请教一下！ 
我的安装及配置状态情况是这样的： 
 OpenVPN Server在内网，通过Cisco网关端口映射到VPN服务器上，OpenVPN启动正常！ 
 server.conf: server 192.168.5.0 255.255.255.0 
 两个客户端，一个在外网，一个在内网，连接状态正常。 
 我的网关上已经具备了从5网段跨到2、1的能力，同时网关设置为192.168.5.1. 
问题：两个客户端均能够ping 192.168.5.1,但是无法ping通192.168.5.*（除1而外）、192.168.2.1、192.168.1.1，即无法访问vpn网段的客户端和其他网段。 
这可能是什么原因呢？<hr size=1 noshadow></blockquote>应该是路由配置的问题。不过我没折腾过这块（我装openvpn只是为了翻墙，这些配置没折腾过）

123	2010-6-26 13:45

0 EL:0 AF:3/1 ] 
Sat Jun 26 20:42:53 2010 Local Options hash (VER=V4): '41690919' 
Sat Jun 26 20:42:53 2010 Expected Remote Options hash (VER=V4): '530fdded' 
Sat Jun 26 20:42:53 2010 UDPv4 link local (bound): [undef]:1194 
Sat Jun 26 20:42:53 2010 UDPv4 link remote: 61.164.41.148:1194 
Sat Jun 26 20:43:53 2010 TLS Error: TLS key negotiation failed to occur within 6 
0 seconds (check your network connectivity) 
Sat Jun 26 20:43:53 2010 TLS Error: TLS handshake failed 
Sat Jun 26 20:43:53 2010 TCP/UDP: Closing socket 
Sat Jun 26 20:43:53 2010 SIGUSR1[soft,tls-error] received, process restarting 
Sat Jun 26 20:43:53 2010 Restart pause, 2 second(s) 
Sat Jun 26 20:43:55 2010 IMPORTANT: OpenVPN's default port number is now 1194, b 
ased on an official port number assignment by IANA. OpenVPN 2.0-beta16 and earl 
ier used 5000 as the default port. 
Sat Jun 26 20:43:55 2010 Re-using SSL/TLS context 
Sat Jun 26 20:43:55 2010 LZO compression initialized 
Sat Jun 26 20:43:55 2010 Control Channel MTU parms [ L:1542 D:138 EF:38 EB:0 ET: 
0 EL:0 ] 
Sat Jun 26 20:43:55 2010 Data Channel MTU parms [ L:1542 D:1450 EF:42 EB:135 ET: 
0 EL:0 AF:3/1 ] 
Sat Jun 26 20:43:55 2010 Local Options hash (VER=V4): '41690919' 
Sat Jun 26 20:43:55 2010 Expected Remote Options hash (VER=V4): '530fdded' 
Sat Jun 26 20:43:55 2010 UDPv4 link local (bound): [undef]:1194 
Sat Jun 26 20:43:55 2010 UDPv4 link remote: 61.164.41.148:1194 
一直出现这个问题，但是服务器上的 UDP 1194端口是开放的，不知道为何，请教

wei	2010-8-3 13:46

每次重启完服务器都要重新做以下步骤，否则不能上网。为什么呢？ 
 
iptables -t nat -A POSTROUTING -s 10.8.8.0/24 -o eth0 -j SNAT --to-source x.x.x.x 
/etc/init.d/iptables save 
/etc/init.d/iptables restart 
不同的机器，-o eth0 参数可能不一样，具体可输入 ifconfig 查看，搞清 ip(70.8.7.6)所在的网卡号. 
 
 
同时, 需要将 ip forward 打开. 不要用 echo 1 > /proc/sys/net/ipv4/ip_forward 的方式, 这种方式重启后无效. 先查看一下: 
 
代码: 
 
 
sysctl -a | grep for 
#查看结果: 
net.ipv4.conf.tun0.mc_forwarding = 0 
net.ipv4.conf.tun0.forwarding = 1 
net.ipv4.conf.eth0.mc_forwarding = 0 
net.ipv4.conf.eth0.forwarding = 1 
net.ipv4.conf.lo.mc_forwarding = 0 
net.ipv4.conf.lo.forwarding = 1 
net.ipv4.conf.default.mc_forwarding = 0 
net.ipv4.conf.default.forwarding = 1 
net.ipv4.conf.all.mc_forwarding = 0 
net.ipv4.conf.all.forwarding = 1 
net.ipv4.ip_forward = 1 
如果你的主机上列数值不是为1, 则要将其改成1, 例如: 
 
代码: 
 
sysctl -w net.ipv4.ip_forward=1 
 
每次重启完，所有的 net.ipv4.xxxx 都 = 0 ,怎么解决呢？

查看完整版本: Linux 下 OpenVPN 安装和 Windows OpenVPN GUI 安装笔记