I2P Bugtracker: Ticket #2425: Bootstrap nodes are unreachablehttps://trac.i2p2.de/ticket/2425
<p>
As of Feb 2019 all hardcoded bootstrap nodes are unreachable making new installs unable to join the Kademlia network and rendering them non-functional.
</p>
en-usI2P Bugtrackerhttps://trac.i2p2.de/chrome/site/i2plogo.pnghttps://trac.i2p2.de/ticket/2425
Trac 1.0.5subatomicSat, 02 Feb 2019 17:05:03 GMThttps://trac.i2p2.de/ticket/2425#comment:1
https://trac.i2p2.de/ticket/2425#comment:1
<p>
As a workaround I have published a list of peers:
magnet:?xt=urn:btih:bcdb811d635379effcec4dfa6dfa368515783fdd&amp;tr=http://tracker2.postman.i2p/announce.php
</p>
TicketzzzWed, 06 Feb 2019 12:34:52 GMTowner, status changed; cc sethttps://trac.i2p2.de/ticket/2425#comment:2
https://trac.i2p2.de/ticket/2425#comment:2
<ul>
<li><strong>cc</strong>
<em>mhatta</em> added
</li>
<li><strong>owner</strong>
changed from <em>zzz</em> to <em>str4d</em>
</li>
<li><strong>status</strong>
changed from <em>new</em> to <em>assigned</em>
</li>
</ul>
<p>
Research by mhatta;
</p>
<p>
There are 4 hardcoded bootstraps.
</p>
<ul><li>1 run by kytv, who vanished several years ago.
</li><li>1 run by thetinhat
</li><li>2 run by str4d
</li></ul><p>
mhatta contacted thetinhat and str4d.
</p>
<ul><li>thetinhat said he forgot he was running it, will try to bring it back, but is not sure he can do so, and it will take a few days to investigate
</li><li>str4d said he would restore them, but did not provide a time estimate, and hasn't yet.
</li></ul><p>
Until one of them comes back, or people start new bootstrap nodes AND somebody releases a new bote version (which would require people delete the old version, because the signer is different), bote is dead.
</p>
<p>
Another possibility is for str4d to give one or both of his keys to others to run the bootstraps.
</p>
Ticketstr4dMon, 22 Apr 2019 19:28:02 GMThttps://trac.i2p2.de/ticket/2425#comment:3
https://trac.i2p2.de/ticket/2425#comment:3
<p>
My primary bootstrap has always been running, and was definitely active at the time mhatta contacted me (I checked after he asked me). My secondary bootstrap has been down for a while due to server issues, but I did back up the key, and can see about setting it back up.
</p>
<p>
Most likely the problem is that Bote's DHT implementation simply isn't functional with only one bootstrap node (I've never delved into it in any depth, so I don't actually know off-hand how it behaves under such conditions). So we need new bootstrap volunteers.
</p>
<p>
Also as a reminder, all I2P-Bote issues have been moved to <a class="ext-link" href="https://github.com/i2p/i2p.i2p-bote/issues"><span class="icon">​</span>https://github.com/i2p/i2p.i2p-bote/issues</a>, and new issues should be opened there.
</p>
Ticketstr4dMon, 22 Apr 2019 21:07:25 GMThttps://trac.i2p2.de/ticket/2425#comment:4
https://trac.i2p2.de/ticket/2425#comment:4
<p>
Hmm, another possible cause: my bootstrap peer has been alive for so long, that when restarting it tries connecting to peers that no longer exist instead of searching for new ones. A fresh I2P-Bote plugin install on a fresh I2P Router appears to bootstrap far more quickly. I've restarted my bootstrap peer after deleting its <tt>dht_peers.txt</tt> and <tt>relay_peers.txt</tt> files, and it is now connected to far more peers.
</p>
Ticketstr4dWed, 24 Apr 2019 10:20:26 GMThttps://trac.i2p2.de/ticket/2425#comment:5
https://trac.i2p2.de/ticket/2425#comment:5
<p>
Nope, my primary bootstrap subsequently disconnected from them all. Perhaps it is because it is on a router that is also overloaded? I'm seeing lots of log messages of the form:
</p>
<pre class="wiki">4/24/19, 2:30:25 AM DEBUG [Kademlia ] ademlia.ClosestNodesLookupTask: Looking up nodes closest to [Hash: 118-MC07OoO5lqDQdssRrsCxMrr6Mgw6nkX0jAQAQko=]
4/24/19, 2:30:25 AM DEBUG [Kademlia ] ademlia.ClosestNodesLookupTask: Lookup status for key 118-MC07...: resp=0 pend=0 notQ=1
4/24/19, 2:30:25 AM ^^^ 1 similar message omitted ^^^
4/24/19, 2:30:36 AM DEBUG [RelayPeerMgr] i2p.bote.network.PacketBatch : Finished waiting. Time now: 1556073036025, #incoming=0, #outgoing=50
4/24/19, 2:30:50 AM ERROR [leTimer2 1/4] lient.impl.I2PSessionMuxedImpl: [OPEN I2P-Bote #64565]: Client not responding? Message not processed! id=60260254: [MessagePayloadMessage:
SessionId: 64565
MessageId: 60260254
Payload: [Payload: 520 bytes]]
4/24/19, 2:30:50 AM ^^^ 15 similar messages omitted ^^^
4/24/19, 2:30:56 AM DEBUG [Kademlia ] ademlia.ClosestNodesLookupTask: FindCloseNodes request to peer zegsejfq... timed out.
4/24/19, 2:30:57 AM INFO [SeedlessInit] ce.seedless.SeedlessParameters: Testing Seedless API
4/24/19, 2:30:57 AM DEBUG [Kademlia ] ademlia.ClosestNodesLookupTask: Node lookup for [Hash: 118-MC07OoO5lqDQdssRrsCxMrr6Mgw6nkX0jAQAQko=] found 0 nodes (may include local node).
</pre>
Ticket