On Sun, 2003-11-16 at 20:50, Art Charbonneau wrote: > Occasionally I am getting one or two levels into "The Freedom Engine", > but mainly I'm just "waiting for 127.0.0.1...". It's something like > "Waiting for Godot" -- you know something is supposed to be happening, > but you don't know just what. > > ;-) > > A couple questions (I'm running build 5036): > > 1. When the message in my browser is, "waiting for 127.0.0.1...", is > it best to leave it running, or to shut down it down and try again > later? If the advice is "wait", how long? Ten minutes? An hour?
If you use mozilla, you can open lots of tabs in one window and keep a lot of requests running in parallel. Or else use "open link in a new window." Then leave it running overnight. <kernel_panic> firebird displays "Waiting for localhost" in the bar <kernel_panic> so, image ok == site up ; image broken == site down ? <greycat> sort of <ejhuff> What you do is open each bookmark in a new tab, and go read your email. <kernel_panic> lol <ejhuff> Image broken means click reload and let it try again. <kernel_panic> ok > > 2. I notice that quite often the load is 100%. Am I queued, or > rejected, along with everyone else? Do I have any priority at my own > node? High load means _your_ node is too busy to accept more queries from other nodes. Local requests go in through a different interface (fproxy -- the web interface, or FCP -- Freenet Client Protocol). Remote requests go through FNP -- FreeNet Protocol. > > 3. I'm behind a software firewall, and have set "local host" to the > firewall IP, with port forwarding to my machine. Is that correct? Do you mean the configuration parameter named IPAddress? (I don't know if windows users see the actual parameter names or not). Look on the "Open Connections" page. If you have incoming connections, it must be right. > > 4. Is 127.0.0.1 a node I must go through? Is it my node? Yes. All IP numbers beginning with 127 are reserved for your own machine. Normally, your hosts file contains a line attaching the name localhost to 127.0.0.1. That is not specific to Freenet. And normally your machine will have a virtual network interface called "loopback", and the IP routing table will specify that to get to network number 127.0.0.0/8, you send traffic to the loopback interface. Loopback doesn't actually send the data anywhere, it just pretends the data came in from the outside and processes it as if it did. Freenet listens on port 8888 of 127.0.0.1 for HTTP requests, i.e., it acts as a web server. That part of Freenet is called fproxy. > > 5. Should Freenet be stopped and started occasionally? (I'm pretty > much just leaving it running.) Check for a new release regularly. The gateway page (where the load bargraph is) will say "build N (latest M)", whenever it encounters a node which claims to be build M, M > N and M < 6000. (Otherwise it would always say "latest 63xx" due to unstable builds on the same network). If you see that, download the new version and replace your freenet.jar. There might be an automatic way to do that, but I don't use Windows, so I don't know for sure. Also, check the log file to make sure something hasn't gone wrong, like an "out of memory" error. If you see that, restart it. -- Ed Huff
signature.asc
Description: This is a digitally signed message part
_______________________________________________ Support mailing list [EMAIL PROTECTED] http://dodo.freenetproject.org/cgi-bin/mailman/listinfo/support
