Apr  5 07:42:12 localhost syslogd 1.4.1: restart.
Apr  5 07:42:12 localhost kernel: klogd 1.4.1, log source = /proc/kmsg started.
Apr  5 07:42:12 localhost kernel: Linux version 2.6.18-308.el5 (mockbuild@builder10.centos.org) (gcc version 4.1.2 20080704 (Red Hat 4.1.2-52)) #1 SMP Tue Feb 21 20:05:41 EST 2012
Apr  5 07:42:12 localhost kernel: BIOS-provided physical RAM map:
Apr  5 07:42:12 localhost kernel:  BIOS-e820: 0000000000010000 - 000000000009f800 (usable)
Apr  5 07:42:12 localhost kernel:  BIOS-e820: 000000000009f800 - 00000000000a0000 (reserved)
Apr  5 07:42:12 localhost kernel:  BIOS-e820: 00000000000ca000 - 00000000000cc000 (reserved)
Apr  5 07:42:12 localhost kernel:  BIOS-e820: 00000000000dc000 - 0000000000100000 (reserved)
Apr  5 07:42:12 localhost kernel:  BIOS-e820: 0000000000100000 - 000000003fef0000 (usable)
Apr  5 07:42:12 localhost kernel:  BIOS-e820: 000000003fef0000 - 000000003feff000 (ACPI data)
Apr  5 07:42:12 localhost kernel:  BIOS-e820: 000000003feff000 - 000000003ff00000 (ACPI NVS)
Apr  5 07:42:12 localhost kernel:  BIOS-e820: 000000003ff00000 - 0000000040000000 (usable)
Apr  5 07:42:12 localhost kernel:  BIOS-e820: 00000000e0000000 - 00000000f0000000 (reserved)
Apr  5 07:42:12 localhost kernel:  BIOS-e820: 00000000fec00000 - 00000000fec10000 (reserved)
Apr  5 07:42:12 localhost kernel:  BIOS-e820: 00000000fee00000 - 00000000fee01000 (reserved)
Apr  5 07:42:12 localhost kernel:  BIOS-e820: 00000000fffe0000 - 0000000100000000 (reserved)
Apr  5 07:42:12 localhost kernel: 128MB HIGHMEM available.
Apr  5 07:42:12 localhost kernel: 896MB LOWMEM available.
Apr  5 07:42:12 localhost kernel: found SMP MP-table at 000f6bf0
Apr  5 07:42:12 localhost kernel: Memory for crash kernel (0x0 to 0x0) notwithin permissible range
Apr  5 07:42:12 localhost kernel: disabling kdump
Apr  5 07:42:12 localhost kernel: Using x86 segment limits to approximate NX protection
Apr  5 07:42:12 localhost kernel: DMI present.
Apr  5 07:42:12 localhost kernel: Using APIC driver default
Apr  5 07:42:12 localhost kernel: ACPI: PM-Timer IO Port: 0x1008
Apr  5 07:42:12 localhost kernel: ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled)
Apr  5 07:42:12 localhost kernel: Processor #0 7:7 APIC version 21
Apr  5 07:42:12 localhost kernel: ACPI: LAPIC_NMI (acpi_id[0x00] high edge lint[0x1])
Apr  5 07:42:12 localhost kernel: ACPI: IOAPIC (id[0x01] address[0xfec00000] gsi_base[0])
Apr  5 07:42:12 localhost kernel: IOAPIC[0]: apic_id 1, version 17, address 0xfec00000, GSI 0-23
Apr  5 07:42:12 localhost kernel: ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 high edge)
Apr  5 07:42:12 localhost kernel: Enabling APIC mode:  Flat.  Using 1 I/O APICs
Apr  5 07:42:12 localhost kernel: ACPI: HPET id: 0x8086af01 base: 0xfed00000
Apr  5 07:42:12 localhost kernel: Using ACPI (MADT) for SMP configuration information
Apr  5 07:42:12 localhost kernel: Allocating PCI resources starting at 50000000 (gap: 40000000:a0000000)
Apr  5 07:42:12 localhost kernel: TSC: Frequency read from the hypervisor
Apr  5 07:42:12 localhost kernel: Detected 2926.030 MHz processor.
"messages" 3522L, 277835C

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

# 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
server 192.168.1.0 255.255.255.0

# Maintain a record of client <-> virtual IP address
# associations in this file.  If OpenVPN goes down or
# is restarted, reconnecting clients can be assigned
# the same virtual IP address from the pool that was
# previously assigned.
ifconfig-pool-persist ipp.txt

# Configure server mode for ethernet bridging.
# You must first use your OS's bridging capability
# to bridge the TAP interface with the ethernet
# NIC interface.  Then you must manually set the
# IP/netmask on the bridge interface, here we
# assume 10.8.0.4/255.255.255.0.  Finally we
# must set aside an IP range in this subnet
# (start=10.8.0.50 end=10.8.0.100) to allocate
# to connecting clients.  Leave this line commented
# out unless you are ethernet bridging.
;server-bridge 10.8.0.4 255.255.255.0 10.8.0.50 10.8.0.100

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

# Push routes to the client to allow it
# to reach other private subnets behind
# the server.  Remember that these
# private subnets will also need
# to know to route the OpenVPN client
# address pool (10.8.0.0/255.255.255.0)
# back to the OpenVPN server.
push "route 192.168.1.0 255.255.255.0"
push "route 10.0.0.0 255.0.0.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 wwwect 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 "wwwect-gateway def1 bypass-dhcp"

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

rw-r--r-- 1 root root 3785 Apr 24 05:19 01.pem
-rw-r--r-- 1 root root 1159 Apr 24 05:16 ca.crt
-rw------- 1 root root 887 Apr 24 05:16 ca.key
-rw-r--r-- 1 root root 245 Apr 24 05:18 dh1024.pem
-rw-r--r-- 1 root root 97 Apr 24 05:19 index.txt
-rw-r--r-- 1 root root 21 Apr 24 05:19 index.txt.attr
-rw-r--r-- 1 root root 0 Apr 24 05:16 index.txt.old
-rw-r--r-- 1 root root 3 Apr 24 05:19 serial
-rw-r--r-- 1 root root 3 Apr 24 05:16 serial.old
-rw-r--r-- 1 root root 3785 Apr 24 05:19 server.crt
-rw-r--r-- 1 root root 660 Apr 24 05:19 server.csr
-rw------- 1 root root 887 Apr 24 05:19 server.key
-rw------- 1 root root 636 Apr 24 05:20 ta.key
[root@vpn-ldap keys]#

Apr 25 03:22:49 2013 SIGUSR1[soft,tls-error] received, process restarting
Thu Apr 25 03:22:49 2013 Restart pause, 2 second(s)
Thu Apr 25 03:22:51 2013 IMPORTANT: OpenVPN's default port number is now 1194, based on an official port number assignment by IANA.  OpenVPN 2.0-beta16 and earlier used 5000 as the default port.
Thu Apr 25 03:22:51 2013 Re-using SSL/TLS context
Thu Apr 25 03:22:51 2013 LZO compression initialized
Thu Apr 25 03:22:51 2013 Control Channel MTU parms [ L:1542 D:166 EF:66 EB:0 ET:0 EL:0 ]
Thu Apr 25 03:22:51 2013 Data Channel MTU parms [ L:1542 D:1450 EF:42 EB:135 ET:0 EL:0 AF:3/1 ]
Thu Apr 25 03:22:51 2013 Local Options hash (VER=V4): '504e774e'
Thu Apr 25 03:22:51 2013 Expected Remote Options hash (VER=V4): '14168603'
Thu Apr 25 03:22:51 2013 UDPv4 link local: [undef]
Thu Apr 25 03:22:51 2013 UDPv4 link remote: 192.168.1.200:1194
Thu Apr 25 03:22:51 2013 TLS: Initial packet from 192.168.1.200:1194, sid=4b23ae8d 086e8696
Thu Apr 25 03:22:51 2013 VERIFY ERROR: depth=1, error=self signed certificate in certificate chain: /C=VN/ST=CA/L=HCM/O=VPN/CN=VPN_CA/emailAddress=ngockhanhqb@gmail.com
Thu Apr 25 03:22:51 2013 TLS_ERROR: BIO read tls_read_plaintext error: error:14090086:SSL routines:SSL3_GET_SERVER_CERTIFICATE:certificate verify failed
Thu Apr 25 03:22:51 2013 TLS Error: TLS object -> incoming plaintext read error
Thu Apr 25 03:22:51 2013 TLS Error: TLS handshake failed
Thu Apr 25 03:22:51 2013 TCP/UDP: Closing socket
Thu Apr 25 03:22:51 2013 SIGUSR1[soft,tls-error] received, process restarting
Thu Apr 25 03:22:51 2013 Restart pause, 2 second(s)
Thu Apr 25 03:22:53 2013 IMPORTANT: OpenVPN's default port number is now 1194, based on an official port number assignment by IANA.  OpenVPN 2.0-beta16 and earlier used 5000 as the default port.
Thu Apr 25 03:22:53 2013 Re-using SSL/TLS context
Thu Apr 25 03:22:53 2013 LZO compression initialized
Thu Apr 25 03:22:53 2013 Control Channel MTU parms [ L:1542 D:166 EF:66 EB:0 ET:0 EL:0 ]
Thu Apr 25 03:22:53 2013 Data Channel MTU parms [ L:1542 D:1450 EF:42 EB:135 ET:0 EL:0 AF:3/1 ]
Thu Apr 25 03:22:53 2013 Local Options hash (VER=V4): '504e774e'
Thu Apr 25 03:22:53 2013 Expected Remote Options hash (VER=V4): '14168603'
Thu Apr 25 03:22:53 2013 UDPv4 link local: [undef]
Thu Apr 25 03:22:53 2013 UDPv4 link remote: 192.168.1.200:1194
Thu Apr 25 03:22:53 2013 TCP/UDP: Closing socket
Thu Apr 25 03:22:53 2013 SIGTERM[hard,] received, process exiting