過程 47.3. CREATE KEYS FOR THE SERVER AND THE CLIENTS

1. Change to the directory /usr/share/doc/openvpn/examples/easy-rsa/2.0

   netkiller@shenzhen:~$ cd /usr/share/doc/openvpn/examples/easy-rsa/2.0
   netkiller@shenzhen:/usr/share/doc/openvpn/examples/easy-rsa/2.0$ ls
   build-ca  build-dh  build-inter  build-key  build-key-pass  build-key-pkcs12  build-key-server  build-req  build-req-pass  clean-all  inherit-inter  list-crl  Makefile  openssl-0.9.6.cnf.gz  openssl.cnf  pkitool  README.gz  revoke-full  sign-req  vars  whichopensslcnf
   					

   backup vars to vars.original

   sudo cp vars vars.original
   					

   vi vars and change with you

   export KEY_COUNTRY="CN"
   export KEY_PROVINCE="GD"
   export KEY_CITY="Shenzhen"
   export KEY_ORG="http://netkiller.sourceforge.net/"
   export KEY_EMAIL="openunix@163.com"
   					

   type the commands

   • vars

   • clean-all

   • build-ca

   • build-key-server server

   • build-key client1

   • build-dh

2. vars and clean-all

   netkiller@shenzhen:/usr/share/doc/openvpn/examples/easy-rsa/2.0$ source ./vars
   NOTE: If you run ./clean-all, I will be doing a rm -rf on /usr/share/doc/openvpn/examples/easy-rsa/2.0/keys
   netkiller@shenzhen:/usr/share/doc/openvpn/examples/easy-rsa/2.0$ ./clean-all
   
   $ sudo mkdir keys
   $ sudo chown neo.neo keys
   					

3. build-ca

   netkiller@shenzhen:/usr/share/doc/openvpn/examples/easy-rsa/2.0$ ./build-ca
   Generating a 1024 bit RSA private key
   ..........................++++++
   .............++++++
   writing new private key to 'ca.key'
   -----
   You are about to be asked to enter information that will be incorporated
   into your certificate request.
   What you are about to enter is what is called a Distinguished Name or a DN.
   There are quite a few fields but you can leave some blank
   For some fields there will be a default value,
   If you enter '.', the field will be left blank.
   -----
   Country Name (2 letter code) [CN]:
   State or Province Name (full name) [GD]:
   Locality Name (eg, city) [Shenzhen]:
   Organization Name (eg, company) [http://netkiller.8800.org]:
   Organizational Unit Name (eg, section) []:
   Common Name (eg, your name or your server's hostname) [http://netkiller.8800.org CA]:
   Email Address [openunix@163.com]:
   					

4. build-key-server server

   You will have to answer the same questions above. It will ask you for a password, I suggest you don’t put a password when it ask.

   netkiller@shenzhen:/usr/share/doc/openvpn/examples/easy-rsa/2.0$ ./build-key-server server
   Generating a 1024 bit RSA private key
   ...................................++++++
   ...........................................++++++
   writing new private key to 'server.key'
   -----
   You are about to be asked to enter information that will be incorporated
   into your certificate request.
   What you are about to enter is what is called a Distinguished Name or a DN.
   There are quite a few fields but you can leave some blank
   For some fields there will be a default value,
   If you enter '.', the field will be left blank.
   -----
   Country Name (2 letter code) [CN]:
   State or Province Name (full name) [GD]:
   Locality Name (eg, city) [Shenzhen]:
   Organization Name (eg, company) [http://netkiller.8800.org]:
   Organizational Unit Name (eg, section) []:
   Common Name (eg, your name or your server's hostname) [server]:
   Email Address [openunix@163.com]:
   
   Please enter the following 'extra' attributes
   to be sent with your certificate request
   A challenge password []:
   An optional company name []:
   Using configuration from /usr/share/doc/openvpn/examples/easy-rsa/2.0/openssl.cnf
   Check that the request matches the signature
   Signature ok
   The Subject's Distinguished Name is as follows
   countryName           :PRINTABLE:'CN'
   stateOrProvinceName   :PRINTABLE:'GD'
   localityName          :PRINTABLE:'Shenzhen'
   organizationName      :PRINTABLE:'http://netkiller.8800.org'
   commonName            :PRINTABLE:'server'
   emailAddress          :IA5STRING:'openunix@163.com'
   Certificate is to be certified until Nov 10 18:09:52 2017 GMT (3650 days)
   Sign the certificate? [y/n]:y
   
   
   1 out of 1 certificate requests certified, commit? [y/n]y
   Write out database with 1 new entries
   Data Base Updated
   					

   enter yes to sign the certificate.

5. build-dh

   # ./build-dh
   Generating DH parameters, 1024 bit long safe prime, generator 2
   This is going to take a long time
   .........................+..............................+....................................................+..........................................................................................+............................................................+..........................................+..........................+.............................................................................................................+....................+...................+...............................................+..+...........................................................+................+..........................................................+............................................................................+..........+..........................................................................+...........+.............................................................................................................................................................................+....+..........................................................+........+...................................+.........................................................+...........................................................................................+..............................................................................................+.................................++*++*++*
   					

過程 47.4. create keys for the clients

1. build-key client1

   Now to build the client files

   netkiller@shenzhen:/usr/share/doc/openvpn/examples/easy-rsa/2.0$ ./build-key client1
   Generating a 1024 bit RSA private key
   .++++++
   ...........++++++
   writing new private key to 'client1.key'
   -----
   You are about to be asked to enter information that will be incorporated
   into your certificate request.
   What you are about to enter is what is called a Distinguished Name or a DN.
   There are quite a few fields but you can leave some blank
   For some fields there will be a default value,
   If you enter '.', the field will be left blank.
   -----
   Country Name (2 letter code) [CN]:
   State or Province Name (full name) [GD]:
   Locality Name (eg, city) [Shenzhen]:
   Organization Name (eg, company) [http://netkiller.8800.org]:
   Organizational Unit Name (eg, section) []:
   Common Name (eg, your name or your server's hostname) [client1]:
   Email Address [openunix@163.com]:
   
   Please enter the following 'extra' attributes
   to be sent with your certificate request
   A challenge password []:
   An optional company name []:
   Using configuration from /usr/share/doc/openvpn/examples/easy-rsa/2.0/openssl.cnf
   Check that the request matches the signature
   Signature ok
   The Subject's Distinguished Name is as follows
   countryName           :PRINTABLE:'CN'
   stateOrProvinceName   :PRINTABLE:'GD'
   localityName          :PRINTABLE:'Shenzhen'
   organizationName      :PRINTABLE:'http://netkiller.8800.org'
   commonName            :PRINTABLE:'client1'
   emailAddress          :IA5STRING:'openunix@163.com'
   Certificate is to be certified until Nov 10 18:15:39 2017 GMT (3650 days)
   Sign the certificate? [y/n]:y
   
   
   1 out of 1 certificate requests certified, commit? [y/n]y
   Write out database with 1 new entries
   Data Base Updated
   				

   And once again you will need to answer the questions above. I still don’t recommend you putting a password as it can cause problems when I have tried.

   注意在進入 Common Name (eg, your name or your server's hostname) []: 的輸入時, 每個證書輸入的名字必須不同.

2. All the files you just generated are located in /usr/share/doc/openvpn/examples/easy-rsa/2.0/keys

   If you do a list command in the keys folder you should have something like:

   netkiller@shenzhen:/usr/share/doc/openvpn/examples/easy-rsa/2.0$ ls keys/
   01.pem  ca.crt  client1.crt  client1.key  index.txt       index.txt.attr.old  serial      server.crt  server.key
   02.pem  ca.key  client1.csr  dh1024.pem   index.txt.attr  index.txt.old       serial.old  server.csr
   			

   Copy the files ca.crt, ca.key, dh1024.pem, server.crt, and server.key to the /etc/openvpn/keys

   netkiller@shenzhen:/usr/share/doc/openvpn/examples/easy-rsa/2.0$ cd keys/
   netkiller@shenzhen:/usr/share/doc/openvpn/examples/easy-rsa/2.0/keys$ sudo cp keys/ca.key keys/ca.crt keys/dh1024.pem keys/server.key keys/server.crt /etc/openvpn/
   				

   We will worry about the client files after we configure the client config file.

3. CONFIGURE THE SERVER

   Change to the directory /usr/share/doc/openvpn/examples/sample-config-files

   netkiller@shenzhen:/usr/share/doc/openvpn/examples/sample-config-files$ sudo gunzip server.conf.gz
   netkiller@shenzhen:/usr/share/doc/openvpn/examples/sample-config-files$ sudo cp server.conf /etc/openvpn/
   netkiller@shenzhen:/usr/share/doc/openvpn/examples/sample-config-files$ cd /etc/openvpn/
   netkiller@shenzhen:/etc/openvpn$
   			

   為用戶添加路由

   push "route 192.168.1.0 255.255.255.0"

   例 47.2. server.conf

   				
   #################################################
   # 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
   ;local 192.168.1.7
   
   # 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
   
   # 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
   
   # 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
   
   # 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.1.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
   # 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 nogroup
   
   # 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 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         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
   					
   					

   
   

   test

   netkiller@shenzhen:/etc/openvpn$ sudo openvpn --config /etc/openvpn/server.conf
   Tue Nov 13 14:12:33 2007 OpenVPN 2.0.9 i486-pc-linux-gnu [SSL] [LZO] [EPOLL] built on Mar  2 2007
   Tue Nov 13 14:12:33 2007 Diffie-Hellman initialized with 1024 bit key
   Tue Nov 13 14:12:33 2007 TLS-Auth MTU parms [ L:1542 D:138 EF:38 EB:0 ET:0 EL:0 ]
   Tue Nov 13 14:12:33 2007 TUN/TAP device tun0 opened
   Tue Nov 13 14:12:33 2007 ifconfig tun0 10.8.0.1 pointopoint 10.8.0.2 mtu 1500
   Tue Nov 13 14:12:33 2007 route add -net 10.8.0.0 netmask 255.255.255.0 gw 10.8.0.2
   Tue Nov 13 14:12:33 2007 Data Channel MTU parms [ L:1542 D:1450 EF:42 EB:135 ET:0 EL:0 AF:3/1 ]
   Tue Nov 13 14:12:33 2007 UDPv4 link local (bound): [undef]:1194
   Tue Nov 13 14:12:33 2007 UDPv4 link remote: [undef]
   Tue Nov 13 14:12:33 2007 MULTI: multi_init called, r=256 v=256
   Tue Nov 13 14:12:33 2007 IFCONFIG POOL: base=10.8.0.4 size=62
   Tue Nov 13 14:12:33 2007 IFCONFIG POOL LIST
   Tue Nov 13 14:12:33 2007 Initialization Sequence Completed
   				

4. Start

   netkiller@shenzhen:~$ sudo /etc/init.d/openvpn start
   Starting virtual private network daemon: server(OK).
   				

過程 47.6. For Windows Server

1. http://openvpn.se/

   http://openvpn.se/files/install_packages/openvpn-2.0.9-gui-1.0.3-install.exe

   下載安裝後,會在系統托盤上顯示表徵圖.這時並不能使用,使用創建配置檔案後托盤表徵圖才會顯示連接菜單

2. 創建證書

   C:\Documents and Settings\Neo>cd "\Program Files\OpenVPN\easy-rsa"
   C:\Program Files\OpenVPN\easy-rsa>
   C:\Program Files\OpenVPN\easy-rsa>init-config.bat
   				

   編輯vars.bat

   set KEY_COUNTRY=CN
   set KEY_PROVINCE=GD
   set KEY_CITY=Shenzhen
   set KEY_ORG=netkiller.org.cn
   set KEY_EMAIL=openunix@163.com
   				

   C:\Program Files\OpenVPN\easy-rsa>clean-all.bat
   C:\Program Files\OpenVPN\easy-rsa>vars.bat
   				

   創建CA證書

   				
   C:\Program Files\OpenVPN\easy-rsa>build-ca.bat
   Loading 'screen' into random state - done
   Generating a 1024 bit RSA private key
   ......++++++
   ......++++++
   writing new private key to 'keys\ca.key'
   -----
   You are about to be asked to enter information that will be incorporated
   into your certificate request.
   What you are about to enter is what is called a Distinguished Name or a DN.
   There are quite a few fields but you can leave some blank
   For some fields there will be a default value,
   If you enter '.', the field will be left blank.
   -----
   Country Name (2 letter code) [CN]:
   State or Province Name (full name) [GD]:
   Locality Name (eg, city) [Shenzhen]:
   Organization Name (eg, company) [netkiller.org.cn]:
   Organizational Unit Name (eg, section) []:vpn
   Common Name (eg, your name or your server's hostname) []:netkiller.org.cn
   Email Address [openunix@163.com]:
   
   C:\Program Files\OpenVPN\easy-rsa>
   				
   				

   dh

   				
   C:\Program Files\OpenVPN\easy-rsa>build-dh.bat
   Loading 'screen' into random state - done
   Generating DH parameters, 1024 bit long safe prime, generator 2
   This is going to take a long time
   ..........................+...................+.................................
   .................................+...........+.....................+.......+....
   ...............................................................+..+.............
   .+.......................................+......................................
   ...+..+...........+................................+............................
   ................................................+.....+.........................
   ................................................+.....+......+..................
   ....................................+...........................................
   .........................................................................+.....+
   .......................................+.....................+..................
   ....+...........................................................................
   ......................+............................+............................
   ................................................................................
   ................................................................................
   ............................+.................+......................+......+...
   .............+...................+..............................................
   .................+............................................+.................
   ................................................................................
   ................................+....+.................+........................
   ...................+.......+....................................................
   ..+...............+.............................................................
   ................................................................................
   ...............................................................+................
   .......+.........................................................++*++*++*
   
   C:\Program Files\OpenVPN\easy-rsa>
   				
   				

   server key

   				
   C:\Program Files\OpenVPN\easy-rsa>build-key-server.bat server
   Loading 'screen' into random state - done
   Generating a 1024 bit RSA private key
   ........++++++
   ....................++++++
   writing new private key to 'keys\server.key'
   -----
   You are about to be asked to enter information that will be incorporated
   into your certificate request.
   What you are about to enter is what is called a Distinguished Name or a DN.
   There are quite a few fields but you can leave some blank
   For some fields there will be a default value,
   If you enter '.', the field will be left blank.
   -----
   Country Name (2 letter code) [CN]:
   State or Province Name (full name) [GD]:
   Locality Name (eg, city) [Shenzhen]:
   Organization Name (eg, company) [netkiller.org.cn]:
   Organizational Unit Name (eg, section) []:vpn
   Common Name (eg, your name or your server's hostname) []:netkiller.org.cn
   Email Address [openunix@163.com]:
   
   Please enter the following 'extra' attributes
   to be sent with your certificate request
   A challenge password []:chen
   An optional company name []:
   Using configuration from openssl.cnf
   Loading 'screen' into random state - done
   Check that the request matches the signature
   Signature ok
   The Subject's Distinguished Name is as follows
   countryName           :PRINTABLE:'CN'
   stateOrProvinceName   :PRINTABLE:'GD'
   localityName          :PRINTABLE:'Shenzhen'
   organizationName      :PRINTABLE:'netkiller.org.cn'
   organizationalUnitName:PRINTABLE:'vpn'
   commonName            :PRINTABLE:'netkiller.org.cn'
   emailAddress          :IA5STRING:'openunix@163.com'
   Certificate is to be certified until Jun  9 03:14:55 2017 GMT (3650 days)
   Sign the certificate? [y/n]:y
   
   
   1 out of 1 certificate requests certified, commit? [y/n]y
   Write out database with 1 new entries
   Data Base Updated
   
   C:\Program Files\OpenVPN\easy-rsa>
   				
   				

   client key

   				
   C:\Program Files\OpenVPN\easy-rsa>build-key.bat client
   Loading 'screen' into random state - done
   Generating a 1024 bit RSA private key
   ......++++++
   ....................++++++
   writing new private key to 'keys\client.key'
   -----
   You are about to be asked to enter information that will be incorporated
   into your certificate request.
   What you are about to enter is what is called a Distinguished Name or a DN.
   There are quite a few fields but you can leave some blank
   For some fields there will be a default value,
   If you enter '.', the field will be left blank.
   -----
   Country Name (2 letter code) [CN]:
   State or Province Name (full name) [GD]:
   Locality Name (eg, city) [Shenzhen]:
   Organization Name (eg, company) [netkiller.org.cn]:
   Organizational Unit Name (eg, section) []:vpn
   Common Name (eg, your name or your server's hostname) []:netkiller.org.cn
   Email Address [openunix@163.com ]:
   
   Please enter the following 'extra' attributes
   to be sent with your certificate request
   A challenge password []:chen
   An optional company name []:
   Using configuration from openssl.cnf
   Loading 'screen' into random state - done
   DEBUG[load_index]: unique_subject = "yes"
   Check that the request matches the signature
   Signature ok
   The Subject's Distinguished Name is as follows
   countryName           :PRINTABLE:'CN'
   stateOrProvinceName   :PRINTABLE:'GD'
   localityName          :PRINTABLE:'Shenzhen'
   organizationName      :PRINTABLE:'netkiller.org.cn'
   organizationalUnitName:PRINTABLE:'vpn'
   commonName            :PRINTABLE:'netkiller.org.cn'
   emailAddress          :IA5STRING:'openunix@163.com^I'
   Certificate is to be certified until Jun  9 03:17:55 2017 GMT (3650 days)
   Sign the certificate? [y/n]:y
   failed to update database
   TXT_DB error number 2
   
   C:\Program Files\OpenVPN\easy-rsa>
   				
   				

3. 配置

   例 47.4. server.ovpn

   
   #################################################
   # 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 ca.crt
   cert server.crt
   key 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 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
   
   # 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
   # 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 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         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
   
   
   					

   
   

過程 47.7. For Windows Client

1. 配置檔案

   將C:\Program Files\OpenVPN\sample-config目錄下的client.ovpn複製到C:\Program Files\OpenVPN\config

   ca.crt, client.crt, client.key 三個檔案複製到 C:\Program Files\OpenVPN\config

   修改;remote my-server-1 1194

   remote vpn.netkiller.8800.org 1194
   					

   編輯client.ovpn檔案

   例 47.5. client.ovpn

   ##############################################
   # 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 netkiller.8800.org 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
   						

   
   

2. 連接到VPN伺服器

   托盤表徵圖上->右鍵->選擇 [Connect] 菜單

過程 47.9. server

1. yum -y install bridge-utils
   				

2. server.conf

   dev tap0
   server-bridge 192.168.3.5 255.255.255.0 192.168.3.200  192.168.3.250
   push "redirect-gateway local def1"
   push "dhcp-option DNS 208.67.222.222"
   push "dhcp-option DNS 208.67.220.220"
   				

3. cp /usr/share/doc/openvpn-2.1.1/sample-scripts/bridge-st* /etc/openvpn/
   chmod +x /etc/openvpn/bridge*
   				

   config bridge-start

   vim /etc/openvpn/bridge-start
   eth="eth0"
   eth_ip="192.168.3.5"
   eth_netmask="255.255.255.0"
   eth_broadcast="192.168.3.255"
   				

4. start

   /etc/openvpn/bridge-start
   /etc/init.d/openvpn start
   				

5. stop

   /etc/init.d/openvpn stop
   /etc/openvpn/bridge-stop
   				

過程 47.10. client

1. client.ovpn

   dev tap
   dev-node tap-bridge
   				

2. 網路上的芳鄰右鍵，選擇屬性，TAP-Win32 Adapter V8 重命名為 tap-bridge

   vista windows7 操作系統注意：

   OpenVPN GUI 右鍵“以管理員身份運行”
   
   client.ovpn 中加入
   route-method exe
   route-delay 2