On Thu, Nov 29, 2001 at 12:27:01PM +0100, Volker Stolz wrote:
> I need a mechanism to specify rules *which* of the available nodes my
> local Freenet-node should connect (otherwise, this will leave nasty
> entries in the firewall log). To do this in a more general way, I though
> of this: Let?s take a file in similar format as the seedNodes, but allow
> regular expressions for hostnames and portnumbers. Whenever the node
> wants to establish an outgoing connection (or, better: when he throws the
> dice which node to use) the filter is checked (e.g. only connect to nodes
> running on port 113,80,8080,22 or in the same subnet).
Two things: 1) the best solution would be just to modify the routing table
so that it never stores references to these nodes in the first place,
and 2) the number of nodes running on those ports is going to be
virtually zero so there is just no point in doing it, you might as well
not run a permanent node.
Is your subnet actually large enough to benefit from freenet routing
within the subnet?
> On a related note, I?d like to know if the node relies on the
> data obtained from the socket (i.e. the peer?s address & port)
> or if it just accepts the connection and takes those data from
> the peer?s messages? I?m thinking of putting a proxy between
> my node and the network, so obviously those connection data
> would no longer match because the sockets are established from
> localhost.
An incoming request includes the node ref of the requester which
contains the network address.
--
:: tavin cole (tcole at espnow.com) ::
if there's been a way to build it
there'll be a way to destroy it
things are not all that out of control
- stereolab
_______________________________________________
Devl mailing list
Devl at freenetproject.org
http://lists.freenetproject.org/mailman/listinfo/devl
