On Wednesday 26 January 2011 10:04:27 Jep wrote: > Jep : > > ... must at mine be read as > > 'Freenet is *not* connecting to the network no matter what- this may > > take forever and a day.' > > > > > > As long as I'm using FN, which is nearly a year; > > my working scheme when updating, rebooting the system or for some other > > reason having to restart Freenet looks like this: > > > > 1 Just try it - this almost never works. Okay okay, say 3 out of 4 times > > it doesn't. > > 2 delete nodedb4o and try it > > 3 delete nodedb4o and everything with the port numbers in its name and > > try it > > 4 put the datastore folder and freenet.ini aside, uninstall Freenet and > > reinstall, put the stuff back and try it > > > > More often than not, only after step 4 it finally finds its stranger > > peers. But today again, nothing and nothing helps so Freenet is dead and > > I am, again, out of options. > > > > > > What I see happening is that when starting FN, for some 45 seconds, some > > seednodes are found and connected to. > > Then those connections drop and are never built up again. > > After that, the wrapper log only adds, line after line: 'Trying to > > connect to some seednodes...' and nothing else happens. > > > > > > XP, plenty of RAM and HD space, java up to date, ports fwd'd in the router. > > Once FN does connect, it stays that way. That is, apart from the backoff > > problem that seems to get worse. > > > > > > If there is any tip, short of giving up on Freenet, please let me know. > > > > > > Thanks for your reply. > > > > > > > > A question asked earlier, to which I have not seen an answer: > > Can I conclude the Freenet wrapper no longer runs as a service, meaning > > that the FN service can be removed? > > > > And yet another. > > Matthew, you asked for a big log some time ago, and I sent it. And I > > have not seen any conclusion of it other than that you hoped a new FN > > build would solve my connection problems. Which was a little bit true, > > but only a very little bit. > > It connected finally then, but it still stays hell if if I need to > > restart FN. > > 1335 somehow connected to strangers once more, after being off FN for > more than a day. > But, there's a new build already, mandatory on Friday, and I am for > obvious reason not very keen to update. > > The backoff problem seems to have gone worse than ever, currently 8 > connected and 32 backoffs. Maybe all will backoff today and not come > back, and I will have to try to connect anyway... > > Very nice, those plans for .8 but am I asking too much if I solely want > FN to work?
Bootstrapping has been a lot slower for the last couple of weeks (you obviously have some other problem, maybe a low MTU, as well). I have checked all the obvious possibilities, I'm fairly sure there isn't anything seriously broken in the opennet code, it seems to be a side effect of wider network problems (e.g. the backoff when fetching stuff through fproxy). It is being worked on; if I had an easy and low-risk solution I'd deploy it.
signature.asc
Description: This is a digitally signed message part.
_______________________________________________ Support mailing list [email protected] http://news.gmane.org/gmane.network.freenet.support Unsubscribe at http://emu.freenetproject.org/cgi-bin/mailman/listinfo/support Or mailto:[email protected]?subject=unsubscribe
