Opened 5 years ago

Closed 5 weeks ago

#1162 closed defect (fixed)

Minimize waiting delay for I2PTunnel clients

Reported by: dg Owned by:
Priority: minor Milestone: 0.9.39
Component: apps/i2ptunnel Version: 0.9.9
Keywords: Cc: zab
Parent Tickets:


After I2P is started, it can take 3-4 minutes (sometimes up to 5) for I2PTunnel to kick in. This isn't a concern for me but it affects some users of I2P that come to me for support; they get frustrated in having to retry several times to logon to XMPP and IRC.

Any sort of control option for the delay in the console or optimization of the delay would be neat.


Change History (4)

comment:1 Changed 4 years ago by zzz

  • Milestone changed from 0.9.10 to 0.9.18

Bump. A big source of support requests to TAILS, and contributes to a general reputation among their users that I2P doesn't work. As reported at 31c3. Also requested by tuna at DEFCON 2013.

May require a more robust startup state machine. See also the ticket about reseeding finishing before netdb is ready #1384.

comment:2 Changed 4 years ago by zzz

In 2985798e33b03f58635fa7e66030fef8fcf817e0 0.9.17-7:

State machine added but not yet used for much.

i2ptunnel start delay reduced from 120 seconds to 35 seconds. This is safe because we refuse to build a client tunnel with a paired zero-hop exploratory, we will sleep and retry in BuildRequestor?.

Leaving open to investigate additional speedups.

comment:3 Changed 3 years ago by str4d

  • Status changed from new to open

comment:4 Changed 5 weeks ago by zzz

  • Cc zab added
  • Milestone changed from 0.9.18 to 0.9.39
  • Resolution set to fixed
  • Status changed from open to closed

This was fixed in 0.9.39, see #2377

Note: See TracTickets for help on using tickets.