1
0
mirror of https://github.com/PurpleI2P/i2pd_docs_en synced 2025-01-12 07:57:52 +00:00
i2pd_docs_en/docs/tutorials/floodfill-bootstrap.md

18 lines
1006 B
Markdown
Raw Normal View History

2017-04-13 12:20:33 +00:00
Bootstrapping without Reseed Servers
==============================================
2017-09-25 05:37:32 +00:00
In some cases I2P's default reseed servers (servers used to fill I2P router's netdb with initial peers) are blocked.
2017-04-13 12:20:33 +00:00
2017-09-25 05:37:32 +00:00
i2pd has a unique feature that allows it to bootstrap off of any I2P router that is participating in the DHT, they are called floodfill routers and have the router capacity `f` in their router info.
2017-04-13 12:20:33 +00:00
## How To
* obtain a `router.info` file of a floodfill router out of band, save to `/tmp/floodfill.router.info` or some other path
* run `i2pd --reseed.floodfill=/tmp/floodfill.router.info` and if that router is online you'll be able to bootstrap into the network from just that routers
2017-08-09 19:49:53 +00:00
## Caveats
2017-04-13 12:20:33 +00:00
* The floodfill *must* be trustworthy, it could give you all colluding peers if it's a baddie.
* *DO NOT* use a random floodfill unless you don't care about high security and just want to test out this feature.
* Java I2P routers seem to dislike this feature (sometimes) and may back off exponentially