The only real concern is that it is connecting anywhere 26 times in less than a minute. That some refs will be broken is unavoidable - it doesn't matter whether they are IPs on the wrong network or simply names that don't resolve, they _should_ be flushed out soon enough.
On Mon, Oct 22, 2001 at 11:15:48AM -0500, Will Glynn wrote: > I had a packet catcher running while I was checkingo out a suspicion I > had and I stumbled across some private addresses. Sure enough, my node > was trying to connect to 192.168.0.1 -- 26 times in under a minute. What > is being done to stop private addresses from polluting the routing tables? > > A related question: how can this be accomplished while allowing Freenets > to exist in private blocks with the ability to connect to the larger > network as well as directly with each other? > > --Will > > > > _______________________________________________ > Devl mailing list > Devl at freenetproject.org > http://lists.freenetproject.org/mailman/listinfo/devl -- Oskar Sandberg oskar at freenetproject.org _______________________________________________ Devl mailing list Devl at freenetproject.org http://lists.freenetproject.org/mailman/listinfo/devl
