Sorry for being rude. I have hellish migarine today. I will do another try at explaining why a node needs to know its own IP.
Consider this.. you request a file from your node. Your node doesn't have this file in its cache. In order to deliver this file to you your node has to fetch it from some other node. Your node has a number of noderefs which, somewhat simplified, are encrypted files that links a public key to an ipaddress and port. The connectivity information inside these files are then used by your node to establish a connection to the other node, from where it might fetch the file you requested. These noderef files are only createable by the node that holds the private key associated with the public one (standard pki theory).. which usually is the node holding the ip and port inside the noderef file, and in the example above is the node your node wants to connect to. Because of this way of identifying/referencing nodes every node that wants to be contactable has to know its own public ip and port. Whenever your node recieves a new valid noderef file for a certain node/public key this new noderef file will replace to old one. Current mechanisms for a node for propagating its noderef file includes announcements and ARKs. Hmm.. someone correct my terminology if you want to and if it is to far off. /N _______________________________________________ devl mailing list [EMAIL PROTECTED] http://hawk.freenetproject.org:8080/cgi-bin/mailman/listinfo/devl
