From 2a4e8cabad7b5e3d55c4bd2e9baca43649244072 Mon Sep 17 00:00:00 2001 From: hagen Date: Wed, 9 Dec 2015 09:47:55 +0000 Subject: [PATCH] * tunnels.cfg --- tunnels.cfg.md | 18 +++++++++--------- 1 file changed, 9 insertions(+), 9 deletions(-) diff --git a/tunnels.cfg.md b/tunnels.cfg.md index a658968..4da72b8 100644 --- a/tunnels.cfg.md +++ b/tunnels.cfg.md @@ -10,18 +10,18 @@ Section type is specified by 'type' parameter with possible values 'client', 's Client tunnels -------------- -Mnemonic: WE can connect to someone as client +Mnemonic: we can connect to someone as client Must contain few mandatory parameters, some optional parameters might be also presented. Example of client tunnel: - [irc-out] - type = client - address = 127.0.0.1 - port = 6668 - destination = irc.echelon.i2p - keys = irc.dat + [irc-out] + type = client + address = 127.0.0.1 + port = 6668 + 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. @@ -29,12 +29,12 @@ Client tunnels might share same local destination, if keys file contains same id '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. -So, if we telnet to 127.0.0.1/6668 on localhost, i2pd will connect us to irc.echelon.i2p:6668 +So, with example above, if you telnet to 127.0.0.1:6668 on localhost, i2pd will connect to irc.echelon.i2p:6668 Server/generic tunnels ---------------------- -Mnemonic: WE serving some service to others in network +Mnemonic: we serving some service to others in network Example of server tunnel: