e1lama/i2pd
1
0
Fork 0
mirror of https://github.com/PurpleI2P/i2pd.git synced 2025-03-07 06:09:42 +00:00
Code Issues Packages Projects Releases Wiki Activity

notes about matchtunnels option

Jeff
2017-09-03 12:20:33 -04:00
parent f8d87cb5b0
commit 6ab21587a8
1 changed files with 4 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
tunnels.conf.md

@@ -22,6 +22,7 @@ Example of client tunnel:
port = 6668
destination = irc.echelon.i2p
keys = irc.dat
matchtunnels = true
If *keys* is empty, transient keys will be created on every restart. If keys file is not found, new keys will be created and stored into specified file.
Client tunnels might share same local destination, if keys file contains same identity.
@@ -31,6 +32,7 @@ Optional parameters:
* address -- local interface tunnel binds to, '127.0.0.1' for connections from local host only, '0.0.0.0' for connections from everywhere. '127.0.0.1' by default.
* signaturetype -- signature type for new keys. 0 (DSA), 1 (ECDSA-P256), 7 (EDDSA). 1 by default
* destinationport -- connect to particular port at destination. 0 by default
* matchtunnels -- align our outbound tunnels with remote's inbound tunnels (experimental but improves latency) currently only applicable with `client` and `udpclient`
So, with example above, if you telnet to 127.0.0.1:6668 on localhost, i2pd will connect to irc.echelon.i2p:6668
@@ -99,11 +101,13 @@ There are 2 types of UDP tunnels: `udpclient` and `udpserver`
type = udpclient
destination = something.b32.i2p
port = 1194
matchtunnels = true
* destination -- the i2p destination of a udpserver tunnel, required parameter
* address -- ip address to bind local udp endpoint to, defaults to `127.0.0.1`
* port -- port to bind local udp endpoint to, required parameter
* matchtunnels -- align our outbound tunnels with the remote destination's inbound tunnels. very useful with `udpclient`
`udpserver` forwards traffic from N i2p destinations to 1 local udp endpoint