2024年1月28日发(作者：)

Windows平台下实现搭建OpenVpn虚拟专用网络

一、环境准备

1. 操作系统：适用于Windows平台

2. 公网地址：:端口

3. 内网地址：

4. 路由器做好端口影射

5. 单网卡

6.

以下利用公司提前准备好的环境来在Windows平台下实现OpenVpn虚拟专用网服务器的搭建；公司准备好的环境条件有：

A. 操作系统：Windows 2008 Server R2（32位）

B. 公网地址：59.108.107.42

C. 内网地址：168.168.168.170

D. 影射端口：8081和8082（端口使用一个即可，以下配置中使用的是8081）

E. 单网卡

二、服务器端安装部署

1.安装

图1

图2

图3

图4

图5

图6

安装完毕后，在网络连接中会出现一个新的"本地连接2"，将名字改外"vpn"，如下图：

图7

2.服务器端OpenVpn详细配置

A. 修改

在C:Program FilesOpenVPNeasy-rsa目录下用写字板打开。（不建议使用记事本打开，记事本打开有可能会破坏此文档的格式）

如下：

set KEY_COUNTRY=CN

set KEY_PROVINCE=BJ

set KEY_CITY=BJ

set KEY_ORG=LHJ

set KEY_EMAIL=381364654@

B. 命令行配置

开始-运行-输入cmd

(1) cd C:Program FilesOpenVPNeasy-rsa

图1

(2) init-config

图2

(3) vars ------------此步骤是必须的，以后的各个证书生成之前都需要进行初始化

图3

(4) clean-all

图4

(5) 生成根证书CA

vars

图5

build-ca

图6

(6) 生成文件，server使用TLS必须使用的一个文件。

vars

图7

build-dh

图8

(7) 生成服务器端证书

vars

图9

build-key-server server01

图10

图11

到此server端使用的证书生成完毕。

(8) 生成客户端证书

vars

图12

build-key client01

图13

图14

(9) 生成文件

vars

图15

openvpn --genkey --secret keys/

图16

到此为止根ca、客户端、服务器端所需要的证书和密钥文件就已经全部准备就绪，接下来

要做的是配置服务器端文件和客户端文件。

C. 服务器端文件配置

(1) 服务器端的配置文件在C:Program FilesOpenVPNsample-config文件夹下：

内容如下（备注：以下的批注部分为当处的说明，严格按照这种格式，一处的格式不对，在启动openvpn服务器时都有可能连接不上）

#################################################

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

# #

# Comments are preceded with '#' or ';' #

#################################################

# Which local IP address should OpenVPN

# listen on? (optional)

local 168.168.168.170

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

# 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

cert

key # This file should be kept secret

# Diffie hellman parameters.

# Generate your own with:

# openssl dhparam -out 1024

# Substitute 2048 for 1024 if you are using

# 2048 bit keys.

dh

# 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

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

#route-method exe

#route-delay 2

# 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

;push "route 168.168.168.0 255.255.255.0"

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

# /#dhcpcaveats

# The addresses below refer to the public

# DNS servers provided by .

push "dhcp-option DNS 59.108.107.42"

push "dhcp-option DNS 202.106.0.20"

# 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

#

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

# 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

;log-append

# 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

(2) 把配置文件复制到C:Program FilesOpenVPNconfig目录下，把C:Program FilesOpenVPNeasy-rsakeys目录下的、、、、、、 复制到C:Program FilesOpenVPNconfig目录下。

(3) regedit修改注册表

HKEY_LOCAL_MACHINESYSTEMCurrentControlSetServicesTcpipParameters

将IPEnableRouter改为1

(4) 关闭防火墙或将8081端口加入到防火墙允许通过的端口中去

C. OpenVpn服务器端启动成功

到此server端的配置完成，可以启动server了，以下为启动连接成功的标志

图17

3.客户端OpenVpn详细配置

A. 安装

安装同服务器端安装图解一样，此处不再做解释。

B. 客户端文件配置

(1) 客户端的配置文件也在C:Program FilesOpenVPNsample-config目录

内容示例如下（备注：以下的批注部分为当处的说明，严格按照这种格式，一处的格式不对，在启动openvpn服务器时都有可能连接不上）

##############################################

# 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 59.108.107.42 8081

;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

cert

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:

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

(2) 把配置文件复制到客户端机器的C:Program FilesOpenVPNconfig目录下，并且把服务器C:Program FilesOpenVPNeasy-rsakeys目录下的、、、、、 文件一起复制到客户端机器的C:Program FilesOpenVPNconfig 目录下（以上文件由服务器端生成，客户端需要向服务器端索取这七个文件）

(3) 关闭防火墙或将8081端口加入到防火墙允许通过的端口中去

C. OpenVpn客户端启动成功

到此client端的配置完成，可以启动client了，以下为启动连接成功的标志

D. 远程OpenVpn服务器互ping检查网络

(1) 远程到服务器端虚拟IP：10.8.0.1

(2) 在服务器端ping公司局域网：

(3) 在服务器端访问公司共享文件:RWCD

(4) 客户端处ping本端的局域网