The problem with all of these approaches is that it is very hard to tell when it is OK for there to be private network addresses and when it is not. It is basically either looking at the Interfaces available and making a guess, or asking the user.
The former isn't foolproof and can't be done in java AFAIK, the latter is annoying and will confuse users. I would suggest: 4) Change the protocol so that nodes inserting data don't point references at themselves, thereby avoiding the issue... On Fri, Jun 29, 2001 at 05:03:46PM -0700, Mr.Bad wrote: > >>>>> "GJ" == Gianni Johansson <giannijohansson at mediaone.net> writes: > > GJ> I disagree. Truly ridiculous addresses shouldn't make it into > GJ> the data store (or whatever the 0.4 routing mechanism's analog > GJ> is) in the first place. > > OK, well, I can think of a few ways to fix this: > > 1) Change tcpAddress so that it throws an exception if a private > address is used. (This would prevent using a private network and a > "gateway", however). > > 2) Change the code in StoreData so that it does a validity check on an > address before saving it to the datastore. If the address is bad, > it changes the address for use downstream to its own, and it stores > a null reference. > > 3) Change the code in Node so that if the address it's using isn't > valid, sets itself to transient and continues on its way. > > Actually, probably a combo of 2) and 3) is the best thing. -- 'DeCSS would be fine. Where is it?' 'Here,' Montag touched his head. 'Ah,' Granger smiled and nodded. Oskar Sandberg oskar at freenetproject.org _______________________________________________ Devl mailing list Devl at freenetproject.org http://lists.freenetproject.org/mailman/listinfo/devl
