Hi, On 12/01/15 16:26, Alfredo Palhares wrote: > Hello, > >> you would have to use a different client configuration for each client, >> tied to the corresponding obfsproxy config. You can bind a client to a >> specific port using >> lport XXXXX >> where XXXXX is a port number > 1024 > So, I would need to have an obfsproxy for the server and **one for each > client** ?? > > That seems a bit counterproductive. > if obfsproxy can not deal with a "dynamic" client connection (that is, you do not know the client side port in advance) then yes, this is indeed necessary, unfortunately.
Alternatively you could try using socat , which offers socks4 support, to convert obfsproxy socks4 calls to socat to openvpn TCP. HTH, JJK ------------------------------------------------------------------------------ New Year. New Location. New Benefits. New Data Center in Ashburn, VA. GigeNET is offering a free month of service with a new server in Ashburn. Choose from 2 high performing configs, both with 100TB of bandwidth. Higher redundancy.Lower latency.Increased capacity.Completely compliant. vanity: www.gigenet.com _______________________________________________ Openvpn-users mailing list Openvpn-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/openvpn-users
