From Newsgroup: rocksolid.shared.i2p
I'm running Debian's i2pd-2.53.0-1 on Debian11/amd64, Devuan12/armel and Devuan12/armhf and (Surprise!) I've questions.
W3M's output of <
http://localhost:7070> (with tunnels "renamed"): ------------------------------------------------------------------------
i2pd webconsole
Main page
Router commands
Local Destinations
Tunnels
Transit Tunnels
Transports
I2P tunnels
SAM sessions
Client Tunnels:
IRC-ILITA rcE aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa.b32.i2p
HTTP Proxy rcE bbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbb.b32.i2p SOCKS Proxy rcE bbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbb.b32.i2p
Server Tunnels:
kumari_ssh rcA cccccccccccccccccccccccccccccccccccccccccccccccccccc.b32.i2p:22 ------------------------------------------------------------------------
(On the ARMish systems I've web server tunnels too.)
1. The tunnel config for ILITA has only commented lines on all of my
systems because I prefer to use the socks proxy for IRC. Why is that
tunnel active on every system I run I2PD on? It even stays active
when its config file is removed. That just does not feel right.
2. I see the HTTP and SOCKs proxy use the same "address" and sure they
use different ports. So I tried to run the HTTP and SSH with the
same key.dat file and it works too.
Because I'm not trying to hide and just want constant addresses from
I2P(D), for some systems having only one address might be nicer for
my neighbours connecting to them.
Is there a reason *not* to do this?
--
2. Hitchhiker 17: (110) "Careful with that hammer, sir," he said.
--- Synchronet 3.21a-Linux NewsLink 1.2