ToB企服应用市场:ToB评测及商务社交产业平台

标题: openvpn组网技术原理及设置过程(centos服务器/安卓客户端/linux客户端) [打印本页]

作者: 不到断气不罢休    时间: 2024-6-20 20:43
标题: openvpn组网技术原理及设置过程(centos服务器/安卓客户端/linux客户端)
     最近研究了一段时间的openvpn组网技术,也试着搭建了一个openvpn环境,大概明白了其中利用的一些技术原理,还是记载一下。本篇文章对专业搞网络的人大概用处不大,但是对于初次接触这些技术(好比vpn,代理技术,加密隧道,防火墙,路由,局域网组网)的人还是有肯定价值的,便于理清整个vpn组网技术的脉络,也可以在碰到题目的时候自己排查。
      openvpn是浩繁vpn种类的一种,是一个开源的产品,也是应用最广泛的一种vpn。支持的平台许多,我们常用的系统平台linux,window,安卓都支持。我搭建的openvpn服务端是运行在centos上,客户端是运行在安卓手机上的。实在不管运行在哪个平台,设置基本都是一样的。openvpn还有一个重要的功能是可以利用UDP协议传输数据,这相对于利用TCP传输数据的vpn,速率要快许多。
     openvpn能构建一个虚拟专用网络(VPN),许多人大概不是很了解这句话包含的内容。一个是“虚拟的”,说的是这个网络内的各个主机在地理位置上,大概不是在相邻的地域,大概在地球的两端,大概横跨了整个互联网。如许看起来,这个网络就不像一个局域网,但是在逻辑上,是真正意义上的一个局域网。”虚拟“实在重点是指数据传输的通道上,这个通道是虚拟的,主机的网卡也是虚拟的,不是真实的网卡。还有一个形容词”专用“,这个就是指能和外部网络隔绝起来,为了不被外部网络影响,数据不被窥伺盗取篡改,VPN网络中两个主机之间的通信数据都会颠末加密,如许的加密通信通道我们就称之为加密隧道。而且任何一台主机想要加入这个网络,都需要颠末严格的认证授权。
      VPN的数据包是在TCP/UDP数据包的底子上做了一层封装,这个封装的数据里就是VPN网络里面的局域网数据包,其中和正常的TCP/UDP数据包一样,也有源ip端口,目的ip端口。当然,这些局域网的数据包信息,只有解密了才能看到,外部即使截获了这个数据包,也解密不了其中的数据。这个数据包(大概是在互联网上)颠末了漫长的传输后,到达最终目的地后才会能被精确的解密,递交给上层应用。
      安装VPN客户端的主机上,当认证授权乐成后加入VPN网络,都会新增一个虚拟网卡,作为VPN网络通信的专用网卡,VPN服务器启动乐成后也一样虚拟出这个专用网卡。网卡的名称一般为tun0,就像下面的:

一、openvpn数据收发工作原理      

其中openvpn收发数据处理过程,我大抵画了一下,如下图:

        上面的VPN主机1就相称于openvpn的客户端,VPN主机2就相称于openvpn的服务器。其中eth0网卡是真实的网卡,对外连接外部网络,tun0是openvpn的虚拟出来的网卡,专门处理openvpn的数据。
       数据发送历程,想要给VPN网络中的其他节点发送数据,就利用对端局域网的ip来发送,也就是10.8.0.2这个ip。这个数据发送历程发送的数据,先交给内核的协议栈举行TCP/IP数据包的封装,这个TCP/IP数据包颠末当地路由后,当地的路由会直接交给tun0网卡(留意,此处还有一个重要的角色当地路由表),因为tun0网卡是openvpn这个历程虚拟出来的网卡,数据包交给tun0网卡后都会颠末openvpn这个历程的处理,openvpn会把收到的数据用自己的openvpn协议举行封装,然后加密成密文(这个加密过程应该是利用开源的ssl或者tls协议),加密完成后就发送给对端(数据吸收端)的openvpn历程。至于是怎么知道吸收端的openvpn历程的ip端口的,是在开始的时候openvpn客户端和服务端的一些列认证完成后,这个连接才能创建乐成的。发送端的openvpn举行把密文数据发出后,也会颠末内核的协议栈,举行TCP/IP的协议组包,然后再次颠末当地的路由表举行路由,路由表会把这个TCP/IP包交给外网出口网卡eth0发送出去。此时,整个数据的发送过程结束。
       VPN主机1从网卡eth0发送的TCP/IP数据包,颠末漫长的路由和转发,最终到达目的地,也就是,数据包通过VPN主机2的外网网卡eth0进入,内核协议栈解析这个TCP/IP数据包,知道这个数据包的目的ip端标语(2.2.2.2:1194),于是交给了openvpn历程(openvpn吸收历程)处理。openvpn历程对吸收到的数据先举行解密,得到openvpn协议数据,然后把VPN主机1数据发送历程发送的数据,转发到tun0网卡(这个转发的处理过程不是很清晰,究竟是重新组TCP/IP包还是原样把发送历程颠末tun0网卡后的TCP/IP包转发,我们不去深究,最终的到达VPN主机2的tun0网卡时都是一样的),数据到达tun0网卡后也会颠末内核去分发,内核协议栈把TCP/IP的包头都去掉,只把数据部分交给数据吸收历程。
     至此,数据收发的过程完成。
二、openvpn认证(加密隧道创建)

     上面的章节,介绍了openvpn网络中两个主机的数据收发过程,但是两个主机在能举行数据收发前,要先创建数据传输通道,这个就是加入openvpn网络的认证过程。数据通道的创建的过程,也是openvpn客户端和服务端举行协商的过程。openvpn采用ssl协议通信,既然采用ssl,那么就会有证书验证,协商对称加密密钥的过程。需要天生ca证书,服务端证书客户端证书等。具体的原理这里不细说,可以自行去谷歌。openvpn客户端认证通过后就和服务端创建了一条加密隧道,也就是一条安全的数据通道。
三、路由表在openvpn组网中的作用

          在第一部分介绍原理的时候,说发往数据吸收端ip10.8.0.2的数据包,都转发给tun0网卡处理,这是怎么做到的?答案就是路由表。在openvpn客户端和服务器之间认证通过后,openvpn客户端就会修改我们当地的路由表,添加一条路由记载,指示当地路由收到发往ip10.8.0.2的数据包,都交给tun0网卡转发。
        除了上面提到的第一个作用之外,在openvpn工作的过程中,路由表还有一个作用,就是把当地全部的数据包(流量)都路由到openvpn服务端的机器上,也就是把openvpn服务端的机器,作为当地机器的网关。把openvpn服务端作为网关的一个作用是,可以让openvpn局域网中的节点,通过openvpn服务端机器访问互联网,作为外网的出口。就类似我们寻常用路由器上网的网络拓扑结构,路由器(openvpn服务端所在机器)作为NAT设备,代理接入互联网。真正起到NAT作用的是服务端所在主机的防火墙历程,而不是openvpn服务端历程。linux下的防火墙也是一门高深的技术,功能十分强盛。
       openvpn客户端认证乐成后,路由表的信息类似以下的截图:

tun0网卡的信息如下:

  即openvpn客户端认证接入openvpn服务器后,分配到的局域网ip是10.8.0.6,服务器本身的局域网ip是10.8.0.5,这是一个点对点的网络。红线圈住的那几条就是openvpn新增的路由规则,其中第一条就是把openvpn服务端作为网关的路由规则。
四、openvpn安装设置过程

1、服务器端(centos)

        我的服务端是部署在centos操纵系统上的,安装openvpn就很简单了,直接用yum命令安装:
       yum install -y openvpn
       linux下安装的openvpn,客户端和服务端是一起的,运行的是服务端还是客户端,重要取决于设置文件。这个跟stunnel类似。
      安装完成后,会有同时安装一些设置样例文件,用下面的命令举行查找:
      find / -name "*openvpn*"

一般是/usr/share/doc/openvpn-xxx目次下,xxx是版本号。其中我们需要的几个文件就在sample/sample-config-files目次下,如下图:

安装服务端的时候,我们复制firewall.sh、openvpn-shutdown.sh、openvpn-startup.sh、server.conf这几个文件到一个单独的目次下,好比/root/openvpn-server,假如你能看懂这几个设置文件里面的信息,就可以对应着修改一下,以符合你的部署要求。
下面是我修改以后的设置:
openvpn-startup.sh文件:
  1. #!/bin/sh
  2. # A sample OpenVPN startup script
  3. # for Linux.
  4. # openvpn config file directory
  5. # 此处获取当前目录路径
  6. dir=`pwd`
  7. # load the firewall
  8. # 调用firewall.sh脚本配置防火墙
  9. $dir/firewall.sh
  10. #iptables -t nat -A POSTROUTING -o eth0 -j MASQUERADE
  11. # load TUN/TAP kernel module
  12. modprobe tun
  13. # enable IP forwarding 打开ipv4的转发功能
  14. echo 1 > /proc/sys/net/ipv4/ip_forward
  15. # Invoke openvpn for each VPN tunnel
  16. # in daemon mode.  Alternatively,
  17. # you could remove "--daemon" from
  18. # the command line and add "daemon"
  19. # to the config file.
  20. #
  21. # Each tunnel should run on a separate
  22. # UDP port.  Use the "port" option
  23. # to control this.  Like all of
  24. # OpenVPN's options, you can
  25. # specify "--port 8000" on the command
  26. # line or "port 8000" in the config
  27. # file.
  28. # 启动openvpn服务端
  29. openvpn --cd $dir --daemon --config server.conf
复制代码
firewall.sh文件:
  1. #!/bin/sh
  2. # A Sample OpenVPN-aware firewall.
  3. # eth0 is connected to the internet.
  4. # eth1 is connected to a private subnet.
  5. # Change this subnet to correspond to your private
  6. # ethernet subnet.  Home will use HOME_NET/24 and
  7. # Office will use OFFICE_NET/24.
  8. PRIVATE=10.8.0.0/24
  9. # Loopback address
  10. LOOP=127.0.0.1
  11. # Delete old iptables rules
  12. # and temporarily block all traffic.
  13. iptables -P OUTPUT DROP
  14. iptables -P INPUT DROP
  15. iptables -P FORWARD DROP
  16. # 这条是删除原有的防火墙规则,删除的是filter表的规则,filter表的规则部分是作用在INPUT链上的
  17. iptables -F
  18. # Set default policies 重新设置链的默认策略
  19. iptables -P OUTPUT ACCEPT
  20. iptables -P INPUT DROP
  21. iptables -P FORWARD DROP
  22. # Prevent external packets from using loopback addr 这里是避免外部发来的数据包的源地址和目的
  23. # 地址是回环地址,从而错误的递交给本地的进程。这应该是避免攻击的一些手段
  24. iptables -A INPUT -i eth0 -s $LOOP -j DROP
  25. iptables -A FORWARD -i eth0 -s $LOOP -j DROP
  26. iptables -A INPUT -i eth0 -d $LOOP -j DROP
  27. iptables -A FORWARD -i eth0 -d $LOOP -j DROP
  28. # Anything coming from the Internet should have a real Internet address
  29. # 这里是对一些有可能是错误发送的包进行丢弃
  30. iptables -A FORWARD -i eth0 -s 192.168.0.0/16 -j DROP
  31. iptables -A FORWARD -i eth0 -s 172.16.0.0/12 -j DROP
  32. iptables -A FORWARD -i eth0 -s 10.0.0.0/8 -j DROP
  33. iptables -A INPUT -i eth0 -s 192.168.0.0/16 -j DROP
  34. iptables -A INPUT -i eth0 -s 172.16.0.0/12 -j DROP
  35. iptables -A INPUT -i eth0 -s 10.0.0.0/8 -j DROP
  36. # Block outgoing NetBios (if you have windows machines running
  37. # on the private subnet).  This will not affect any NetBios
  38. # traffic that flows over the VPN tunnel, but it will stop
  39. # local windows machines from broadcasting themselves to
  40. # the internet.
  41. # 这里是对windows的一些服务端口进行屏蔽,我们是linux不用管
  42. iptables -A FORWARD -p tcp --sport 137:139 -o eth0 -j DROP
  43. iptables -A FORWARD -p udp --sport 137:139 -o eth0 -j DROP
  44. iptables -A OUTPUT -p tcp --sport 137:139 -o eth0 -j DROP
  45. iptables -A OUTPUT -p udp --sport 137:139 -o eth0 -j DROP
  46. # Check source address validity on packets going out to internet
  47. #iptables -A FORWARD -s ! $PRIVATE -i eth1 -j DROP
  48. #iptables -A FORWARD -m iprange ! --src-range 10.0.0.0-10.0.0.255 -i eth1 -j DROP
  49. # Allow local loopback 这里是对回环地址放行
  50. iptables -A INPUT -s $LOOP -j ACCEPT
  51. iptables -A INPUT -d $LOOP -j ACCEPT
  52. # Allow incoming pings (can be disabled) 这里是对icmp协议放行,也就是能响应ping命令
  53. iptables -A INPUT -p icmp --icmp-type echo-request -j ACCEPT
  54. # Allow services such as www and ssh (can be disabled) 这里是对常用的服务端口入栈放行
  55. iptables -A INPUT -p tcp --dport http -j ACCEPT
  56. iptables -A INPUT -p tcp --dport ssh -j ACCEPT
  57. iptables -A INPUT -p tcp --dport 6679 -j ACCEPT
  58. # Allow incoming OpenVPN packets
  59. # Duplicate the line below for each
  60. # OpenVPN tunnel, changing --dport n
  61. # to match the OpenVPN UDP port.
  62. #
  63. # In OpenVPN, the port number is
  64. # controlled by the --port n option.
  65. # If you put this option in the config
  66. # file, you can remove the leading '--'
  67. #
  68. # If you taking the stateful firewall
  69. # approach (see the OpenVPN HOWTO),
  70. # then comment out the line below.
  71. # 这里是自己想要放行的端口和协议数据,有其他端口可以自行添加
  72. iptables -A INPUT -p udp --dport 1194 -j ACCEPT
  73. iptables -A INPUT -p udp --dport 9981 -j ACCEPT
  74. iptables -A INPUT -p tcp --dport 9981 -j ACCEPT
  75. iptables -A INPUT -p tcp --dport 6379 -j ACCEPT
  76. iptables -A INPUT -p udp --dport 6379 -j ACCEPT
  77. iptables -A INPUT -p udp --dport 6680 -j ACCEPT
  78. iptables -A INPUT -p tcp --dport 6680 -j ACCEPT
  79. iptables -A INPUT -p tcp --dport 1723 -j ACCEPT
  80. # Allow packets from TUN/TAP devices.
  81. # When OpenVPN is run in a secure mode,
  82. # it will authenticate packets prior
  83. # to their arriving on a tun or tap
  84. # interface.  Therefore, it is not
  85. # necessary to add any filters here,
  86. # unless you want to restrict the
  87. # type of packets which can flow over
  88. # the tunnel.
  89. # 这里主要是对tun+网卡和tap+网卡的入栈和转发数据包放行,+号应该表示的是一个通配符
  90. iptables -A INPUT -i tun+ -j ACCEPT
  91. iptables -A FORWARD -i tun+ -j ACCEPT
  92. iptables -A INPUT -i tap+ -j ACCEPT
  93. iptables -A FORWARD -i tap+ -j ACCEPT
  94. # Allow packets from private subnets 这里是对eth1网卡的入栈和转发数据包放行
  95. iptables -A INPUT -i eth1 -j ACCEPT
  96. iptables -A FORWARD -i eth1 -j ACCEPT
  97. # Keep state of connections from local machine and private subnets
  98. # 这里是放行状态为NEW的出栈数据包
  99. iptables -A OUTPUT -m state --state NEW -o eth0 -j ACCEPT
  100. # 这里放行已经建立连接和关联的入栈数据包
  101. iptables -A INPUT -m state --state ESTABLISHED,RELATED -j ACCEPT
  102. # 这里放行需要转发的包,有这两条,本机才能作为NAT代理客户端访问互联网
  103. iptables -A FORWARD -m state --state NEW -o eth0 -j ACCEPT
  104. iptables -A FORWARD -m state --state ESTABLISHED,RELATED -j ACCEPT
  105. # Masquerade local subnet
  106. # 对于需要通过openvpn服务端访问外网的客户端节点,这个防火墙配置是必需的,也是最重要的配置
  107. # 这个防火墙的配置是将路由后的源IP地址是10.8.0.0/24,输出网卡是eth0的数据包的源ip地址进行修改,改成本机的ip地址,这样响应数据包才能正确的给我们转发回来
  108. iptables -t nat -A POSTROUTING -s $PRIVATE -o eth0 -j MASQUERADE
复制代码
这个防火墙设置,比较磨练技术,新手一般看不懂,除非对防火墙的原理很熟悉,假如要介绍完全这些防火墙设置,需要另一篇长篇大论 。这个设置是根据样例文件修改后的,大体还是不变,只做了小部分的修改。这个官方给的样例,是对防火墙规则做了细密的设计。假如你对安全性要求不高,可以将防火墙的INPUT、FORWARD、OUTPUT链的策略都改成ACCEPT,那么就只需要少许的防火墙设置就能到达目的,好比如下的设置(没有实际调试过,不保证精确性):
  1. PRIVATE=10.8.0.0/24
  2. # 清空原有INPUT链的防火墙规则
  3. iptables -F
  4. # 放行所有输出包
  5. iptables -P OUTPUT ACCEPT
  6. # 放行所有输入包
  7. iptables -P INPUT ACCEPT
  8. # 放行所有需要转发的包
  9. iptables -P FORWARD ACCEPT
  10. # 对于需要通过openvpn服务端访问外网的客户端节点,这个防火墙配置是必需的,也是最重要的配置
  11. # 这个防火墙的配置是将路由后的源IP地址是10.8.0.0/24,输出网卡是eth0的数据包的源ip地址进行修改,改成本机的ip地址,这样响应数据包才能正确的给我们转发回来
  12. iptables -t nat -A POSTROUTING -s $PRIVATE -o eth0 -j MASQUERADE
复制代码
server.conf文件:
  1. #################################################
  2. # Sample OpenVPN 2.0 config file for            #
  3. # multi-client server.                          #
  4. #                                               #
  5. # This file is for the server side              #
  6. # of a many-clients <-> one-server              #
  7. # OpenVPN configuration.                        #
  8. #                                               #
  9. # OpenVPN also supports                         #
  10. # single-machine <-> single-machine             #
  11. # configurations (See the Examples page         #
  12. # on the web site for more info).               #
  13. #                                               #
  14. # This config should work on Windows            #
  15. # or Linux/BSD systems.  Remember on            #
  16. # Windows to quote pathnames and use            #
  17. # double backslashes, e.g.:                     #
  18. # "C:\\Program Files\\OpenVPN\\config\\foo.key" #
  19. #                                               #
  20. # Comments are preceded with '#' or ';'         #
  21. #################################################
  22. # Which local IP address should OpenVPN
  23. # listen on? (optional)
  24. ;local a.b.c.d
  25. # Which TCP/UDP port should OpenVPN listen on?
  26. # If you want to run multiple OpenVPN instances
  27. # on the same machine, use a different port
  28. # number for each one.  You will need to
  29. # open up this port on your firewall.
  30. # 这个是监听端口
  31. port 6379
  32. # TCP or UDP server?
  33. # 使用的协议,推荐使用udp协议,速度会快两三倍
  34. proto tcp
  35. ;proto udp
  36. # "dev tun" will create a routed IP tunnel,
  37. # "dev tap" will create an ethernet tunnel.
  38. # Use "dev tap0" if you are ethernet bridging
  39. # and have precreated a tap0 virtual interface
  40. # and bridged it with your ethernet interface.
  41. # If you want to control access policies
  42. # over the VPN, you must create firewall
  43. # rules for the the TUN/TAP interface.
  44. # On non-Windows systems, you can give
  45. # an explicit unit number, such as tun0.
  46. # On Windows, use "dev-node" for this.
  47. # On most systems, the VPN will not function
  48. # unless you partially or fully disable
  49. # the firewall for the TUN/TAP interface.
  50. # 这里我们就使用tun,tap是以太网桥接方式,没有深究
  51. ;dev tap
  52. dev tun
  53. # Windows needs the TAP-Win32 adapter name
  54. # from the Network Connections panel if you
  55. # have more than one.  On XP SP2 or higher,
  56. # you may need to selectively disable the
  57. # Windows firewall for the TAP adapter.
  58. # Non-Windows systems usually don't need this.
  59. ;dev-node MyTap
  60. # SSL/TLS root certificate (ca), certificate
  61. # (cert), and private key (key).  Each client
  62. # and the server must have their own cert and
  63. # key file.  The server and all clients will
  64. # use the same ca file.
  65. #
  66. # See the "easy-rsa" directory for a series
  67. # of scripts for generating RSA certificates
  68. # and private keys.  Remember to use
  69. # a unique Common Name for the server
  70. # and each of the client certificates.
  71. #
  72. # Any X509 key management system can be used.
  73. # OpenVPN can also use a PKCS #12 formatted key file
  74. # (see "pkcs12" directive in man page).
  75. # 这里配置ca证书,服务端证书,服务端密钥
  76. ca ./crt/ca.crt
  77. cert ./crt/server.crt
  78. key ./crt/server.key  # This file should be kept secret
  79. # Diffie hellman parameters.
  80. # Generate your own with:
  81. #   openssl dhparam -out dh2048.pem 2048
  82. # 都告诉你了,直接使用命令openssl dhparam -out dh2048.pem 2048生成,具体作用可以自行谷歌
  83. dh ./crt/dh2048.pem
  84. # Network topology
  85. # Should be subnet (addressing via IP)
  86. # unless Windows clients v2.0.9 and lower have to
  87. # be supported (then net30, i.e. a /30 per client)
  88. # Defaults to net30 (not recommended)
  89. ;topology subnet
  90. # Configure server mode and supply a VPN subnet
  91. # for OpenVPN to draw client addresses from.
  92. # The server will take 10.8.0.1 for itself,
  93. # the rest will be made available to clients.
  94. # Each client will be able to reach the server
  95. # on 10.8.0.1. Comment this line out if you are
  96. # ethernet bridging. See the man page for more info.
  97. # 这里配置openvpn网络,包括ip和子网掩码,我们就用默认的
  98. server 10.8.0.0 255.255.255.0
  99. # Maintain a record of client <-> virtual IP address
  100. # associations in this file.  If OpenVPN goes down or
  101. # is restarted, reconnecting clients can be assigned
  102. # the same virtual IP address from the pool that was
  103. # previously assigned.
  104. # 这里是为了保证同一个客户端多次连接后分配给相同的局域网ip地址
  105. ifconfig-pool-persist ipp.txt
  106. # Configure server mode for ethernet bridging.
  107. # You must first use your OS's bridging capability
  108. # to bridge the TAP interface with the ethernet
  109. # NIC interface.  Then you must manually set the
  110. # IP/netmask on the bridge interface, here we
  111. # assume 10.8.0.4/255.255.255.0.  Finally we
  112. # must set aside an IP range in this subnet
  113. # (start=10.8.0.50 end=10.8.0.100) to allocate
  114. # to connecting clients.  Leave this line commented
  115. # out unless you are ethernet bridging.
  116. ;server-bridge 10.8.0.4 255.255.255.0 10.8.0.50 10.8.0.100
  117. # Configure server mode for ethernet bridging
  118. # using a DHCP-proxy, where clients talk
  119. # to the OpenVPN server-side DHCP server
  120. # to receive their IP address allocation
  121. # and DNS server addresses.  You must first use
  122. # your OS's bridging capability to bridge the TAP
  123. # interface with the ethernet NIC interface.
  124. # Note: this mode only works on clients (such as
  125. # Windows), where the client-side TAP adapter is
  126. # bound to a DHCP client.
  127. ;server-bridge
  128. # Push routes to the client to allow it
  129. # to reach other private subnets behind
  130. # the server.  Remember that these
  131. # private subnets will also need
  132. # to know to route the OpenVPN client
  133. # address pool (10.8.0.0/255.255.255.0)
  134. # back to the OpenVPN server.
  135. ;push "route 192.168.10.0 255.255.255.0"
  136. ;push "route 192.168.20.0 255.255.255.0"
  137. # To assign specific IP addresses to specific
  138. # clients or if a connecting client has a private
  139. # subnet behind it that should also have VPN access,
  140. # use the subdirectory "ccd" for client-specific
  141. # configuration files (see man page for more info).
  142. # EXAMPLE: Suppose the client
  143. # having the certificate common name "Thelonious"
  144. # also has a small subnet behind his connecting
  145. # machine, such as 192.168.40.128/255.255.255.248.
  146. # First, uncomment out these lines:
  147. ;client-config-dir ccd
  148. ;route 192.168.40.128 255.255.255.248
  149. # Then create a file ccd/Thelonious with this line:
  150. #   iroute 192.168.40.128 255.255.255.248
  151. # This will allow Thelonious' private subnet to
  152. # access the VPN.  This example will only work
  153. # if you are routing, not bridging, i.e. you are
  154. # using "dev tun" and "server" directives.
  155. # EXAMPLE: Suppose you want to give
  156. # Thelonious a fixed VPN IP address of 10.9.0.1.
  157. # First uncomment out these lines:
  158. ;client-config-dir ccd
  159. ;route 10.9.0.0 255.255.255.252
  160. # Then add this line to ccd/Thelonious:
  161. #   ifconfig-push 10.9.0.1 10.9.0.2
  162. # Suppose that you want to enable different
  163. # firewall access policies for different groups
  164. # of clients.  There are two methods:
  165. # (1) Run multiple OpenVPN daemons, one for each
  166. #     group, and firewall the TUN/TAP interface
  167. #     for each group/daemon appropriately.
  168. # (2) (Advanced) Create a script to dynamically
  169. #     modify the firewall in response to access
  170. #     from different clients.  See man
  171. #     page for more info on learn-address script.
  172. ;learn-address ./script
  173. # If enabled, this directive will configure
  174. # all clients to redirect their default
  175. # network gateway through the VPN, causing
  176. # all IP traffic such as web browsing and
  177. # and DNS lookups to go through the VPN
  178. # (The OpenVPN server machine may need to NAT
  179. # or bridge the TUN/TAP interface to the internet
  180. # in order for this to work properly).
  181. # 这里是将客户端的所有流量定向到服务器端,也就是让客户端修改自己的路由表
  182. # 把服务器端的局域网ip地址作为网关,在上面的《三、路由表在openvpn组网中的作用》中有提到
  183. push "redirect-gateway def1 bypass-dhcp"
  184. # Certain Windows-specific network settings
  185. # can be pushed to clients, such as DNS
  186. # or WINS server addresses.  CAVEAT:
  187. # http://openvpn.net/faq.html#dhcpcaveats
  188. # The addresses below refer to the public
  189. # DNS servers provided by opendns.com.
  190. # 这里是给客户端推送DNS服务器地址,如果没有这个推送,客户端还是会用本地默认的DNS地址,有可能导致
  191. # DNS解析失败,这个我是使用命令查看服务器本地的DNS服务器:cat /etc/resolv.conf
  192. # 你也可以使用其他的DNS服务器,只要客户端能正确解析出域名
  193. push "dhcp-option DNS 100.100.2.136"
  194. push "dhcp-option DNS 100.100.2.138"
  195. # Uncomment this directive to allow different
  196. # clients to be able to "see" each other.
  197. # By default, clients will only see the server.
  198. # To force clients to only see the server, you
  199. # will also need to appropriately firewall the
  200. # server's TUN/TAP interface.
  201. # 这里是配置让接入到服务器的多个客户端彼此能看到对方,即能正常通信
  202. client-to-client
  203. # Uncomment this directive if multiple clients
  204. # might connect with the same certificate/key
  205. # files or common names.  This is recommended
  206. # only for testing purposes.  For production use,
  207. # each client should have its own certificate/key
  208. # pair.
  209. #
  210. # IF YOU HAVE NOT GENERATED INDIVIDUAL
  211. # CERTIFICATE/KEY PAIRS FOR EACH CLIENT,
  212. # EACH HAVING ITS OWN UNIQUE "COMMON NAME",
  213. # UNCOMMENT THIS LINE OUT.
  214. # 这里允许使用同一个证书的多个客户端登录
  215. duplicate-cn
  216. # The keepalive directive causes ping-like
  217. # messages to be sent back and forth over
  218. # the link so that each side knows when
  219. # the other side has gone down.
  220. # Ping every 10 seconds, assume that remote
  221. # peer is down if no ping received during
  222. # a 120 second time period.
  223. keepalive 10 120
  224. # For extra security beyond that provided
  225. # by SSL/TLS, create an "HMAC firewall"
  226. # to help block DoS attacks and UDP port flooding.
  227. #
  228. # Generate with:
  229. #   openvpn --genkey --secret ta.key
  230. #
  231. # The server and each client must have
  232. # a copy of this key.
  233. # The second parameter should be '0'
  234. # on the server and '1' on the clients.
  235. # 这里的ta.key文件也是根据命令openvpn --genkey --secret ta.key直接生成
  236. tls-auth ./crt/ta.key 0 # This file is secret
  237. # Select a cryptographic cipher.
  238. # This config item must be copied to
  239. # the client config file as well.
  240. # Note that v2.4 client/server will automatically
  241. # negotiate AES-256-GCM in TLS mode.
  242. # See also the ncp-cipher option in the manpage
  243. # 这里是指定对称加密算法,服务端和客户的配置要一样
  244. cipher AES-256-GCM
  245. # Enable compression on the VPN link and push the
  246. # option to the client (v2.4+ only, for earlier
  247. # versions see below)
  248. # 这里是允许压缩,并且把这个压缩配置推送给了客户端,客户端可以不用配置
  249. compress lz4-v2
  250. push "compress lz4-v2"
  251. # For compression compatible with older clients use comp-lzo
  252. # If you enable it here, you must also
  253. # enable it in the client config file.
  254. ;comp-lzo
  255. # The maximum number of concurrently connected
  256. # clients we want to allow.
  257. ;max-clients 100
  258. # It's a good idea to reduce the OpenVPN
  259. # daemon's privileges after initialization.
  260. #
  261. # You can uncomment this out on
  262. # non-Windows systems.
  263. # 这里设置openvpn允许使用的角色和用户组
  264. user root
  265. group root
  266. # The persist options will try to avoid
  267. # accessing certain resources on restart
  268. # that may no longer be accessible because
  269. # of the privilege downgrade.
  270. # 这里不是很懂,直接保持原样,没有这个有时候会报错
  271. persist-key
  272. persist-tun
  273. # Output a short status file showing
  274. # current connections, truncated
  275. # and rewritten every minute.
  276. # 这里是每分钟记录客户端的状态
  277. status openvpn-status.log
  278. # By default, log messages will go to the syslog (or
  279. # on Windows, if running as a service, they will go to
  280. # the "\Program Files\OpenVPN\log" directory).
  281. # Use log or log-append to override this default.
  282. # "log" will truncate the log file on OpenVPN startup,
  283. # while "log-append" will append to it.  Use one
  284. # or the other (but not both).
  285. # 这里是日志输出文件,log是每次启动覆盖之前的日志,log-append会往后追加,不要同时配置两个
  286. log         ./openvpn.log
  287. ;log-append  ./openvpn.log
  288. # Set the appropriate level of log
  289. # file verbosity.
  290. #
  291. # 0 is silent, except for fatal errors
  292. # 4 is reasonable for general usage
  293. # 5 and 6 can help to debug connection problems
  294. # 9 is extremely verbose
  295. # 这里是日志输出等级,数字越高,日志越详细
  296. verb 3
  297. # Silence repeating messages.  At most 20
  298. # sequential messages of the same message
  299. # category will be output to the log.
  300. ;mute 20
  301. # Notify the client that when the server restarts so it
  302. # can automatically reconnect.
  303. ;explicit-exit-notify 1
复制代码
这个server.conf服务端设置文件也是根据样例文件做的一些修改。一些比较重要的设置我已经标注出来了。证书的话需要自己制作,利用openssl命令就可以天生。参考:OPenSSL-天生证书-CSDN博客
       openvpn-shutdown.sh文件就不用改了,全部设置都配好就就可以启动openvpn服务器:
       ./openvpn-startup.sh
假如有报错就看当前目次下的openvpn.log文件查看错误 
      检查是否启动乐成:
      netstat -nlap | grep openvpn

看到6379端口在监听就阐明启动乐成

2、客户端(centos)

        服务端启动乐成后,可以利用linux的客户端连接一下,看能不能正常工作,一般都不会一次乐成,都会有各种各样的题目。
         centos系统上的openvpn客户端和服务端是不区分的,前面讲服务的部署的时候提到有一个client.conf的样例设置文件,我也是拿这个来改了一下。
client.conf文件如下:
  1. ##############################################
  2. # Sample client-side OpenVPN 2.0 config file #
  3. # for connecting to multi-client server.     #
  4. #                                            #
  5. # This configuration can be used by multiple #
  6. # clients, however each client should have   #
  7. # its own cert and key files.                #
  8. #                                            #
  9. # On Windows, you might want to rename this  #
  10. # file so it has a .ovpn extension           #
  11. ##############################################
  12. # Specify that we are a client and that we
  13. # will be pulling certain config file directives
  14. # from the server.
  15. # 这里需要指明是客户端才行
  16. client
  17. # Use the same setting as you are using on
  18. # the server.
  19. # On most systems, the VPN will not function
  20. # unless you partially or fully disable
  21. # the firewall for the TUN/TAP interface.
  22. # 这里跟服务端的配置一样
  23. ;dev tap
  24. dev tun
  25. # Windows needs the TAP-Win32 adapter name
  26. # from the Network Connections panel
  27. # if you have more than one.  On XP SP2,
  28. # you may need to disable the firewall
  29. # for the TAP adapter.
  30. ;dev-node MyTap
  31. # Are we connecting to a TCP or
  32. # UDP server?  Use the same setting as
  33. # on the server.
  34. # 这里是使用协议,必须跟服务端一致
  35. proto tcp
  36. ;proto udp
  37. # The hostname/IP and port of the server.
  38. # You can have multiple remote entries
  39. # to load balance between the servers.
  40. # 这里填服务器端的IP端口
  41. remote 1.1.1.1 6679
  42. #remote my-server-2 1194
  43. # Choose a random host from the remote
  44. # list for load-balancing.  Otherwise
  45. # try hosts in the order specified.
  46. ;remote-random
  47. # Keep trying indefinitely to resolve the
  48. # host name of the OpenVPN server.  Very useful
  49. # on machines which are not permanently connected
  50. # to the internet such as laptops.
  51. # 这里就用默认的配置
  52. resolv-retry infinite
  53. # Most clients don't need to bind to
  54. # a specific local port number.
  55. # 这里指明通信绑定的端口,一般都不指定,系统随机分配
  56. nobind
  57. # Downgrade privileges after initialization (non-Windows only)
  58. ;user nobody
  59. ;group nobody
  60. # Try to preserve some state across restarts.
  61. # 这里不是很懂用来干嘛的,看注释是重启的时候维持一些状态,我们就使用默认配置
  62. persist-key
  63. persist-tun
  64. # If you are connecting through an
  65. # HTTP proxy to reach the actual OpenVPN
  66. # server, put the proxy server/IP and
  67. # port number here.  See the man page
  68. # if your proxy server requires
  69. # authentication.
  70. ;http-proxy-retry # retry on connection failures
  71. ;http-proxy [proxy server] [proxy port #]
  72. # Wireless networks often produce a lot
  73. # of duplicate packets.  Set this flag
  74. # to silence duplicate packet warnings.
  75. ;mute-replay-warnings
  76. # SSL/TLS parms.
  77. # See the server config file for more
  78. # description.  It's best to use
  79. # a separate .crt/.key file pair
  80. # for each client.  A single ca
  81. # file can be used for all clients.
  82. # 这里就配置ssl通信用的ca证书,客户端证书,客户端私钥,可以指定路径,默认是当前目录
  83. ca ca.crt
  84. cert client.crt
  85. key client.key
  86. # Verify server certificate by checking that the
  87. # certicate has the correct key usage set.
  88. # This is an important precaution to protect against
  89. # a potential attack discussed here:
  90. #  http://openvpn.net/howto.html#mitm
  91. #
  92. # To use this feature, you will need to generate
  93. # your server certificates with the keyUsage set to
  94. #   digitalSignature, keyEncipherment
  95. # and the extendedKeyUsage to
  96. #   serverAuth
  97. # EasyRSA can do this for you.
  98. # 这里需要注更改默认的配置,默认是打开的,因为我制作的服务端证书没有它指定的几个信息,我就不做校验了,当然你也可以按他的指示重新制作服务端证书,这个是为了避免潜在的攻击的
  99. #remote-cert-tls server
  100. # If a tls-auth key is used on the server
  101. # then every client must also have the key.
  102. # 这里配置tls认证key,这个就是服务器使用的ta.key,两端是同一个文件
  103. tls-auth ta.key 1
  104. # Select a cryptographic cipher.
  105. # If the cipher option is used on the server
  106. # then you must also specify it here.
  107. # Note that v2.4 client/server will automatically
  108. # negotiate AES-256-GCM in TLS mode.
  109. # See also the ncp-cipher option in the manpage
  110. # 加密算法,跟服务端要一致,但是我发现服务端配置的是AES-256-GCM,这里配置的是AES-256-CBC,也一样能正常加解密,比较奇怪,可能最终协商一致就可以
  111. cipher AES-256-CBC
  112. # Enable compression on the VPN link.
  113. # Don't enable this unless it is also
  114. # enabled in the server config file.
  115. #comp-lzo
  116. # Set log file verbosity.
  117. # 日志等级
  118. verb 3
  119. # Silence repeating messages
  120. ;mute 20
  121. # 服务端已经配置,这里不需要重新配置
  122. ;redirect-gateway autolocal
复制代码
设置完成后开始启动客户端:openvpn --config client.conf
假如打印如下的日记,就是连接乐成了

连接乐成后我们查看一下网卡设置:

 看到tun0网卡已经被创建好,服务端分配给我们客户端的ip是10.8.0.6,因为是点对点的网络,对端显示的ip是10.8.0.5,但是我们试着ping一下这个ip,发现ping不通,似乎这个ip是不存在的。但是我们此时去服务端查看一下服务端的tun0网卡的ip发现是10.8.0.1,于是实验ping这个ip证明我们已经和服务端创建了通信:

看到能ping通,阐明已经能和服务端通信,vpn网络已经组网完成。
        在测试过程中我发现客户端和服务器端是能举行通信,但是客户端主机解析不了域名,用命令:cat /etc/resolv.conf 查看了一下域名服务器地址,发现域名服务器地址还是当地的ip,没有自动改成服务器端给我们推送的DNS地址。我手动把这个文件的DNS地址改成服务端推送的DNS地址就可以正常举行域名解析了。此时就可以通过openvpn访问外网,客户端全部流量都会通过服务器端转发。
3、客户端(Android)

        对于openvpn的安卓客户端,有两款,一款叫OpenVPN Connect,一款叫OpenVPN For Android,两款都可以用,大概需要一点技术才能下载到。
        openvpn的安卓客户,在制作设置文件的时候会有点麻烦,但是假如掌握了方法也很简单。刚开始我认为设置文件在各个平台都通用,我已经在linux上设置好设置文件,直接拷贝到安卓上就行,但是发现导入设置文件的时候只能导入一个文件,那还有ca证书,客户端证书,客户端私钥,还有ta.key文件怎么导入?没法办只能求助谷歌,找了很久才在openvpn的社区中找到安卓设置文件的制作方法。
        原来openvpn的设置文件支持把这些证书文件内联到设置文件中。就拿以上centos客户端的设置文件来举例,需要以下四个设置项
  1. ca ca.crt
  2. cert client.crt
  3. key client.key
  4. tls-auth ta.key 1
复制代码
        即需要内联四个证书,内联的时候只需要将证书文件内容包含在<configItemName></configItemName>中就可以,例如ca证书内联后就为
  1. <ca>
  2. ...
  3. </ca>
复制代码
         于是就可以拿上面的centos客户端设置来制作,先把client.conf改成文件名client.ovpn,安卓只支持这个后缀名文件。然后实行下面的命令将证书内联进设置文件:
  1. echo "<ca>" >> client.ovpn
  2. cat ca.crt >> client.ovpn
  3. echo "</ca>" >> client.ovpn
  4. echo "<cert>" >> client.ovpn
  5. cat client.crt >> client.ovpn
  6. echo "</cert>" >> client.ovpn
  7. echo "<key>" >> client.ovpn
  8. cat client.key >> client.ovpn
  9. echo "</key>" >> client.ovpn
  10. echo "key-direction 1" >> client.ovpn
  11. echo "<tls-auth>" >> client.ovpn
  12. cat ta.key >> client.ovpn
  13. echo "</tls-auth>" >> client.ovpn
复制代码
 因为tls-auth ta.key 1这个设置除了设置ta.key证书文件,还有一个设置参数,所以内联了ta.key文件后,还需要添加key-direction 1这个设置参数。
         OpenVPN Connect导入设置文件,就是点右下角的加号->Upload File->BROWSE,选择设置文件后导入。OpenVPN For Android导入设置,就是点击右上角的加号->IMPORT导入。这两款App的设置文件都通用
        导入设置文件后,就可以点连接,假如没连上可以点右上角的按钮查看日记,然后再排查文件。假如显示连接乐成,那么恭喜你,可以利用自己的openvpn了。



免责声明:如果侵犯了您的权益,请联系站长,我们会及时删除侵权内容,谢谢合作!更多信息从访问主页:qidao123.com:ToB企服之家,中国第一个企服评测及商务社交产业平台。




欢迎光临 ToB企服应用市场:ToB评测及商务社交产业平台 (https://dis.qidao123.com/) Powered by Discuz! X3.4