Opened 5 years ago

Last modified 6 months ago

#1192 accepted defect

Hidden mode needs major improvement

Reported by: zzz Owned by: zzz
Priority: major Milestone: 0.9.37
Component: router/general Version: 0.9.10
Keywords: privacy reliability scalability peer-selection Cc:
Parent Tickets:

Description

Doesn't work well at all, which is a problem since we enable it by default in China and other countries.

Very difficult to build tunnels and keep them open, especially inbound. Do we restore tunnel testing when in hidden mode? Periodic publishing to a certain group of peers? What else can be done? Dramatic reductions over the years in idle timeouts, conn limits, etc have probably made things worse.

http://forum.i2p/viewtopic.php?t=10962

related tickets?

Subtickets (add)

#1314: Participating Traffic While in Hidden Modedefectclosed

Change History (7)

comment:1 Changed 5 years ago by zzz

One idea - when hidden, make pseudo-bidirectional tunnels, where the IB tunnel uses the same peers as the OB tunnel, in the reverse order.

Hidden mode is important because Tails enables it. We need to get it working better, or else try to get it disabled in Tails.

comment:2 Changed 4 years ago by str4d

  • Keywords privacy reliability scalability peer-selection added
  • Milestone 0.9.15 deleted

comment:3 Changed 3 years ago by str4d

  • Status changed from new to open

comment:4 Changed 3 years ago by zzz

Enabled tunnel testing in 88e26feb752a31eebb310dbb2c387665dfa91b8e 0.9.26-10

comment:5 Changed 12 months ago by zzz

  • Milestone set to 0.9.37
  • Owner set to zzz
  • Status changed from open to accepted

Tunnel peer selection improvements in 0.9.34.
Leaving open for further testing and improvements.

comment:6 Changed 12 months ago by slumlord

I've been using hidden mode (enabled manually by me, not automatically enabled by the router) for the past few months and found it to be generally usable and reliable. No major issues on my end.

comment:7 Changed 6 months ago by peekachoo

One issue I find with hidden mode (enabled automatically by I2P) is when the browser enters a "zombie state." The way this usually works is:

  1. Start I2P. Run it all night.
  2. Go to bed.
  3. Laptop goes to sleep.
  4. Wake up laptop.

Often (but not always) the I2P Router will now enter a zombie state. The router process is running and it reports itself as fine but I will not be able to connect to external I2P services. (Note I can still use local services running on the same machine but I can't, for example, connect to IRC.)

When the router enters a zombie state reseeding does not work. The only thing that fixes the problem is shutting down and restarting I2P.

The problem likely has to do with the router slowly forgetting about all the other peers on the network. Over time Active and Fast Peers will dwindle to zero and then the router is just stuck.

Note: See TracTickets for help on using tickets.