[freenet-support] Re: node on a server, and at home?
[EMAIL PROTECTED] writes: I control a unix (linux enterprise) server for my web sites. Can I run a node on this and access it from home? Obviously typing As long as you can install a decent JVM (Sun 1.4.2_05 seems to work reasonably well), yes. http://127.0.0.1: will not pull it up since it is at a server farm in another state. (USA). You need to set fcpHosts (for client programs like FIW, Fuqid, Frost etc) and mainport.allowedHosts (the web interface) to allow access from other computers. Also, using a tunnel (SSH, SSL or VPN) to access the node would be wise. And even then you should refrain from inserting big files via FCP, because it's somewhat bandwidth-intensive. Also, if I have a router at home and 2 comps (XP machines) can I have each computer running a node? Yes, but the limiting factor might be your bandwidth, and your two home nodes will probably end up competing for it. It's better to run a single node and give it more bandwidth. With the above resources how do I get the most out of it? (configuration). My BIGGEST thing is speed. I hate not finding what I am looking for and I hate file not founds. What would be better, unstable or stable? Stable. The network is bigger, and most of the recent performance tweaks are in stable, too. You should run unstable only if you don't mind occassional network meltdowns, updating daily and/or want to help with Freenet development. -- Mika Hirvonen <[EMAIL PROTECTED]> http://nightwatch.mine.nu/ Get Freenet from: http://cs181027153.pp.htv.fi:8891/J0~0J7ajDJE/ ___ Support mailing list [EMAIL PROTECTED] http://news.gmane.org/gmane.network.freenet.support Unsubscribe at http://dodo.freenetproject.org/cgi-bin/mailman/listinfo/support Or mailto:[EMAIL PROTECTED]
[freenet-support] Re: node on a server, and at home?
S writes: On Tue, 10 Aug 2004 10:31:01 +0300 "Markus" <[EMAIL PROTECTED]> wrote: Ouch, typo in Fuqids configuration (wrong port). Now it doesn't say that node is overloaded or down, but I still can't get it to download anything through stunnel, logs say "Fatal error in download thread: EFCPError: recv failed: 10054". 10054 is the Winsock error code for "Connection Reset," which is likely indicative of a bad setup on the remote side. As Mika mentioned, first ensure that the remote node is allowing your IP address to connect to whichever service you're looking for - mainport or FCP. (For FUQID, it's FCP, and note that you lose anonymity making FCP requests to a node you aren't operating locally.) These are set via freenet.conf options on the server running the node. One gotcha is that when you're using a tunnel, is that the node sees the IP address of the _endpoint_ of the tunnel, not the real source IP. So if you're tunneling straight to the computer running the node, access from localhost is enough. -- Mika Hirvonen <[EMAIL PROTECTED]> http://nightwatch.mine.nu/ Get Freenet from: http://cs181027153.pp.htv.fi:8891/J0~0J7ajDJE/ ___ Support mailing list [EMAIL PROTECTED] http://news.gmane.org/gmane.network.freenet.support Unsubscribe at http://dodo.freenetproject.org/cgi-bin/mailman/listinfo/support Or mailto:[EMAIL PROTECTED]
Re: [freenet-support] Re: node on a server, and at home?
> S writes: > > > On Tue, 10 Aug 2004 10:31:01 +0300 > > "Markus" <[EMAIL PROTECTED]> wrote: > > > >> Ouch, typo in Fuqids configuration (wrong port). Now it doesn't say that > >> node is overloaded or down, but I still can't get it to download anything > >> through stunnel, logs say "Fatal error in download thread: EFCPError: recv > >> failed: 10054". > > > > 10054 is the Winsock error code for "Connection Reset," which is likely > > indicative of a bad setup on the remote side. As Mika mentioned, first > > ensure that the remote node is allowing your IP address to connect to > > whichever service you're looking for - mainport or FCP. (For FUQID, it's > > FCP, and note that you lose anonymity making FCP requests to a node you > > aren't operating locally.) These are set via freenet.conf options on the > > server running the node. > > One gotcha is that when you're using a tunnel, is that the node sees the IP > address of the _endpoint_ of the tunnel, not the real source IP. So if > you're tunneling straight to the computer running the node, access from > localhost is enough. > > -- > Mika Hirvonen <[EMAIL PROTECTED]> > http://nightwatch.mine.nu/ > Get Freenet from: http://cs181027153.pp.htv.fi:8891/J0~0J7ajDJE/ Problem solved, it was that "gotcha", FCP was dropping connections from localhost. I commented out "fcpHosts=client.domain.name" so Freenet allows localhost to connect fcp port. Markus ___ Support mailing list [EMAIL PROTECTED] http://news.gmane.org/gmane.network.freenet.support Unsubscribe at http://dodo.freenetproject.org/cgi-bin/mailman/listinfo/support Or mailto:[EMAIL PROTECTED]
