Project

General

Profile

Bug #10461

Determine when I2P is ready for use

Added by kytv about 4 years ago. Updated over 3 years ago.

Status:
Confirmed
Priority:
Normal
Assignee:
-
Category:
-
Target version:
-
Start date:
10/31/2015
Due date:
% Done:

0%

Feature Branch:
Type of work:
Wait
Blueprint:
Starter:
Affected tool:
I2P

Description

Due to what seems to be a bug in I2P, checking whether the "eepproxy" tunnel is ready for use with netstat -nlp |grep 4444 doesn't work. This was found while working on #6306.

Upstream bugs 1697, 1698 and maybe 1650 apply.

When the bug is fixed upstream the static sleep in config/chroot_local-includes/usr/local/sbin/tails-i2p should be removed.


Related issues

Related to Tails - Feature #6306: Write tests for I2P Resolved 09/26/2013 07/15/2015
Related to Tails - Bug #10185: Fix tails-i2p's "i2p_has_bootstrapped" function in newer java/newer I2P versions Resolved 09/12/2015

History

#1 Updated by kytv about 4 years ago

#2 Updated by kytv about 4 years ago

  • Related to Bug #10185: Fix tails-i2p's "i2p_has_bootstrapped" function in newer java/newer I2P versions added

#3 Updated by intrigeri almost 4 years ago

kytv wrote:

Upstream bugs 1697, 1698 and maybe 1650 apply.

The two last ones are marked as fixed.

#4 Updated by BitingBird over 3 years ago

  • Assignee deleted (kytv)

no news from kytv -> removing assignee

Also available in: Atom PDF