- Just before midnight, flood to new location too so lookups
don't fail after keyspace rotation (ticket #510)
- Refactor RoutingKeyGenerator and UpdateRoutingKeyModifierJob
in support of the above
- Display next key on LS debug page
- Increase new kad size to K=24, B=4
- Fix router count by counting in the data store, not the kbuckets
- Randomize the order we load router infos at startup so we
don't bias the kbuckets
- Windows: Self-compiled with VS2010 in Windows 7. The icon has been
changed from Tanuki's default to Itoopie.
- Linux ARMv6: Compiled on a RaspberryPi using gcc 4.6.3-14+rpi1,
Icedtea6 6b27-1.12.5-1+rpi1 and stripped
- All other binaries are from the "community edition" deltapack offered by
Tanuki.
- Put garlicked DSM messages in the InNetMessagePool instead of handling directly,
so the IterativeSearchJob will see the response and declare success.
Only affected LS lookups as we do not request encrypted replies for RI lookups.
Similar to the fix for verifies 6dc5bed94321ae2b290cfe351511d18465e08f91
This bug was causing initial lookups to fail but subsequent ones to succeed.
Broken since 0.9.7 when encrypted replies was introduced.
Ticket #1125
- Increase threshold for idle timeout reduction from 33% to 60%.
This was reduced from 75% to 33% in -10 and it caused significant
tunnel build problems, for reasons that aren't entirely clear.
- Don't change the SSU idle timeout quicker when firewalled.
- log tweaks
- Don't use fallback expl. tunnels as the paired tunnel
for a client tunnel build.
This will cause more client tunnel breakage but it's
really bad to use a zero-hop for this.
- Fix selection of an expl. tunnel close to a hash
- Don't update build generation stat if the generation failed
- log tweaks
- Check blacklist/whitelist before connection limits, so
a blacklisted peer does not increment the counters
- Don't increment total throttle if peer is throttled
- Fix blacklist NPE after config change (ticket #1070)
Route connections to specific targets based on incoming I2P port
with custom option targetForPort.xxxx=myserver:yyyy
This allows multiple services on a single server tunnel (ticket #1066)
- Allow host:port targets; set defaults in i2ptunnel.config (ticket #1066)
- Don't fail start if hostname is unresolvable; retry at connect time (ticket #946)
- Output IRC message on connect fail
- Update target list on-the-fly when configuration changes
