openpvn2.4配置文件说明

opevpn2.4配置文件说明

 

#################################################
# 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      // 注：默认监听在upd的1194端口
# number for each one.  You will need to
# open up this port on your firewall.
port 1194                                       

# TCP or UDP server?                            // 选择tcp还是upd，生产环境可以使用tcp，考虑到要传文件，因为tcp是可靠的，但用udp应该会快点
;proto tcp                                      // 默认是udp
proto udp

# "dev tun" will create a routed IP tunnel,      // 选择设备驱动的模式，根据需求选择
# "dev tap" will create an ethernet tunnel.      // dev tun 将创建一个路由隧道(推荐)
# Use "dev tap0" if you are ethernet bridging    // dev tap 将创建一个网络隧道
# 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                                   // linux系统不需要考虑这个选项

# 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.            // 指定ca、cert、key，可以是绝对路径和相对路径
# 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

# Diffie hellman parameters.                            // 指定Diffie hellman文件路径
# Generate your own with:
#   openssl dhparam -out dh2048.pem 2048
dh dh2048.pem

# Network topology
# Should be subnet (addressing via IP)
# unless Windows clients v2.0.9 and lower have to
# be supported (then net30, i.e. a /30 per client)
# Defaults to net30 (not recommended)
;topology subnet

# Configure server mode and supply a VPN subnet        // 配置vpn客户端使用的网段，会dhcp自动分配
# 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                           // 维持一个客户端和virtual IP的对应表，以方便客户端重新
                                                        // 连接可以获得同样的IP

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

# 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          // 该语句会通知客户端把默认网关设为服务器，所有的的流量会经过vpn服务端，这种适合做proxy
# 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          // 推送给客户端的dns
# 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.
;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             // 2.4版本客户端/服务端默认选择AES-256-GCM模式
# the client config file as well.                // 注：AES-256-GCM模式应该兼容其它的模式
# Note that v2.4 client/server will automatically
# negotiate AES-256-GCM in TLS mode.
# See also the ncp-cipher option in the manpage
cipher AES-256-CBC

# Enable compression on the VPN link and push the    // 启用vpn链路压缩并且推送这个选项给客户端，仅2.4或以上版本支持
# option to the client (v2.4+ only, for earlier
# versions see below)
;compress lz4-v2
;push "compress lz4-v2"

# For compression compatible with older clients use comp-lzo   // 是否启用lzo压缩, 
# 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      // 启动openvpn的用户和组，比较好的建议是用普通用户启动openvpn
# daemon's privileges after initialization.   // 比如，默认使用nobody用户启动
#
# You can uncomment this out on               // windows系统不考虑(不配置)这个选项
# 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        // 客户端连接状态日志，可以看到客户端什么时候连接、ip等信息
# current connections, truncated
# and rewritten every minute.
status openvpn-status.log

# By default, log messages will go to the syslog (or            // 使用log选项将截断日志文件，相当于刷新日志，日志文件中的状态信息将会被更新
# on Windows, if running as a service, they will go to          // log-append选项将追加日志
# 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

# Notify the client that when the server restarts so it   // 服务端通知客户端何时重启，以便客户端重连
# can automatically reconnect.
explicit-exit-notify 1