Many thx for your early reply!
Input 1 hour ago   4.26 KiB/Sec
Output                 4.54 KiB/Sec
Both numbers increase as time passes (they are now  7.60 and 5.44...).
Port Darknet   62774   status: unknown
       Opennet  48085   status: may be behind a NAT (although I DID open it in 
my server)
Node has been active for several weeks, only upgrades have been applied.
Hope this helps find out the problem.
Kind regards
Guillaume
PS: Dont' know if this can be meaningful but I attach a copy of the wrapper.log 
file..


> To: support at freenetproject.org
> From: dennisn at dennisn.dyndns.org
> Date: Wed, 24 Nov 2010 20:12:08 -0500
> Subject: Re: [freenet-support] Why, why, why, oooh why???!!!
> 
> On Wed, 24 Nov 2010 19:45:30 +0000, Guillaume LEROY wrote:
> > 
> > Hello support!
> > I did upgrade to Freenet 1305 and I seem to have a correct node ID
> > and correct connection; However, I cannot refresh the boards in FMS
> > and cannot send messages either. Same thing with Frost. Boards carry
> > 0 messages and I cannot insert one... I am running on Vista 32 and
> > all the necessray ports have been opened in my server. What can I do?
> > Thank you for your help. Guillaume 
> 
> On the Status > Statistics page of your fproxy, what are your Input and
> Output rates? And on the Status > Internet connection, what is the
> status of your opennet/darknet ports? How long has your node been up?
> 
> _______________________________________________
> Support mailing list
> Support at freenetproject.org
> http://news.gmane.org/gmane.network.freenet.support
> Unsubscribe at http://emu.freenetproject.org/cgi-bin/mailman/listinfo/support
> Or mailto:support-request at freenetproject.org?subject=unsubscribe

-------------- next part --------------
An HTML attachment was scrubbed...
URL: 
<https://emu.freenetproject.org/pipermail/support/attachments/20101125/7c86cac8/attachment.html>
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: wrapper.log
URL: 
<https://emu.freenetproject.org/pipermail/support/attachments/20101125/7c86cac8/attachment.ksh>

Reply via email to