j3d1/tinc
1
0
Fork 0
Code Issues 1 Pull requests Releases Wiki Activity

Add basic support for SOCKS 4 and HTTP CONNECT proxies.

Browse source 
When the Proxy option is used, outgoing connections will be made via the
specified proxy. There is no support for authentication methods or for having
the proxy forward incoming connections, and there is no attempt to proxy UDP.
This commit is contained in:
Guus Sliepen 2012-04-18 23:19:40 +02:00
parent 84531fb6e6
commit b58d95eb29
8 changed files with 211 additions and 10 deletions
Download patch file Download diff file Expand all files Collapse all files

19
doc/tinc.texi
View file

@ -1050,6 +1050,25 @@ specified in the configuration file.
When this option is used the priority of the tincd process will be adjusted.
Increasing the priority may help to reduce latency and packet loss on the VPN.
@cindex Proxy
@item Proxy = <@var{type}> <@var{address}> <@var{port}> [<@var{username}>] [experimental]
Use the proxy at the given @var{address} and @var{port} when making outgoing connections.
The following proxy types are currently supported:
@table @asis
@cindex socks4
@item socks4
Connects to the proxy using the SOCKS version 4 protocol.
Optionally, a @var{username} can be supplied which will be passed on to the proxy server.
@cindex http
@item http
Connects to the proxy and sends a HTTP CONNECT request.
@end table
No authentication methods are currently supported.
@cindex ReplayWindow
@item ReplayWindow = <bytes> (16)
This is the size of the replay tracking window for each remote node, in bytes.