From 5ed71c83fe30e54cb6826e4491dc0116e09b4537 Mon Sep 17 00:00:00 2001 From: orignal Date: Fri, 13 Mar 2015 19:30:40 -0400 Subject: [PATCH] Updated tunnels.cfg (markdown) --- tunnels.cfg.md | 14 ++++++++------ 1 file changed, 8 insertions(+), 6 deletions(-) diff --git a/tunnels.cfg.md b/tunnels.cfg.md index 6b1e2d8..0196be1 100644 --- a/tunnels.cfg.md +++ b/tunnels.cfg.md @@ -1,13 +1,15 @@ tunnels.cfg is designed to support multiple I2P tunnels. Must be located in ~/.i2pd. -Consists of multiple [client] and [server] sections. -Each [client] specifies I2P client tunnel and each [server] specifies I2P server tunnel. +Consists of multiple sections with unique name each. +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: - `[client]` - `name=IRC` + `[IRC]` + `type=client` `port=6668` `destination=irc.echelon.i2p` `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. Example of server tunnel: - `[server]` - `name=WWW` + `[WWW]` + `type=server` `host=127.0.0.1` `port=80` `keys=eepsite.dat`