- Aug 21, 2005
-
-
- Aug 20, 2005
-
- Aug 17, 2005
-
-
* Revise the SSU peer testing protocol so that Bob verifies Charlie's viability before agreeing to Alice's request. This doesn't work with older SSU peer test builds, but is backwards compatible (older nodes won't ask newer nodes to participate in tests, and newer nodes won't ask older nodes to either).
-
* Revise the SSU peer testing protocol so that Bob verifies Charlie's viability before agreeing to Alice's request. This doesn't work with older SSU peer test builds, but is backwards compatible (older nodes won't ask newer nodes to participate in tests, and newer nodes won't ask older nodes to either).
-
- Aug 16, 2005
-
- Aug 15, 2005
-
- Aug 14, 2005
-
- Aug 12, 2005
-
-
* Keep detailed stats on the peer testing, publishing the results in the netDb. * Don't overwrite the status with 'unknown' unless we haven't had a valid status in a while. * Make sure to avoid shitlisted peers for peer testing. * When we get an unknown result to a peer test, try again soon afterwards. * When a peer tells us that our address is different from what we expect, if we've done a recent peer test with a result of OK, fire off a peer test to make sure our IP/port is still valid. If our test is old or the result was not OK, accept their suggestion, but queue up a peer test for later. * Don't try to do a netDb store to a shitlisted peer, and adjust the way we monitor netDb store progress (to clear up the high netDb.storePeers stat)
-
- Aug 10, 2005
-
-
* Deployed the peer testing implementation to be run every few minutes on each router, as well as any time the user requests a test manually. The tests do not reconfigure the ports at the moment, merely determine under what conditions the local router is reachable. The status shown in the top left will be "ERR-SymmetricNAT" if the user's IP and port show up differently for different peers, "ERR-Reject" if the router cannot receive unsolicited packets or the peer helping test could not find a collaborator, "Unknown" if the test has not been run or the test participants were unreachable, or "OK" if the router can receive unsolicited connections and those connections use the same IP and port.
-
- Aug 09, 2005
-
- Aug 08, 2005
-
-
-
"ERROR [eive on 8887] uter.transport.udp.UDPReceiver: Dropping inbound packet with 1 queued for 1912 packet handlers: Handlers: 3 handler 0 state: 2 handler 1 state: 2 handler 2 state: 2" state = 2 means all three handlers are blocking on udpReceiver.receive()) this can legitimately happen if the bandwidth limiter or router throttle chokes the receive for >= 1s.
-
- Aug 07, 2005
-
-
* Display the average clock skew for both SSU and TCP connections 2005-08-07 jrandom * Fixed the long standing streaming lib bug where we could lose the first packet on retransmission. * Avoid an NPE when a message expires on the SSU queue. * Adjust the streaming lib's window growth factor with an additional Vegas-esque congestion detection algorithm. * Removed an unnecessary SSU session drop * Reduced the MTU (until we get a working PMTU lib) * Deferr tunnel acceptance until we know how to reach the next hop, rejecting it if we can't find them in time. * If our netDb store of our leaseSet fails, give it a few seconds before republishing.
-
- Aug 05, 2005
-
- Aug 03, 2005
-
-
- Aug 02, 2005
-
- Aug 01, 2005
-
- Jul 31, 2005
-
-
* Adjust the netDb search and store per peer timeouts to match the average measured per peer success times, rather than huge fixed values. * Optimized and reverified the netDb peer selection / retrieval process within the kbuckets. * Drop TCP connections that don't have any useful activity in 10 minutes. * If i2np.udp.fixedPort=true, never change the externally published port, even if we are autodetecting the IP address. (also includes most of the new peer/NAT testing, but thats not used atm)
- Jul 30, 2005
-
- Jul 28, 2005
-
- Jul 27, 2005
-
-