File tree Expand file tree Collapse file tree 1 file changed +26
-0
lines changed Expand file tree Collapse file tree 1 file changed +26
-0
lines changed Original file line number Diff line number Diff line change @@ -133,3 +133,29 @@ listening port to 0 when listening for incoming I2P connections and advertises
133
133
its own I2P address with port 0. Furthermore, it will not attempt to connect to
134
134
I2P addresses with a non-zero port number because with SAM v3.1 the destination
135
135
port (` TO_PORT ` ) is always set to 0 and is not in the control of Bitcoin Core.
136
+
137
+ ## Bandwidth
138
+
139
+ I2P routers may route a large amount of general network traffic with their
140
+ default settings. Check your router's configuration to limit the amount of this
141
+ traffic relayed, if desired.
142
+
143
+ With ` i2pd ` , the amount of bandwidth being shared with the wider network can be
144
+ adjusted with the ` bandwidth ` , ` share ` and ` transittunnels ` options in your
145
+ ` i2pd.conf ` file. For example, to limit total I2P traffic to 256KB/s and share
146
+ 50% of this limit for a maximum of 20 transit tunnels:
147
+
148
+ ```
149
+ bandwidth = 256
150
+ share = 50
151
+
152
+ [limits]
153
+ transittunnels = 20
154
+ ```
155
+
156
+ If you prefer not to relay any public I2P traffic and only permit I2P traffic
157
+ from programs which are connecting via the SAM proxy, e.g. Bitcoin Core, you
158
+ can set the ` notransit ` option to ` true ` .
159
+
160
+ Similar bandwidth configuration options for the Java I2P router can be found in
161
+ ` http://127.0.0.1:7657/config ` under the "Bandwidth" tab.
You can’t perform that action at this time.
0 commit comments