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-03-13 19:30:40 -04:00
parent f3b77b42fb
commit 5ed71c83fe
1 changed files with 8 additions and 6 deletions
Download Patch File Download Diff File Expand all files Collapse all files

14
tunnels.cfg.md

@@ -1,13 +1,15 @@
tunnels.cfg is designed to support multiple I2P tunnels. tunnels.cfg is designed to support multiple I2P tunnels.
Must be located in ~/.i2pd. Must be located in ~/.i2pd.
Consists of multiple [client] and [server] sections. Consists of multiple sections with unique name each.
Each [client] specifies I2P client tunnel and each [server] specifies I2P server tunnel. Section type is specified by 'type' parameter with possible values 'client' or 'server'.
Each 'client' specifies I2P client tunnel and each 'server' specifies I2P server tunnel.
Must contain few mandatory parameters, some optional parameters might be also presented.
Example of client tunnel: Example of client tunnel:
`[client]` `[IRC]`
`name=IRC` `type=client`
`port=6668` `port=6668`
`destination=irc.echelon.i2p` `destination=irc.echelon.i2p`
`keys=irc.dat ` `keys=irc.dat `
@@ -17,8 +19,8 @@ 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. Client tunnels might share same local destination, if keys file contains same identity.
Example of server tunnel: Example of server tunnel:
`[server]` `[WWW]`
`name=WWW` `type=server`
`host=127.0.0.1` `host=127.0.0.1`
`port=80` `port=80`
`keys=eepsite.dat` `keys=eepsite.dat`