jrandom authored 20 years ago and zzz committed 20 years ago

updated implementation to match the RandomSource javadocs (inclusive of both 0 and n, unlike SecureRandom, which is inclusive of 0 and exclusive of n)

jrandom authored 20 years ago and zzz committed 20 years ago

only block adding more *outbound* data, not handling data received from I2P.  The data has already been received by the router and delivered to the streaming lib (and is sitting in RAM anyway...)
logging

jrandom authored 20 years ago and zzz committed 20 years ago

have a write() timeout after 60s instead of blocking forever by default (also used when injecting data into an input stream)

jrandom authored 20 years ago and zzz committed 20 years ago

allow remote harvesting by specifying a URL to read routers from (e.g. --netDbURL http://dev.i2p.net/i2pdb/ )

jrandom authored 20 years ago and zzz committed 20 years ago

instead of the standard 'httpclient 4444' or 'httpclient 4444 squid.i2p', you can now specify a comma delimited list of outproxies:
'httpclient 4444 squid.i2p,www1.squid.i2p,www2.squid.i2p' and each individual http request goes through a randomly selected proxy
there are a few general issues with this, such as a lack of affinity (web applications that require a session to always come from a single IP address will break)
but it should work most of the time.

jrandom authored 20 years ago and zzz committed 20 years ago

disabled by default (enable through router.config 'netDb.shouldHarvest=true').
useful if you want to harvest the published router stats, since otherwise you could have data from a few hours back

jrandom authored 20 years ago and zzz committed 20 years ago

* build an i2ptunnel.war

jrandom authored 20 years ago and zzz committed 20 years ago

* don't use static props on the I2PTunnel for I2CP / etc so that we can safely keep multiple instances alive
* propogate errors (if the I2CP host isnt reachable, the socket manager
won't be created) and handle appropriately