Changes between Version 4 and Version 5 of TrafficObfuscation

Timestamp:

02/13/13 20:21:59 (11 years ago)

Author:

David Sommerseth

Comment:

Added example on how to use obfsproxy

TrafficObfuscation

@@ -31 +31 @@
 }}}
 
+
+== A quick obfsproxy setup ==
+
+This setup will start obfsproxy on your openvpn server, listening to the port 21194.  On the client it will start a obfsproxy serving as a SOCKS proxy, listening on the client on port 10194.  The part which says "<some-random-key>" needs to be the same value on both server and client.  The key can be a longer text string, with just random letters.  I'd recommend to keep it long (at least 32 characters, which is 256 bits).
+
+=== Client side ===
+Add the following lines to your existing openvpn config file:
+
+{{{
+socks-proxy-retry
+socks-proxy 127.0.0.1 10194
+}}}
+
+and change the --remote option to be
+{{{
+remote <YOUR-VPN-SERVER> 21194
+}}}
+
+That is, changing the port number to match the port number the server side obfsproxy will listen to.
+
+Then start the obfsproxy like this:
+
+{{{
+ [user@host: ~] $ obfsproxy --log-file=obfsproxy.log --log-min-severity=info obfs2 \
+      --shared-secret=<some-random-key> socks 127.0.0.1:10194
+}}}
+
+=== Server side ===
+Here we tell obfsproxy to listen to TCP port 21194 and to send any obfsproxy clients to the OpenVPN server, listening on 127.0.0.1, port 1194.  And remember to allow TCP connections from the "outside" to port 21194 in your firewall config.  Start obfsproxy like this:
+{{{
+ [user@host: ~] $ obfsproxy --log-file=obfsproxy.log --log-min-severity=info obfs2 \
+      --dest=127.0.0.1:1194 --shared-secret=<some-random-key> server 0.0.0.0:21194
+}}}
+
+The OpenVPN server needs in this case just this line in the config:
+{{{
+port 1194
+}}}
+
+That's all the magic, and should be a complete working setup.
+
 A user provided an OpenVPN installer which bundles OpenVPN with obfsproxy. Look [http://sourceforge.net/mailarchive/message.php?msg_id=28851866 here] for downloads and instructions.
-