[freenet-support] Accessing Freenet 0.7 node over LAN?

[freenet.me...@spamgourmet.com]

I have my 0.5 node set up to allow me to use fproxy and FCP over the
LAN.  This is because my server is up 24/7 and is the best place to run
my node, but my desktop is the better place for browsers and Frost.

I just tried 0.7, and couldn't find anywhere in the configuration page
to do this.  Is this feature planned before 0.7 is released?  Can I
manually add a line to freenet.ini for this?

The relevant lines from my existing freenet.conf that I want to
reproduce are:

mainport.allowedHosts=127.0.0.1,192.168.64.0/24
fcpHosts=127.0.0.1,192.168.64.0/24

[freenet-support] Accessing Freenet 0.7 node over LAN? message 3 of 20)

[freenet.me...@spamgourmet.com]

Whoops, sorry for repeating an earlier question - I did look at the
mailing list archives, but somehow didn't notice it.

I set this in freenet.ini:

fproxy.bindTo=192.168.64.135

But I get an exception when I try to start the node:

Apr 23, 2006 10:21:14:155 (freenet.node.Node, main, ERROR): Failed to
start fproxy: java.net.BindException: Cannot assign requested address
java.net.BindException: Cannot assign requested address
at java.net.PlainSocketImpl.socketBind(Native Method)
at java.net.PlainSocketImpl.bind(Unknown Source)
at java.net.ServerSocket.bind(Unknown Source)
at java.net.ServerSocket.(Unknown Source)
at
freenet.clients.http.SimpleToadletServer.(SimpleToadletServer.java:142)
at
freenet.clients.http.FproxyToadlet.maybeCreateFproxyEtc(FproxyToadlet.java:219)
at freenet.node.Node.start(Node.java:1024)
at freenet.node.Node.main(Node.java:509)

Did I do something wrong, or is this just alpha bugginess?

Joseph Terranova - joeterranova at gmail.com wrote:
> As Toseland has told other mailing list posters, the only way to do so
> in .7 is to change your fproxy.bindTo to your lan ip address (ie
> 192.168.x.x). You'll be able to connect from on the lan, but
> unfortunately unable to do so from the local server.
> 
> On 4/22/06, *freenet.mexon at spamgourmet.com
> *  > wrote:
> 
> I have my 0.5 node set up to allow me to use fproxy and FCP over the
> LAN.  This is because my server is up 24/7 and is the best place to run
> my node, but my desktop is the better place for browsers and Frost.
> 
> I just tried 0.7, and couldn't find anywhere in the configuration page
> to do this.  Is this feature planned before 0.7 is released?  Can I
> manually add a line to freenet.ini for this?
> 
> The relevant lines from my existing freenet.conf that I want to
> reproduce are:
> 
> mainport.allowedHosts=127.0.0.1 ,192.168.64.0/24
> 
> fcpHosts=127.0.0.1 ,192.168.64.0/24
> 
> ___
> 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
> 
> 
> 
> 
> 
> ___
> 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

[freenet-support] Accessing Freenet 0.7 node over LAN? message 6 of 20) message 3 of 20)

[freenet.me...@spamgourmet.com]

Sorry for the noise.  I just realised that I should be binding to the
address of the machine that Freenet is running on, not the address of
the machine I want to give access to.  That works now.  I added this
info to the wiki.

freenet.mexon at spamgourmet.com wrote:
> Whoops, sorry for repeating an earlier question - I did look at the
> mailing list archives, but somehow didn't notice it.
> 
> I set this in freenet.ini:
> 
> fproxy.bindTo=192.168.64.135
> 
> But I get an exception when I try to start the node:
> 
> Apr 23, 2006 10:21:14:155 (freenet.node.Node, main, ERROR): Failed to
> start fproxy: java.net.BindException: Cannot assign requested address
> java.net.BindException: Cannot assign requested address
> at java.net.PlainSocketImpl.socketBind(Native Method)
> at java.net.PlainSocketImpl.bind(Unknown Source)
> at java.net.ServerSocket.bind(Unknown Source)
> at java.net.ServerSocket.(Unknown Source)
> at
> freenet.clients.http.SimpleToadletServer.(SimpleToadletServer.java:142)
> at
> freenet.clients.http.FproxyToadlet.maybeCreateFproxyEtc(FproxyToadlet.java:219)
> at freenet.node.Node.start(Node.java:1024)
> at freenet.node.Node.main(Node.java:509)
> 
> Did I do something wrong, or is this just alpha bugginess?
> 
> Joseph Terranova - joeterranova at gmail.com wrote:
> 
>>As Toseland has told other mailing list posters, the only way to do so
>>in .7 is to change your fproxy.bindTo to your lan ip address (ie
>>192.168.x.x). You'll be able to connect from on the lan, but
>>unfortunately unable to do so from the local server.
>>
>>On 4/22/06, *freenet.mexon at spamgourmet.com
>>* >> wrote:
>>
>>I have my 0.5 node set up to allow me to use fproxy and FCP over the
>>LAN.  This is because my server is up 24/7 and is the best place to run
>>my node, but my desktop is the better place for browsers and Frost.
>>
>>I just tried 0.7, and couldn't find anywhere in the configuration page
>>to do this.  Is this feature planned before 0.7 is released?  Can I
>>manually add a line to freenet.ini for this?
>>
>>The relevant lines from my existing freenet.conf that I want to
>>reproduce are:
>>
>>mainport.allowedHosts=127.0.0.1 ,192.168.64.0/24
>>
>>fcpHosts=127.0.0.1 ,192.168.64.0/24
>>
>>___
>>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
>>
>>
>>
>>
>>
>>___
>>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
> 
> 
> ___
> 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
> 

[freenet-support] Resized datastore, now all my connections have gone?

[freenet.me...@spamgourmet.com]

Hi,

I'm at a loss on this one.  A few days ago I tried to resize my
datastore down from 40G to 30G by editing freenet.conf.  But now the
thing won't connect to anyone.  There aren't any errors in the log, on
the console, or in the web interface that I can see.  It's just not
connecting.

I tried pinging some of the machines in the seednodes, and a couple of
them were visible, so the network's OK.  I'm not behind a NAT, although
my ISP switches my IP address once a day (which worked fine before).  I
had a firewall running (which also worked fine before), but I've turned
it off and it made no difference.

I'm running Freenet 0.5 Build 5107 under Sun Java 1.4.2_08.  The machine
is running Debian Sarge.

My last trick was to try moving away the store to store.bak and starting
again, on the grounds that maybe my screwing with the datastore size
broke something.  But that doesn't seem to have made any difference either.

Any ideas?

Here's what's in freenet.conf:

listenPort=12378
seedNodes=seednodes.ref
storeSize=30G
outputBandwidthLimit=12000
mainport.bindAddress=*
mainport.allowedHosts=127.0.0.1,192.168.64.0/24
fcpHosts=127.0.0.1,192.168.64.0/24

And here's a log file:

24-Jul-2006 19:36:59 (freenet.node.Main, main, NORMAL): Starting Freenet
(Fred)
0.5 node, build #5107 on JVM Sun Microsystems Inc.:Java HotSpot(TM)
Client VM:1.4.2_08-b03
24-Jul-2006 19:37:18 (freenet.node.Main, main, NORMAL): loading node
keys: node
24-Jul-2006 19:37:18 (freenet.node.Main, main, NORMAL): Read node file
24-Jul-2006 19:37:19 (freenet.node.Main, main, NORMAL): starting filesystem
24-Jul-2006 19:38:53 (freenet.node.Main, main, NORMAL): loading data store
24-Jul-2006 19:38:53 (freenet.node.Main, main, NORMAL): loading routing
table
24-Jul-2006 19:38:54 (freenet.node.Main, main, NORMAL): From output: 48000.0
24-Jul-2006 19:38:54 (freenet.node.Main, main, NORMAL): Setting default
initTransferRate to 48000.0
24-Jul-2006 19:38:56 (freenet.node.Main, main, NORMAL): Created new NGRT
24-Jul-2006 19:38:56 (freenet.node.Main, main, NORMAL): Loaded stats
24-Jul-2006 19:38:56 (freenet.node.Main, main, NORMAL): loading temp
bucket factory
24-Jul-2006 19:38:56 (freenet.node.Main, main, NORMAL): loaded temp
bucket factory
24-Jul-2006 19:38:56 (freenet.node.Main, main, NORMAL): Loaded bucket
factory
24-Jul-2006 19:38:56 (freenet.node.Main, main, NORMAL): not seeding
routing table
24-Jul-2006 19:39:00 (freenet.node.Main, main, NORMAL): starting node
24-Jul-2006 19:39:02 (freenet.node.Main, main, NORMAL): loading service:
mainport
24-Jul-2006 19:39:03 (freenet.node.Main, main, NORMAL): loading service:
distribution
24-Jul-2006 19:39:03
(freenet.interfaces.servlet.SingleHttpServletContainer, main, NORMAL):
Loading the single servlet distribution.params.servlet
24-Jul-2006 19:39:04 (freenet.node.Node, main, NORMAL): Starting ticker..
24-Jul-2006 19:39:04 (freenet.node.Node, main, NORMAL): Starting
interfaces..
24-Jul-2006 19:39:04 (freenet.node.http.BookmarkManagerServlet, main,
NORMAL): Bookmarks updated on request
24-Jul-2006 19:39:05 (freenet.node.Node, main, NORMAL): starting
ListenSelector..
24-Jul-2006 19:54:06 (freenet.node.states.announcing.Announcing,
YThread-17, NORMAL): Found 0 announcement targets for this node.
24-Jul-2006 20:09:06 (freenet.node.states.announcing.Announcing,
YThread-13, NORMAL): Found 0 announcement targets for this node.