> From: Oskar Sandberg <md98-osa at nada.kth.se> > To: freenet-dev at lists.sourceforge.net > Date: Tue, 18 Apr 2000 03:02:26 +0200 > Subject: [Freenet-dev] build 121 > Reply-To: freenet-dev at lists.sourceforge.net > > I updated the node with the transient option, which will keep it from ever > setting the "DataSource" to point to itself. Transient makes for a one way > proxy node, so that someone behind a shifting connection can run a node but > not > get any references stuck to it. I know the thing about "taking and not > giving", > but bad references from people behind modems running local nodes when they > insert is just as bad.
What is the difference between this transient type of node and a client accessing someone elses node directly? Is the transient node -> regular node traffic any more obfuscated than client -> regular node traffic (for the purposes of making source side inserts and requests look like the regular routing)? What are the benefits (to the user or the freenet) of running one of these nodes rather than just running a client? It seems to me that the rest of the freenet cannot access anything that may be cached in the transient's store. That means that anything accessed locally by a client from the transient node was either put there by the clients previous request or insert. > > Client writers should take note that this means the "DataSource" field is now > optional. You can stop setting it to a bogus address when you insert, simply > leave it out of the message. People using the java code for clients > (Freeloader) should set Core.transience to true and the this will be done > automatically. The way I am currently handling this is to tolerate null > references in the datastore. Possibly not caching the data at all on the first > step from a transient node is another option, I'm not sure which is better. It seems to me that this is introducing a difference between the first hop requests and inserts from traffic sniffers to pick up on. > > I'm wondering a little about the writing and reading of the StandardDataStore. > During my testing tonight, the DataStore seemed cleared between every > execution > even after the times I had seen the "Writing DataStore to disk" message. Can > someone test that it is actually working (I must sleep). I noticed odd storage behaviour in my newly created node also. Here is some output from the store. [freenet at router .freenet]$ ls -lrt total 1277 -rw-r--r-- 1 freenet users 19456 Apr 17 11:27 t6827577 -rw-r--r-- 1 freenet users 194564 Apr 17 12:40 t4693997 -rw-r--r-- 1 freenet users 80114 Apr 17 14:26 t170350 -rw-r--r-- 1 freenet users 984642 Apr 17 17:04 t6864087 -rw-r--r-- 1 freenet users 1372 Apr 17 17:07 store_19114 -rw-r--r-- 1 freenet users 14848 Apr 17 18:36 t8946413 [freenet at router .freenet]$ cat store_19114 # parsed for readability VERSION 1 (DBEA43207EEA1EE5758A38858DF1B93C8C00D05Btcp/144.89.254.254:19114 (A2EE092D7064C23B3A604F8E1560880455E233CEtcp/216.103.68.2:19114 (6A0B3E3D8F8C385568469DC310A7E82673427EA0tcp/149.159.42.2:19114 (33F483042F961709579ADE3F8C89E547FA5DCA6Ctcp/128.2.144.46:19114 (F55AB68F3E1546BE75400C708E33B54E6C3C8691tcp/212.120.83.98:19114 (40C9873E6D274E2E7688E6288C033259E5734478tcp/209.21.143.71:19114 (0D07920B55556530A6AD24F07574567A25F20BB1tcp/131.155.71.73:19114 (D62AC72891B7602C57CF0E6DBF73A2D4347D60CCtcp/24.7.92.31:19114 (225A2D217CF56DAA280F35A346F91CE17D80E13Btcp/207.229.147.190:19114 (E36D9AB14E4A7F8BD3FB5C3E3AC783A258EB7517tcp/128.61.78.48:19114 (18FCA32916A4DB75B8F383A3BF80CF6C0C94AB8Ftcp/212.74.148.25:19114 (4ED37CE507079EB30CE9C03BD35D9F190564A1C6tcp/132.203.63.57:19114 (23EB0F4DE28B4D59E3ED061750CD9F1FD33E554Ftcp/195.34.152.79:19114 (9E728718A11D162B17ED345D8275567EEAE764FDtcp/142.92.129.37:19114 (FE56E1FAD23BB88594CC2BDAD9A57E352F45D795tcp/24.26.131.81:19114 (ADE4A4D96E884A3AC1183262F6C6EDDD9C146F60tcp/150.243.170.1:19114 (050CF69B9DDA340A489475A96CFE8E69CCED9937tcp/207.229.147.190:19114.freenet/t4693997 (16A2FD9FA4722C86DFDAE02F777F3E1753098674tcp/207.229.147.190:19114.freenet/t170350 (1270FCB41418CD4A3DD1243BD9939D69E120B627tcp/204.254.20.164:19114.freenet/t6864087 [freenet at router .freenet]$ This is a brand new node that I just started today and have not shut down. I was wondering why all of the files in the .freenet directory were not referenced in store? This does not seem to be a time or restart dependent thing since it is the first created and last created file that is unreferenced. It couldn't have reached it's maximum file count or store size quite yet (500 and 50 MB). Could it be that the store is leaving unreferenced files if an insert transfer is terminated prematurely? I have currently made no data inserts or requests. This is just what I have picked up from the ambient freenet. I also noticed that, on a recent cvs upgrade on another long running node of mine, my store was reset. Was this intentional. I realize that this is not a huge deal now and that this is still experimental but later on this could be catastrophic to the Freenet as a whole. Mike _______________________________________________ Freenet-dev mailing list Freenet-dev at lists.sourceforge.net http://lists.sourceforge.net/mailman/listinfo/freenet-dev
