[freenet-support] Some 0.7 questions

2006-06-24 Thread Kevin Bennett
Hello.  Can I ask a question on the new Freenet?

I understand that version 0.7 is supposed to have two parts, an open network
and a "darknet" and that at the moment only the "darknet" part is working
and that to connect to it I have to get somebody else's node reference and
add it to my node whilst the other person does the same with my reference.
OK so far.

1. When I do this process and connect to a few nodes, are those the only
nodes to which I will ever connect, or does the act of joining the network
through those nodes then allow my node to learn about and connect to other
nodes whose references I don't explicitly add myself?

2. If/when the open net appears, will it be completely separate from the
darknet or will being in the darknet automatically join my node to the open
network?

Thank you in advance for any answers you can give.

Kevin.
--
All semiconductors work using smoke. Once you let the smoke out of them they
stop working.






[freenet-support] Some 0.7 questions

2006-06-24 Thread Kevin Bennett
Hello.  Can I ask a question on the new Freenet?

I understand that version 0.7 is supposed to have two parts, an open network
and a darknet and that at the moment only the darknet part is working
and that to connect to it I have to get somebody else's node reference and
add it to my node whilst the other person does the same with my reference.
OK so far.

1. When I do this process and connect to a few nodes, are those the only
nodes to which I will ever connect, or does the act of joining the network
through those nodes then allow my node to learn about and connect to other
nodes whose references I don't explicitly add myself?

2. If/when the open net appears, will it be completely separate from the
darknet or will being in the darknet automatically join my node to the open
network?

Thank you in advance for any answers you can give.

Kevin.
--
All semiconductors work using smoke. Once you let the smoke out of them they
stop working.



___
Support mailing list
Support@freenetproject.org
http://news.gmane.org/gmane.network.freenet.support
Unsubscribe at http://emu.freenetproject.org/cgi-bin/mailman/listinfo/support
Or mailto:[EMAIL PROTECTED]


[freenet-support] 5107 - where?

2006-05-20 Thread Kevin Bennett
Tried to download 5107 from freenetproject.org/snapshots but the download
fails every time.  I see from the release notes on the home page that this
update changes the update scripts to get updates from a different location.
Where is it please since /snapshots seems to be unusable.



Thanks.

Kevin.
--
Faith is the virtue of sticking your fingers in your ears long enough to get
a social validation of being ignorant. 








[freenet-support] 5107 - where?

2006-05-20 Thread Kevin Bennett
Tried to download 5107 from freenetproject.org/snapshots but the download
fails every time.  I see from the release notes on the home page that this
update changes the update scripts to get updates from a different location.
Where is it please since /snapshots seems to be unusable.

 

Thanks.

Kevin.
--
Faith is the virtue of sticking your fingers in your ears long enough to get
a social validation of being ignorant. 

 



___
Support mailing list
Support@freenetproject.org
http://news.gmane.org/gmane.network.freenet.support
Unsubscribe at http://emu.freenetproject.org/cgi-bin/mailman/listinfo/support
Or mailto:[EMAIL PROTECTED]


[freenet-support] V e r y s l o o o o o w download from freenetproject.org/snapshots

2005-10-22 Thread Kevin Bennett
Trying to update to the latest node version by doing what I've done before,
i.e. downloading freenet-latest.jar from freenetproject.org/snapshots but
it's only arriving at 200B/s (Yes, B/s, not KB/s, I didn't miss out the K).
This is slower than downloading a file from Freenet itself :-)

Something wrong with the server?





[freenet-support] V e r y s l o o o o o w download from freenetproject.org/snapshots

2005-10-22 Thread Kevin Bennett
Trying to update to the latest node version by doing what I've done before,
i.e. downloading freenet-latest.jar from freenetproject.org/snapshots but
it's only arriving at 200B/s (Yes, B/s, not KB/s, I didn't miss out the K).
This is slower than downloading a file from Freenet itself :-)

Something wrong with the server?


___
Support mailing list
Support@freenetproject.org
http://news.gmane.org/gmane.network.freenet.support
Unsubscribe at http://emu.freenetproject.org/cgi-bin/mailman/listinfo/support
Or mailto:[EMAIL PROTECTED]


RE: [freenet-support] Stable build 5075 - snapshots lagging behind?

2004-03-14 Thread Kevin Bennett
FYI:

The snapshots don't appear to have been updated.  08:15 GMT Sunday, and I'm
still getting 5074 from freenet-latest.jar.

Kevin.

-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] Behalf Of Toad
Sent: 13 March 2004 18:54
To: [EMAIL PROTECTED]; [EMAIL PROTECTED]
Subject: [freenet-support] Stable build 5075


Freenet stable build 5075 is now available. The snapshots have been
updated. You can get the build via the update.sh script on Linux, BSD,
or OS/X, or use the freenet-webinstall.exe utility to update on Windows,
or get the jar from
http://freenetproject.org/snapshots/freenet-latest.jar . All stable
branch users should upgrade.
Major changes:
* New algorithm for deciding which nodes to drop from the routing table.
* New load measurement based on predicting future downlink bandwidth
  usage. Won't affect the node much at present, it could be combined
  with limits on local clients to prevent nodes from getting high
  messageSendTime's when they request lots of data.
* Increase the default estimated file size (for rate limiting, load
  balancing, etc) to 350kB.
* Tweaks to the rate limiting code.
* Make logInputBytes and logOutputBytes work again.
* Fix a rare NullPointerException when accepting a new FNP connection
  and the connection times out.
--
Matthew J Toseland - [EMAIL PROTECTED]
Freenet Project Official Codemonkey - http://freenetproject.org/
ICTHUS - Nothing is impossible. Our Boss says so.


___
Support mailing list
[EMAIL PROTECTED]
http://news.gmane.org/gmane.network.freenet.support
Unsubscribe at http://dodo.freenetproject.org/cgi-bin/mailman/listinfo/support
Or mailto:[EMAIL PROTECTED]


[freenet-support] Millions(sic) of errors

2004-02-17 Thread Kevin Bennett
Came home tonight to find that my node had crashed earlier on.  Now after
restarting I'm seeing millions (literally) of this message in the logfile:

18-Feb-2004 01:44:20 (freenet.ConnectionHandler, YThread-106, ERROR): Caught
java.lang.IllegalArgumentException: Should be mux protocol, was
[EMAIL PROTECTED] in forceSendPacket
java.lang.IllegalArgumentException: Should be mux protocol, was
[EMAIL PROTECTED]
at
freenet.RateLimitingViolationMessage.resolve(RateLimitingViolationMessage.ja
va:50)
at freenet.PeerHandler.getPacket(PeerHandler.java:1092)
at freenet.ConnectionHandler.forceSendPacket(ConnectionHandler.java:2170)
at freenet.PeerHandler.sendSinglePacket(PeerHandler.java:1025)
at freenet.PeerHandler.innerSendMessageAsync(PeerHandler.java:900)
at freenet.PeerHandler.receivedRequest(PeerHandler.java:1771)
at freenet.node.states.FNP.NewRequest.genReceived(NewRequest.java:67)
at freenet.node.states.FNP.NewDataRequest.received(NewDataRequest.java:35)
at freenet.node.StateChain.received(StateChain.java:183)
at freenet.node.StateChain.received(StateChain.java:67)
at
freenet.node.StandardMessageHandler$Ticket.run(StandardMessageHandler.java:2
36)
at
freenet.node.StandardMessageHandler$Ticket.received(StandardMessageHandler.j
ava:171)
at
freenet.node.StandardMessageHandler$Ticket.access$100(StandardMessageHandler
.java:122)
at
freenet.node.StandardMessageHandler.handle(StandardMessageHandler.java:70)
at freenet.Ticker$Event.run(Ticker.java:395)

In 15 minutes the logfile has reached 1.52GB (yes, GB, that wasn't a typo)
with logging at the default level of normal, and it all seems to be this
'should be mux protocol' message.

In the few moments it's taken to write this mail, the log is now up to
1.85GB.

Aaah.  something new now:

18-Feb-2004 01:55:32 (freenet.RateLimitingViolationMessage, Network writing
thread, NORMAL): AARGH: couldn't send
[EMAIL PROTECTED]

Thousands of these too, and then the logfile seems to have stopped growing
except for a few:

18-Feb-2004 01:57:39 (freenet.node.rt.StandardNodeEstimator, YThread-203,
NORMAL): Caught freenet.node.rt.EstimatorFormatException: Estimate 1088779
over max 100 reading tcp/[snip], sessions=1, presentations=3,1,
ID=DSA([snip]), version=Fred,0.5,STABLE-1.50,5069 from FieldSet :(
freenet.node.rt.EstimatorFormatException: Estimate 1088779 over max 100
at
freenet.node.rt.RoutingPointStore$RoutingPoint.init(RoutingPointStore.java
:93)
at freenet.node.rt.RoutingPointStore.init(RoutingPointStore.java:351)
at
freenet.node.rt.HistoryKeepingRoutingPointStore.init(HistoryKeepingRouting
PointStore.java:31)
at
freenet.node.rt.DecayingKeyspaceEstimator$DecayingKeyspaceEstimatorFactory.c
reate(DecayingKeyspaceEstimator.java:851)
at
freenet.node.rt.StandardNodeEstimator.init(StandardNodeEstimator.java:531)
at
freenet.node.rt.StandardNodeEstimatorFactory.create(StandardNodeEstimatorFac
tory.java:110)
at
freenet.node.rt.StandardNodeEstimatorFactory.create(StandardNodeEstimatorFac
tory.java:170)
at freenet.node.rt.NGRoutingTable.reference(NGRoutingTable.java:463)
at freenet.node.rt.FilterRoutingTable.reference(FilterRoutingTable.java:52)
at freenet.node.Node.reference(Node.java:4863)
at
freenet.node.states.request.AwaitingStoreData.relayStoreData(AwaitingStoreDa
ta.java:139)
at
freenet.node.states.request.AwaitingStoreData.receivedMessage(AwaitingStoreD
ata.java:88)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at freenet.node.State.received(State.java:131)
at freenet.node.StateChain.received(StateChain.java:183)
at freenet.node.StateChain.received(StateChain.java:67)
at
freenet.node.StandardMessageHandler$Ticket.run(StandardMessageHandler.java:2
36)
at
freenet.node.StandardMessageHandler$Ticket.received(StandardMessageHandler.j
ava:171)
at
freenet.node.StandardMessageHandler$Ticket.access$100(StandardMessageHandler
.java:122)
at
freenet.node.StandardMessageHandler.handle(StandardMessageHandler.java:70)
at freenet.Ticker$Event.run(Ticker.java:395)
at freenet.thread.YThreadFactory$YThread.run(YThreadFactory.java:249)

Logfile is now 1.98GB and not growing rapidly.

What can cause this?


___
Support mailing list
[EMAIL PROTECTED]
http://news.gmane.org/gmane.network.freenet.support
Unsubscribe at http://dodo.freenetproject.org/cgi-bin/mailman/listinfo/support
Or mailto:[EMAIL PROTECTED]


[freenet-support] Failed to send IdentifyPacketMessage Errors

2004-02-03 Thread Kevin Bennett
Seeing hundreds of these today, roughly between 1 and 4 per second:

03-Feb-2004 21:39:35 (freenet.IdentifyPacketMessage, YThread-42, NORMAL):
Failed to send IdentifyPacketMessage: freenet.SendFailedException: Against
peer DSA(removed) @ removed - Sent 0 bytes (1551 of packet in notifyDone
(nonterminal)
freenet.SendFailedException: Against peer DSA(removed) @ removed - Sent 0
bytes (1551 of packet in notifyDone (nonterminal)
at freenet.PeerPacket.jobDone(PeerPacket.java:180)
at freenet.MuxConnectionHandler.terminate(MuxConnectionHandler.java:294)
at freenet.PeerHandler.registerConnectionHandler(PeerHandler.java:650)
at
freenet.MuxConnectionHandler.setPeerHandler(MuxConnectionHandler.java:152)
at freenet.OpenConnectionManager.put(OpenConnectionManager.java:235)
at freenet.MuxConnectionHandler.registerOCM(MuxConnectionHandler.java:501)
at
freenet.interfaces.FreenetConnectionRunner.handle(FreenetConnectionRunner.ja
va:141)
at
freenet.interfaces.PublicNIOInterface$ConnectionShell.run(PublicNIOInterface
.java:150)
at freenet.thread.YThreadFactory$YThread.run(YThreadFactory.java:247)

Does this mean anything, or is it just a glitch?  I reseeded earlier on (the
node wasn't transferring any data at all).  Could reseeding have made this
start happening?

Kevin.


___
Support mailing list
[EMAIL PROTECTED]
http://news.gmane.org/gmane.network.freenet.support
Unsubscribe at http://dodo.freenetproject.org/cgi-bin/mailman/listinfo/support
Or mailto:[EMAIL PROTECTED]


RE: [freenet-support] Freenet stable build 5063

2004-01-22 Thread Kevin Bennett
No, permanent.  The numbers have moved slightly since yesterday but they're
still good:

Uptime 35 hours.

Probability of success of an incoming request
22-Jan-2004 07:31:04
0 | 0.33023256
1 | 0.20754717
2 | 0.2094763
3 | 0.14257425
4 | 0.1953125
5 | 0.2006689
6 | 0.15882353
7 | 0.23024055
8 | 0.0941337
9 | 0.06840391
a | 0.078538105
b | 0.16099072
c | 0.25862068
d | 0.19318181
e | 0.22033899
f | 0.24892704

Max: 0.33023256
Most successful: 0

inboundConnectionRatio still ~85%
routingTime 15ms
outputBytesTrailerChunks/outputBytes=0.54
RAM usage creeping up: 200-240MB now  (It'll probably OOM soon, as it's got
a 256MB limit.)
CPU still ~20%
Total amount of data transmitted/received   1,961 MiB/2,506 MiB

Kevin.

-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] Behalf Of Toad
Sent: 22 January 2004 01:45
To: [EMAIL PROTECTED]
Subject: Re: [freenet-support] Freenet stable build 5063


Your numbers are amazing, and far higher than mine or those of another
node I've been able to check. Is this a transient node?

On Wed, Jan 21, 2004 at 05:00:41PM -, Kevin Bennett wrote:
 Been running this for 20 hours now, and I have to say it rocks :)

 Splitfiles in Frost and Fuqid are coming down at a rate of about 10k/s,
 about 15-20x the rate they were coming down a week ago and DBR freesites
 that were slow to arrive are now arriving usually within a few minutes.

 If you want stats, here's a few that seem useful.  If you want more, just
 ask as I don't know which are the most useful.

 According to the connection manager page, in 20 hours it's transferred
1.1GB
 up and 1.5GB down, way more than for the last few weeks (excepting the
brief
 surge when 5054 was still small).  Memory usage varies between 150-170MB,
 CPU usage ~20% of an AMD 2500+.

 Success probabilities are huge in comparison with previous builds:

 Probability of success of an incoming request
 21-Jan-2004 16:39:26
 0 | 0.31746033
 1 | 0.22285715
 2 | 0.19723183
 3 | 0.14285715
 4 | 0.24358974
 5 | 0.2173913
 6 | 0.13824885
 7 | 0.23214285
 8 | 0.13261649
 9 | 0.08004926
 a | 0.07307172
 b | 0.12169312
 c | 0.26865673
 d | 0.16981132
 e | 0.26573426
 f | 0.25

 Max: 0.31746033
 Most successful: 0

 Last week these were all, without exception, 0.01.

 inboundConnectionRatio is ~85%.

 routingTime is ~17ms.

 outputBytesTrailerChunks/outputBytes=0.58

 Once again: nice job guys :)

 Kevin.


 -Original Message-
 From: [EMAIL PROTECTED]
 [mailto:[EMAIL PROTECTED] Behalf Of Toad
 Sent: 20 January 2004 19:56
 To: [EMAIL PROTECTED]; [EMAIL PROTECTED]
 Subject: [freenet-support] Freenet stable build 5063


 Freenet stable build 5063 is now available. {snip}


 ___
 Support mailing list
 [EMAIL PROTECTED]
 http://news.gmane.org/gmane.network.freenet.support

--
Matthew J Toseland - [EMAIL PROTECTED]
Freenet Project Official Codemonkey - http://freenetproject.org/
ICTHUS - Nothing is impossible. Our Boss says so.


___
Support mailing list
[EMAIL PROTECTED]
http://news.gmane.org/gmane.network.freenet.support


RE: [freenet-support] Freenet stable build 5063

2004-01-22 Thread Kevin Bennett
So is there any other data I could send you that would help pinpoint just
why my node is working so (ludicrously) well?

-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] Behalf Of Toad
Sent: 22 January 2004 14:35
To: [EMAIL PROTECTED]
Subject: Re: [freenet-support] Freenet stable build 5063


They are still ludicrous. In that they don't happen anywhere else.

On Thu, Jan 22, 2004 at 07:49:05AM -, Kevin Bennett wrote:
 No, permanent.  The numbers have moved slightly since yesterday but
they're
 still good:

 Uptime 35 hours.

 Probability of success of an incoming request
 22-Jan-2004 07:31:04
 0 | 0.33023256
 1 | 0.20754717
 2 | 0.2094763
 3 | 0.14257425
 4 | 0.1953125
 5 | 0.2006689
 6 | 0.15882353
 7 | 0.23024055
 8 | 0.0941337
 9 | 0.06840391
 a | 0.078538105
 b | 0.16099072
 c | 0.25862068
 d | 0.19318181
 e | 0.22033899
 f | 0.24892704

 Max: 0.33023256
 Most successful: 0

 inboundConnectionRatio still ~85%
 routingTime 15ms
 outputBytesTrailerChunks/outputBytes=0.54
 RAM usage creeping up: 200-240MB now  (It'll probably OOM soon, as it's
got
 a 256MB limit.)
 CPU still ~20%
 Total amount of data transmitted/received 1,961 MiB/2,506 MiB

 Kevin.

 -Original Message-
 From: [EMAIL PROTECTED]
 [mailto:[EMAIL PROTECTED] Behalf Of Toad
 Sent: 22 January 2004 01:45
 To: [EMAIL PROTECTED]
 Subject: Re: [freenet-support] Freenet stable build 5063


 Your numbers are amazing, and far higher than mine or those of another
 node I've been able to check. Is this a transient node?

 On Wed, Jan 21, 2004 at 05:00:41PM -, Kevin Bennett wrote:
  Been running this for 20 hours now, and I have to say it rocks :)
 
  Splitfiles in Frost and Fuqid are coming down at a rate of about 10k/s,
  about 15-20x the rate they were coming down a week ago and DBR freesites
  that were slow to arrive are now arriving usually within a few minutes.
 
  If you want stats, here's a few that seem useful.  If you want more,
just
  ask as I don't know which are the most useful.
 
  According to the connection manager page, in 20 hours it's transferred
 1.1GB
  up and 1.5GB down, way more than for the last few weeks (excepting the
 brief
  surge when 5054 was still small).  Memory usage varies between
150-170MB,
  CPU usage ~20% of an AMD 2500+.
 
  Success probabilities are huge in comparison with previous builds:
 
  Probability of success of an incoming request
  21-Jan-2004 16:39:26
  0 | 0.31746033
  1 | 0.22285715
  2 | 0.19723183
  3 | 0.14285715
  4 | 0.24358974
  5 | 0.2173913
  6 | 0.13824885
  7 | 0.23214285
  8 | 0.13261649
  9 | 0.08004926
  a | 0.07307172
  b | 0.12169312
  c | 0.26865673
  d | 0.16981132
  e | 0.26573426
  f | 0.25
 
  Max: 0.31746033
  Most successful: 0
 
  Last week these were all, without exception, 0.01.
 
  inboundConnectionRatio is ~85%.
 
  routingTime is ~17ms.
 
  outputBytesTrailerChunks/outputBytes=0.58
 
  Once again: nice job guys :)
 
  Kevin.
 
 
  -Original Message-
  From: [EMAIL PROTECTED]
  [mailto:[EMAIL PROTECTED] Behalf Of Toad
  Sent: 20 January 2004 19:56
  To: [EMAIL PROTECTED]; [EMAIL PROTECTED]
  Subject: [freenet-support] Freenet stable build 5063
 
 
  Freenet stable build 5063 is now available. {snip}
 
 
  ___
  Support mailing list
  [EMAIL PROTECTED]
  http://news.gmane.org/gmane.network.freenet.support

 --
 Matthew J Toseland - [EMAIL PROTECTED]
 Freenet Project Official Codemonkey - http://freenetproject.org/
 ICTHUS - Nothing is impossible. Our Boss says so.


 ___
 Support mailing list
 [EMAIL PROTECTED]
 http://news.gmane.org/gmane.network.freenet.support

--
Matthew J Toseland - [EMAIL PROTECTED]
Freenet Project Official Codemonkey - http://freenetproject.org/
ICTHUS - Nothing is impossible. Our Boss says so.


___
Support mailing list
[EMAIL PROTECTED]
http://news.gmane.org/gmane.network.freenet.support


RE: [freenet-support] Freenet stable build 5063

2004-01-21 Thread Kevin Bennett
Been running this for 20 hours now, and I have to say it rocks :)

Splitfiles in Frost and Fuqid are coming down at a rate of about 10k/s,
about 15-20x the rate they were coming down a week ago and DBR freesites
that were slow to arrive are now arriving usually within a few minutes.

If you want stats, here's a few that seem useful.  If you want more, just
ask as I don't know which are the most useful.

According to the connection manager page, in 20 hours it's transferred 1.1GB
up and 1.5GB down, way more than for the last few weeks (excepting the brief
surge when 5054 was still small).  Memory usage varies between 150-170MB,
CPU usage ~20% of an AMD 2500+.

Success probabilities are huge in comparison with previous builds:

Probability of success of an incoming request
21-Jan-2004 16:39:26
0 | 0.31746033
1 | 0.22285715
2 | 0.19723183
3 | 0.14285715
4 | 0.24358974
5 | 0.2173913
6 | 0.13824885
7 | 0.23214285
8 | 0.13261649
9 | 0.08004926
a | 0.07307172
b | 0.12169312
c | 0.26865673
d | 0.16981132
e | 0.26573426
f | 0.25

Max: 0.31746033
Most successful: 0

Last week these were all, without exception, 0.01.

inboundConnectionRatio is ~85%.

routingTime is ~17ms.

outputBytesTrailerChunks/outputBytes=0.58

Once again: nice job guys :)

Kevin.


-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] Behalf Of Toad
Sent: 20 January 2004 19:56
To: [EMAIL PROTECTED]; [EMAIL PROTECTED]
Subject: [freenet-support] Freenet stable build 5063


Freenet stable build 5063 is now available. {snip}


___
Support mailing list
[EMAIL PROTECTED]
http://news.gmane.org/gmane.network.freenet.support


RE: [freenet-support] Number of stable nodes

2004-01-18 Thread Kevin Bennett
Slightly different here, my node is almost up to its limit:

Connections open (Inbound/Outbound/Limit)   507 (471/36/512)
Number of distinct nodes connected  427

Kevin.


-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] Behalf Of Lefebvre Hervé
Sent: 18 January 2004 11:11
To: [EMAIL PROTECTED]
Subject: Re: [freenet-support] Number of stable nodes


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On Dimanche 18 Janvier 2004 09:22, S wrote:

 Connections open (Inbound/Outbound/Limit) 417 (379/38/512)
 Number of distinct nodes connected 333

Same here :

Connections open (Inbound/Outbound/Limit)
350 (329/21/512)

- --
Hervé LEFEBVRE
[EMAIL PROTECTED]
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.2.3 (GNU/Linux)

iD8DBQFACmnD/iEFFjpUUjMRAi1VAJ425dGu/JNcURFZVItqcJep3uoBzQCcCtkc
EEzZA7g1krOFUVniJndhs6k=
=FTpj
-END PGP SIGNATURE-

___
Support mailing list
[EMAIL PROTECTED]
http://news.gmane.org/gmane.network.freenet.support


___
Support mailing list
[EMAIL PROTECTED]
http://news.gmane.org/gmane.network.freenet.support


[freenet-support] Build 5060?

2004-01-14 Thread Kevin Bennett
I see on the web interface page:

Build: 5058 (Latest: 5060)

freenetproject.org/snapshots/freenet-latest.jar still has the same timestamp
as when 5058 came out (13-Jan-2004 18:20)

I don't see any 5060 nodes in the OCM or node status pages.

What can cause this?

Kevin.


___
Support mailing list
[EMAIL PROTECTED]
http://news.gmane.org/gmane.network.freenet.support


RE: [freenet-support] Interpreting error messages

2003-12-24 Thread Kevin Bennett
Thank you :)

Kevin.


___
Support mailing list
[EMAIL PROTECTED]
http://news.gmane.org/gmane.network.freenet.support


[freenet-support] Log entry

2003-12-14 Thread Kevin Bennett
Waited more than 200ms to dequeue, 7 in queue, 3156 millis since enqueued
last item, 483698 maximum waits so far - could indicate serious JVM bug.
Please report to [EMAIL PROTECTED] along with JVM and OS/kernel.

JVM Version: Sun 1.4.2_01-b06
OS: Win2KPro SP4 with all MS updates.


___
Support mailing list
[EMAIL PROTECTED]
http://news.gmane.org/gmane.network.freenet.support


[freenet-support] An amusing statistic

2003-12-02 Thread Kevin Bennett
I looked at the general page of the web interface and was a little amused to
see the following figure:

Current recommended request interval sent to client nodes
1.9478309723356009E9ms

That's roughly 22.5 *days* :D

Kevin.



___
Support mailing list
[EMAIL PROTECTED]
http://dodo.freenetproject.org/cgi-bin/mailman/listinfo/support


RE: [freenet-support] Suddenly unable to connect to network

2003-11-30 Thread Kevin Bennett
Highest ARK here is 227, another ten in the range 50-150 and the rest
between 1 and 4.

Number of node references   49
Contacted node references   22
Node references requesting ARKs 21

Since my last mail to the list (70 minutes ago) I've had the grand total of
2 inbound requests hit my node.  At least I'm not QueryRejecting ;)

Kevin.

-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] Behalf Of Troed Sångberg
Sent: 30 November 2003 21:04
To: [EMAIL PROTECTED]
Subject: Re: [freenet-support] Suddenly unable to connect to network


On Sun, 30 Nov 2003 20:43:04 -, Pete [EMAIL PROTECTED]
wrote:

 Here are my stats for ARK's

 I doubt you're the only one having issues

 Number of node references 87
 Contacted node references 44
 Node references requesting ARKs 46

 This is not a good sign, my highest ARK is 153

I, on the other hand, do not have these problems. My transferrate in FUQID
is low, but it was low since a few stable NGR-snapshots back as well.
Frost actually seems to work better with classic routing as compared to
NGR.

I also reseeded when upgrading the snapshot [how many who do not read this
list will not do that .. ]

Number of node references   50
Contacted node references   33
Node references requesting ARKs 14

I have one ARK at 46, and at 17. The rest are at 4 and below. The absolute
majority are at 1.

The node version histogram also shows a few old nodes still referenced:

Fred,0.5,1.47,5037 |=
Fred,0.5,1.47,5039 |==
Fred,0.5,1.47,5041 |=
Fred,0.5,1.47,5042 |
Fred,0.5,1.47,5043 |
Fred,0.5,1.48,5046 |
Fred,0.6,1.47,6364 |===
Fred,0.6,1.47,6367 |===

regards,
Troed
___
Support mailing list
[EMAIL PROTECTED]
http://dodo.freenetproject.org/cgi-bin/mailman/listinfo/support


___
Support mailing list
[EMAIL PROTECTED]
http://dodo.freenetproject.org/cgi-bin/mailman/listinfo/support


RE: [freenet-support] Freenet Stable Build 5030

2003-11-25 Thread Kevin Bennett
Gah, replied to the wrong damn thread.

-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] Behalf Of Kevin Bennett
Sent: 25 November 2003 22:29
To: [EMAIL PROTECTED]
Subject: RE: [freenet-support] Freenet Stable Build 5030


FYI: After running this version for 50 mins, all activity abruptly stopped.
Input and output went from 56k/20k to 5k/0k over a period of 2 minutes.  No
response from localhost: either yet the node was apparently still
running as there were dozens of these log entries:

(freenet.node.states.request.ReceivingReply, YThread-1008, NORMAL):
Receiving connection died in freenet.node.states.request.ReceivingReply:
etc..

followed by quite literally hundreds like this:

(freenet.message.DataRequest, YThread-2263, NORMAL): Long
messageInitialStateTime 13625 etc...

and then a section with the occasional Long messageInitialStateTime
interspersed with (freenet.Ticker, Ticker immediate execution thread,
NORMAL):

On restarting the node, rates have gone back to normal.  Lets see how long
it stays up...


Kevin.


-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] Behalf Of Toad
Sent: 01 November 2003 17:02
To: [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Subject: [freenet-support] Freenet Stable Build 5030


Freenet stable build 5030 is out. Major changes:
* Makes 5029 mandatory.
* Improvements to the Open Connections page especially in PeerHandler
  mode.
* Improved plausible deniability for high HTL values.
* Increased default size of failure table to 20,000. This should make it
  much more effective, and only use around 2.5MB more memory.
* Don't try to use seednodes with no address to connect to.
* Don't write deprecated options such as the old overall bandwidthLimit
  to the config file.
* Don't show the key request form in simple mode, it confuses newbies.
* Support relative ?date= in fproxy. Example:

http://127.0.0.1:/SSK%40Sc6qV~D6iFhaYord6HtbjJ8MaEYPAgM/YoYo//?date=-1we
ek
* Finally remove the old datastore code, fix lots of eclipse warnings,
  other code tidying up

Use the update.sh or freenet-webinstall.exe utility to upgrade, or get
it from http://freenetproject.org/snapshots/freenet-latest.jar (replace
your existing freenet.jar). By the time you read this mail, certainly
within 20 minutes, the snapshots will have been updated.
--
Matthew J Toseland - [EMAIL PROTECTED]
Freenet Project Official Codemonkey - http://freenetproject.org/
ICTHUS - Nothing is impossible. Our Boss says so.


___
Support mailing list
[EMAIL PROTECTED]
http://dodo.freenetproject.org/cgi-bin/mailman/listinfo/support


___
Support mailing list
[EMAIL PROTECTED]
http://dodo.freenetproject.org/cgi-bin/mailman/listinfo/support


RE: [freenet-support] Freenet stable build 5041

2003-11-25 Thread Kevin Bennett
FYI: After running this version for 50 mins, all activity abruptly stopped.
Input and output went from 56k/20k to 5k/0k over a period of 2 minutes.  No
response from localhost: either yet the node was apparently still
running as there were dozens of these log entries:

(freenet.node.states.request.ReceivingReply, YThread-1008, NORMAL):
Receiving connection died in freenet.node.states.request.ReceivingReply:
etc..

followed by quite literally hundreds like this:

(freenet.message.DataRequest, YThread-2263, NORMAL): Long
messageInitialStateTime 13625 etc...

and then a section with the occasional Long messageInitialStateTime
interspersed with (freenet.Ticker, Ticker immediate execution thread,
NORMAL):

On restarting the node, rates have gone back to normal.  Lets see how long
it stays up...


Kevin.

-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] Behalf Of Toad
Sent: 25 November 2003 20:45
To: [EMAIL PROTECTED]; [EMAIL PROTECTED]
Subject: [freenet-support] Freenet stable build 5041


Freenet stable build 5041 is now available. Upgrade using update.sh or
freenet-webinstall.exe, or get the jar from
http://freenetproject.org/snapshots/freenet.jar .

Changelog:
* Major continuing work on routing:
** Contact the least accessed node every 30 seconds with a recently
requested key. This is estimated to add 3kqph to load, but is very
important given the next item.
** New nodes in the routing table get pessimistic estimators. So routing
is not dominated by new nodes any more. They will get routed to once
they have demonstrated their abilities through the above mechanism.
** Try to manage routing table churn: accept new nodes into the routing
table from any wierd source if we have less than 40 available, not
backed off, nodes. If we have more than that, do probabilistic
referencing for StoreData's, and don't borrow refs from requests.
** Impose a network level maximum file size of 1MB. This should make
multiplexing easier, simplify code, and prevent some bad behaviours that
might be used for traffic analysis.
** Make the global estimate, the request failure time, used in routing,
depend on the key AND the filesize. This prevents bad routing of files
of non-typical sizes.
** Always reset the datasource when we serve data from the store.
** Other minor changes.
* When we do a request with 'skip datastore' enabled, don't actually
delete the file from the datastore, just ignore it.
* Show the version of each node on the inbound requests page. Improve
the open connections and node reference status pages. More diagnostics.
Etc.
* Lots more bugfixes, logging changes, and other minor improvements.
-- 
Matthew J Toseland - [EMAIL PROTECTED]
Freenet Project Official Codemonkey - http://freenetproject.org/
ICTHUS - Nothing is impossible. Our Boss says so.


___
Support mailing list
[EMAIL PROTECTED]
http://dodo.freenetproject.org/cgi-bin/mailman/listinfo/support


RE: [freenet-support] Freenet Stable Build 5039

2003-11-20 Thread Kevin Bennett
Since upgrading to 5039, inserting has slowed to a crawl.  It's taken 8
hours to insert a single 10MB splitfile, where this would have taken
approximately 30 mins with 5038.  Most of the insert threads were timing
out.

Some popular freesites (e.g. YoYo) arrive quite quickly but splitfile
downloads all seem to fail with threads timing out.

My outbound bandwidth has been pegged at 20k with an average of around 150
connections trying to transmit at the  same time during this 8hr period
whereas inbound bandwidth has been running at about 5k.  There have also
been quite a lot of the 'Implausible report' and 'waited more than 5 minutes
in NIOIS.read()' errors, more than with 5038.

There was also this error which I've not seen before:

(freenet.node.ds.FSDataStoreElement$KeyInputStreamImpl, Finalizer, ERROR):
Please close() me manually in finalizer.

Kevin.

-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] Behalf Of Toad
Sent: 19 November 2003 16:51
To: [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Subject: [freenet-support] Freenet Stable Build 5039


Freenet stable build 5039 is now available. Update your freenet node
using update.sh, freenet-webinstall.exe, or the jar (save it over
freenet.jar): http://freenetproject.org/snapshots/freenet-latest.jar .
Don't forget to restart the node (you will need to shut it down before
updating on Windows, but the rabbit icon may do this for you).

This build turns off rejecting queries based on output bandwidth usage,
a feature that is unnecessary (we have other ways of limiting bandwidth
usage) and counterproductive to routing. We have been recently tweaking
various settings to try to improve routing, reenabling it was an
experiment, as there are several theories as to what exactly is going on
on Freenet. It was useful, but we now think that disabling it will yield
better routing.

The corresponding unstable build is 6341.
--
Matthew J Toseland - [EMAIL PROTECTED]
Freenet Project Official Codemonkey - http://freenetproject.org/
ICTHUS - Nothing is impossible. Our Boss says so.


___
Support mailing list
[EMAIL PROTECTED]
http://dodo.freenetproject.org/cgi-bin/mailman/listinfo/support


RE: [freenet-support] Freenet port not listening according tofirewall.

2003-11-17 Thread Kevin Bennett
Hmmm.  At a first glance this seems to be working.  After 5 mins there were
8 incoming connections (though none were transferring) and about 60
outbound, some of which were transferring.  No instances of the
non-listening port error this time, but to confuse matters further there are
now a lot of TCP non-syn/non-ack packet on invalid connection. Packet has
been dropped entries, one every few seconds.  If I cross-reference an entry
like this, it corresponds with an outgoing connection that is already open
and in some cases already transferring.  Weird.

I'll leave it running as-is while I go to work and check it again when I get
home.

The firewall is Norton Internet Security 2003, but I have no clue how it
knows if a port is listening or not.

Thanks,

Kevin.

-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] Behalf Of Edward J. Huff
Sent: 17 November 2003 00:50
To: [EMAIL PROTECTED]
Subject: RE: [freenet-support] Freenet port not listening according
tofirewall.


On Sun, 2003-11-16 at 17:51, Kevin Bennett wrote:
...
 BUT.  This is with the firewall switched off.  If I switch the firewall on
 the number of connections to listenPort dwindles over time to 0 and then
 never increases, and the firewall log fills up with thousands of those
TCP
 Syn Packet on non-listening port. Packet has been dropped errors.


Try this:  Switch the firewall on.  Then restart fred.  The firewall
might need to be running when the listen begins.  But I don't quite
understand how that could be, because I don't think any packets are
sent out when listen begins.  How does the firewall know the port
isn't listening, anyway?  What firewall is it?

-- Ed Huff


___
Support mailing list
[EMAIL PROTECTED]
http://dodo.freenetproject.org/cgi-bin/mailman/listinfo/support


RE: [freenet-support] Freenet port not listening according tofirewall.

2003-11-16 Thread Kevin Bennett
Yes, it's Win2K, and yes, netstat -a gives myhostname:0 instead of
0.0.0.0:0 with netstat -a -n.

I've currently got 300+ entries connected to the listenPort and a fair
number are transferring data so yes again, my node is currently working
well.

BUT.  This is with the firewall switched off.  If I switch the firewall on
the number of connections to listenPort dwindles over time to 0 and then
never increases, and the firewall log fills up with thousands of those TCP
Syn Packet on non-listening port. Packet has been dropped errors.

There are, so far as I can tell, three things which might have changed to
cause this behaviour:

1. The OS.  I can rule that out since I haven't run any updates during the
period that this started to happen.

2. The firewall.  Again, no changes to the firewall were made.

3. Fred.  This is the only thing that's changed.  When running 5028, the
unstable builds until NGR was merged into stable, and then 5029/30,
everything was working as expected.  Then I changed to 5031 and bang, no
incoming connections.  (Or it might have been 5032.  I'm not sure exactly
when this happened as I only noticed it by accident when checking the
connection manager page, something which I didn't do more than once or twice
a day before this happened.)

To me this suggests that the problem lies somewhere with the way that Fred
is listening, but if not it wouldn't be the first time I've been wrong about
something :)

Thanks for your help so far,

Kevin.


-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] Behalf Of Edward J. Huff
Sent: 16 November 2003 21:49
To: [EMAIL PROTECTED]
Subject: RE: [freenet-support] Freenet port not listening according
tofirewall.


On Sun, 2003-11-16 at 03:37, Kevin Bennett wrote:
 I only used the -a switch.  If I add -n as well it becomes:

 TCP   0.0.0.0:49247   0.0.0.0:0   LISTENING.

 and many

 TCP   myIP:49247foreignIP:port  ESTABLISHED
...

I suppose that 0.0.0.0:0 means the same thing as
0.0.0.0:*, i.e. that it will accept connections on
any IP and any port.  Is this windows?

Try without -n.  Does 0.0.0.0:0 change to myhostname:0?
That would be kind of weird, but MS$ has done weirder things.
On the other hand, it might be that the situation is different
now and you get 0.0.0.0:0 with -a -n and with -a.

If you have established connections on your listenPort,
they must be incoming so your system seems to be working.
Is the firewall on?

-- Ed Huff



___
Support mailing list
[EMAIL PROTECTED]
http://dodo.freenetproject.org/cgi-bin/mailman/listinfo/support


[freenet-support] Freenet port not listening according to firewall.

2003-11-15 Thread Kevin Bennett
I noticed that once again I have no incoming connections.

Looking at my software firewall logs I see a lot of the following entries
(dozens per minute):

TCP Syn Packet on non-listening port. Packet has been dropped
Source IP address: removed
Destination IP address: removed
TCP Source Port: 4991
TCP Destination Port: 49247
TCP Message Flags: 0x0002

Adding an 'allow all TCP connections to use this port' rule makes no
difference.

If I switch off the software firewall (that's okay as I'm behind a hardware
wall too) then I straight away get plenty of incoming connections.

So for some reason the firewall seems to think that Freenet isn't listening
on 49247 despite the fact that it obviously is.

Does this mean that Freenet isn't advertising its port's 'openness'
correctly?


___
Support mailing list
[EMAIL PROTECTED]
http://dodo.freenetproject.org/cgi-bin/mailman/listinfo/support


[freenet-support] Some advice on thread numbers etc please

2003-11-15 Thread Kevin Bennett
Would someone be so kind as to recommend optimum settings (assuming such
things exist) for maximum threads and maximum connections for a machine
connected to a 512down/256 up ADSL connection?  The box the node runs on and
the connection it uses is used for little except being a node and some
browsing, and has a 20GB store.

Thanks.


___
Support mailing list
[EMAIL PROTECTED]
http://dodo.freenetproject.org/cgi-bin/mailman/listinfo/support


RE: [freenet-support] Freenet port not listening according tofirewall.

2003-11-15 Thread Kevin Bennett
According to netstat -a, 49247 is listening:

  TCPmyhostname:49247   myhostname:0   LISTENING
  TCPmyhostname:49247   myhostname:0   LISTENING
  TCPmyhostname:49247   myhostname:0   LISTENING

with the firewall on, but those are the only entries for that port.

If I disable the firewall I immediately see many like this:

  TCPmyhostname:49247   somebodyelse:portnumber
ESTABLISHED

The reason I ask is that this seemed to happen when updating from either
5030 to 5031 or from 5031 to 5032.  Nothing was changed in the firewall
conf, but all of a sudden I started to see many of the log entries I
mentioned and ended up with no incoming connections so I wondered if maybe
something had broken.

Thanks,

Kevin.


-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] Behalf Of Niklas Bergh
Sent: 15 November 2003 18:16
To: [EMAIL PROTECTED]
Subject: Re: [freenet-support] Freenet port not listening according
tofirewall.



- Original Message -
From: Kevin Bennett [EMAIL PROTECTED]
To: Freenet Support [EMAIL PROTECTED]
Sent: Saturday, November 15, 2003 3:01 PM
Subject: [freenet-support] Freenet port not listening according to firewall.


 I noticed that once again I have no incoming connections.

 Looking at my software firewall logs I see a lot of the following entries
 (dozens per minute):

 TCP Syn Packet on non-listening port. Packet has been dropped
 Source IP address: removed
 Destination IP address: removed
 TCP Source Port: 4991
 TCP Destination Port: 49247
 TCP Message Flags: 0x0002

 Adding an 'allow all TCP connections to use this port' rule makes no
 difference.

 If I switch off the software firewall (that's okay as I'm behind a
hardware
 wall too) then I straight away get plenty of incoming connections.

This definitely indicates to me that the firewall is the problem.

 So for some reason the firewall seems to think that Freenet isn't
listening
 on 49247 despite the fact that it obviously is.

 Does this mean that Freenet isn't advertising its port's 'openness'
 correctly?

Hardly, applications doesn't need to do any kind of 'advertising'.
Applications just open a port and the OS does the rest. What does the
appropriate OS tools (netstat for instance) tell you about which ports that
is open?. Any differences in the output with the firewall on and off?

/N

___
Support mailing list
[EMAIL PROTECTED]
http://dodo.freenetproject.org/cgi-bin/mailman/listinfo/support


___
Support mailing list
[EMAIL PROTECTED]
http://dodo.freenetproject.org/cgi-bin/mailman/listinfo/support


[freenet-support] The logfile told me to report this

2003-11-15 Thread Kevin Bennett
TransferInsert source connection died! Report if occurs often. 

and

TransferInsert source sent bad data! Report if occurs often.

Both have been appearing many times since updating to 5034.

___
Support mailing list
[EMAIL PROTECTED]
http://dodo.freenetproject.org/cgi-bin/mailman/listinfo/support


[freenet-support] No incoming connections

2003-11-08 Thread Kevin Bennett
A few days ago I used to have a pretty good balance of incoming and outgoing
connections.  Then all of a sudden I no longer had any incoming connections
at all, and have had none since.  I have tried a few simple things like
stopping and restarting the node, reseeding etc, but this has not made any
difference.

I've also noticed when restarting the node that all attempts to announce to
other nodes fail.  The failures are usually down to No open connections and
can't contact node (terminal) with the occasional QueryRejected.

It's a permanent node, 5031, Win2K.

Any suggestions as to what I can do to see if it's down to my node or just
network conditions?

Thanks,

Kevin.


___
Support mailing list
[EMAIL PROTECTED]
http://dodo.freenetproject.org/cgi-bin/mailman/listinfo/support


RE: [freenet-support] No incoming connections

2003-11-08 Thread Kevin Bennett
Now that's strange.  All of a sudden I'm back to a normal spread of in and
outbound.

Ah well, weirder things have happened I expect.


___
Support mailing list
[EMAIL PROTECTED]
http://dodo.freenetproject.org/cgi-bin/mailman/listinfo/support


[freenet-support] Viewing rotated logs - Windows Freenet launcher needs updating

2003-11-01 Thread Kevin Bennett
I've switched to using rotating logs, and noticed that whilst the web pages
show the correct log under the 'Recent Logs' link, the system tray icon is
showing my old freenet.log instead of the time-rotated ones.


___
Support mailing list
[EMAIL PROTECTED]
http://dodo.freenetproject.org/cgi-bin/mailman/listinfo/support


[freenet-support] How to tell if my node is working well?

2003-10-31 Thread Kevin Bennett
I've been running a node for a couple of weeks now and am wondering how to
tell if my node is

a) well integrated into the network and
b) filling requests that are sent to it.

There is a bewildering array of graphs and stats, and I have no idea which
ones will give an indication of those 2 things.

Also, in the node reference status page there are some estimate figure that
aren't clear to me.  'Lowest global time estimate', 'Highest global time
estimate' and the first column after the peer address is 'Last estimate'.
Estimates of what?

Thanks.


___
Support mailing list
[EMAIL PROTECTED]
http://dodo.freenetproject.org/cgi-bin/mailman/listinfo/support