Opened 6 years ago

Closed 5 years ago

#1496 closed enhancement (wontfix)

delay own tunnels

Reported by: user Owned by:
Priority: maintenance Milestone: undecided
Component: router/general Version: 0.9.18
Keywords: Cc:
Parent Tickets: Sensitive: no


On startup we wait 10 minutes until we start accepting request to participate in others' tunnels. It might be a good idea to optionally (so impatient users do not need to enable this setting) wait with building own client tunnels as well these 10 minutes, so that own tunnels can be covered in participating traffic right from the start.


Change History (4)

comment:1 Changed 6 years ago by zzz

Milestone: 0.9.21undecided

Sounds difficult to implement. A lot easier would be to reduce the part. tunnel delay (again)

Also the benefit isn't so clear. Maybe more benefit for server than client tunnels? And even without part. tunnels, you're still getting cover traffic in the form of the part. tunnel build requests coming in, and the rejections going out.

comment:2 Changed 6 years ago by zzz

Status: newinfoneeded_new

A user can delay all i2ptunnel-started tunnels by editing clients.config and changing the TunnelControllerGroup? delay to e.g. 600.

Is this sufficient? Need more info on the use case.

comment:3 Changed 6 years ago by user

Status: infoneeded_newnew

Zes, this sounds good.

Use case is simply that a service that is not on 24/7 should not pop up right in the moment when its router comes online. a small delay, ideally randomized a bit, in order not to be exactly 10 min either, which would be trivial.

comment:4 Changed 5 years ago by zzz

Resolution: wontfix
Status: newclosed

closing as the OP, in comment 3, is happy with the workaround in comment 2.

Note: See TracTickets for help on using tickets.