- Jan 29, 2010
- Jan 28, 2010
- Jan 26, 2010
- Jan 24, 2010
-
-
zzz authored
-
zzz authored
- Store and report UDP clock skews even for large values, so a badly skewed local clock will be reported to the console - Don't shitlist for NTCP clock skew if we don't know what time it is - If NTP hasn't worked yet, have NTCP or SSU update the clock one time - Include failed clock skew in NTCP skew vector if there aren't many connections - Don't include NTCP clock skews for non-established connections - Fix framed clock skew frame size - Report framed clock skew even if for only one peer, if NTP hasn't worked yet - Don't log RRD errors after clock adjustment - Reduce min skew for console warning to 30s (was 45s) - More Java 5 cleanups
-
zzz authored
-
zzz authored
-
zzz authored
-
zzz authored
to branch 'i2p.i2p' (head 9383c447b12abf45f80bd0059f719acfce4c70a3)
-
zzz authored
and 'ba40565ead71f8ce02500978ca95ca90340a294d'
-
zzz authored
- Move stat initialization, reduce number of rates - Add basic DOS prevention by not flooding if stores are too-frequent
-
zzz authored
-
zzz authored
- Don't let a client update the router clock - Restore and enhance vanished clock error log message
-
zzz authored
-
- Jan 23, 2010
- Jan 22, 2010
- Jan 21, 2010