Re: [freenet-support] windows 0.5.0.4 monolithic installer updated
Go to http://127.0.0.1:/servlet/nodestatus/nodestatus.html and click the Download References button. Rename the resulting file from noderefs.txt to seednodes.ref. try setting Minimum successful connections to 0 before clicking on the download button, so you get all yet unconnected nodes, too I'm not sure you'd want to export node references to nodes that you can't actually reach. A lot of bogus node references get sent out in announcements, and are eventually dropped from the routing table because they don't work. depends. * the routing tale is cleared out somewhat over time (i loose noderefs, so there must be a way to find those evil entries), so a nonfunct noderef does not hurt much * some nodes may have not been contacted, but would work if thes are tried, so why drop these? ergo: gather as much noderefs as possible (i make snapshots once at a time and merge the noderef files together (and let fred find the double entries), but i have a lot of noderefs!) The information transmitted is intended only for the person or entity to which it is addressed and may contain confidential and/or privileged material. Any review, retransmission, dissemination or other use of, or taking of any action in reliance upon, this information by persons or entities other than the intended recipient is prohibited. If you received this in error, please contact the sender and delete the material from any computer. ___ support mailing list [EMAIL PROTECTED] http://hawk.freenetproject.org/cgi-bin/mailman/listinfo/support
Re: [freenet-support] windows 0.5.0.4 monolithic installer updated
Secret options are bad :) I still seem to have an un-needed 'temporary directory' setting - which it warns me about on every startup. Can you expound on this one? 28-Oct-02 17:26:01 (freenet.node.Main, main): WORKAROUND: Ignoring obsolete fproxy.* lines in freenet.conf/ini. You can remove them. Possibly unrelated, but what is the option to allow arbitary clients to connect on the client port or the web port - or is this incredibly unsafe? In the windows client, the option is on the advanced page in the FCP access box. For mainport, there is no option in the config program yet. Not sure I understood that. All I see is a line where you can give a list of addresses which can connect. 'must include localhost' it says. No (obvious) way to set up 'allow any' Hmm. If we have dyndns would this make routing via dynamic IP a more sensible thing? In which case, might renaming transient mode to 'client only' or something similar help? Was wondering whether, if nodes have a dynamic DNS, it might become easier to contact them - less chance of sending requests to IP addresses which are no longer populated. Fproxy will tell you when higher build numbers are available. So it does. Can I ask where I find a changelog? I don't need or want to stay on the cutting edge, not after what 529 did to me. The problem with that is that sane settings vary widely. For example, at home I can upload at about 3 times what is safe for me to upload here, due to additional congestion, but I can download about twice as fast here as at home. Sure, but if you ask 'cable or 56k modem?' and then set 128kbit or 32kbit respectively, you'd get a lot more sensible settings straight away and let the power users reconfigure it to cope with their own environments. Also, on windows, offerring an option to set the registry keys that frost advises (that set your socket limits up for server working) might be a good idea. what? I'll try and find the freesite again (one problem with freenet, URIs are hardly memorable) There is a problem when you try to run frost on windows 9x - and in general a problem with the default socket settings in freenet on win9x. The symptom is winsock errors (or in frost: java.socket exception: out of buffer space) and it pretty much kills your network connection. There are a couple of registry settings: One to set your MTU and one to set the max number of sockets. Autoconfiguring these may help. (Though give a warning, since gamers especially tend to change those things) ___ support mailing list [EMAIL PROTECTED] http://hawk.freenetproject.org/cgi-bin/mailman/listinfo/support
Re: [freenet-support] windows 0.5.0.4 monolithic installer updated
Dammit. System crashed, and the databugs ate my routing table again. A thousand thousand blessings upon the person who explained how to export my routes :) Upgraded to 531 (since I crashed, I might as well) ___ support mailing list [EMAIL PROTECTED] http://hawk.freenetproject.org/cgi-bin/mailman/listinfo/support
Re: [freenet-support] windows 0.5.0.4 monolithic installer updated
- Original Message -
From: Vitenka - Zen [EMAIL PROTECTED]
Nodeconfig refuses point blank to run on my machine as of main build 529.
* make it so that nodeconf can change every option
Secret options are bad :) I still seem to have an un-needed 'temporary
directory' setting - which it warns me about on every
startup.
Can you expound on this one?
* have nodeconf just edit the config in place (effectively, have it treat
%'s and not have to be manually rewritten)
It isn't doing this already?
Nope. The lifecycle of the options is as follows: defaults set in program;
options in config file read overwriting defaults; changes made; new file
written in big slew of printfs.
* fix import/export ref on bunny
Can we have an export all known references option? At least until the
routing table stops getting eaten by the datastore
bugs :)
* popup window when # of threads is changed to equal 0
Is that a bad option to set then?
Telling fred it can spawn as many threads as it wants? Yes.
* make windows installer using windows installer.
Strongly disagree - the nullsoft installer is a fine and accepted piece of
work, whereas the default windows installer is a
horrible piece of junk. Unless you are having some major problems with
the nullsoft explorer, what is the incentive to
change? If you are worried about transparence then most people would
probably be happy with a zip file and a 'run this
first' file.
Zip files don't work. Too many users can't figure out how they work (yes,
we've had complaints on that before). This is just a longterm goal. Not
having to have an adhoc collection o things that can go wrong would be nice.
* allow selection of java's if don't want first one found out of the
registry
Please, yes please. Give us a list of all of them and let us choose.
Would it be possible to list what version each java
is, since it's not always obvious from the directory.
* have nodeconfig popup a window when using an invalid ip address
(192.168.*.*, 10.*.*.*, phlemball.aol)
Possibly unrelated, but what is the option to allow arbitary lients to
connect on the client port or the web port - or is
this incredibly unsafe?
In the windows client, the option is on the advanced page in the FCP access
box. For mainport, there is no option in the config program yet.
* rewrite in c++ so I don't have to deal with java sh*t.
* automatically register dyndns if they don't have it already (until
arks)
(freenetnode.com would probably be setup fairly easily)
A dyndns for frenetnode.com would be kinda nice to have built in. Make
sure the explanation of what this is, is
comprehensible to the average user :)
Hmm. If we have dyndns would this make routing via dynamic IP a more
sensible thing? In which case, might renaming
transient mode to 'client only' or something similar help?
?
* add messagebox before stopping the node when updating snapshot
* add update option on systray app
How often are updates checked for? And is it done just by getting a
freenet message or do we poll or is it via some out of
band method?
Fproxy will tell you when higher build numbers are available.
* allow for negative # of threads (add checkbox. Give big warning when
set
since FastThreadFactory = evil)
Uh - negative threads? What would that be?
If the value of maxThreads is negative, a different thread factory is used
which doesn't remove threads ever, which may potentially speed things up but
other than that is similar to maxThreads = 0
* fix the file naming of freenet-webinstall.exe to
freenet-webinstall-{$VER}.exe
Uh - surely the webinstaller installs whatever the latest version of
freenet there is?
Yes. The problem is that files in the webinstaller change. There needs to be
atleast some versioning of that, otherwise people are blindly downloading
As to using the monolithic installer: A couple of times downloading via
the normal update or web update I got an out of date
version of the software - so I dropped back to the monolithic one, which
worked once I altered the version number in the
url...
Is there transparent http caching by your ISP, becuase I download the new
jars VIA the update mechanism here myself.
Right, what else would I request? Some more sensible defaults would be
good - perhaps default choke of bandwidth to the
kinds of levels that make sense on a cable / DSL connection.
The problem with that is that sane settings vary widely. For example, at
home I can upload at about 3 times what is safe for me to upload here, due
to additional congestion, but I can download about twice as fast here as at
home.
Also, on windows, offerring an option to set the registry keys that frost
advises (that set your socket limits up for server
working) might be a good idea.
what?
-Mathew
___
support mailing list
[EMAIL PROTECTED]
http://hawk.freenetproject.org/cgi-bin/mailman/listinfo/support
Re: [freenet-support] windows 0.5.0.4 monolithic installer updated
* fix import/export ref on bunny Can we have an export all known references option? At least until the routing table stops getting eaten by the datastore bugs :) Go to http://127.0.0.1:/servlet/nodestatus/nodestatus.html and click the Download References button. Rename the resulting file from noderefs.txt to seednodes.ref. try setting Minimum successful connections to 0 before clicking on the download button, so you get all yet unconnected nodes, too The information transmitted is intended only for the person or entity to which it is addressed and may contain confidential and/or privileged material. Any review, retransmission, dissemination or other use of, or taking of any action in reliance upon, this information by persons or entities other than the intended recipient is prohibited. If you received this in error, please contact the sender and delete the material from any computer. ___ support mailing list [EMAIL PROTECTED] http://hawk.freenetproject.org/cgi-bin/mailman/listinfo/support
Re: [freenet-support] windows 0.5.0.4 monolithic installer updated
[EMAIL PROTECTED] ([EMAIL PROTECTED]) wrote: Go to http://127.0.0.1:/servlet/nodestatus/nodestatus.html and click the Download References button. Rename the resulting file from noderefs.txt to seednodes.ref. try setting Minimum successful connections to 0 before clicking on the download button, so you get all yet unconnected nodes, too I'm not sure you'd want to export node references to nodes that you can't actually reach. A lot of bogus node references get sent out in announcements, and are eventually dropped from the routing table because they don't work. -- Greg Wooledge | Truth belongs to everybody. [EMAIL PROTECTED] |- The Red Hot Chili Peppers http://wooledge.org/~greg/ | msg01969/pgp0.pgp Description: PGP signature
Re: [freenet-support] windows 0.5.0.4 monolithic installer updated
Excellent! Build 530 CPU usage is WAY down! Great job! Just curious what changed to improve performance? ___ support mailing list [EMAIL PROTECTED] http://hawk.freenetproject.org/cgi-bin/mailman/listinfo/support
Re: [freenet-support] windows 0.5.0.4 monolithic installer updated
Ahhh ... oops! Couple hourse later, freenet is back up to 100% CPU. My excitement was premature :( - Original Message - From: Robert Carroll [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Monday, November 04, 2002 6:54 PM Subject: Re: [freenet-support] windows 0.5.0.4 monolithic installer updated Excellent! Build 530 CPU usage is WAY down! Great job! Just curious what changed to improve performance? ___ support mailing list [EMAIL PROTECTED] http://hawk.freenetproject.org/cgi-bin/mailman/listinfo/support ___ support mailing list [EMAIL PROTECTED] http://hawk.freenetproject.org/cgi-bin/mailman/listinfo/support
Re: [freenet-support] windows 0.5.0.4 monolithic installer updated
Nodeconfig refuses point blank to run on my machine as of main build 529.
* make it so that nodeconf can change every option
Secret options are bad :) I still seem to have an un-needed 'temporary directory'
setting - which it warns me about on every
startup.
* have nodeconf just edit the config in place (effectively, have it treat
%'s and not have to be manually rewritten)
It isn't doing this already?
* fix import/export ref on bunny
Can we have an export all known references option? At least until the routing table
stops getting eaten by the datastore
bugs :)
* popup window when # of threads is changed to equal 0
Is that a bad option to set then?
* make windows installer using windows installer.
Strongly disagree - the nullsoft installer is a fine and accepted piece of work,
whereas the default windows installer is a
horrible piece of junk. Unless you are having some major problems with the nullsoft
explorer, what is the incentive to
change? If you are worried about transparence then most people would probably be
happy with a zip file and a 'run this
first' file.
* allow selection of java's if don't want first one found out of the
registry
Please, yes please. Give us a list of all of them and let us choose. Would it be
possible to list what version each java
is, since it's not always obvious from the directory.
* have nodeconfig popup a window when using an invalid ip address
(192.168.*.*, 10.*.*.*, phlemball.aol)
Possibly unrelated, but what is the option to allow arbitary lients to connect on the
client port or the web port - or is
this incredibly unsafe?
* rewrite in c++ so I don't have to deal with java sh*t.
* automatically register dyndns if they don't have it already (until arks)
(freenetnode.com would probably be setup fairly easily)
A dyndns for frenetnode.com would be kinda nice to have built in. Make sure the
explanation of what this is, is
comprehensible to the average user :)
Hmm. If we have dyndns would this make routing via dynamic IP a more sensible thing?
In which case, might renaming
transient mode to 'client only' or something similar help?
* add messagebox before stopping the node when updating snapshot
* add update option on systray app
How often are updates checked for? And is it done just by getting a freenet message
or do we poll or is it via some out of
band method?
* allow for negative # of threads (add checkbox. Give big warning when set
since FastThreadFactory = evil)
Uh - negative threads? What would that be?
* fix the file naming of freenet-webinstall.exe to
freenet-webinstall-{$VER}.exe
Uh - surely the webinstaller installs whatever the latest version of freenet there is?
As to using the monolithic installer: A couple of times downloading via the normal
update or web update I got an out of date
version of the software - so I dropped back to the monolithic one, which worked once I
altered the version number in the
url...
Right, what else would I request? Some more sensible defaults would be good -
perhaps default choke of bandwidth to the
kinds of levels that make sense on a cable / DSL connection.
Also, on windows, offerring an option to set the registry keys that frost advises
(that set your socket limits up for server
working) might be a good idea.
___
support mailing list
[EMAIL PROTECTED]
http://hawk.freenetproject.org/cgi-bin/mailman/listinfo/support
Re: [freenet-support] windows 0.5.0.4 monolithic installer updated
Vitenka - Zen ([EMAIL PROTECTED]) wrote: * fix import/export ref on bunny Can we have an export all known references option? At least until the routing table stops getting eaten by the datastore bugs :) Go to http://127.0.0.1:/servlet/nodestatus/nodestatus.html and click the Download References button. Rename the resulting file from noderefs.txt to seednodes.ref. -- Greg Wooledge | Truth belongs to everybody. [EMAIL PROTECTED] |- The Red Hot Chili Peppers http://wooledge.org/~greg/ | msg01950/pgp0.pgp Description: PGP signature
Re: [freenet-support] windows 0.5.0.4 monolithic installer updated
Am 01.11.2002 04:17:56 schrieb Mathew Ryden [EMAIL PROTECTED]: I've uploaded the monolithic installer incase anyone actually uses that horrific thing (actually, an amazingly large amount of the freenet installs have been the monolithic installer) I've tried to install one (running a small second node ;-)) but freenet doesn't want to. It says : Nov 1, 2002 12:42:46 PM (freenet.node.Main, main): Monolithic datastore no longer supported. Converting to native. You had better ...blabla Nov 1, 2002 12:42:53 PM (freenet.node.Main, main): Unexpected Exception: java.io.IOException java.io.IOException: couldn't create native directory at freenet.fs.dir.NativeFSDirectory.init(NativeFSDirectory.java:383) at freenet.node.Main.main(Main.java:446) I set: # The type of store we have (this text will get clearer soon). storeType=monolithic pity ___ support mailing list [EMAIL PROTECTED] http://hawk.freenetproject.org/cgi-bin/mailman/listinfo/support
Re: [freenet-support] windows 0.5.0.4 monolithic installer updated
GrimHunter ([EMAIL PROTECTED]) wrote: Am 01.11.2002 04:17:56 schrieb Mathew Ryden [EMAIL PROTECTED]: I've uploaded the monolithic installer incase anyone actually uses that horrific thing (actually, an amazingly large amount of the freenet installs have been the monolithic installer) I've tried to install one (running a small second node ;-)) but freenet doesn't want to. It says : Nov 1, 2002 12:42:46 PM (freenet.node.Main, main): Monolithic datastore no longer supported. Converting to native. You had better ...blabla You're confusing the monolithic datastore with the monolithic Windows installer. The monolithic Windows installer has freenet.jar inside it, as opposed to the Windows web-installer which downloads freenet.jar from freenetproject.org at installation time. -- Greg Wooledge | Truth belongs to everybody. [EMAIL PROTECTED] |- The Red Hot Chili Peppers http://wooledge.org/~greg/ | msg01897/pgp0.pgp Description: PGP signature
[freenet-support] windows 0.5.0.4 monolithic installer updated
I've uploaded the monolithic installer incase anyone actually uses that
horrific thing (actually, an amazingly large amount of the freenet installs
have been the monolithic installer)
Anyways, the new installer is up, with no changes over the last monolithic
installer (0.5.0.4-2).
Hmm - I don't think I ever officially said what was changed in 0.5.0.4-2
over 0.5.0.4-1. The config program now has localhost and mp3-delete
protection built in. Both systems should be greatly improved, right now both
protections take effect when the OK button is clicked to write out the
config. Quick and dirty? Yes. Works? Also yes.
I'm looking at my freenet installer todo list and trying to prioritize it to
get something effective done this weekend (actually, probably only 8 hours
on friday). Is there anything on this list people would like to expound on?
Anything you think I need to do ASAP (is now a good time to remind everyone
that the nodeconfig program is just about the first non-console program I've
ever touched? :)
Anyways - My list of things to do (similar to this email, I often don't make
any sense):
* make it so that nodeconf can change every option
* have nodeconf just edit the config in place (effectively, have it treat
%'s and not have to be manually rewritten)
* build in search for fproxy.*, nodeinfo.*, and nodestatus.* so that we can
save those options if any
* fix import/export ref on bunny
* popup window when # of threads is changed to equal 0
* make windows installer using windows installer.
* have pathfind buttons on nodeconfig/normal work
* debug proxies for blocked port 80 on install (it has code to detect them!)
* create directories inside of directories in createthread.c (freenet.exe)
* add 2k/xp directory security preferences on temp directory
* Popup window when nodeconfig is trying to get references
* find out why new installs always use same port (which changes)
* allow selection of java's if don't want first one found out of the
registry
* get rid of having to manually modify 7 different strings to change the
release directories start menu folder
* have nodeconfig popup a window when using an invalid ip address
(192.168.*.*, 10.*.*.*, phlemball.aol)
* rewrite in c++ so I don't have to deal with java sh*t.
* automatically register dyndns if they don't have it already (until arks)
(freenetnode.com would probably be setup fairly easily)
* add messagebox before stopping the node when updating snapshot
* add update option on systray app
* allow for negative # of threads (add checkbox. Give big warning when set
since FastThreadFactory = evil)
* fix the file naming of freenet-webinstall.exe to
freenet-webinstall-{$VER}.exe
* do documentation changes on freenetproject.org faq and readme to make sure
everything makes sense (unlike this todo item)
* Anything else?
-Mathew
___
support mailing list
[EMAIL PROTECTED]
http://hawk.freenetproject.org/cgi-bin/mailman/listinfo/support
