博客

[root@clu2 open***]# cat client.conf

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

# Sample client-side Open××× 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 .o*** 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 ××× 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 192.168.1.146 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 Open××× 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 Open×××

# 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 /etc/open***/ca.crt

cert /etc/open***/aaa.crt

key /etc/open***/aaa.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://open***.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 ××× 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

然后启动客户端

[root@clu2 open***]# /usr/local/sbin/open*** –config /etc/open***/client.conf

Sat Oct 17 17:23:39 2009 Open××× 2.0.9 i686-pc-linux [SSL] [LZO] [EPOLL] built on Oct 17 2009

Sat Oct 17 17:23:39 2009 IMPORTANT: Open×××’s default port number is now 1194, based on an official port number assignment by IANA.  Open××× 2.0-beta16 and earlier used 5000 as the default port.

Sat Oct 17 17:23:39 2009 WARNING: No server certificate verification method has been enabled.  See

http://open***.net/howto.html#mitm

for more info.

Sat Oct 17 17:23:39 2009 LZO compression initialized

Sat Oct 17 17:23:39 2009 Control Channel MTU parms [ L:1574 D:138 EF:38 EB:0 ET:0 EL:0 ]

Sat Oct 17 17:23:39 2009 RESOLVE: Cannot resolve host address: 192.l68.1.146: [TRY_AGAIN] A temporary error occurred on an authoritative name server.

Sat Oct 17 17:23:39 2009 Data Channel MTU parms [ L:1574 D:1450 EF:42 EB:135 ET:32 EL:0 AF:3/1 ]

Sat Oct 17 17:23:39 2009 Local Options hash (VER=V4): ‘d79ca330’

Sat Oct 17 17:23:39 2009 Expected Remote Options hash (VER=V4): ‘f7df56b8’

Sat Oct 17 17:23:39 2009 RESOLVE: Cannot resolve host address: 192.l68.1.146: [TRY_AGAIN] A temporary error occurred on an authoritative name server.

Sat Oct 17 17:23:44 2009 RESOLVE: Cannot resolve host address: 192.l68.1.146: [TRY_AGAIN] A temporary error occurred on an authoritative name server.

Sat Oct 17 17:23:49 2009 RESOLVE: Cannot resolve host address: 192.l68.1.146: [TRY_AGAIN] A temporary error occurred on an authoritative name server.

Sat Oct 17 17:23:54 2009 RESOLVE: Cannot resolve host address: 192.l68.1.146: [TRY_AGAIN] A temporary error occurred on an authoritative name server.

Sat Oct 17 17:23:59 2009 RESOLVE: Cannot resolve host address: 192.l68.1.146: [TRY_AGAIN] A temporary error occurred on an authoritative name server.

Sat Oct 17 17:24:04 2009 RESOLVE: Cannot resolve host address: 192.l68.1.146: [TRY_AGAIN] A temporary error occurred on an authoritative name server.

Sat Oct 17 17:24:09 2009 RESOLVE: Cannot resolve host address: 192.l68.1.146: [TRY_AGAIN] A temporary error occurred on an authoritative name server.

Sat Oct 17 17:24:14 2009 RESOLVE: Cannot resolve host address: 192.l68.1.146: [TRY_AGAIN] A temporary error occurred on an authoritative name server.

Sat Oct 17 17:24:19 2009 RESOLVE: Cannot resolve host address: 192.l68.1.146: [TRY_AGAIN] A temporary error occurred on an authoritative name server.

Sat Oct 17 17:24:24 2009 RESOLVE: Cannot resolve host address: 192.l68.1.146: [TRY_AGAIN] A temporary error occurred on an authoritative name server.

Sat Oct 17 17:24:29 2009 RESOLVE: Cannot resolve host address: 192.l68.1.146: [TRY_AGAIN] A temporary error occurred on an authoritative name server.

Sat Oct 17 17:24:34 2009 RESOLVE: Cannot resolve host address: 192.l68.1.146: [TRY_AGAIN] A temporary error occurred on an authoritative name server.

Sat Oct 17 17:24:39 2009 RESOLVE: Cannot resolve host address: 192.l68.1.146: [TRY_AGAIN] A temporary error occurred on an authoritative name server.

Sat Oct 17 17:24:44 2009 RESOLVE: Cannot resolve host address: 192.l68.1.146: [TRY_AGAIN] A temporary error occurred on an authoritative name server.

Sat Oct 17 17:24:49 2009 RESOLVE: Cannot resolve host address: 192.l68.1.146: [TRY_AGAIN] A temporary error occurred on an authoritative name server.

Sat Oct 17 17:24:50 2009 RESOLVE: signal received during DNS resolution attempt

Sat Oct 17 17:24:50 2009 TCP/UDP: Closing socket

Sat Oct 17 17:24:50 2009 SIGINT[hard,init_instance] received, process exiting

将客户端配置中的192.168.1.146,更改为CLU1后

[root@clu2 open***]# /usr/local/sbin/open*** –config /etc/open***/client.conf

Sat Oct 17 17:44:58 2009 Open××× 2.0.9 i686-pc-linux [SSL] [LZO] [EPOLL] built on Oct 17 2009

Sat Oct 17 17:44:58 2009 IMPORTANT: Open×××’s default port number is now 1194, based on an official port number assignment by IANA.  Open××× 2.0-beta16 and earlier used 5000 as the default port.

Sat Oct 17 17:44:58 2009 WARNING: No server certificate verification method has been enabled.  See

http://open***.net/howto.html#mitm

for more info.

Sat Oct 17 17:44:58 2009 LZO compression initialized

Sat Oct 17 17:44:58 2009 Control Channel MTU parms [ L:1574 D:138 EF:38 EB:0 ET:0 EL:0 ]

Sat Oct 17 17:44:58 2009 Data Channel MTU parms [ L:1574 D:1450 EF:42 EB:135 ET:32 EL:0 AF:3/1 ]

Sat Oct 17 17:44:58 2009 Local Options hash (VER=V4): ‘d79ca330’

Sat Oct 17 17:44:58 2009 Expected Remote Options hash (VER=V4): ‘f7df56b8’

Sat Oct 17 17:44:58 2009 UDPv4 link local: [undef]

Sat Oct 17 17:44:58 2009 UDPv4 link remote: 192.168.1.146:1194

Sat Oct 17 17:44:58 2009 TLS: Initial packet from 192.168.1.146:1194, sid=1c0c4a4a d6aa0664

Sat Oct 17 17:44:58 2009 VERIFY OK: depth=1,
/C=cn/ST=Beijing/L=haidian/O=llpw/OU=ca/CN=ca/emailAddress=database@bjepiao.com

Sat Oct 17 17:44:58 2009 VERIFY OK: depth=0,
/C=cn/ST=Beijing/O=llpw/OU=clu1/CN=clu1/emailAddress=database@bjepiao.com

Sat Oct 17 17:44:58 2009 Data Channel Encrypt: Cipher ‘BF-CBC’ initialized with 128 bit key

Sat Oct 17 17:44:58 2009 Data Channel Encrypt: Using 160 bit message hash ‘SHA1’ for HMAC authentication

Sat Oct 17 17:44:58 2009 Data Channel Decrypt: Cipher ‘BF-CBC’ initialized with 128 bit key

Sat Oct 17 17:44:58 2009 Data Channel Decrypt: Using 160 bit message hash ‘SHA1’ for HMAC authentication

Sat Oct 17 17:44:58 2009 Control Channel: TLSv1, cipher TLSv1/SSLv3 DHE-RSA-AES256-SHA, 1024 bit RSA

Sat Oct 17 17:44:58 2009 [clu1] Peer Connection Initiated with 192.168.1.146:1194

Sat Oct 17 17:44:59 2009 SENT CONTROL [clu1]: ‘PUSH_REQUEST’ (status=1)

Sat Oct 17 17:44:59 2009 PUSH: Received control message: ‘PUSH_REPLY,route-gateway 172.18.1.1,ping 10,ping-restart 120,ifconfig 172.18.1.10 255.255.255.0’

Sat Oct 17 17:44:59 2009 OPTIONS IMPORT: timers and/or timeouts modified

Sat Oct 17 17:44:59 2009 OPTIONS IMPORT: –ifconfig/up options modified

Sat Oct 17 17:44:59 2009 OPTIONS IMPORT: route options modified

Sat Oct 17 17:44:59 2009 TUN/TAP device tap0 opened

Sat Oct 17 17:44:59 2009 /sbin/ifconfig tap0 172.18.1.10 netmask 255.255.255.0 mtu 1500 broadcast 172.18.1.255

Sat Oct 17 17:44:59 2009 Initialization Sequence Completed

以上可以发现已成功发送×××地址，总结如下：

OPEN×××会优先走DNS解析，然后才走IP，在这种情况下，如果本机对此IP地址有解析，应该优先使用域名解析。