Opened 5 years ago

Last modified 4 years ago

#1585 open defect

Tunnels can be built even without any peers?

Reported by: killyourtv Owned by: zzz
Priority: minor Milestone: undecided
Component: router/general Version: 0.9.19
Keywords: Cc:
Parent Tickets: Sensitive: no

Description

While testing something in Tails I sabotaged I2P by setting it to reseed from a server that can't be reached.

Reseeding failed, as expected, but I see

Exploratory: 6
Client: 3

and a green star next to the Shared Clients tunnel, but there are absolutely no peers.

I'm filing this as a bug because I don't see how tunnels can be built without peers to connect to, but maybe I'm misunderstanding what the green star next to Shared Clients signifies and this isn't really a problem.

I2P 0.9.19-0

Subtickets

Change History (6)

comment:1 Changed 5 years ago by DjJeshk

If there is 0 active peers and you have shared tunnels opened, wait at least 11 minutes and they will disappear too. If not, check shared tunnels settings and look if tunnel length is zero. Setting ± variance has no effect, it just resets to zero (I entered trac to report it), so no reason to care about it at the moment. If you haven't set zero length, then there is bug. If so, repost your report with settings you have set about shared tunnels.

I have seen exploratory zero length tunnels at startup, looks like required to be able to integrate in network.

comment:2 Changed 5 years ago by killyourtv

As I wrote above, I sabotaged the reseeding so it would fail. Everything else was left at the defaults and I2P was started for the first time, as if it was a new installation.

comment:3 Changed 5 years ago by zzz

Component: router/transportrouter/general

Zero-hop tunnels don't require peers. Exploratory tunnels can always be zero-hop (for bootstrapping as explained in comment 1), but client tunnels shouldn't be. In addition, client tunnels of any length shouldn't be built through zero-hop exploratory. So something's not right. Probably some sort of fallback code somewhere.

The ± bug referenced in comment 1 (#1587) is unrelated.

comment:4 Changed 5 years ago by zzz

actually it was 15 in 400 ms, 12 were omitted as "similar" in the router log section, but weren't displayed or noted in the crit section (which is a minor logging bug)

comment:5 Changed 5 years ago by zzz

Log bug fixed in cd971f0067e6a1d3ca5f4f9e045b7711c09adda6 i2p.i2p.zzz.test2 to be propped for 0.9.21

comment:6 Changed 4 years ago by str4d

Status: newopen
Note: See TracTickets for help on using tickets.