我已經能連上SERVER了(感謝樓主 )
不過不知道為什麼網芳，跳版都不行
以下是SERVER LOG

Mon Sep 08 07:48:57 2008 OpenVPN 2.0.9 Win32-MinGW [SSL] [LZO] built on Oct  1 2006
Mon Sep 08 07:48:57 2008 Diffie-Hellman initialized with 2048 bit key
Mon Sep 08 07:48:57 2008 TLS-Auth MTU parms [ L:1544 D:140 EF:40 EB:0 ET:0 EL:0 ]
Mon Sep 08 07:48:57 2008 TAP-WIN32 device [MyTap] opened: \\.\Global\{5831788D-3824-4099-AD37-43C2C2D51509}.tap
Mon Sep 08 07:48:57 2008 TAP-Win32 Driver Version 8.4
Mon Sep 08 07:48:57 2008 TAP-Win32 MTU=1500
Mon Sep 08 07:48:57 2008 Notified TAP-Win32 driver to set a DHCP IP/netmask of 192.168.5.1/255.255.255.252 on interface {5831788D-3824-4099-AD37-43C2C2D51509} [DHCP-serv: 192.168.5.2, lease-time: 31536000]
Mon Sep 08 07:48:57 2008 Sleeping for 10 seconds...
Mon Sep 08 07:49:07 2008 NOTE: FlushIpNetTable failed on interface [3] {5831788D-3824-4099-AD37-43C2C2D51509} (status=1413) : 無效的索引。  
Mon Sep 08 07:49:07 2008 route ADD 192.168.5.0 MASK 255.255.255.0 192.168.5.2
Mon Sep 08 07:49:07 2008 Route addition via IPAPI succeeded
Mon Sep 08 07:49:07 2008 Data Channel MTU parms [ L:1544 D:1450 EF:44 EB:135 ET:0 EL:0 AF:3/1 ]
Mon Sep 08 07:49:07 2008 Listening for incoming TCP connection on [undef]:1194
Mon Sep 08 07:49:07 2008 TCPv4_SERVER link local (bound): [undef]:1194
Mon Sep 08 07:49:07 2008 TCPv4_SERVER link remote: [undef]
Mon Sep 08 07:49:07 2008 MULTI: multi_init called, r=256 v=256
Mon Sep 08 07:49:07 2008 IFCONFIG POOL: base=192.168.5.4 size=62
Mon Sep 08 07:49:07 2008 MULTI: TCP INIT maxclients=10 maxevents=14
Mon Sep 08 07:49:07 2008 Initialization Sequence Completed
Mon Sep 08 08:05:05 2008 MULTI: multi_create_instance called
Mon Sep 08 08:05:05 2008 Re-using SSL/TLS context
Mon Sep 08 08:05:05 2008 LZO compression initialized
Mon Sep 08 08:05:05 2008 Control Channel MTU parms [ L:1544 D:140 EF:40 EB:0 ET:0 EL:0 ]
Mon Sep 08 08:05:05 2008 Data Channel MTU parms [ L:1544 D:1450 EF:44 EB:135 ET:0 EL:0 AF:3/1 ]
Mon Sep 08 08:05:05 2008 Local Options hash (VER=V4): 'c0103fa8'
Mon Sep 08 08:05:05 2008 Expected Remote Options hash (VER=V4): '69109d17'
Mon Sep 08 08:05:05 2008 TCP connection established with XXX.XXX.XXX.XXX:60707
Mon Sep 08 08:05:05 2008 TCPv4_SERVER link local: [undef]
Mon Sep 08 08:05:05 2008 TCPv4_SERVER link remote: XXX.XXX.XXX.XXX:60707
Mon Sep 08 08:05:05 2008 XXX.XXX.XXX.XXX:60707 TLS: Initial packet from XXX.XXX.XXX.XXX:60707, sid=24876ed9 95501780
Mon Sep 08 08:05:17 2008 XXX.XXX.XXX.XXX:60707 VERIFY OK: depth=1, /C=TW/ST=TW/L=TaiPei/O=home/OU=A/CN=home/emailAddress=xxx@xxxx.com
Mon Sep 08 08:05:17 2008 XXX.XXX.XXX.XXX:60707 VERIFY OK: depth=0, /C=TW/ST=TW/O=home/OU=B/CN=maohunter/emailAddress=xxx@xxx.com.tw
Mon Sep 08 08:05:19 2008 XXX.XXX.XXX.XXX:60707 Data Channel Encrypt: Cipher 'BF-CBC' initialized with 128 bit key
Mon Sep 08 08:05:19 2008 XXX.XXX.XXX.XXX:60707 Data Channel Encrypt: Using 160 bit message hash 'SHA1' for HMAC authentication
Mon Sep 08 08:05:19 2008 XXX.XXX.XXX.XXX:60707 Data Channel Decrypt: Cipher 'BF-CBC' initialized with 128 bit key
Mon Sep 08 08:05:19 2008 XXX.XXX.XXX.XXX:60707 Data Channel Decrypt: Using 160 bit message hash 'SHA1' for HMAC authentication
Mon Sep 08 08:05:20 2008 XXX.XXX.XXX.XXX:60707 Control Channel: TLSv1, cipher TLSv1/SSLv3 DHE-RSA-AES256-SHA, 2048 bit RSA
Mon Sep 08 08:05:20 2008 XXX.XXX.XXX.XXX:60707 [maohunter] Peer Connection Initiated with XXX.XXX.XXX.XXX:60707
Mon Sep 08 08:05:20 2008 maohunter/XXX.XXX.XXX.XXX:60707 MULTI: Learn: 192.168.5.6 -> maohunter/XXX.XXX.XXX.XXX:60707
Mon Sep 08 08:05:20 2008 maohunter/XXX.XXX.XXX.XXX:60707 MULTI: primary virtual IP for maohunter/XXX.XXX.XXX.XXX:60707: 192.168.5.6
Mon Sep 08 08:05:21 2008 maohunter/XXX.XXX.XXX.XXX:60707 PUSH: Received control message: 'PUSH_REQUEST'
Mon Sep 08 08:05:21 2008 maohunter/XXX.XXX.XXX.XXX:60707 SENT CONTROL [maohunter]: 'PUSH_REPLY,route 192.168.5.0 255.255.255.0,redirect-gateway,route 192.168.5.1,ping 10,ping-restart 120,ifconfig 192.168.5.6 192.168.5.5' (status=1)

CLIENT LOG

Mon Sep 08 08:45:51 2008 OpenVPN 2.0.9 Win32-MinGW [SSL] [LZO] built on Oct  1 2006
Mon Sep 08 08:45:51 2008 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.
Mon Sep 08 08:45:51 2008 WARNING: No server certificate verification method has been enabled.  See http://openvpn.net/howto.html#mitm for more info.
Mon Sep 08 08:45:51 2008 LZO compression initialized
Mon Sep 08 08:45:51 2008 Control Channel MTU parms [ L:1544 D:140 EF:40 EB:0 ET:0 EL:0 ]
Mon Sep 08 08:45:51 2008 Data Channel MTU parms [ L:1544 D:1450 EF:44 EB:135 ET:0 EL:0 AF:3/1 ]
Mon Sep 08 08:45:51 2008 Local Options hash (VER=V4): '69109d17'
Mon Sep 08 08:45:51 2008 Expected Remote Options hash (VER=V4): 'c0103fa8'
Mon Sep 08 08:45:51 2008 Attempting to establish TCP connection with XXX.XXX.XXX.XXX:1194
Mon Sep 08 08:45:52 2008 TCP connection established with XXX.XXX.XXX.XXX:1194
Mon Sep 08 08:45:52 2008 TCPv4_CLIENT link local: [undef]
Mon Sep 08 08:45:52 2008 TCPv4_CLIENT link remote: XXX.XXX.XXX.XXX:1194
Mon Sep 08 08:45:52 2008 TLS: Initial packet from XXX.XXX.XXX.XXX:1194, sid=51a39c05 7d913ddc
Mon Sep 08 08:45:57 2008 VERIFY OK: depth=1, /C=TW/ST=TW/L=TaiPei/O=home/OU=A/CN=mao/emailAddress=xxx@xxxx.com
Mon Sep 08 08:45:57 2008 VERIFY OK: depth=0, /C=TW/ST=TW/O=home/OU=A/CN=mao/emailAddress=xxx@xxxx.com
Mon Sep 08 08:46:05 2008 Data Channel Encrypt: Cipher 'BF-CBC' initialized with 128 bit key
Mon Sep 08 08:46:05 2008 Data Channel Encrypt: Using 160 bit message hash 'SHA1' for HMAC authentication
Mon Sep 08 08:46:05 2008 Data Channel Decrypt: Cipher 'BF-CBC' initialized with 128 bit key
Mon Sep 08 08:46:05 2008 Data Channel Decrypt: Using 160 bit message hash 'SHA1' for HMAC authentication
Mon Sep 08 08:46:05 2008 Control Channel: TLSv1, cipher TLSv1/SSLv3 DHE-RSA-AES256-SHA, 2048 bit RSA
Mon Sep 08 08:46:05 2008 [mao] Peer Connection Initiated with XXX.XXX.XXX.XXX:1194
Mon Sep 08 08:46:07 2008 SENT CONTROL [mao]: 'PUSH_REQUEST' (status=1)
Mon Sep 08 08:46:07 2008 PUSH: Received control message: 'PUSH_REPLY,route 192.168.5.0 255.255.255.0,redirect-gateway,route 192.168.5.1,ping 10,ping-restart 120,ifconfig 192.168.5.6 192.168.5.5'
Mon Sep 08 08:46:07 2008 OPTIONS IMPORT: timers and/or timeouts modified
Mon Sep 08 08:46:07 2008 OPTIONS IMPORT: --ifconfig/up options modified
Mon Sep 08 08:46:07 2008 OPTIONS IMPORT: route options modified
Mon Sep 08 08:46:07 2008 TAP-WIN32 device [MyTap] opened: \\.\Global\{60447443-0155-484F-957C-9F94E24271F1}.tap
Mon Sep 08 08:46:07 2008 TAP-Win32 Driver Version 8.4
Mon Sep 08 08:46:07 2008 TAP-Win32 MTU=1500
Mon Sep 08 08:46:07 2008 Notified TAP-Win32 driver to set a DHCP IP/netmask of 192.168.5.6/255.255.255.252 on interface {60447443-0155-484F-957C-9F94E24271F1} [DHCP-serv: 192.168.5.5, lease-time: 31536000]
Mon Sep 08 08:46:07 2008 Successful ARP Flush on interface [3] {60447443-0155-484F-957C-9F94E24271F1}
Mon Sep 08 08:46:07 2008 TEST ROUTES: 0/0 succeeded len=2 ret=0 a=0 u/d=down
Mon Sep 08 08:46:07 2008 Route: Waiting for TUN/TAP interface to come up...
Mon Sep 08 08:46:09 2008 TEST ROUTES: 0/0 succeeded len=2 ret=0 a=0 u/d=down
Mon Sep 08 08:46:09 2008 Route: Waiting for TUN/TAP interface to come up...
Mon Sep 08 08:46:10 2008 TEST ROUTES: 0/0 succeeded len=2 ret=0 a=0 u/d=down
Mon Sep 08 08:46:10 2008 Route: Waiting for TUN/TAP interface to come up...
Mon Sep 08 08:46:11 2008 TEST ROUTES: 0/0 succeeded len=2 ret=0 a=0 u/d=down
Mon Sep 08 08:46:11 2008 Route: Waiting for TUN/TAP interface to come up...
Mon Sep 08 08:46:12 2008 TEST ROUTES: 3/3 succeeded len=2 ret=1 a=0 u/d=up
Mon Sep 08 08:46:12 2008 route ADD XXX.XXX.XXX.XXX MASK 255.255.255.255 192.168.0.1
Mon Sep 08 08:46:12 2008 Route addition via IPAPI succeeded
Mon Sep 08 08:46:12 2008 route DELETE 0.0.0.0 MASK 0.0.0.0 192.168.0.1
Mon Sep 08 08:46:12 2008 Route deletion via IPAPI succeeded
Mon Sep 08 08:46:12 2008 route ADD 0.0.0.0 MASK 0.0.0.0 192.168.5.5
Mon Sep 08 08:46:12 2008 Route addition via IPAPI succeeded
Mon Sep 08 08:46:12 2008 route ADD 192.168.5.0 MASK 255.255.255.0 192.168.5.5
Mon Sep 08 08:46:12 2008 Route addition via IPAPI succeeded
Mon Sep 08 08:46:12 2008 route ADD 192.168.5.1 MASK 255.255.255.255 192.168.5.5
Mon Sep 08 08:46:12 2008 Route addition via IPAPI succeeded
Mon Sep 08 08:46:12 2008 Initialization Sequence Completed

===修改e-mail address===
By SSE-CMM，我已經寄信給您，請您將私密資料刪除後，
再傳設定檔給我；

最近在忙proxy設定問題，
暫時比較沒空喔，不好意思嘿^^"

[ 本文最後由 sse-cmm 於 2008-9-8 18:30 編輯 ]

請問，
不知道您跳版是要來作啥的？

目前因公司需求，
急需架設proxy伺服器，
我剛研究出來，它這套軟體可以達到PROXY伺服器的用途，
JanaServer 2官網

除了proxy，還有：
smtp、mail、dns等相關功能(但這些我用不到，就沒研究)，
需要的話，我看情況再放教學上來。

這套軟體很小，若是個人、學校、非營利單位都算是免費軟體喔！
我研究約半天就架好了，不過，安裝時最好別選中文，
因為只有簡中，並無正體中文喔。

目前還在等您傳設定檔給我看。
(除非您上面留的mail是錯的，哈)

===9/12新增文章如下：===

這真的很神奇耶，
是因為我一開始無線沒關，
所以導致使用tun模式出問題？
現在使用tun可以連到server網芳了，

從tap改為tun後，記錄上確實也會有問題，
(不過，看記錄應該是server與用戶端同個網段造成的)
不過，連線是沒問題的喔。

目前跳板還是沒能成功耶，
我明天再找間試看看囉。
不過，我上網找了資料，
不知道底下的資料是不是能讓您使用喔。

CCPROXY使用教學，可玩WOW當跳板

先回應一下資料，
有空我再整理刪除我的回文。

目前找到一些資料，但都是英文，
需要點時間消化：

Overall, routing is probably a better choice for most people, as it is more efficient and easier to set up (as far as the OpenVPN configuration itself) than bridging. Routing also provides a greater ability to selectively control access rights on a client-specific basis.
總之，對多數人而言，就更有效率及容易設定下(就OpenVPN自我配置下)，routing比橋接模式大概是一個較好的選擇。routing在用戶端指定基礎下也提供一個更大的能力可選擇性的控制存取權。

I would recommend using routing unless you need a specific feature which requires bridging, such as:
我會推薦使用routing，除非您需要以下一個具體特點才會要用橋接模式，例如：

    * the VPN needs to be able to handle non-IP protocols such as IPX,
    * you are running applications over the VPN which rely on network broadcasts (such as LAN games), or
    * you would like to allow browsing of Windows file shares across the VPN without setting up a Samba or WINS server.
    * VPN需要能處理非IP協議例如IPX，
    * 您在網路廣播(例如LAN遊戲)中在VPN上執行應用程式，或者
    * 您希望不需設定Samba或WINS伺服器就能透過VPN允許瀏覽Windows檔案分享。

由此看來，似乎二位都得使用橋接模式比較適合？

bridging跟routing的差異

嗯，太晚了，先這樣吧，有空再修改、刪除回文。

[ 本文最後由 sse-cmm 於 2008-9-14 19:12 編輯 ]

剛剛發現一套軟體，竟然也是使用openvpn作vpn耶，
不過，不用設定是個不錯的部份，
但裡面有沒有被加料我不清楚，
想玩的話：

Hotspot Shield官網

下載下來後，這套軟體有點討厭，一堆廣告軟體，
所以，在安裝時，我沒記錯的話，
只需第一個按同意，其它都不要！

不然會被裝一堆討人厭的玩意。
裝完後，類似openvpn gui會有個小圖示在右下角，
可以選connect跟伺服器連結，
因為資料都已寫入，所以，不用管設定，
如果你有防火牆，
就會發現防火牆告知有新軟體(openvpn)要求連線，

此時放通行後，會向伺服器登入，
並更新openvpn，防火牆又會再警告一次，
若是上網的話，會在最上面出現要邀請的畫面也是可以關掉的，

你可以發現，你的ip都是伺服器的ip，
剛我要試著登入巴哈，就不行，
因為之前曾設過只允許國內ip，所以就無法登入。

但我不清楚是否能玩線上遊戲，
等等我再試看看其它協定是否也變成跳版，再修改內文。

剛試過，玩wow的話，
應該是可以的，但因伺服器在國外，
所以連線品質......未知(因為我還是不敢輸入帳密啦)

===

不過，我是不敢確定它這個包的openvpn是不是一樣的，
是有很大的可能是不太一樣的，
有可能只是取相同程式名字而已喔。

===
根據這篇文章：
http://forum.slime.com.tw/thread165780.html

若想要跳版玩遊戲，
可以使用遊戲又不支持普通HTTP代理。
這種情況可以用SOCKS代理......

若是這樣，可以參考我上面所貼的ccproxy，
我記得它有支援socks代理，
只不過，我裝好的電腦具還原功能，
又，颱風天有停電，所以目前不能幫你測試喔。

我已經試出來，要如何在伺服器設定tap模式了，
但因為我的nb一直無法使用橋接模式，
一直出現：「設定網路橋接器時發生意外的錯誤」，
查了微軟文章，
卻是一點用都沒有，唉~~

[ 本文最後由 sse-cmm 於 2008-9-14 21:36 編輯 ]

最後測試完畢後，會將我所有的回文作一總整理(刪除)，
不好意思......

最近可能是老年痴呆症又發作了，
弄好了這邊，那邊又忘了設定，
然後生這套軟體怎麼這麼難設定，
結果是我的問題，唉~~~~

我先不抓圖，若真的需要再回文吧，
我儘量寫清楚一點，

要架橋架模式的話，
必須先在「網路連線」作一些設定，
(「網路上的芳鄰」按右鍵選「內容」就是啦)

首先，將「區域連線 x」(TAP-Win32 Adapter V8)這個網路連線改名為：
MyTAP

接下來，將「區域連線」、「MyTAP」一起選起來(也就是使用Ctrl鍵啦)，
選完後，右鍵點下去，選「橋接器連線」，
此時會視電腦速度，1x秒到1分都有可能，

成功架好橋接器後，會在「網路連線」中，
多出一個「橋接器？」(不好意思，因為我改名了，
所以正確的名字忘了)

請先把它改名為：「OpenVPN Bridge」

接下來，將這個多出來的網路連線「OpenVPN Bridge」按右鍵選「內容」，
重點來了，不知道是不是因為xp spx版本的不同，
因為網路上找的資料都是直接改裡面的tcp/ip值，
但我一直試不出來，結果不知道怎麼回事，
點下「其它設定」標籤後，一切都明朗了起來，

原來，並不是直接在一般那邊更改tcp/ip值，
否則會連server都連不上網路啦！

當然，如果你的ip是真實ip的話，
一定要在「一般」這邊設定真實ip，

設定完後，切到「其它設定」，
選「使用者設定」，
ip位址，設為：192.168.8.4
子網路遮罩為：255.255.255.0
目前gateway我是設定為ip分享器，有可能還是留空，
這部份我還在測。

接下來的dns部份，就設定你的isp公司的dns主機囉。

如此一來，server端的網路，差不多設定完成了，
測試一下server能不能上網，應該是可以才對。

接下來，server端的設定如下：
# Which local IP address should OpenVPN
# listen on? (optional)我mark起來，讓它自動偵測ip
; local

# 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設定埠號，因為1194被我另一台使用了，ip分享器不能再指定這個埠號所以改用2000
port 2000

# TCP or UDP server?我記得看文章，tap模式得使用tcp喔？
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這邊是因為我們要測tap模式，當然就不用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.後面這個參數就是上面我們改掉openvpn預設連線的名稱
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.使用tap模式就不能使用server參數，相反亦然
; server 10.8.0.0 255.255.255.0
; server 192.168.2.0 255.255.255.0
; server 192.168.8.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.使用tap模式就得使用server-bridge參數，相反亦然
; server-bridge 10.8.0.4 255.255.255.0 10.8.0.50 10.8.0.100
; server-bridge 192.168.2.1 255.255.255.0 192.168.2.2 192.168.2.255
server-bridge 192.168.8.4 255.255.255.0 192.168.8.128 192.168.8.254

# 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.8.0 255.255.255.0"
;push "route 10.8.0.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.8.0 255.255.255.0
# 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.強制用戶端轉向gateway變server端以達到跳板目的
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強制用戶端改用server端的dns
push "dhcp-option DNS 168.95.1.1"
push "dhcp-option DNS 168.95.121.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
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
;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


以上是server端的設定，
因為我很白痴，在公司忘了改連接的ip，
應該要改為domain name才能連，
所以，得等明天再來測試了。

我在家測試因為NB還是無法作橋接器的設定，
所以，雖然有連到server，但還是無法正常運作。
(不管是在內網，還是使用ADSL撥接再連亦然)，
所以，我對我的NB已經投降了，測那麼多天我也......

===新增如下===

我舉雙手投降了，
可能server端使用linux比較適合吧？
server端使用windows，真的會「昏到死」~~

我有空玩一台ubuntu後，再看看是不是比較好用，
不然我已經要宣告windows下架openvpn是件超難過的事了，唉~~

[ 本文最後由 sse-cmm 於 2008-9-16 20:28 編輯 ]

我都照著第一篇來做
SERVER OK了
CLIENT 也可以連上去
可以同時2個以上連上去
但是
網芳就是沒有辦法開
可以PING的到

都照第一篇的話，
那就是使用tun模式，沒有使用跳板囉？
即然ping的到？那為何網芳沒辦法連呢？

請問，您xp的防火牆有關掉嗎？

我試過了
沒用防火牆真的可以
但是我把防火牆例外
加openvpn.exe
位什麼也是不行??
那要加什麼例外勒??

[ 本文最後由 asd301171 於 2008-9-19 00:22 編輯 ]

請問，您是使用xp內建的防火牆嗎？
那就要再開「檔案及印表機共用」這個才能使用網芳，
若不是內建防火牆，就需要設定port，需要再說，
我再貼port。

若您的例外沒有出現這個的話，
請用精靈將您的防火牆設定打洞囉。

我都有勾選了
但是還是連不到
不知道為什麼

請問，您還有使用別的防火牆嗎？

在openvpn官網的說明，是將虛擬網卡部份取消防火牆啦，
因為只有您作的認証的資料才能連入，
除非您是給很多人使用同一個帳號，
像這種就要防帳號外流的情況，

一般而言，一旦建好虛擬ip連線，
虛擬網段可以不用特別使用防火牆，
除非有人中毒就比較危險。

還有，若您的server端有養動物或使用BT等軟體，
最好找一下軟體，將半連線狀態10連線的部份加大一點，
之前發現若沒加大，很可能雖然暫時連線成功，
但也可能因為養動物、BT的關係，之後連線會失敗的機率蠻大的。
(這是微軟在XP sp2以上的樣子，推出來防病毒的爛點子)
我好像設2000吧？

[ 本文最後由 sse-cmm 於 2008-9-21 17:21 編輯 ]