Bug #10461

Determine when I2P is ready for use

Added by kytv 2015-10-31 11:40:22 . Updated 2016-07-01 11:33:04 .

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

0%

Feature Branch:
Type of work:
Wait
Blueprint:

Starter:
Affected tool:
I2P
Deliverable for:

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 Feature #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.

Subtasks

Related issues

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

History

#1 Updated by kytv 2015-10-31 11:40:54

#2 Updated by kytv 2015-10-31 11:41:02

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

#3 Updated by intrigeri 2015-12-05 15:33:34

kytv wrote:
> Upstream bugs 1697, 1698 and maybe 1650 apply.

The two last ones are marked as fixed.

#4 Updated by BitingBird 2016-07-01 11:33:04

  • Assignee deleted (kytv)

no news from kytv -> removing assignee