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

Updated tunnels.cfg (markdown)

orignal
2016-01-03 21:55:13 -05:00
parent 7235661f0d
commit 297d85e000
1 changed files with 7 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files

11
tunnels.cfg.md

@@ -23,11 +23,14 @@ Example of client tunnel:
destination = irc.echelon.i2p
keys = irc.dat
If 'keys' is empty, transient keys will be created on every restart. If keys file is not found, new keys will be created and store into specified file.
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.
'address' means local interface tunnel binds to, '127.0.0.1' for connections from local host only, '0.0.0.0' for connections from everywhere.
Optional parameters:
'address' means 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' means 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.
So, with example above, if you telnet to 127.0.0.1:6668 on localhost, i2pd will connect to irc.echelon.i2p:6668
@@ -49,8 +52,8 @@ Example of server tunnel:
Optional parameters:
'inport' - what port at local destination server tunnel listens to. Same as 'port' by default.
'accesslist' - list of comma-separated of b32 address (without .b32.i2p) allowed to connect. Everybody is allowed by default.
'signaturetype' means signature type for new keys. 0 - DSA, 1- ECDSA-P256, 7 -EDDSA. 1 by default.
Server/http tunnels
-------------------