From 54074e76b53b9c913616b8a3e344e43d67575070 Mon Sep 17 00:00:00 2001 From: jrandom Date: Wed, 7 Sep 2005 22:31:11 +0000 Subject: [PATCH] 2005-09-07 BarkerJr * HTML cleanup for the router console (thanks!) 2005-09-07 jrandom * Lay the foundation for 'client routers' - the ability for peers to opt out of participating in tunnels entirely due to firewall/NAT issues. Individual routers have control over where those peers are used in tunnels - in outbound or inbound, exploratory or client tunnels, or none at all. The defaults with this build are to simply act as before - placing everyone as potential participants in any tunnel. * Another part of the foundation includes the option for netDb participants to refuse to answer queries regarding peers who are marked as unreachable, though this too is disabled by default (meaning the routerInfo is retrievable from the netDb). --- apps/routerconsole/jsp/config.jsp | 2 +- apps/routerconsole/jsp/configlogging.jsp | 2 +- apps/routerconsole/jsp/configservice.jsp | 2 +- apps/routerconsole/jsp/oldconsole.jsp | 2 +- apps/routerconsole/jsp/oldstats.jsp | 2 +- history.txt | 17 ++- readme.html | 10 +- .../src/net/i2p/router/PeerManagerFacade.java | 9 ++ router/java/src/net/i2p/router/Router.java | 25 ++++ .../src/net/i2p/router/RouterVersion.java | 4 +- .../HandleDatabaseLookupMessageJob.java | 38 ++++- .../networkdb/PublishLocalRouterInfoJob.java | 1 + .../networkdb/kademlia/FloodfillStoreJob.java | 2 +- .../KademliaNetworkDatabaseFacade.java | 5 +- .../router/networkdb/kademlia/SearchJob.java | 2 +- .../i2p/router/peermanager/PeerManager.java | 92 +++++++++++- .../peermanager/PeerManagerFacadeImpl.java | 22 ++- .../router/startup/CreateRouterInfoJob.java | 1 + .../router/startup/RebuildRouterInfoJob.java | 1 + .../transport/CommSystemFacadeImpl.java | 5 +- .../router/transport/udp/UDPTransport.java | 131 +++++++++++------- .../tunnel/pool/ClientPeerSelector.java | 8 +- .../tunnel/pool/ExploratoryPeerSelector.java | 7 +- .../tunnel/pool/TunnelPeerSelector.java | 50 ++++++- 24 files changed, 347 insertions(+), 93 deletions(-) diff --git a/apps/routerconsole/jsp/config.jsp b/apps/routerconsole/jsp/config.jsp index 8d032f7465..5edc79c0c8 100644 --- a/apps/routerconsole/jsp/config.jsp +++ b/apps/routerconsole/jsp/config.jsp @@ -2,7 +2,7 @@ -I2P Router Console - logs +I2P Router Console - config networking diff --git a/apps/routerconsole/jsp/configlogging.jsp b/apps/routerconsole/jsp/configlogging.jsp index 672c7e11d8..b660a15198 100644 --- a/apps/routerconsole/jsp/configlogging.jsp +++ b/apps/routerconsole/jsp/configlogging.jsp @@ -3,7 +3,7 @@ -I2P Router Console - config clients +I2P Router Console - config logging diff --git a/apps/routerconsole/jsp/configservice.jsp b/apps/routerconsole/jsp/configservice.jsp index 36bc763070..59dfc3e755 100644 --- a/apps/routerconsole/jsp/configservice.jsp +++ b/apps/routerconsole/jsp/configservice.jsp @@ -3,7 +3,7 @@ -I2P Router Console - config clients +I2P Router Console - config service diff --git a/apps/routerconsole/jsp/oldconsole.jsp b/apps/routerconsole/jsp/oldconsole.jsp index 3d1ec31cd0..9ac26ced46 100644 --- a/apps/routerconsole/jsp/oldconsole.jsp +++ b/apps/routerconsole/jsp/oldconsole.jsp @@ -3,7 +3,7 @@ -I2P Router Console - home +I2P Router Console - internals diff --git a/apps/routerconsole/jsp/oldstats.jsp b/apps/routerconsole/jsp/oldstats.jsp index 15a39fc53a..5764eeb070 100644 --- a/apps/routerconsole/jsp/oldstats.jsp +++ b/apps/routerconsole/jsp/oldstats.jsp @@ -3,7 +3,7 @@ -I2P Router Console - home +I2P Router Console - statistics diff --git a/history.txt b/history.txt index 6da80281e3..ab5f53f65f 100644 --- a/history.txt +++ b/history.txt @@ -1,4 +1,19 @@ -$Id: history.txt,v 1.239 2005/09/04 15:26:42 jrandom Exp $ +$Id: history.txt,v 1.240 2005/09/05 14:30:09 jrandom Exp $ + +2005-09-07 BarkerJr + * HTML cleanup for the router console (thanks!) + +2005-09-07 jrandom + * Lay the foundation for 'client routers' - the ability for peers to opt + out of participating in tunnels entirely due to firewall/NAT issues. + Individual routers have control over where those peers are used in + tunnels - in outbound or inbound, exploratory or client tunnels, or + none at all. The defaults with this build are to simply act as before - + placing everyone as potential participants in any tunnel. + * Another part of the foundation includes the option for netDb + participants to refuse to answer queries regarding peers who are marked + as unreachable, though this too is disabled by default (meaning the + routerInfo is retrievable from the netDb). 2005-09-05 jrandom * Expose the HTTP headers to EepGet status listeners diff --git a/readme.html b/readme.html index 89d4326851..0174818c4a 100644 --- a/readme.html +++ b/readme.html @@ -5,13 +5,12 @@ the number of "Active: " peers rise, and you should see some local "destinations listed (if not, see below). Once those are up, you can: