[freenet-support] (no subject)

[Markus Hahn]

Dear Supporters,

I am a total newbie in freenet. Every time I start freenet I get the alert that 
my node lies behind a NAT-device or a Firewall and that I should forward my 
port-Number 11833. After some discovery-attempts in the administration tool of 
my router I found out that there is actually a firewall running. 
I am able to reach and open some of the sites I want to, but frequently I get 
the message that a site seems to be unreachable, sometimes concerning a site 
that opens some minutes later.
I am totally new in this subject and all my real-world-friends are no-techies 
and no-nerds, so I still have no "firends" in the sense of trustworthy nodes to 
connect with or in the sense of darknet-members. Might this be the reason why 
some sites are closed for me?
Should I try to manipulate the router in order to "forward" or should I turn 
off the firewall?
Or is freenet running properly and the seemingly closed doors seem so due to 
the restrictions a newbie in darknet with a fresh node has to come around with?


Thank you a lot for the support



-- next part --
An HTML attachment was scrubbed...
URL: 
<https://emu.freenetproject.org/pipermail/support/attachments/20081115/e9872bf1/attachment.html>

[freenet-support] (no subject)

[Matthew Toseland]

Correct. This should go away after 1178 is mandatory on Sunday, provided you 
restart your node at that point. However, the trend so far suggests that it 
won't go away and is still present. :< In any case we need to be told if it 
happens after Sunday.

On Saturday 15 November 2008 08:54, Peter J. wrote:
> On Saturday 15 November 2008 09:48:26 Peter J. wrote:
> > On Saturday 15 November 2008 01:05:57 Mike Cook wrote:
> > > 2 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 https://bugs.freenetproject.org/ 
or
> > > at support at freenetproject.org. Please include this message and what
> > > version of the node you are running. The affected peers (you may not 
want
> > > to include this in your bug report if they are darknet peers) are:
> > >
> > >
> > > My Node
> > >  * Freenet 0.7 Build #1178 r23592M
> > >  * Freenet-ext Build #24 r23199
> >
> > 
> >
> > Got the same message with the same build of freenet. But I've got 4 peers
> > reported to have severe problems.
> 
> 
> 
> Ok I didn't read the other new messages on the list before I read this one. 
So 
> it is to be expected that this message is gone after Sunday when the new 
> version of freenet is mandatory? 
> 
> 
> ___
> 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 --
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 827 bytes
Desc: not available
URL: 
<https://emu.freenetproject.org/pipermail/support/attachments/20081115/bda3b7f7/attachment.pgp>

[freenet-support] Freenet 0.7 build 1178 (and 1176, 1177)

[Dennis Nezic]

On Fri, 14 Nov 2008 18:21:50 -0500, Dennis Nezic
 wrote:

> On Fri, 14 Nov 2008 19:39:45 +, Matthew Toseland
>  wrote:
> 
> > Freenet 0.7 build 1178 is now available.

I spoke too soon. It works fine for an hour or two, but then, at least
for me, all communcation (net input/output) STOPS. (Well, ~100Bytes/sec
both ways--but, for all intents and purposes, it's offline.)

After almost exactly 3 hours, it begins Announcing itself
(successfully, apparently) although nothing really changes.

And this is repeatable. Restarting the node leads to the exact same
behaviour.

There are very few errors in the freenet logs. A couple per hour,
maybe. But, the "common" one that I spotted freenet.node.PeerManager,
UdpSocketHandler ERROR addPeerNodeStatus(): "node already in
peerNodeStatuses" ... "status DISCONNECTED". But, it's ip address is
still listed as CONNECTED, and data is still being transferred with it,
although the port number in the log file is different than the one that
is listed as connected. (I'm not sure if this is related.)

[freenet-support] Some downloads failing since updating to 1178

[Guido Winkelmann]

I can confirm the described behaviour.

My system:
Linux on x86_64, Java 1.6.0_07-b06.
The downloads were started with frost, but they have not been inserted by 
Frost.

Guido

Am Freitag, 14. November 2008 23:01:27 schrieb Victor Denisov:
> Several downloads from my download queue failed to start after my node
> autoupgraded to 1178 (some *did* restart normally). Error messages
> (Reason column in the "Failed downloads") in the web interface vary:
>
> Temporary files error: invalid stored block lengths
> Temporary files error: Corrupt GZIP trailer
> Temporary files error: invalid literal/length code
> Temporary files error: invalid distance code
> Temporary files error: invalid block type
>
> The node gives me two options: Remove and Restart. If I click on
> restart, the item fails almost immediately with the same error it had
> before.
>
> I've migrated to salted-hash store when 1175 went out. I tried
> restarting the node again and cleaning up ./tmp - not helped any. I have
> plenty of disk space. Log files don't seem to contain anything related
> to the issue I'm experiencing.
>
> Running on Windows XP x64 with Java 1.6.0_06, 64 bit.
>
> Regards,
> Victor Denisov.

-- 
Truth as the authority instead of truth by authority!
-- 
|  _  | ASCII Ribbon Campaign Against HTML Emails.
| ( ) |
|  X  |
| / \ |

[freenet-support] Probably a bug: please report: 2 peers forcibly disconnected due to not acknowledging packets.

[d...@darkn3t.net]

2 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
https://bugs.freenetproject.org/<http://127.0.0.1:/?_CHECKED_HTTP_=https://bugs.freenetproject.org/>or
at
support at freenetproject.org. Please include this message and what version of
the node you are running. The affected peers (you may not want to include
this in your bug report if they are darknet peers) are:

   - 85.25.130.157:9134
   - 81.209.35.6:10232


 Version du noeud

   - Freenet 0.7 version #1178 r23592M
   - Freenet-ext version #24 r23199

  Informations sur la JVM

   - M?moire utilis?e par Java : 29.4 MiB
   - M?moire allou?e par Java : 59.6 MiB
   - M?moire maximum pour Java : 254 MiB
   - Processus en cours : 223/500
   - Processeurs disponibles : 1
   - Version de Java : 1.6.0_07
   - Distributeur de la JVM : Sun Microsystems Inc.
   - Version de la JVM : 10.0-b23
   - Nom de l'OS : Linux
   - Version de l'OS : 2.6.24.5-grsec--grs-ipv6-32
   - Architecture de l'OS : i386


 Load limiting

   - Global window: 20.192453353961174
   - Real global window: 1.3461635569307449
   - CHK Request RTT=6,763s delay=0,334s bw=98107B/sec
   - SSK Request RTT=46,709s delay=2,313s bw=442B/sec
   - CHK Insert RTT=24,976s delay=1,236s bw=26511B/sec
   - SSK Insert RTT=20,472s delay=1,013s bw=1010B/sec
   - CHK window: freenet.node.ThrottleWindowManager at 1aa8b56 w:
   2.5080165060084187, d:0.64041173=47719/74513, SSK window:
   freenet.node.ThrottleWindowManager at 1a1cf72 w: 0.7387861074483295,
   d:0.6570007=52156/79385
   - Request window: freenet.node.ThrottleWindowManager at 3a5cc5 w:
   0.9491558356793726, d:0.8450394=4608/5453, Insert window:
   freenet.node.ThrottleWindowManager at 1a0b7ca w: 2.9888353678397963,
   d:0.27093595=55/203
-- next part --
An HTML attachment was scrubbed...
URL: 
<https://emu.freenetproject.org/pipermail/support/attachments/20081115/c7a28636/attachment.html>

[freenet-support] bug

[dalej8]

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
https://bugs.freenetproject.org/

or at support at freenetproject.org. Please include this message and what
version of the node you are running. The affected peers (you may not
want to include this in your bug report if they are darknet peers) are:

* 83.250.207.180:30547

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
https://bugs.freenetproject.org/

or at support at freenetproject.org. Please include this message and what
version of the node you are running. The affected peers (you may not
want to include this in your bug report if they are darknet peers) are:

* 75.172.65.161:55979

Re: [freenet-support] Freenet 0.7 build 1178 (and 1176, 1177)

[Dennis Nezic]

On Fri, 14 Nov 2008 18:21:50 -0500, Dennis Nezic
<[EMAIL PROTECTED]> wrote:

> On Fri, 14 Nov 2008 19:39:45 +, Matthew Toseland
> <[EMAIL PROTECTED]> wrote:
> 
> > Freenet 0.7 build 1178 is now available.

I spoke too soon. It works fine for an hour or two, but then, at least
for me, all communcation (net input/output) STOPS. (Well, ~100Bytes/sec
both ways--but, for all intents and purposes, it's offline.)

After almost exactly 3 hours, it begins Announcing itself
(successfully, apparently) although nothing really changes.

And this is repeatable. Restarting the node leads to the exact same
behaviour.

There are very few errors in the freenet logs. A couple per hour,
maybe. But, the "common" one that I spotted freenet.node.PeerManager,
UdpSocketHandler ERROR addPeerNodeStatus(): "node already in
peerNodeStatuses" ... "status DISCONNECTED". But, it's ip address is
still listed as CONNECTED, and data is still being transferred with it,
although the port number in the log file is different than the one that
is listed as connected. (I'm not sure if this is related.)
___
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] Bug Report

[Ted Hexter]

2 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 https://bugs.freenetproject.org/ 
or at support at freenetproject.org. Please include this message and what
version of the node you are running. The affected peers (you may not
want to include this in your bug report if they are darknet peers) are:
* 24.213.86.235:29470
* 217.236.111.120:25601
-- next part --
An HTML attachment was scrubbed...
URL: 
<https://emu.freenetproject.org/pipermail/support/attachments/20081115/92906506/attachment.html>

[freenet-support] (no subject)

[Peter J.]

On Saturday 15 November 2008 09:48:26 Peter J. wrote:
> On Saturday 15 November 2008 01:05:57 Mike Cook wrote:
> > 2 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 https://bugs.freenetproject.org/ or
> > at support at freenetproject.org. Please include this message and what
> > version of the node you are running. The affected peers (you may not want
> > to include this in your bug report if they are darknet peers) are:
> >
> >
> > My Node
> >  * Freenet 0.7 Build #1178 r23592M
> >  * Freenet-ext Build #24 r23199
>
> 
>
> Got the same message with the same build of freenet. But I've got 4 peers
> reported to have severe problems.



Ok I didn't read the other new messages on the list before I read this one. So 
it is to be expected that this message is gone after Sunday when the new 
version of freenet is mandatory? 

[freenet-support] (no subject)

[Peter J.]

On Saturday 15 November 2008 01:05:57 Mike Cook wrote:
> 2 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 https://bugs.freenetproject.org/ or at
> support at freenetproject.org. Please include this message and what version of
> the node you are running. The affected peers (you may not want to include
> this in your bug report if they are darknet peers) are:
>
>
> My Node
>  * Freenet 0.7 Build #1178 r23592M
>  * Freenet-ext Build #24 r23199
>


Got the same message with the same build of freenet. But I've got 4 peers 
reported to have severe problems.

Re: [freenet-support] (no subject)

[Matthew Toseland]

Correct. This should go away after 1178 is mandatory on Sunday, provided you 
restart your node at that point. However, the trend so far suggests that it 
won't go away and is still present. :< In any case we need to be told if it 
happens after Sunday.

On Saturday 15 November 2008 08:54, Peter J. wrote:
> On Saturday 15 November 2008 09:48:26 Peter J. wrote:
> > On Saturday 15 November 2008 01:05:57 Mike Cook wrote:
> > > 2 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 https://bugs.freenetproject.org/ 
or
> > > at [EMAIL PROTECTED] Please include this message and what
> > > version of the node you are running. The affected peers (you may not 
want
> > > to include this in your bug report if they are darknet peers) are:
> > >
> > >
> > > My Node
> > >  * Freenet 0.7 Build #1178 r23592M
> > >  * Freenet-ext Build #24 r23199
> >
> > 
> >
> > Got the same message with the same build of freenet. But I've got 4 peers
> > reported to have severe problems.
> 
> 
> 
> Ok I didn't read the other new messages on the list before I read this one. 
So 
> it is to be expected that this message is gone after Sunday when the new 
> version of freenet is mandatory? 
> 
> 
> ___
> 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]
> 
> 


pgpn7V3QtXSJl.pgp
Description: PGP signature
___
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] Some downloads failing since updating to 1178

[Guido Winkelmann]

I can confirm the described behaviour.

My system:
Linux on x86_64, Java 1.6.0_07-b06.
The downloads were started with frost, but they have not been inserted by 
Frost.

Guido

Am Freitag, 14. November 2008 23:01:27 schrieb Victor Denisov:
> Several downloads from my download queue failed to start after my node
> autoupgraded to 1178 (some *did* restart normally). Error messages
> (Reason column in the "Failed downloads") in the web interface vary:
>
> Temporary files error: invalid stored block lengths
> Temporary files error: Corrupt GZIP trailer
> Temporary files error: invalid literal/length code
> Temporary files error: invalid distance code
> Temporary files error: invalid block type
>
> The node gives me two options: Remove and Restart. If I click on
> restart, the item fails almost immediately with the same error it had
> before.
>
> I've migrated to salted-hash store when 1175 went out. I tried
> restarting the node again and cleaning up ./tmp - not helped any. I have
> plenty of disk space. Log files don't seem to contain anything related
> to the issue I'm experiencing.
>
> Running on Windows XP x64 with Java 1.6.0_06, 64 bit.
>
> Regards,
> Victor Denisov.

-- 
Truth as the authority instead of truth by authority!
-- 
|  _  | ASCII Ribbon Campaign Against HTML Emails.
| ( ) |
|  X  |
| / \ |
___
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] Some downloads failing since updating to 1178

[Victor Denisov]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

>> Argh. Are these simple downloads (CHK at .../filename), or parts of
freesites
>> (mutliple slashes, maybe USKs)??

All simple CHKs, inserted with Frost (judging by the redirects).

Regards,
Victor Denisov.
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.5 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFJHhUA1O5++4rTuI0RAuaSAKCknxRlhjs1GXrec8vXKCNpzNMo5ACdHk8U
IZ3SQUslfl4EZprfUVpF6r0=
=PMOs
-END PGP SIGNATURE-

[freenet-support] Wrapper does not start

[free...@chello.at]

 Matthew Toseland  schrieb:
> On Friday 14 November 2008 01:09, freenet at chello.at wrote:
> > Since last update on 13.11. Freenet fails to start.
> > I get the following Message in wrapper.log:
> 
> You let freenet auto-update itself, or you used update.sh/update.cmd?

I used update.cmd

> If you let Freenet auto-update itself, then please send me your wrapper.log, 
> as this is a serious bug we've been trying to gather more info on ...
> 
> You can get your node back by running update.sh/update.cmd.

I did it, but then the same error happens again.  :(
Is there no "rollback" for updates?

[freenet-support] Some downloads failing since updating to 1178

[Victor Denisov]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Several downloads from my download queue failed to start after my node
autoupgraded to 1178 (some *did* restart normally). Error messages
(Reason column in the "Failed downloads") in the web interface vary:

Temporary files error: invalid stored block lengths 
Temporary files error: Corrupt GZIP trailer
Temporary files error: invalid literal/length code
Temporary files error: invalid distance code
Temporary files error: invalid block type

The node gives me two options: Remove and Restart. If I click on
restart, the item fails almost immediately with the same error it had
before.

I've migrated to salted-hash store when 1175 went out. I tried
restarting the node again and cleaning up ./tmp - not helped any. I have
plenty of disk space. Log files don't seem to contain anything related
to the issue I'm experiencing.

Running on Windows XP x64 with Java 1.6.0_06, 64 bit.

Regards,
Victor Denisov.
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.5 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFJHfU31O5++4rTuI0RAhAFAKDFwm8VLevPNMI3v/+ArCgrIkAs0wCgp7kX
rcAT4OtPrWEnOiMuRGKSz68=
=YYIA
-END PGP SIGNATURE-

Re: [freenet-support] (no subject)

[Peter J.]

On Saturday 15 November 2008 09:48:26 Peter J. wrote:
> On Saturday 15 November 2008 01:05:57 Mike Cook wrote:
> > 2 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 https://bugs.freenetproject.org/ or
> > at [EMAIL PROTECTED] Please include this message and what
> > version of the node you are running. The affected peers (you may not want
> > to include this in your bug report if they are darknet peers) are:
> >
> >
> > My Node
> >  * Freenet 0.7 Build #1178 r23592M
> >  * Freenet-ext Build #24 r23199
>
> 
>
> Got the same message with the same build of freenet. But I've got 4 peers
> reported to have severe problems.



Ok I didn't read the other new messages on the list before I read this one. So 
it is to be expected that this message is gone after Sunday when the new 
version of freenet is mandatory? 


___
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] (no subject)

[Peter J.]

On Saturday 15 November 2008 01:05:57 Mike Cook wrote:
> 2 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 https://bugs.freenetproject.org/ or at
> [EMAIL PROTECTED] Please include this message and what version of
> the node you are running. The affected peers (you may not want to include
> this in your bug report if they are darknet peers) are:
>
>
> My Node
>  * Freenet 0.7 Build #1178 r23592M
>  * Freenet-ext Build #24 r23199
>


Got the same message with the same build of freenet. But I've got 4 peers 
reported to have severe problems.
___
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] (no subject)

[Mike Cook]

2 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 https://bugs.freenetproject.org/ or at support at 
freenetproject.org. Please include this message and what version of the node 
you are running. The affected peers (you may not want to include this in your 
bug report if they are darknet peers) are:


My Node
 * Freenet 0.7 Build #1178 r23592M
 * Freenet-ext Build #24 r23199