歡迎您光臨本站 註冊首頁

請大家幫幫忙,openvpn linux做伺服器 xp客戶端, 連不上報錯

←手機掃碼閱讀     火星人 @ 2014-03-04 , reply:0

請大家幫幫忙,openvpn linux做伺服器 xp客戶端, 連不上報錯

我的配置如下

linux伺服器 rhel6.3 裝openvpn 2.2.2
內網eth1: 網段192.168.11.0/24 , ip 192.168.11.1
外網eth0: 網段192.168.61.0/24 , ip 192.168.61.247
selinux關閉
iptables全部允許
iptables nat 如下:
iptables -t nat -A POSTROUTING -A POSTROUTING -s 192.168.11.0/24 -o eth0 -j SNAT --to-source 192.168.61.247
iptables -t nat -A POSTROUTING -A POSTROUTING -s 10.8.0.0/24 -o eth0 -j SNAT --to-source 192.168.61.247

openvpn伺服器端配置文件內容如下:

server.conf

# Which local IP address should OpenVPN
# listen on? (optional)
# 指定vpnopen伺服器所要監聽的IP
local 192.168.61.247

# 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 ca.crt
#cert server.crt
#key server.key  # This file should be kept secret
ca /etc/openvpn/userkey/ca.crt
cert /etc/openvpn/userkey/openvpnserver.crt
key /etc/openvpn/userkey/openvpnserver.key

# 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
dh /etc/openvpn/userkey/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

# 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

# Configure server mode for ethernet bridging
# using a DHCP-proxy, where clients talk
# to the OpenVPN server-side DHCP server
# to receive their IP address allocation
# and DNS server addresses.  You must first use
# your OS's bridging capability to bridge the TAP
# interface with the ethernet NIC interface.
# Note: this mode only works on clients (such as
# Windows), where the client-side TAP adapter is
# bound to a DHCP client.
;server-bridge

# 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.11.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
# or bridge the TUN/TAP interface to the internet
# in order for this to work properly).
;push "redirect-gateway def1 bypass-dhcp"

# Certain Windows-specific network settings
# can be pushed to clients, such as DNS
# or WINS server addresses.  CAVEAT:
# http://openvpn.net/faq.html#dhcpcaveats
# The addresses below refer to the public
# DNS servers provided by opendns.com.
;push "dhcp-option DNS 208.67.222.222"
;push "dhcp-option DNS 208.67.220.220"

# 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.
#可以讓客戶端之間相互訪問直接通過openvpn程序轉發
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.
# 允許多個客戶端使用同一個CA
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.
#允許最大的vpn併發連接數
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.
#定義vpn用戶和組
;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 /usr/local/logs/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         /usr/local/logs/openvpn.log
log-append  /usr/local/logs/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


客戶端配置文件如下:

client.conf

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

# 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:\\Program Files\\OpenVpn\\config\\ca.crt"
cert "C:\\Program Files\\OpenVpn\\config\\openvpnserver.crt"
key "C:\\Program Files\\OpenVpn\\config\\openvpnserver.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

#自己添加的
script-security 2
up ./update-resolv-conf
down ./update-resolv-conf



伺服器端openvpn日誌:
un Jan  6 15:07:03 2013 MULTI: multi_create_instance called
Sun Jan  6 15:07:03 2013 Re-using SSL/TLS context
Sun Jan  6 15:07:03 2013 LZO compression initialized
Sun Jan  6 15:07:03 2013 Control Channel MTU parms [ L:1544 D:140 EF:40 EB:0 ET:0 EL:0 ]
Sun Jan  6 15:07:03 2013 Data Channel MTU parms [ L:1544 D:1450 EF:44 EB:135 ET:0 EL:0 AF:3/1 ]
Sun Jan  6 15:07:03 2013 Local Options hash (VER=V4): 'c0103fa8'
Sun Jan  6 15:07:03 2013 Expected Remote Options hash (VER=V4): '69109d17'
Sun Jan  6 15:07:03 2013 TCP connection established with 192.168.61.170:1435
Sun Jan  6 15:07:03 2013 TCPv4_SERVER link local:
Sun Jan  6 15:07:03 2013 TCPv4_SERVER link remote: 192.168.61.170:1435
Sun Jan  6 15:07:03 2013 192.168.61.170:1435 TLS: Initial packet from 192.168.61.170:1435, sid=d0b94a9e 19fa94df
Sun Jan  6 15:07:03 2013 192.168.61.170:1435 Connection reset, restarting [-1]
Sun Jan  6 15:07:03 2013 192.168.61.170:1435 SIGUSR1 received, client-instance restarting
Sun Jan  6 15:07:03 2013 TCP/UDP: Closing socket
Sun Jan  6 15:07:08 2013 MULTI: multi_create_instance called
Sun Jan  6 15:07:08 2013 Re-using SSL/TLS context
Sun Jan  6 15:07:08 2013 LZO compression initialized
Sun Jan  6 15:07:08 2013 Control Channel MTU parms [ L:1544 D:140 EF:40 EB:0 ET:0 EL:0 ]
Sun Jan  6 15:07:08 2013 Data Channel MTU parms [ L:1544 D:1450 EF:44 EB:135 ET:0 EL:0 AF:3/1 ]
Sun Jan  6 15:07:08 2013 Local Options hash (VER=V4): 'c0103fa8'
Sun Jan  6 15:07:08 2013 Expected Remote Options hash (VER=V4): '69109d17'
Sun Jan  6 15:07:08 2013 TCP connection established with 192.168.61.170:1436
Sun Jan  6 15:07:08 2013 TCPv4_SERVER link local:
Sun Jan  6 15:07:08 2013 TCPv4_SERVER link remote: 192.168.61.170:1436
Sun Jan  6 15:07:08 2013 192.168.61.170:1436 TLS: Initial packet from 192.168.61.170:1436, sid=e76deb23 bd8f8fe1
Sun Jan  6 15:07:08 2013 192.168.61.170:1436 Connection reset, restarting [-1]
Sun Jan  6 15:07:08 2013 192.168.61.170:1436 SIGUSR1 received, client-instance restarting
Sun Jan  6 15:07:08 2013 TCP/UDP: Closing socket
Sun Jan  6 15:07:13 2013 MULTI: multi_create_instance called
Sun Jan  6 15:07:13 2013 Re-using SSL/TLS context
Sun Jan  6 15:07:13 2013 LZO compression initialized
Sun Jan  6 15:07:13 2013 Control Channel MTU parms [ L:1544 D:140 EF:40 EB:0 ET:0 EL:0 ]
Sun Jan  6 15:07:13 2013 Data Channel MTU parms [ L:1544 D:1450 EF:44 EB:135 ET:0 EL:0 AF:3/1 ]
Sun Jan  6 15:07:13 2013 Local Options hash (VER=V4): 'c0103fa8'
Sun Jan  6 15:07:13 2013 Expected Remote Options hash (VER=V4): '69109d17'
Sun Jan  6 15:07:13 2013 TCP connection established with 192.168.61.170:1437
Sun Jan  6 15:07:13 2013 TCPv4_SERVER link local:
Sun Jan  6 15:07:13 2013 TCPv4_SERVER link remote: 192.168.61.170:1437
Sun Jan  6 15:07:13 2013 192.168.61.170:1437 TLS: Initial packet from 192.168.61.170:1437, sid=80b4abbb d7cac629
Sun Jan  6 15:07:14 2013 192.168.61.170:1437 Connection reset, restarting [-1]
Sun Jan  6 15:07:14 2013 192.168.61.170:1437 SIGUSR1 received, client-instance restarting
Sun Jan  6 15:07:14 2013 TCP/UDP: Closing socket


xp客戶端日誌文件如下:

Sun Jan 06 15:08:05 2013 OpenVPN 2.2.2 Win32-MSVC++ built on Dec 15 2011
Sun Jan 06 15:08:05 2013 NOTE: OpenVPN 2.1 requires '--script-security 2' or higher to call user-defined scripts or executables
Sun Jan 06 15:08:05 2013 LZO compression initialized
Sun Jan 06 15:08:05 2013 Control Channel MTU parms [ L:1544 D:140 EF:40 EB:0 ET:0 EL:0 ]
Sun Jan 06 15:08:05 2013 Socket Buffers: R= S=
Sun Jan 06 15:08:05 2013 Data Channel MTU parms [ L:1544 D:1450 EF:44 EB:135 ET:0 EL:0 AF:3/1 ]
Sun Jan 06 15:08:05 2013 Local Options hash (VER=V4): '69109d17'
Sun Jan 06 15:08:05 2013 Expected Remote Options hash (VER=V4): 'c0103fa8'
Sun Jan 06 15:08:05 2013 Attempting to establish TCP connection with 192.168.61.247:1194
Sun Jan 06 15:08:05 2013 TCP connection established with 192.168.61.247:1194
Sun Jan 06 15:08:05 2013 TCPv4_CLIENT link local:
Sun Jan 06 15:08:05 2013 TCPv4_CLIENT link remote: 192.168.61.247:1194
Sun Jan 06 15:08:05 2013 TLS: Initial packet from 192.168.61.247:1194, sid=51e27557 5630f43d
Sun Jan 06 15:08:06 2013 VERIFY ERROR: depth=1, error=self signed certificate in certificate chain: /C=cn/ST=tianjin/L=tianjin/O=summerx/OU=it/CN=myopenvpn/name=summer/[email protected]
Sun Jan 06 15:08:06 2013 TLS_ERROR: BIO read tls_read_plaintext error: error:14090086:SSL routines:SSL3_GET_SERVER_CERTIFICATE:certificate verify failed
Sun Jan 06 15:08:06 2013 TLS Error: TLS object -> incoming plaintext read error
Sun Jan 06 15:08:06 2013 TLS Error: TLS handshake failed
Sun Jan 06 15:08:06 2013 Fatal TLS error (check_tls_errors_co), restarting
Sun Jan 06 15:08:06 2013 TCP/UDP: Closing socket
Sun Jan 06 15:08:06 2013 SIGUSR1 received, process restarting
Sun Jan 06 15:08:06 2013 Restart pause, 5 second(s)
《解決方案》

自己看看是不是客戶端證書路徑寫錯了
《解決方案》

回復 2# 刺頭21


我的客戶端證書路徑是,檢查過了,沒問題的...

ca "C:\\Program Files\\OpenVpn\\config\\ca.crt"
cert "C:\\Program Files\\OpenVpn\\config\\openvpnserver.crt"
key "C:\\Program Files\\OpenVpn\\config\\openvpnserver.key"
《解決方案》

回復 3# owenbush


client

dev tun
proto udp

remote serverip 1494
resolv-retry infinite

route-method exe

route-delay 2

nobind

ca ca.crt
cert client.crt
key client.key
tls-auth ta.key 1

comp-lzo

verb 3
mute 20

這是我的客戶端配置文件
port 1494
proto udp
dev tun

ca /etc/openvpn/keys/ca.crt
cert /etc/openvpn/keys/server.crt
key /etc/openvpn/keys/server.key
dh /etc/openvpn/keys/dh1024.pem
tls-auth /etc/openvpn/keys/ta.key 0

server 10.1.0.0 255.255.255.0

push "route 10.1.0.0 255.255.255.0"
push "dhcp-option DNS 202.106.0.20" #客戶端所獲得的DNS

push "redirect-gateway"

client-to-client


comp-lzo

keepalive 10 120

user nobody
group nobody

status openvpn-status.log

persist-key
persist-tun

verb 3

這是我的伺服器端的配置文件
你自己看看,對比一下。

[火星人 ] 請大家幫幫忙,openvpn linux做伺服器 xp客戶端, 連不上報錯已經有823次圍觀

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