Re: [freenet-support] unable to get Freenet going on OS X 10.2.8

[Ben Dougall]

Maybe it's a firewall/NAT issue?

I actually have no idea if I'm behind a firewall/NAT or not I'm afraid.  
I'm connected to the net via a home broadband connection which goes  
into an ADSL ethernet modem, to an Airport (wireless) base station, to  
my laptop. Some people have told me your base station is not a  
firewall and others have told me your base station acts as a  
firewall. That's why I have no idea if I'm behind a firewall or not.  
In the Sharing system preferences panel I have the firewall (which is a  
software one on my machine I think) turned off, and there are no  
firewall settings turned on or off on the base station that I'm aware  
of.

So whether the base station is causing me to not be able to connect to  
http://127.0.0.1:/wizard/ I'm not sure. Freenet's help docs are not  
helping. Assuming the base station is acting as a firewall/NAT, here  
http://freenetproject.org/faq.html#firewall it says:

 How do I get freenet working with a Firewall/NAT?
...
 Configure your NAT or firewall to forward connections to the   
 node.listenPort number (You can find it in a file called freenet.ini  
 in the freenet folder), to the same port on your computer (you will  
 probably need to know your computer's  internal IP address which will  
 often begin with 192.168.x.x). Remember that freenet 0.7 uses UDP.

There is no such information in the freenet.ini file from what I can  
tell. This is what that file looks like:

node.updater.enabled=true
[EMAIL PROTECTED]:/// 
Applications/Freenet/plugins/Librarian.jar;[EMAIL PROTECTED]:/// 
Applications/Freenet/plugins/UPnP.jar;[EMAIL PROTECTED]:/// 
Applications/Freenet/plugins/ 
JSTUN.jar;[EMAIL PROTECTED]:///Applications/ 
Freenet/plugins/MDNSDiscovery.jar;
fproxy.enabled=true
fproxy.port=
fcp.enabled=true
fcp.port=9481
console.enabled=true
console.port=2323
fproxy.enabled=true
fproxy.port=
fcp.enabled=true
fcp.port=9481
console.enabled=true
console.port=2323


Any help / suggestions as to why it's not possible for me to access  
http://127.0.0.1:/wizard/ would be much appreciated.

Ben.

___
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:[EMAIL PROTECTED]

[freenet-support] unable to get Freenet going on OS X 10.2.8

[Ben Dougall]

Hi,

I am unable to get Freenet 0.7 going at all in Mac OS X 10.2.8, Java 
1.4.1.

I've tried a number of ways. The most recent way is the "Install 
Freenet 0.7 using JavaWebStart." option under Mac OSX on this page 
.

It went through the installation process and I think installed OK.

At a couple of points it attempted to load the welcome.html file in a 
browser (I think). Here's what's in the Freenet folder (some of which 
are folders, contents of not shown):

bin
freenet-ext.jar
freenet-ext.jar.sha1
freenet-stable-latest.jar
freenet-stable-latest.jar.sha1
freenet.ini
freenet.jar
frost
frost.zip
frost.zip.sha1
jSite
lib
LICENSE.Freenet
LICENSE.Mantissa
logs
plugins
README
run.sh
Thaw
Uninstaller
update.sh
update.sh.sha1
welcome.html
wrapper.conf
wrapper.log


Opening the welcome.html file in Firefox 2 I'm told the first thing to 
do is go to http://127.0.0.1:/wizard/

Attempting to access that address (and a number of others that I've 
tried, localhost: instead of that IP number, 10.0.1.2:, and the 
address that going to a "what is my ip address" page gives with : 
on the end) fails.

Any ideas what might make Freenet work ?

Thanks, Ben.

[freenet-support] unable to get Freenet going on OS X 10.2.8

[Ben Dougall]

On Monday, June 4, 2007, at 08:22  pm, Ben Dougall wrote:

> At a couple of points it attempted to load the welcome.html file in a
> browser (I think).

I say "I think" there because it used something I haven't come across 
before: some Java browser thing, then in BBEdit (a text editor). It 
just failed to open it up in an actual web browser because I have .html 
files associated with BBEdit -- I think that's what happened there -- 
so is a non issue.

[freenet-support] unable to get Freenet going on OS X 10.2.8

[Ben Dougall]

Maybe it's a firewall/NAT issue?

I actually have no idea if I'm behind a firewall/NAT or not I'm afraid.  
I'm connected to the net via a home broadband connection which goes  
into an ADSL ethernet modem, to an Airport (wireless) base station, to  
my laptop. Some people have told me "your base station is not a  
firewall" and others have told me "your base station acts as a  
firewall". That's why I have no idea if I'm behind a firewall or not.  
In the Sharing system preferences panel I have the firewall (which is a  
software one on my machine I think) turned off, and there are no  
firewall settings turned on or off on the base station that I'm aware  
of.

So whether the base station is causing me to not be able to connect to  
http://127.0.0.1:/wizard/ I'm not sure. Freenet's help docs are not  
helping. Assuming the base station is acting as a firewall/NAT, here  
 it says:

> How do I get freenet working with a Firewall/NAT?
...
> Configure your NAT or firewall to forward connections to the   
> node.listenPort number (You can find it in a file called freenet.ini  
> in the freenet folder), to the same port on your computer (you will  
> probably need to know your computer's  internal IP address which will  
> often begin with 192.168.x.x). Remember that freenet 0.7 uses UDP.

There is no such information in the freenet.ini file from what I can  
tell. This is what that file looks like:

node.updater.enabled=true
pluginmanager.loadplugin=plugins.Librarian.Librarian at file:/// 
Applications/Freenet/plugins/Librarian.jar;plugins.UPnP.UPnP at file:/// 
Applications/Freenet/plugins/UPnP.jar;plugins.JSTUN.JSTUN at file:/// 
Applications/Freenet/plugins/ 
JSTUN.jar;plugins.MDNSDiscovery.MDNSDiscovery at file:///Applications/ 
Freenet/plugins/MDNSDiscovery.jar;
fproxy.enabled=true
fproxy.port=
fcp.enabled=true
fcp.port=9481
console.enabled=true
console.port=2323
fproxy.enabled=true
fproxy.port=
fcp.enabled=true
fcp.port=9481
console.enabled=true
console.port=2323


Any help / suggestions as to why it's not possible for me to access  
http://127.0.0.1:/wizard/ would be much appreciated.

Ben.

[freenet-support] unable to get Freenet going on OS X 10.2.8

[Ben Dougall]

How come the welcome.html file tells me to open 
http://127.0.0.1:/wizard/ when there is not a single file on my 
machine called wizard or that has the word wizard in it? Should there 
be?

How come the welcome.html says:

> Freenet 0.7 Installation Successful!
>
> Next, configure your node and connect your node to the network.
> The next step is to access the First time wizard.  ...

and doesn't say anything about making sure Freenet is started up and 
how to go about starting it up? Should Freenet be started up before you 
attempt going to http://127.0.0.1:/wizard/ ? Once installed, does 
that automatically start up Freenet? Does Freenet stay started up or 
does it shut down after a while? Does it shut down and need starting up 
again after you restart you machine?

[freenet-support] unable to get Freenet going on OS X 10.2.8

[Ben Dougall]

> Should Freenet be started up before you
> attempt going to http://127.0.0.1:/wizard/ ?

In the Terminal (command line):

1/tmp>cd /Applications/Freenet
2/Applications/Freenet>./run.sh start
Starting Freenet 0.7...
3/Applications/Freenet>

Is that a successful Freenet startup? Is that the way to do it -- using 
the command line? Still, following the instructions in the welcome.html 
file to go to http://127.0.0.1:/wizard/ results in "Firefox can't 
establish a connection to the server at 127.0.0.1:."

Maybe "freenet.jar" (which is an alias file in the Freenet folder) does 
it? Double clicking on that result in a window:

Jar Launcher

The jar file "freenet-stable-lates.jar" couldn't be launched. Check the 
Consode for possible error messages. Does that mean the Console app? If 
so the Console says:

Exception in thread "main" java.lang.NoClassDefFoundError: 
com/sleepycat/je/DatabaseException
2007-06-04 21:33:18.884 Jar Launcher[769] CFLog (20): Jar Launcher:  
The jar file "freenet-stable-latest.jar" couldn't be launched. Check 
the Console for possible error messages

Hmm, that's good, we're in the Console looking at the "console.log" 
file. How can I check the Console any further?

[freenet-support] unable to get Freenet going on OS X 10.2.8

[Ben Dougall]

This is the contents of the "freenet-latest.log" file in the logs 
folder in the Freenet folder (I have no idea what's going on):

Jun 04, 2007 20:16:41:525 (freenet.node.NodeStarter, 
WrapperListener_start_runner, NORMAL): freenet.jar built with 
freenet-ext.jar Build #13 r12938
Jun 04, 2007 20:16:42:619 (freenet.node.Node, 
WrapperListener_start_runner, NORMAL): Initializing Node using Freenet 
Build #1036 r13439 and freenet-ext Build #13 r12938 with "Apple 
Computer, Inc." JVM version 1.4.1_01-24 running on ppc Mac OS X 10.2.8
Jun 04, 2007 20:16:43:644 (java.lang.String, 
WrapperListener_start_runner, NORMAL): The translation for 
IPDetectorPluginManager.noConnectivityTitle hasn't been found! please 
tell the maintainer.
Jun 04, 2007 20:16:43:646 (java.lang.String, 
WrapperListener_start_runner, NORMAL): The translation for 
IPDetectorPluginManager.noConnectivity hasn't been found! please tell 
the maintainer.
Jun 04, 2007 20:16:43:647 (java.lang.String, 
WrapperListener_start_runner, NORMAL): The translation for 
IPDetectorPluginManager.symmetricTitle hasn't been found! please tell 
the maintainer.
Jun 04, 2007 20:16:43:648 (java.lang.String, 
WrapperListener_start_runner, NORMAL): The translation for 
IPDetectorPluginManager.symmetric hasn't been found! please tell the 
maintainer.
Jun 04, 2007 20:16:43:649 (java.lang.String, 
WrapperListener_start_runner, NORMAL): The translation for 
IPDetectorPluginManager.portRestrictedTitle hasn't been found! please 
tell the maintainer.
Jun 04, 2007 20:16:43:650 (java.lang.String, 
WrapperListener_start_runner, NORMAL): The translation for 
IPDetectorPluginManager.portRestricted hasn't been found! please tell 
the maintainer.
Jun 04, 2007 20:16:43:651 (java.lang.String, 
WrapperListener_start_runner, NORMAL): The translation for 
IPDetectorPluginManager.restrictedTitle hasn't been found! please tell 
the maintainer.
Jun 04, 2007 20:16:43:662 (java.lang.String, 
WrapperListener_start_runner, NORMAL): The translation for 
IPDetectorPluginManager.restricted hasn't been found! please tell the 
maintainer.
Jun 04, 2007 20:16:43:684 (java.lang.String, 
WrapperListener_start_runner, NORMAL): The translation for 
IPDetectorPluginManager.fullConeTitle hasn't been found! please tell 
the maintainer.
Jun 04, 2007 20:16:43:685 (java.lang.String, 
WrapperListener_start_runner, NORMAL): The translation for 
IPDetectorPluginManager.fullCone hasn't been found! please tell the 
maintainer.
Jun 04, 2007 20:16:43:716 (java.lang.String, 
WrapperListener_start_runner, NORMAL): The translation for 
IPDetectorPluginManager.directTitle hasn't been found! please tell the 
maintainer.
Jun 04, 2007 20:16:43:717 (java.lang.String, 
WrapperListener_start_runner, NORMAL): The translation for 
IPDetectorPluginManager.direct hasn't been found! please tell the 
maintainer.
Jun 04, 2007 20:16:43:971 (freenet.node.Node, 
WrapperListener_start_runner, NORMAL): FNP port created on 0.0.0.0:31766
Jun 04, 2007 20:16:43:977 (freenet.node.Node, 
WrapperListener_start_runner, NORMAL): Creating node...
Jun 04, 2007 20:16:44:124 (freenet.node.Node, 
WrapperListener_start_runner, NORMAL): Testnet mode DISABLED. You may 
have some level of anonymity. :)
Note that this version of Freenet is still a very early alpha, and may 
well have numerous bugs and design flaws.
In particular: YOU ARE WIDE OPEN TO YOUR IMMEDIATE DARKNET PEERS! They 
can eavesdrop on your requests with relatively little difficulty at 
present (correlation attacks etc).
Jun 04, 2007 20:16:44:158 (freenet.node.Node, 
WrapperListener_start_runner, NORMAL): Creating new node file from 
scratch
Jun 04, 2007 20:16:46:069 (freenet.node.Node, 
WrapperListener_start_runner, ERROR): Check your JVM settings 
especially the JCE!java.security.NoSuchAlgorithmException: SHA-256 
MessageDigest not available

[freenet-support] unable to get Freenet going on OS X 10.2.8

[Matthew Toseland]

Check your browser proxy settings. You want to set no proxy for 127.0.0.1.

BTW your airport is almost certainly a NAT, but that shouldn't prevent you 
from accessing your node's local interface.

On Monday 04 June 2007 22:21, Ben Dougall wrote:
> This is the contents of the "freenet-latest.log" file in the logs
> folder in the Freenet folder (I have no idea what's going on):
>
> Jun 04, 2007 20:16:41:525 (freenet.node.NodeStarter,
> WrapperListener_start_runner, NORMAL): freenet.jar built with
> freenet-ext.jar Build #13 r12938
> Jun 04, 2007 20:16:42:619 (freenet.node.Node,
> WrapperListener_start_runner, NORMAL): Initializing Node using Freenet
> Build #1036 r13439 and freenet-ext Build #13 r12938 with "Apple
> Computer, Inc." JVM version 1.4.1_01-24 running on ppc Mac OS X 10.2.8
> Jun 04, 2007 20:16:43:644 (java.lang.String,
> WrapperListener_start_runner, NORMAL): The translation for
> IPDetectorPluginManager.noConnectivityTitle hasn't been found! please
> tell the maintainer.
> Jun 04, 2007 20:16:43:646 (java.lang.String,
> WrapperListener_start_runner, NORMAL): The translation for
> IPDetectorPluginManager.noConnectivity hasn't been found! please tell
> the maintainer.
> Jun 04, 2007 20:16:43:647 (java.lang.String,
> WrapperListener_start_runner, NORMAL): The translation for
> IPDetectorPluginManager.symmetricTitle hasn't been found! please tell
> the maintainer.
> Jun 04, 2007 20:16:43:648 (java.lang.String,
> WrapperListener_start_runner, NORMAL): The translation for
> IPDetectorPluginManager.symmetric hasn't been found! please tell the
> maintainer.
> Jun 04, 2007 20:16:43:649 (java.lang.String,
> WrapperListener_start_runner, NORMAL): The translation for
> IPDetectorPluginManager.portRestrictedTitle hasn't been found! please
> tell the maintainer.
> Jun 04, 2007 20:16:43:650 (java.lang.String,
> WrapperListener_start_runner, NORMAL): The translation for
> IPDetectorPluginManager.portRestricted hasn't been found! please tell
> the maintainer.
> Jun 04, 2007 20:16:43:651 (java.lang.String,
> WrapperListener_start_runner, NORMAL): The translation for
> IPDetectorPluginManager.restrictedTitle hasn't been found! please tell
> the maintainer.
> Jun 04, 2007 20:16:43:662 (java.lang.String,
> WrapperListener_start_runner, NORMAL): The translation for
> IPDetectorPluginManager.restricted hasn't been found! please tell the
> maintainer.
> Jun 04, 2007 20:16:43:684 (java.lang.String,
> WrapperListener_start_runner, NORMAL): The translation for
> IPDetectorPluginManager.fullConeTitle hasn't been found! please tell
> the maintainer.
> Jun 04, 2007 20:16:43:685 (java.lang.String,
> WrapperListener_start_runner, NORMAL): The translation for
> IPDetectorPluginManager.fullCone hasn't been found! please tell the
> maintainer.
> Jun 04, 2007 20:16:43:716 (java.lang.String,
> WrapperListener_start_runner, NORMAL): The translation for
> IPDetectorPluginManager.directTitle hasn't been found! please tell the
> maintainer.
> Jun 04, 2007 20:16:43:717 (java.lang.String,
> WrapperListener_start_runner, NORMAL): The translation for
> IPDetectorPluginManager.direct hasn't been found! please tell the
> maintainer.
> Jun 04, 2007 20:16:43:971 (freenet.node.Node,
> WrapperListener_start_runner, NORMAL): FNP port created on 0.0.0.0:31766
> Jun 04, 2007 20:16:43:977 (freenet.node.Node,
> WrapperListener_start_runner, NORMAL): Creating node...
> Jun 04, 2007 20:16:44:124 (freenet.node.Node,
> WrapperListener_start_runner, NORMAL): Testnet mode DISABLED. You may
> have some level of anonymity. :)
> Note that this version of Freenet is still a very early alpha, and may
> well have numerous bugs and design flaws.
> In particular: YOU ARE WIDE OPEN TO YOUR IMMEDIATE DARKNET PEERS! They
> can eavesdrop on your requests with relatively little difficulty at
> present (correlation attacks etc).
> Jun 04, 2007 20:16:44:158 (freenet.node.Node,
> WrapperListener_start_runner, NORMAL): Creating new node file from
> scratch
> Jun 04, 2007 20:16:46:069 (freenet.node.Node,
> WrapperListener_start_runner, ERROR): Check your JVM settings
> especially the JCE!java.security.NoSuchAlgorithmException: SHA-256
> MessageDigest not available
>
> ___
> 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
-- next part --
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
URL: 
<https://emu.freenetproject.org/pipermail/support/attachments/20070604/4d239042/attachment.pgp>

[freenet-support] unable to get Freenet going on OS X 10.2.8

[Ben Dougall]

Thanks very much for the reply.

On Monday, June 4, 2007, at 10:28  pm, Matthew Toseland wrote:

> Check your browser proxy settings. You want to set no proxy for 
> 127.0.0.1.

I can't see any proxy setting in either Firefox nor Safari's 
preferences. I've certainly never turned any on before. There is a 
Proxy settings tab in the Network panel in the System preferences, but 
no setting are on here apart from one box is checked: "Use Passive FTP 
Mode (PASV)" which I guess is nothing to do with this.

> BTW your airport is almost certainly a NAT, but that shouldn't prevent 
> you
> from accessing your node's local interface.

I think it does allow NAT but NAT is not turned on.

[freenet-support] unable to get Freenet going on OS X 10.2.8

[Matthew Toseland]

Under connection settings?

On Monday 04 June 2007 22:44, Ben Dougall wrote:
> Thanks very much for the reply.
>
> On Monday, June 4, 2007, at 10:28  pm, Matthew Toseland wrote:
> > Check your browser proxy settings. You want to set no proxy for
> > 127.0.0.1.
>
> I can't see any proxy setting in either Firefox nor Safari's
> preferences. I've certainly never turned any on before. There is a
> Proxy settings tab in the Network panel in the System preferences, but
> no setting are on here apart from one box is checked: "Use Passive FTP
> Mode (PASV)" which I guess is nothing to do with this.
>
> > BTW your airport is almost certainly a NAT, but that shouldn't prevent
> > you
> > from accessing your node's local interface.
>
> I think it does allow NAT but NAT is not turned on.
>
> ___
> 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
-- next part --
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
URL: 
<https://emu.freenetproject.org/pipermail/support/attachments/20070604/681d9bc8/attachment.pgp>

[freenet-support] unable to get Freenet going on OS X 10.2.8

[Ben Dougall]

On Monday, June 4, 2007, at 10:44  pm, Ben Dougall wrote:

> Thanks very much for the reply.
>
> On Monday, June 4, 2007, at 10:28  pm, Matthew Toseland wrote:
>
>> Check your browser proxy settings. You want to set no proxy for
>> 127.0.0.1.
>
> I can't see any proxy setting in either Firefox nor Safari's
> preferences. I've certainly never turned any on before. There is a
> Proxy settings tab in the Network panel in the System preferences, but
> no setting are on

I found a Proxy button in Safari's preferences, which when clicked 
opens the above mentioned Proxy settings in the System Prefs (which has 
nothing set), so having something set for 127.0.0.1 is definitely not 
the problem.

[freenet-support] unable to get Freenet going on OS X 10.2.8

[Ben Dougall]

> I found a Proxy button in Safari's preferences, which when clicked 
> opens the above mentioned Proxy settings in the System Prefs (which 
> has nothing set), so having something set for 127.0.0.1 is definitely 
> not the problem.

And I've just found the Firefox one: it's set to "Direct Connection to 
the Internet"

[freenet-support] unable to access http://127.0.0.1:8888/ as instructed in welcome page (OS X 10.2.8)

[Ben Dougall]

Hello,

I can't get Freenet working on OS X 10.2.8.

I've installed Freenet (0.7) which appears to have gone successfully: 
in Applications there's a folder called Freenet with a number of files 
inside, including welcome.html which says I've successfully installed 
it. The next instruction is to access http://127.0.0.1:/  -- this I 
can't do. In both Safari and Firefox. I've tried a number of different 
things but that page can't be accessed at all.

Any ideas why it's not possible for me to follow the configure 
instructions on the welcome page?

Thanks.