Opened 8 years ago

Closed 8 years ago

#953 closed defect (no response)

Destination gets ready only when it gets configured quantity of tunnels

Reported by: DISABLED Owned by:
Priority: minor Milestone: 0.9.8
Component: apps/i2ptunnel Version: 0.9.6
Keywords: Cc:
Parent Tickets: Sensitive: no


…when it's possible to use just one.

Also, there is some kind of bug when it can't get needed quantity of tunnels.
It launches that destination-client again, and then i have 2 (or even more) destination-clients in non-shared tunnel mode.
And no way to kill them without restart. Even "stop all" button does not stop them.

Also, i can't kill destination before it gets ready. And getting ready takes quite a while on routers with small netdb.


Change History (4)

comment:1 Changed 8 years ago by zzz

I don't think this is true. I2CP waits only for a leaseset (inbound tunnels). In addition, I changed it several years ago so that the leaseset only needs one tunnel, not the configured number. This change was in 0.7.1 f000ad746779a486084f555ce19b2d710c72fdc8

So it only needs one inbound tunnel and zero outbound tunnels.

Unless it's broken of course. Please provide more info including configuration (client or server, shared client or not, number of tunnels and length, etc) and logs if available.

Not sure about the other issues but there are definitely locking problems especially with shared clients. See other tickets below.

Possibly related: #642 #915 #946 #947

comment:2 Changed 8 years ago by zzz

correction to related: #815 (not #915)

comment:3 Changed 8 years ago by zzz

Also #650

comment:4 Changed 8 years ago by zzz

Resolution: no response
Status: newclosed

No response, and the router does indeed only wait for a single lease (tunnel) to send it to the client for signing, which completes the connect() call (I2PSessionImpl.setLeaseSet()).

The other issues are covered in the other tickets referenced above will be addressed in 0.9.8.

Closing this ticket, no response, please reopen if you have any more evidence i2ptunnel isn't ready after one inbound tunnel.

Note: See TracTickets for help on using tickets.