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
2015-06-05 09:08:38 -04:00
parent 32d241ec4c
commit 80a71e0fe5
1 changed files with 14 additions and 5 deletions
Download Patch File Download Diff File Expand all files Collapse all files

19
tunnels.cfg.md

@@ -3,8 +3,9 @@ Must be located in ~/.i2pd.
.ini file format.
Consists of multiple sections with unique name each.
Section type is specified by 'type' parameter with possible values 'client' or 'server'.
Section type is specified by 'type' parameter with possible values 'client', 'server' or 'http'.
Each 'client' specifies I2P client tunnel and each 'server' specifies I2P server tunnel.
'http' is special type of server tunnel for eepsites.
Must contain few mandatory parameters, some optional parameters might be also presented.
Example of client tunnel:
@@ -20,15 +21,23 @@ If keys file is not found, new keys will be created and store into specified fil
Client tunnels might share same local destination, if keys file contains same identity.
Example of server tunnel:
`[WWW]`
`[smtp]`
`type=server`
`host=127.0.0.1`
`port=80`
`keys=eepsite.dat`
`port=25`
`keys=sendmail.dat`
Keys must be presented, LeaseSet of address from keys file will be published.
Server tunnel must use it's own local destination.
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.
accesslist - list of comma-separated of b32 address (without .b32.i2p) allowed to connect. Everybody is allowed by default.
'http' tunnel works same way as server tunnel, but replace 'Host: ' field in HTTP header to address provided in configuration. Also resolves it if necessary.
Example of http tunnel:
`[i2pd]`
`type=http`
`host=i2pd.website`
`port=80`
`keys=i2pd.dat`