igitally signed message part.
URL:
<https://emu.freenetproject.org/pipermail/devl/attachments/20110211/3773bc51/attachment.pgp>
Freenet 0.7.5 build 1352 is now available, please upgrade, it will be mandatory
on the 19th. This build significantly speeds up bulk transfers; we were only
allowing one packet in flight at a time, now we allow up to 100 depending on
various factors (provided that the peer we are talking to supp
signed message part.
URL:
<https://emu.freenetproject.org/pipermail/devl/attachments/20110211/c2dc7a6b/attachment.pgp>
On Friday 11 Feb 2011 21:39:34 Arne Babenhauserheide wrote:
> On Saturday 05 February 2011 18:39:49 Matthew Toseland wrote:
> > We need more seednodes. I will explain the broader situation below. If you
> > can run a seednode - which means you need a forwarded port, a reasonably
> > static IP addre
ject.org/pipermail/devl/attachments/20110211/743faefa/attachment.pgp>
On Saturday 05 February 2011 18:39:49 Matthew Toseland wrote:
> We need more seednodes. I will explain the broader situation below. If you
> can run a seednode - which means you need a forwarded port, a reasonably
> static IP address (or dyndns name), and a reasonable amount of bandwidth
> (especia
Freenet 0.7.5 build 1351 is now available, please upgrade, it will be mandatory
on Friday. This build should fix Update Over Mandatory: When we connected to a
TOO OLD peer, because of a bug (returning false instead of true and vice
versa), we would immediately disconnect rather than connecting a
Freenet 0.7.5 build 1350 is now available, please upgrade! It will be mandatory
next Friday. Announcements/bootstrapping appear to be working now, much faster
than they have been recently, however announcements and update over mandatory
on old nodes still isn't, which hopefully this build will f
idea what's going on now...
-- next part --
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 198 bytes
Desc: This is a digitally signed message part.
URL:
<https://emu.freenetproject.org/pipermail/devl/attachments/20110211/50e11b9a/attachment.pgp>
> * routingMissDistanceOverall: 0.0261
> * backedOffPercent: 22.3%
> * pInstantReject: 95.8%
> * unclaimedFIFOSize: 2663
> * RAMBucketPoolSize: 12.8 MiB / 150 MiB
> * uptimeAverage: 99.3%
Ping times that high mean your node won't accept any requests at all, although
it might accept some announcements.
Usually this is caused by network or CPU problems. When I've run my seednode
lately it hasn't had high ping times, nor have any of my other nodes.
The NPE is fixed btw.
-- next part --
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 198 bytes
Desc: This is a digitally signed message part.
URL:
<https://emu.freenetproject.org/pipermail/devl/attachments/20110211/13413e58/attachment.pgp>
; requests, 0 B routed test messages.
> Node to node messages: 1.45 MiB
> Load allocation notices: 288 KiB
> Other output: 6.59 MiB (7%)
> Total non-request overhead: 31.4 KiB/sec (96%).
-- next part --
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 198 bytes
Desc: This is a digitally signed message part.
URL:
<https://emu.freenetproject.org/pipermail/devl/attachments/20110211/fb780672/attachment.pgp>
11 matches
Mail list logo
