Probably a bug: please report: 1 peers forcibly disconnected due to not
acknowledging packets.
1 of your peers are having severe problems (not acknowledging packets even
after 10 minutes). This is probably due to a bug in the code. Please report
it to us at the bug tracker at
I don't know if this has been reported. Finding info on freenet is hard.
I'm now using 1230 with winxp pro. my computer is gaming spec device.
Problem: The defragmenting of node.db4o is a cool idea. Doing it half assed
and including it without testing is a bad idea. Not saying that has been
done
- Freenet 0.7.5 Build #1232 build01232
- Freenet-ext Build #26 r23771
So far I've understood the backoff percentages in advanced connection
details but no longer.
The attached picture shows what I'm saying.
What ticks me off the most is being connected for over 90 minutes to peers
that are
https://bugs.freenetproject.org/view.php?id=3465
I saw that bug about a guy's datastore being only 10 GB filled over a year
and figure I'd report something I thought about skipping.
After I updated to
- Freenet 0.7.5 Build #1233 build01233
- Freenet-ext Build #26 r23771
I've noticed that
Using:
- Freenet 0.7.5 Build #1236 build01236
- Freenet-ext Build #26 r23771
I'd like to provide some extra info about the problem, DL's stuck at 100%
Here's another guy's report
https://bugs.freenetproject.org/view.php?id=3146
What I can offer:
1) I had about 40 DLs stuck at 100%
2) I
Installing while offline causes store and cache to stay at 0 keys/bytes.
Resizing store fixes it
1223 was the last version of freenet that actually worked. But I guess the
term: if it aint broke dont fix it. Has newer reached that far.
For example
Certain someone said (not per word):
1) This
- Freenet 0.7.5 Build #1237 build01237
- Freenet-ext Build #26 r23771
Lot's of people are saying they got slow downloads. I have never bitched
about it but I can offer you some info.
I use WinXpPro with 1GB allocated to freenet and big rambuckets.
The problem isn't just with this release
