Daxter :
On Feb 13, 2011, at 12:28 PM, Jep wrote:
Daxter :
On Jan 1, 2011, at 7:08 AM, <lukas...@centrum.cz> <lukas...@centrum.cz> wrote:
this is how my node is connected to the network, from page:
Peer statistics

  * Connected: 2
  * Too old: 1
  * Disconnected: 12
  * Never connected: 26
  * Seed nodes: 4
  * Max peers: 40
  * Max strangers: 40


  * Input Rate: 587 B/s (of 512 KiB/s)
  * Output Rate: 1.69 KiB/s (of 128 KiB/s)
  * Session Total Input: 17.1 MiB (1.61 KiB/s average)
  * Session Total Output: 24.7 MiB (2.33 KiB/s average)
  * Payload Output: 2.38 MiB (231 B/sec)(9%)
  * Global Total Input: 35.5 GiB
  * Global Total Output: 40.8 GiB
When i start Freenet, it take maybe one hour to be connected at least 2 nodes, 
result is very, very slow connection to Freenet.

Cann please somebody help?

It really shouldn't be taking that long. Though, the past couple weeks have 
been pretty bad because of low-level changes to Freenet. What OS are you using? 
how long have you had Freenet installed? How long has it been since you've had 
stable connections?
So that we have a better idea of your problem, please run through this quick 
1. update freenet to the most recent version. it can be done by running 
"update.sh" in your Freenet directory.
2. ensure that port forwarding is set up correctly (do some googling. if it 
still doesn't make sense, ask)
3. If at this point it still isn't working, temporarily turn off your router 
and computer firewall to see if that doesn't fix the issue.
For the sake of clear results, try to not have tons of extra stuff running 
while doing all this, and be sure to restart when it might help.
temporarily turn off your router
This I don't understand, no router = no network; what to test then?

Look at the rest of the phrase:

temporarily turn off your router and computer firewall

In other words: temporarily turn off your router firewall and your computer 

Ah. Could've known there's some kind of misunderstanding.

Can confirm a software firewall can be a problem, mine still kept the FN ports 
closed no matter I told it otherwise.
There was a link somewhere in the FN help pages pointing to a site that can 
test if particular ports are actually opened.

Oh yeah, thanks for reminding me. The one I use all the time is 
[www.canyouseeme.org]. I can't believe I forgot to mention that.

A problem when choosing a firewall app is that many only allow for applications 
to connect, not to open ports manually. Back then the wrapper ran as a windows 
service and I didn't see possibillities to allow a service internet access.

I'm not too familiar with the specifics of windows networking--could you 
explain in greater detail?

Me neither, I only know what practice forces me to.
The app I used is a free firewall, GhostWall, which did fine for me until I needed the FN ports open. Made 'holes' and yet it kept them closed. Exit GhostWall.

Most more elaborate firewalls, like ZoneAlarm and Outpost want you to select an app which you can allow upstream internet access that way. Which is a good approach because the main function of a winz firewall when there's already a NATting router, is to prevent stuff on my box to 'phone home' or do malicious things. When something wants to connect to the net, then the firewall asks what I want to do with it, making it a pain in the ... the first days because each and every program must be allowed or denied. And mostly a PITA because not all attempts to connect are picked up by the firewall but still blocked. Such a firewall makes it hard on me if there can't simply be port numbers opened. What is the .exe of a winz service, I don't know.

Is this a good answer?

Support mailing list
Unsubscribe at http://emu.freenetproject.org/cgi-bin/mailman/listinfo/support
Or mailto:support-requ...@freenetproject.org?subject=unsubscribe

Reply via email to