PurpleI2P
/
i2pd_docs_en
mirror of https://github.com/PurpleI2P/i2pd_docs_en
1
0
Fork 0
Code Issues Releases Wiki Activity
Browse Source

Merge pull request #85 from Vort/ff_ipv4 

add public IPv4 requirement for floodfill
pull/87/head
orignal 10 months ago committed by GitHub
parent
b81deaa118 d14731c25d
commit
6e278b4377
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 1 additions and 1 deletions
Whitespace
Show all changes Ignore whitespace when comparing lines Ignore changes in amount of whitespace Ignore changes in whitespace at EOL
Split View
Diff Options
Show Stats Download Patch File Download Diff File
  1. 2
      docs/user-guide/FAQ.md

2
docs/user-guide/FAQ.md
Unescape View File

@ -74,7 +74,7 @@ i2pd's socks proxy has an option to pass all non-I2P traffic to the Tor socks pr @@ -74,7 +74,7 @@ i2pd's socks proxy has an option to pass all non-I2P traffic to the Tor socks pr
## What is a floodfill mode?
Floodfill mode make your router a floodfill, that means what other routers will publish and get LeaseSets and RIs on your router. [Read more](http://geti2p.net/en/docs/how/network-database).
Floodfill mode require more bandwith, CPU time. If you sure, what you have stable uptime, you can enable floodfill: `floodfill = true`
Floodfill mode require more bandwith, CPU time. You can enable floodfill only if it has public ipv4 address and minimal bandwidth O: `floodfill = true`
## How is I2P different from Tor?

Write Preview
Loading…
Cancel
Save