help
support-requ...@freenetproject.org wrote:
> Send Support mailing list submissions to
> support@freenetproject.org
>
> To subscribe or unsubscribe via the World Wide Web, visit
> http://emu.freenetproject.org/cgi-bin/mailman/listinfo/support
> or, via email, send a message with subject or body 'help' to
> support-requ...@freenetproject.org
>
> You can reach the person managing the list at
> support-ow...@freenetproject.org
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of Support digest..."
>
>
> Today's Topics:
>
>1. Re: freenet fails to run 3 (Evan Daniel)
>2. Re: freenet fails to run 3 (Evan Daniel)
>3. Re: freenet fails to run 3 (Egbert van der Meer)
>4. Re: freenet fails to run 3 (Evan Daniel)
>5. Re: freenet fails to run 3 (Egbert van der Meer)
>6. Re: freenet fails to run 4 (Egbert van der Meer)
>
>
> --
>
> Message: 1
> Date: Sat, 20 Jun 2009 09:57:30 -0400
> From: Evan Daniel
> Subject: Re: [freenet-support] freenet fails to run 3
> To: virtualstud...@tiscali.nl, support@freenetproject.org
> Message-ID:
> <4f9383510906200657p209e0acboa6239d662b1ed...@mail.gmail.com>
> Content-Type: text/plain; charset=ISO-8859-1
>
> On Sat, Jun 20, 2009 at 6:32 AM, Egbert van der
> Meer wrote:
>> No matter wich links I try to load, non of them do.
>> Not after one hour, not after one day and not after one week.
>> I am not new to freenet and I know it is slow but this symply not working at
>> all.
>>
>> Also FROST has problems with it.
>> Looks to me on the contrary it is not 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:support-requ...@freenetproject.org?subject=unsubscribe
>>
>
> This is a very weird problem.
>
> What browser and OS are you using (including versions)?
>
> It would be helpful to have a paste of your full statistics page in
> advanced mode, your wrapper.log (or at least the recent portions), and
> your freenet-latest.log. (If they're large, it would be best to put
> them online somewhere rather than mailing to the list; if you can't do
> that, emailing them just to me is fine. I'd warn about potential
> anonymity issues with freenet-latest.log, but it doesn't sound like
> it's working enough for that to be a problem :/ )
>
> Evan Daniel
>
> P.S. If you could continue this thread instead of starting new ones, I
> would find that easier to organize and see everything you've posted,
> and be less likely to ask questions you've already answered.
>
>
> --
>
> Message: 2
> Date: Sat, 20 Jun 2009 14:51:50 -0400
> From: Evan Daniel
> Subject: Re: [freenet-support] freenet fails to run 3
> To: virtualstud...@tiscali.nl
> Cc: support@freenetproject.org
> Message-ID:
> <4f9383510906201151x680be959x807071c9e7c9f...@mail.gmail.com>
> Content-Type: text/plain; charset=ISO-8859-1
>
> On Sat, Jun 20, 2009 at 11:40 AM, Egbert van der
> Meer wrote:
>> I am using Windows XP and Firefox both up to date.
>> I hope this mail will not bounce because it'srather big.
> [...]
>> Node status overview * bwlimitDelayTime:
>> 0ms * nodeAveragePingTime: 378ms * darknetSizeEstimateSession: 0 nodes *
>> opennetSizeEstimateSession: 57 nodes * nodeUptime: 58m27s *
>> routingMissDistance: 0, * backedOffPercent: 0,0% * pInstantReject:
>> 100,0% * unclaimedFIFOSize: 0 * RAMBucketPoolSize: 168 B / 10.0 MiB *
>
> First, notice the pInstantReject: 100%. This means your node is
> rejecting all requests, ie something is seriously wrong. This
> normally means that either your network is badly misbehaving or
> Freenet is starved for CPU time. Also, total payload output of 0B
> means that your node has never had a connection to another node that
> completed and lasted long enough to handle a (successful) request.
>
> Second, the wrapper.log shows *lots* of announcements. This isn't
> normal. I *strongly* suspect there is something wrong with your
> network connection. The obvious suspects are port forwarding at your
> router for UDP ports (not TCP!), and your ISP doing something weird.
> If you're absolutely, 100% certain your UDP ports are properly
> forwarded, find a computer (ideally on a different ISP) and test
> whether you can send UDP packets and receive them to the ports in
> question. I've used iperf for that purpose, but I'm sure there are
> other ways to do it as well.
>
> The other possible source of problems is overzealous or misconfigured
> firewall or antivirus software. If you're using any such, consider
> disabling them to test whether that solves the problem.
>
> If none of those gets anywhere, I'm stumped. Perhaps someone else has
> a better idea.
>
> Evan Dan
