[freenet-support] 15000-level ports
I'm setting up a secondary Freenet node on a very particular network that I don't have control over. Every incoming connection is blocked, save for ones over a handful of ports in the 15000 range. I've tested these ports with TCP services and nmap (scanning TCP and UDP). With things like ssh they work fine, but Freenet cannot connect to Opennet peers at all. I set node.opennet.listenPort and node.listenPort in the freenet.ini file to ports in the 15000 range proven to work, but Freenet still will not connect. Does anyone have experience using Freenet on such high port numbers? ___ 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:support-requ...@freenetproject.org?subject=unsubscribe
Re: [freenet-support] Moving Freenet to another partition
On May 31, 2011, at 6:11 PM, Matthew Toseland wrote: > On Sunday 29 May 2011 00:02:45 Daxter wrote: >> On May 28, 2011, at 8:35 AM, Stephen Mollett wrote: >>> On Friday 27 May 2011 21:40:27 Daxter wrote: >>>> After further testing, I am absolutely sure that something is wrong here. >>>> To make sure that my findings were true, I renamed my original Freenet >>>> folder in /Applications/ to Freenet22, and then attempted run.sh from the >>>> new location. Every time it recreated a folder... >>> >>> Have a look in your freenet.ini file and see if it references the original >>> location at all. If so, try changing the references to point to the new >>> folder. >>> >>> I'm not a Mac person so I don't know whether there may be other factors >>> (such >>> as the OS somehow "remembering" the original path as the program's working >>> directory or something) but this would seem to be the most likely cause of >>> the >>> behaviour you see. >>> >>> Hope this helps, >>> Stephen >> >> Thanks for the tip. I'll manually modify these and see if my node then works >> properly. >> >> Unless there's some weird security issue requiring absolute path references, >> why aren't we looking for these files in the current directory? > > Check wrapper.conf. > > If it's not that then it might be some mac-specific startup/launch script. Turns out Stephen was right, the issue was the freenet.ini file. The list below holds all of the settings that specify a directory. As you can see, all but ssl.sslKeyStore and node.install.storeDir specify full paths from the root directory. Why is this? From my understanding they all should refer to the local directory (for portability) or there should be a single one that sets the absolute path for all the code to inherit. Why do some refer to the local directory, but most refer to the absolute directory? ssl.sslKeyStore=datastore/certs node.masterKeyFile=/Applications/Freenet/master.keys node.downloadsDir=/Applications/Freenet/downloads node.install.userDir=/Applications/Freenet node.install.tempDir=/Applications/Freenet/temp-43346 node.install.pluginDir=/Applications/Freenet/plugins node.install.persistentTempDir=/Applications/Freenet/persistent-temp-43346 node.install.cfgDir=/Applications/Freenet node.install.runDir=/Applications/Freenet node.install.nodeDir=/Applications/Freenet node.install.storeDir=datastore ___ 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:support-requ...@freenetproject.org?subject=unsubscribe
Re: [freenet-support] Moving Freenet to another partition
On May 28, 2011, at 8:35 AM, Stephen Mollett wrote: > On Friday 27 May 2011 21:40:27 Daxter wrote: >> After further testing, I am absolutely sure that something is wrong here. >> To make sure that my findings were true, I renamed my original Freenet >> folder in /Applications/ to Freenet22, and then attempted run.sh from the >> new location. Every time it recreated a folder... > > Have a look in your freenet.ini file and see if it references the original > location at all. If so, try changing the references to point to the new > folder. > > I'm not a Mac person so I don't know whether there may be other factors (such > as the OS somehow "remembering" the original path as the program's working > directory or something) but this would seem to be the most likely cause of > the > behaviour you see. > > Hope this helps, > Stephen Thanks for the tip. I'll manually modify these and see if my node then works properly. Unless there's some weird security issue requiring absolute path references, why aren't we looking for these files in the current directory? ___ 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:support-requ...@freenetproject.org?subject=unsubscribe
Re: [freenet-support] Moving Freenet to another partition
On May 27, 2011, at 2:46 PM, Dsoslglece wrote: > Le 27/05/11 21:32, Daxter a écrit : >> >> On May 27, 2011, at 2:28 PM, Dsoslglece wrote: >>> Le 27/05/11 20:38, Daxter a écrit : >>>> >>>> Hello all, >>>> >>>> I want to move my Freenet folder to a larger partition in my computer >>>> which is running Mac OSX 10.6. I copied it over and moved the original >>>> folder in /Applications/ to the trash (not yet deleting it), and then >>>> attempted to run it from its new location. While starting up, however, it >>>> warned me that no seednodes.fref file existed and as such it could not >>>> connect to the opennet. A quick glance into /Applications/ and I found >>>> that Freenet had recreated a folder there and was repopulating it with a >>>> number of files, all of which probably were not properly loaded from the >>>> new location. >>>> >>>> I have two theories as to what might be the cause: >>>> 1) After I chose the install directory during the original installation, >>>> the install script changed a preference file telling Freenet to always >>>> look for such files in /Applications/Freenet/ (the original install >>>> location) instead of the current directory. >>>> 2) regardless of where you choose to install Freenet, something has been >>>> hard-coded to look in /Applications/Freenet (for my OS at least). >>>> >>>> Does anybody know why this is happening? I want to devote a larger portion >>>> of my HDD to Freenet, but this issue is preventing me from doing so. >>> Normally, Freenet works anywhere (at least on Mac snow leopard). >>> For instance, I've got it on my hard disk, but localized in a encrypted >>> sparse image bundle. >>> in fact, it is possible to take the whole folder containing it (after it >>> has been shutted), putting it somewhere else, and start it again, and >>> evrerything goes fine again. >>> >>> The only thing then that has to be changed, is the path to it (for the >>> commands), and also not to forget to indicate its new position to >>> LittleSnitch… >> >> You say that, and yet my experience proves otherwise. I originally installed >> it in my Applications folder and then tried relocating it to another >> partition. When starting via run.sh in the new directory, I had the issues >> mentioned in my first email. > Well I can only speak from what I have personnally experienced. But, are you > sure that you had the new path correctly indicated in terminal? > One of the surest method I know for this is to first enter : cd space, and > then, slide the Freenet folder on top of terminal, then enter. > By the way, normally, you don't even need to get the old folder out of reach > in the garbage, you can have few FN Folders, as long as only one is started, > no problem > You could also have put the original folder in the new location and started > it then… > > Maybe you could open both folders side by side and compare the content ans > especially those files mentionned as missing… After further testing, I am absolutely sure that something is wrong here. To make sure that my findings were true, I renamed my original Freenet folder in /Applications/ to Freenet22, and then attempted run.sh from the new location. Every time it recreated a folder with the following files in it. After checking that the folder had been recreated, I stopped Freenet and deleted the folder. I moved my new copy (on the larger partition) to a different directory, and the results were still the same. I even tried renaming the folder and it still happened. bookmarks.dat downloads/ node.db4o.crypt persistent-temp-43346/ bootID extra-peer-data-43346/ opennet-10718 plugins/ client-throttle.dat master.keys openpeers-10718 temp-43346/ completed.list.downloadsnode-43346 openpeers-old-10718 uptime.dat completed.list.uploads node-throttle.dat peers-43346 ___ 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:support-requ...@freenetproject.org?subject=unsubscribe
Re: [freenet-support] Moving Freenet to another partition
On May 27, 2011, at 2:28 PM, Dsoslglece wrote: > Le 27/05/11 20:38, Daxter a écrit : >> >> Hello all, >> >> I want to move my Freenet folder to a larger partition in my computer which >> is running Mac OSX 10.6. I copied it over and moved the original folder in >> /Applications/ to the trash (not yet deleting it), and then attempted to run >> it from its new location. While starting up, however, it warned me that no >> seednodes.fref file existed and as such it could not connect to the opennet. >> A quick glance into /Applications/ and I found that Freenet had recreated a >> folder there and was repopulating it with a number of files, all of which >> probably were not properly loaded from the new location. >> >> I have two theories as to what might be the cause: >> 1) After I chose the install directory during the original installation, the >> install script changed a preference file telling Freenet to always look for >> such files in /Applications/Freenet/ (the original install location) instead >> of the current directory. >> 2) regardless of where you choose to install Freenet, something has been >> hard-coded to look in /Applications/Freenet (for my OS at least). >> >> Does anybody know why this is happening? I want to devote a larger portion >> of my HDD to Freenet, but this issue is preventing me from doing so. > Normally, Freenet works anywhere (at least on Mac snow leopard). > For instance, I've got it on my hard disk, but localized in a encrypted > sparse image bundle. > in fact, it is possible to take the whole folder containing it (after it has > been shutted), putting it somewhere else, and start it again, and evrerything > goes fine again. > > The only thing then that has to be changed, is the path to it (for the > commands), and also not to forget to indicate its new position to > LittleSnitch… You say that, and yet my experience proves otherwise. I originally installed it in my Applications folder and then tried relocating it to another partition. When starting via run.sh in the new directory, I had the issues mentioned in my first email.___ 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:support-requ...@freenetproject.org?subject=unsubscribe
[freenet-support] Moving Freenet to another partition
Hello all, I want to move my Freenet folder to a larger partition in my computer which is running Mac OSX 10.6. I copied it over and moved the original folder in /Applications/ to the trash (not yet deleting it), and then attempted to run it from its new location. While starting up, however, it warned me that no seednodes.fref file existed and as such it could not connect to the opennet. A quick glance into /Applications/ and I found that Freenet had recreated a folder there and was repopulating it with a number of files, all of which probably were not properly loaded from the new location. I have two theories as to what might be the cause: 1) After I chose the install directory during the original installation, the install script changed a preference file telling Freenet to always look for such files in /Applications/Freenet/ (the original install location) instead of the current directory. 2) regardless of where you choose to install Freenet, something has been hard-coded to look in /Applications/Freenet (for my OS at least). Does anybody know why this is happening? I want to devote a larger portion of my HDD to Freenet, but this issue is preventing me from doing so. ___ 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:support-requ...@freenetproject.org?subject=unsubscribe
Re: [freenet-support] Mac OSX 10.5 unable to connect since Freenet build 1372
On May 26, 2011, at 10:10 PM, harry smythe wrote: > Hello, > > Please excuse my very limited technical knowledge. > > I'm running Mac OSX 10.5.8 with 2 GB RAM and Firefox 4.0.1 on a Macbook. My > JavaVM seems to be 12.8 and I can't find a newer one for Mac. Mac OS X 10.5 has Java 1.5 installed by default, which is what Freenet requires. If you want to check for yourself you can type "java -version" into the command line. > Up until Freenet 0.7.5 Build #1372 build01372, Freenet-ext Build #26 r23771, > I had no problems. Normally, I would install the Mac version from the > "downloads" webpage, or use the offline installer for Linux. Either worked > well. IZPack install always took the browser to 127.0.0.1:/wizard. Using > the line command "status", I could see: > "macbook:*** ***$ ./run.sh status > Freenet 0.7 is running (10433)." > >> > With all the updated install programs after build #1372, the installs would > seem to finish, but the browser at 127.0.0.1: wouldn't launch, or if it > did, it would show: > "Unable to connect, Firefox can't establish a connection to the server at > 127.0.0.1:." > Double-checking through Terminal with the line command "status", I could see: > "macbook:*** ***$ ./run.sh status > Freenet 0.7 is running (6006). > macbook:*** ***$ ./run.sh status > Freenet 0.7 is not running." > From "running" to "not running" takes about 8-10 seconds. You really, *really* shouldn't be upgrading Freenet by downloading and re-installing it. Updating should be a painless procedure. Depending on the setting you chose when you first set up your node, it will either auto update or ask you to update when a new version is released. You might not be able to connect to 127.0.0.1: because you had not shut down Freenet properly before you installed the new version directly over the old version. That means that port is still being reserved for the old (now defunct) process. In my experience for that situation, Freenet will simply use the next available port (usually 8889). Why not try connecting through that? > For some weeks, I offline-installed build 1372 for Linux, had no problem with > the browser interface, waited for a few connections (2/40 connections after 2 > hours) and for the "update" button to appear on the 127.0.0.1 webpage. > (Without connections, that update option isn't available.) This was slow but > seemed to work after some time. 2 connections after 2 hours? That can't be right. I've always gotten a minimum of 10 connections after 30 or so minutes of uptime. Admittedly I am not familiar with the Linux installer, but you shouldn't be using it when you're running Mac OS X. > Now, 1372 still installs but can't make any connections at all, in any amount > of time. So I can't use that method any more. The 1376 webpage jnlp installs, > but line command "status" shows that the program stops after some seconds > (resulting in Firefox's "unable to connect" message, I guess), as do all the > Linux offline installers after 1372. That's odd. Have you checked the log files to see what might be causing it to shut down like that? > After a 1372 install, a line command called ",/update.sh start" seems to show > all kinds of downloading and installing of jars and ext-jars, but the updated > program still dies after about 8 seconds. What program are you referring to that dies after 8 seconds? Freenet, or the update.sh script? If you mean running update.sh only lasts 8 seconds, then I would expect that means that it quickly checked and found that everything was updated. > So with a 1372 Linux offline installer, I can install and get a browser > interface because it continues to run but cannot connect to others. With any > of the updated installers, I can install, but get no browser interface, > because the program seems to die too soon, I guess. AFAIK the Linux version might not be able to make any connections because some part of the install is incompatible with Mac OS X. After doing a clean install of the Mac version, try my suggestion above to try connecting to 127.0.0.1:8889 and consecutively higher ports. I would suggest keeping a copy of the log files of any installs you currently have, as they may prove useful. Hope this helps, Daxter___ 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:support-requ...@freenetproject.org?subject=unsubscribe
Re: [freenet-support] Problem with Java
On May 23, 2011, at 9:39 AM, Benjie wrote: > Hello! > > My freenet doesn't work anymore. > I suppose it' because I'm still on Java 1.5, but since I'm on Os 10.4, I > can't upgrade, even with openjdk6. What can I do? What do you mean it doesn't work anymore? Was it working and then it self-updated and stopped working, or did you recently reinstall it and you found that this new install doesn't work? AFAIK Freenet still runs on Java 1.5, though there has been a lot of talk of upgrading to 1.6 it hasn't happened yet. Even if it has been upgraded, previous conversations on this mailing list hinted that you can install Java 1.6 on OS X 10.4. Either way though, I strongly suggest you upgrade your OS to 10.5. By upgrading you have more up-to-date software and less security vulnerabilities, and I know from personal experience that (any computer I've tested) that was capable of running 10.4 is also able to run 10.5. ___ 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:support-requ...@freenetproject.org?subject=unsubscribe
[freenet-support] Japanese-language Identities
Is it possible to create them? I tried, but since then Freenet has bogged down my computer with endless (senseless?) computations. Oddly enough, every part of my node not having to do with WoT still works fine–but if I try to load any WoT-related page my browser just sits there. I searched through the bug tracker but couldn't find anything to do with this issue, which makes me wonder... is it currently possible to create /any/ foreign-language identity? In the event that there isn't a good reason to implement this or there's a very compelling reason NOT to, at the very least we should tell the user this, instead of burning up their computer. ___ 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:support-requ...@freenetproject.org?subject=unsubscribe
Re: [freenet-support] headless install on OpenSolaris
On May 1, 2011, at 11:57 PM, Dennis Nezic wrote: > On Sun, 1 May 2011 23:18:07 -0500, Daxter wrote: >> After running the last command, the text below was printed over the >> period of 10-20 minutes. I'm not sure what's going wrong, >> [...] >> java.io.IOException: No space left on device > > Perhaps you don't have enough space on your freenet device? :p There's a terabyte available in that location--I don't know why it's throwing that error. ___ 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:support-requ...@freenetproject.org?subject=unsubscribe
[freenet-support] headless install on OpenSolaris
Hi all, I'm trying to install Freenet on an OpenSolaris box using these commands: wget http://downloads.freenetproject.org/alpha/installer/freenet07.tar.gz tar xvzf freenet07.tar.gz cd freenet ./run.sh start After running the last command, the text below was printed over the period of 10-20 minutes. I'm not sure what's going wrong, but it appears to be looking for OS-specific binaries that don't exist (among other problems)... I tried configuring the node through ssh & links, but it still fails to connect to opennet peers. Any help would be appreciated. -Daxter Enabling the auto-update feature Detecting tcp-ports availability... Downloading update.sh Downloading wrapper_SunOS.zip Downloading freenet-stable-latest.jar Downloading freenet-ext.jar Downloading the JSTUN plugin Downloading the UPnP plugin Downloading seednodes.fref Installing cron job to start Freenet on reboot... @reboot "/export/home/nom/freenet/run.sh" start 2>&1 >/dev/null #FREENET AUTOSTART - crontab: error on previous line; unexpected character found in line. crontab: errors detected in input, no crontab file generated. Unable to locate any of the following binaries: /export/home/nom/freenet/./bin/wrapper-solaris-i86pc-32 /export/home/nom/freenet/./bin/wrapper Starting Freenet 0.7... Let's start the node without the wrapper, you'll have to daemonize it yourself. WrapperManager: Initializing... WrapperManager: WARNING - The wrapper.native_library system property was not WrapperManager: set. Using the default value, 'wrapper'. WrapperManager: WrapperManager: WARNING - Unable to load the Wrapper's native library because none of the WrapperManager: following files: WrapperManager: libwrapper-solaris-x86-32.so WrapperManager: libwrapper.so WrapperManager: could be located on the following java.library.path: WrapperManager: /usr/jdk/instances/jdk1.6.0/jre/lib/i386/server WrapperManager: /usr/jdk/instances/jdk1.6.0/jre/lib/i386 WrapperManager: /usr/jdk/instances/jdk1.6.0/jre/../lib/i386 WrapperManager: /usr/jdk/packages/lib/i386 WrapperManager: /lib WrapperManager: /usr/lib WrapperManager: Please see the documentation for the wrapper.java.library.path WrapperManager: configuration property. WrapperManager: System signals will not be handled correctly. WrapperManager: freenet.jar built with freenet-ext.jar Build #26 r23771 running with ext build 26 r23771 Using default config filename freenet.ini Creating config from freenet.ini Creating logger... Set interval to 10 and multiplier to 1 Starting executor... Finding old log files. New log file is /export/home/nom/freenet/logs/freenet-1368-2011-05-01-22.log.gz Created log files Initializing Node using Freenet Build #1368 rbuild01368 and freenet-ext Build #26 r23771 with Sun Microsystems Inc. JVM version 1.6.0_18 running on x86 SunOS 5.11 Starting FProxy on 127.0.0.1,0:0:0:0:0:0:0:1: INFO: Native CPUID library jcpuid not loaded, reason: 'Dont know jcpuid library name for os type 'SunOS'' - will not be able to read CPU information using CPUID INFO: Native BigInteger library jbigi not loaded, reason: 'Dont know jbigi library name for os type 'SunOS'' - using pure java Not creating node.db4o for now, waiting for config as to security level... FNP port created on 0.0.0.0:55400 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 PEERS! They can eavesdrop on your requests with relatively little difficulty at present (correlation attacks etc). Trying to read node file backup ... Creating new cryptographic keys... Creating PeerManager Memory is 656 MiB (687865856 bytes) Setting standard 500 thread limit. This should be enough for most nodes but more memory is usually a good thing. Database corrupted (before entering NodeClientCore)! Deleted 0 of 0 temporary files (0 non-temp files in temp directory) in 0s Initializing USK Manager Database corrupted (leaving NodeClientCore)! Initializing Node Updater Max packet size: 1252 Initializing Plugin Manager Node constructor completed Starting DNSRequester Created uptime estimator, time offset is 79352 uptime at startup is 0.00 Starting PacketSender Starting Ticker NOT using wrapper (at least not correctly). Your freenet-ext.jar <http://downloads.freenetproject.org/alpha/freenet-ext.jar> and/or wrapper.conf <https://emu.freenetproject.org/svn/trunk/apps/installer/installclasspath/config/wrapper.conf> need to be updated. Freenet 0.7.5 Build #1368 rbuild01368 FNP port is on 0.0.0.0:55400 Starting FCP server on 127.0.0.1,0:0:0:0:0:0:0:1:9
Re: [freenet-support] Connectiong problem
On Feb 13, 2011, at 12:28 PM, Jep wrote: > Daxter : >> On Jan 1, 2011, at 7:08 AM, >> wrote: >>> Hi, >>> this is how my node is connected to the network, from >>> http://127.0.0.1:/stats/ page: >>> >>> Peer statistics >>> >>> * Connected: 2 >>> * Too old: 1 >>> * Disconnected: 12 >>> * Never connected: 26 >>> * Seed nodes: 4 >>> * Max peers: 40 >>> * Max strangers: 40 >>> >>> Bandwidth >>> >>> * Input Rate: 587 B/s (of 512 KiB/s) >>> * Output Rate: 1.69 KiB/s (of 128 KiB/s) >>> * Session Total Input: 17.1 MiB (1.61 KiB/s average) >>> * Session Total Output: 24.7 MiB (2.33 KiB/s average) >>> * Payload Output: 2.38 MiB (231 B/sec)(9%) >>> * Global Total Input: 35.5 GiB >>> * Global Total Output: 40.8 GiB >>> >>> When i start Freenet, it take maybe one hour to be connected at least 2 >>> nodes, result is very, very slow connection to Freenet. >>> >>> Cann please somebody help? >>> >> It really shouldn't be taking that long. Though, the past couple weeks have >> been pretty bad because of low-level changes to Freenet. What OS are you >> using? how long have you had Freenet installed? How long has it been since >> you've had stable connections? >> So that we have a better idea of your problem, please run through this quick >> checklist: >> 1. update freenet to the most recent version. it can be done by running >> "update.sh" in your Freenet directory. >> 2. ensure that port forwarding is set up correctly (do some googling. if it >> still doesn't make sense, ask) >> 3. If at this point it still isn't working, temporarily turn off your router >> and computer firewall to see if that doesn't fix the issue. >> For the sake of clear results, try to not have tons of extra stuff running >> while doing all this, and be sure to restart when it might help. > >> temporarily turn off your router > > This I don't understand, no router = no network; what to test then? Look at the rest of the phrase: >> temporarily turn off your router and computer firewall In other words: temporarily turn off your router firewall and your computer firewall. > Can confirm a software firewall can be a problem, mine still kept the FN > ports closed no matter I told it otherwise. > There was a link somewhere in the FN help pages pointing to a site that can > test if particular ports are actually opened. Oh yeah, thanks for reminding me. The one I use all the time is [www.canyouseeme.org]. I can't believe I forgot to mention that. > A problem when choosing a firewall app is that many only allow for > applications to connect, not to open ports manually. Back then the wrapper > ran as a windows service and I didn't see possibillities to allow a service > internet access. I'm not too familiar with the specifics of windows networking--could you explain in greater detail? ___ 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:support-requ...@freenetproject.org?subject=unsubscribe
[freenet-support] Weird wording on the download page
At the bottom of http://freenetproject.org/download.html there is a section labeled "Upgrading." The paragraph I'm concerned with is pasted below: "Freenet provides now an update-over-freenet mechanism: It will keep itself up to date automatically from other Freenet nodes, and this will normally work even if it is unable to route to them due to them being too new. This is anonymous and secure, and we recommend people use it. However, if something is severely broken, you can update your node manually from our servers:" Changes that would make it flow better: 1. either "Freenet //now// provides..." or simply "Freenet provides..." I would recommend simply removing "now", as it gives the impression that the project is volatile, untrustworthy, and just plain bad software. While the seasoned user knows not to trust Freenet, it's better to appeal to someone's logic before their read-a-book-by-its-cover instinct makes us lose another potential user/contributor. ___ 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:support-requ...@freenetproject.org?subject=unsubscribe
Re: [freenet-support] Connectiong problem
On Jan 1, 2011, at 7:08 AM, wrote: > > Hi, > this is how my node is connected to the network, from > http://127.0.0.1:/stats/ page: > > Peer statistics > >* Connected: 2 >* Too old: 1 >* Disconnected: 12 >* Never connected: 26 >* Seed nodes: 4 >* Max peers: 40 >* Max strangers: 40 > > Bandwidth > >* Input Rate: 587 B/s (of 512 KiB/s) >* Output Rate: 1.69 KiB/s (of 128 KiB/s) >* Session Total Input: 17.1 MiB (1.61 KiB/s average) >* Session Total Output: 24.7 MiB (2.33 KiB/s average) >* Payload Output: 2.38 MiB (231 B/sec)(9%) >* Global Total Input: 35.5 GiB >* Global Total Output: 40.8 GiB > > When i start Freenet, it take maybe one hour to be connected at least 2 > nodes, result is very, very slow connection to Freenet. > > Cann please somebody help? > It really shouldn't be taking that long. Though, the past couple weeks have been pretty bad because of low-level changes to Freenet. What OS are you using? how long have you had Freenet installed? How long has it been since you've had stable connections? So that we have a better idea of your problem, please run through this quick checklist: 1. update freenet to the most recent version. it can be done by running "update.sh" in your Freenet directory. 2. ensure that port forwarding is set up correctly (do some googling. if it still doesn't make sense, ask) 3. If at this point it still isn't working, temporarily turn off your router and computer firewall to see if that doesn't fix the issue. For the sake of clear results, try to not have tons of extra stuff running while doing all this, and be sure to restart when it might help. ___ 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:support-requ...@freenetproject.org?subject=unsubscribe
Re: [freenet-support] Route Not Found error
On Dec 6, 2010, at 8:37 PM, Skinner Family wrote:
> Yes, there is a lot more to this networking stuff than I ever imagined. I
> made the above changes per the comments below and 12 hours later, no
> improvement :-(
> At this point I need to determine if the problem is with Freenet, my router
> or firewall. I can turn off the firewalls and at least eliminate that
> possibility. Thanks.
>
> S.
>
> -Original Message-
> From: support-boun...@freenetproject.org
>> Dear Support:
>>
>> I installed Freenet 24 hours ago and continue to get the Route Not Found
>> error.
>> ...
>> (2) I know nothing about forwarding ports, but I set as the start
>> port and 46185 as the end port - traffic is allowed both ways.
>
> This might be the problem:
>
> - on port , the internal http server is running on your PC
> ("localhost" ip adress 127.0.0.1); this port need/must not be forwarded
> on the router
>
> Okay... have fixed.
>
> - if 46185 is the port that freenet says it's running opennet on, THIS
> (and only this) port has to be forwarded from the router to the PC
> (check that you're using the correct local IP, like 192.168.0.1 or
> something .. you find it e.g. in the status report of your ethernet
> network connection or by typing "ipconfig" in the command line window.
>
> The port forwarding config on the router for HTTP requires a start port, and
> end port, and the local IP. I've used port 80 and 46185 and have set the
> local ip.
This is definitely NOT what you want to do. From what you said, I know that
your port forwarding configuration will not work. You want both the in-port and
the out-port to be 46185. If you have the in-port set to 80 and the out-port as
46185, that means that incoming connections will only be accepted on port 80,
and before they get to your computer they will be rerouted to port 46185. So no
Freenet nodes will be able to connect to you through 46185 until you fix the
configuration.
As Skinner Family wrote, this port is the only one that you need forwarded, but
it has to be done correctly.
> - do not use trigger ports: port triggering implies that the ports are
> closed after a time again - you want the port constantly open for
> freenet (you're running a server, after all!)
>
> Yeah... good point. I've removed all port triggering.
>
> All in all - read up the wiki pages and your router manual thoroughly
> (again).
> As at part of the wiki isn't an easy read, I would give you a link to
> easy-to-understand networking basics, yet, I don't have one at hand
> atm., sorry.
>
> A.
___
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:support-requ...@freenetproject.org?subject=unsubscribe
Re: [freenet-support] Login with Mac
On Feb 13, 2011, at 3:03 AM, Dsoslglece wrote: > Hi, > first of all, to start Freenet, you can use Terminal (very simple) : > > 1) cd[space]and the path to the freenet folder… for exemple, my freenet is on > a sparseimage disc called perso (made with disk utility and PW protected), > so, I type : > > cd /Volumes/Perso/Freenet > An easy way to write the correct path is, after having written "cd+space", is > to slide the Freenet folder's icon on terminal, so the path is automatically > written. > > 2) press the "next line key" > > 3) type : ./run.sh start > > 4) press the next line key. > > > Normally, and with the little rabbit icon, it is even more simple: > > <>> > > > Of course, here, Freenet runs already, and so, one can only stop it, but when > it is stopped, you have the choice to 'start Freenet'. > That little icon, by the way should automatically go onto that menu bar when > one clicks on it from the application folder (doesn't go in the dock !). I have installed Freenet on multiple Mac computers, and never was there an icon in the menu bar. I have always used the Java WebStart installer from the main page, having used it on computers with operating systems ranging from 10.3 to 10.6. Since that icon has never been available, I have always used the commands "run.sh start" and "run.sh stop". Is there something I'm doing wrong? Note to Fritz: 1.I noticed that Dsoslglece didn't explicitly describe how to shut down Freenet with the same method he described. From context, simply replace the argument "start" with "stop". 2. He also didn't explain where/what Terminal is. In case you don't know, it's located in /Applications/Utilities/ on your hard drive. To put it simply, Terminal lets you run commands through text, unlike graphical interfaces. So when you "cd" to a folder, you're telling your computer to only look at files in that folder when running commands. run.sh is a file in the Freenet folder which contains many pre-written commands to get Freenet running (and shut it down), so when you tell it to start it starts Freenet, and the same for shutting down. 3. If you ever want to know more about commands like "cd" that are built into your computer, type "man [command-name]". Man is short for manual, so as it sounds you'll be shown the manual to that command. > > A little advice still, if you are using normally Firefox, use another browser > for Freenet ONLY, for instance Opera, that is very similar and just as secure. > You can even locate it together with Freenet if you decided to use a > protected disc image… so you can keep bookmarks safe > > Sorry, the message came back saying it was to big, so I reduced the pict and > hope it passes now > ___ 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:support-requ...@freenetproject.org?subject=unsubscribe
Re: [freenet-support] jFCPlib jar?
On Feb 12, 2011, at 7:03 PM, Roland Haeder wrote: > I would bet he is not a user. Please take a look at the date he sent it. > > Please also remember that Frost has similar legit-looking messages but > they are spam. > > I could be wrong, but does mail really take so long? :) I've been subscribed to these mailing lists for about 6 months, and it's the oddest occurrence when every month-or-so there's this huge barrage of incoming messages. If it's a spamming attempt, it's not very effective. I mean, it's not like the mailing list is inoperative now. However, it's an even weirder situation if these are legitimate support requests sent a year ago that never made it here... > > On Sun, 2011-02-13 at 01:44 +0100, David ‘Bombe’ Roden wrote: >> On Sunday 12 December 2010 21:44:28 Robert Foss wrote: >> >>> Where can I find a compiled version of the jFCPlib jar? >> >> Nowhere, I’m afraid. At least I don’t offer any precompiled versions. You >> have >> to build it yourself. >> >> >>> thanks :) >> >> No problem. :) >> >> David >> ___ >> 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:support-requ...@freenetproject.org?subject=unsubscribe > > ___ > 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:support-requ...@freenetproject.org?subject=unsubscribe ___ 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:support-requ...@freenetproject.org?subject=unsubscribe
Re: [freenet-support] Freenet 0.7.5 build 1329 (big!)
On Jan 13, 2011, at 1:00 PM, Dennis Nezic wrote: > On Thu, 13 Jan 2011 19:56:41 +0100, Dsoslglece wrote: >> Hi, >> I must say that since about a week, The band use seems to be >> completely stabilized… I'm still on the version 1327 (the update will >> eventually be done some time automatically) and everything seems fine. >> Thanks. >> >> iMac-Intel Snow Leopard > > Strangely, 1327 worked for me too (for at least a day). Running OS X 10.6, I never noticed unruly bandwidth usage over the past couple weeks. My node's currently running 1329 and it's still stable. ___ 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:support-requ...@freenetproject.org?subject=unsubscribe
Re: [freenet-support] Freenet is clogging the tubes?
On Jan 12, 2011, at 3:41 PM, Edzard Pasma wrote: > Op 12-jan-2011, om 19:32 heeft Daxter het volgende geschreven: >> I can't figure out what exactly is the cause, so I'll just explain the >> symptoms. Freenet is running fine, but most attempts to load a "normal" >> (WWW) web page either stall or load very slowly. My guess is that, starting >> somewhere around build 1315, my node started creating so many connections >> that it borders the max number my router supports, thus leaving little room >> for other applications to create their own connections. I am sure that >> Freenet is the issue because as soon as I shut down my node, pages load at >> their normal rate. >> >> This leads to two questions: >> 1. How can I determine that this is indeed the issue? (that my router's >> connection limit is maxed out, and/or that Freenet is causing it) >> 2. What might my node be doing to cause in the first place? An alternate >> theory would be that it isn't properly terminating old connections to my >> router's liking. >> > Here is an answer to question 1, but just for Linux. > > On Linux you have netstat to find out about open connections. The plain > command returns some hundred lines, on a quiet system. I think the limit is > in the order of the number of available ports or at least those in the > dynamic range (5.000?). > > Netstat -p prints the process id that owns a connection. Grep and co should > find the freenet processes. On my system this yields just 5 connections. I'm running Mac OS X, but it already has netstat installed. The problem is that "-p" refers to something to do with protocols, instead of processes. I searched the man page and couldn't find any reference to an ability to show the processes holding the connections. I don't know how large the limit of connections is, but the range of ports at least goes to 65,535 (according to what I could find on a quick web search). Oddly there weren't that many connections (a few hundred). Now I'm really confused; how, then, is Freenet preventing other applications from communicating? This symptom only exists when it's running... Freenet rarely even uses 1/4 of my download bandwidth. ___ 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:support-requ...@freenetproject.org?subject=unsubscribe
[freenet-support] Freenet is clogging the tubes?
I can't figure out what exactly is the cause, so I'll just explain the symptoms. Freenet is running fine, but most attempts to load a "normal" (WWW) web page either stall or load very slowly. My guess is that, starting somewhere around build 1315, my node started creating so many connections that it borders the max number my router supports, thus leaving little room for other applications to create their own connections. I am sure that Freenet is the issue because as soon as I shut down my node, pages load at their normal rate. This leads to two questions: 1. How can I determine that this is indeed the issue? (that my router's connection limit is maxed out, and/or that Freenet is causing it) 2. What might my node be doing to cause in the first place? An alternate theory would be that it isn't properly terminating old connections to my router's liking. ___ 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:support-requ...@freenetproject.org?subject=unsubscribe
Re: [freenet-support] Source Code Link Problems on Main Download Page
On Dec 18, 2010, at 1:04 PM, Matthew Toseland wrote: > On Tuesday 14 December 2010 16:27:17 Daxter wrote: >> I know that's there (I noted that in my original message). We're currently >> on build 1310, though, not 1306. The problem isn't that no source code is >> available; it's that [a] the link on our main website consistently 404's >> and [b] the most recent source isn't available through the only method noted >> on the Freenet download page. > > Sorry, scripting foulup. Will be fixed as soon as the uploads complete (hour > or less). Now that I finally noticed your reply, I wanted to officially close this matter as your fix worked. Thank you Matthew for fixing that link; I'm sure that many people have been frustrated by that 404. ...Which leads me to wonder how long it's been since your script worked correctly and since that link had been up to date. Surely it must have been working at some time in the recent past. I can't be the only person to have ever, in the history of Freenet, tried to download the source code from the main website... right? ___ 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:support-requ...@freenetproject.org?subject=unsubscribe
Re: [freenet-support] No SHA1 or MD5 hashes for the installer?
On Jan 1, 2011, at 11:57 AM, Matthew Toseland wrote: > On Saturday 01 January 2011 17:51:41 Fabio Spelta wrote: >> >> Glad to know it. Where are they published? >> I'd suggest you to publish the instructions and the links to do so right >> into the install instructions. > > We do, but it's not very prominent because most users don't use it. Reread > the download page. You can say that again! It's only ever mentioned in the Linux download instructions. There's no reference to it for Mac or Windows. The worst part about the current setup is that even if a person that's running Windows or Mac reads the instructions word-for-word they still will have no idea that there is anything available to ensure that the file they want to download isn't molested. How can we expect newbies to take security precautions when the methods aren't well-explained, and sometimes aren't explained at all? I tried it out using GnuPG (for Mac) to verify the offline installer .jar file, but I received an error: "Can't check signature: public key not found" The command I typed was -> gpg --verify [installer] [.sig] Am I doing something wrong? ___ 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:support-requ...@freenetproject.org?subject=unsubscribe
Re: [freenet-support] Source Code Link Problems on Main Download Page
I know that's there (I noted that in my original message). We're currently on build 1310, though, not 1306. The problem isn't that no source code is available; it's that [a] the link on our main website consistently 404's and [b] the most recent source isn't available through the only method noted on the Freenet download page. On Dec 14, 2010, at 10:08 AM, Mel Charters wrote: > Check > http://code.google.com/p/freenet/downloads/detail?name=freenet-build01306-source.tar.bz2&can=2&q= > Mel Charters > mcharter...@q.com > > > > On Dec 14, 2010, at 2:27 AM, Daxter wrote: > >> I noticed this problem previously but I never bothered until now to report >> it. That is, the /download.html page on freenetproject.org has a link to >> source code that rarely can actually be accessed. The last line of the page >> links to the source code here: >> http://freenet.googlecode.com/files/freenet-build01310-source.tar.bz2 and >> yet it cannot be accessed because it isn't actually there. After some >> checking I found that build 1306 is the newest version available this way. >> So, for at least 4 releases this (likely auto-updated) link has been >> pointing to (a manually updated) file that hasn't been uploaded, resulting >> in a lot of responses like my initial one: "WTC? Why can't I download this!? >> Are they trying to hide some CIA call-home code??" >> >> Whatever people might think, this consistently unavailable link only serves >> to turn away those who might help improve our code in the future. Now, how >> do we keep this from happening again? >> >> This is a particularly unique problem because, unlike with most projects >> where the vast majority of normal users only update when major releases come >> around every couple months/years, our entire user-base must update to the >> newest code something like once a week. It's easy for everyone else to >> simply triple-check their links before publishing, but for us it can get >> quite tiring to do that every week. >> >> I don't know what the best solution would be, but I think it's important >> that we fix this chronic broken-link syndrome. ___ 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:support-requ...@freenetproject.org?subject=unsubscribe
[freenet-support] Source Code Link Problems on Main Download Page
I noticed this problem previously but I never bothered until now to report it. That is, the /download.html page on freenetproject.org has a link to source code that rarely can actually be accessed. The last line of the page links to the source code here: http://freenet.googlecode.com/files/freenet-build01310-source.tar.bz2 and yet it cannot be accessed because it isn't actually there. After some checking I found that build 1306 is the newest version available this way. So, for at least 4 releases this (likely auto-updated) link has been pointing to (a manually updated) file that hasn't been uploaded, resulting in a lot of responses like my initial one: "WTC? Why can't I download this!? Are they trying to hide some CIA call-home code??" Whatever people might think, this consistently unavailable link only serves to turn away those who might help improve our code in the future. Now, how do we keep this from happening again? This is a particularly unique problem because, unlike with most projects where the vast majority of normal users only update when major releases come around every couple months/years, our entire user-base must update to the newest code something like once a week. It's easy for everyone else to simply triple-check their links before publishing, but for us it can get quite tiring to do that every week. I don't know what the best solution would be, but I think it's important that we fix this chronic broken-link syndrome. ___ 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:support-requ...@freenetproject.org?subject=unsubscribe
Re: [freenet-support] A beginner's analysis of Freenet's method of communication
On Oct 24, 2010, at 3:22 PM, Romain Dalmaso wrote: > On Sun, Oct 24, 2010 at 9:38 PM, Daxter wrote: >> From my understanding, there is a fundamental flaw in p2p technologies like >> Freenet for those that want to deploy in highly-censored countries. That is, >> it's too obvious. The censor doesn't have to know what's being transmitted, >> only that /something/ is that's outside of their control. All they have to >> do is disallow the ports on which the technology runs. Torrenters can at >> least get around this by changing the port they're using; Freenet has no >> such option. > > Every node chooses random ports for opennet and darknet during the > installation. You can change them if you want. I hadn't understood that. Thank you for explaining. How would someone change those ports? >> From my understanding of internet communication protocols, the use of udp is >> too obvious; it stands out like a sore thumb. Why not tunnel the connection >> over tcp? Wouldn't that prevent potential censors from differentiating it >> from the rest of transmitted data? As well, wouldn't it solve the closed >> ports issue? > > No, it's not that easy. You clearly don't know what you're talking about. No, I don't I had already said so in my post, but thank you for stating the obvious. I'm not here because I know everything and I want to bestow divine wisdom; I'm here because I want to learn. Would you care to explain what I don't understand, or at least point me towards topical resources? In particular I'm asking: why not tunnel connections in a manner similar to VPN? ___ 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:support-requ...@freenetproject.org?subject=unsubscribe
[freenet-support] A beginner's analysis of Freenet's method of communication
>From my understanding, there is a fundamental flaw in p2p technologies like >Freenet for those that want to deploy in highly-censored countries. That is, >it's too obvious. The censor doesn't have to know what's being transmitted, >only that /something/ is that's outside of their control. All they have to do >is disallow the ports on which the technology runs. Torrenters can at least >get around this by changing the port they're using; Freenet has no such option. >From my understanding of internet communication protocols, the use of udp is >too obvious; it stands out like a sore thumb. Why not tunnel the connection >over tcp? Wouldn't that prevent potential censors from differentiating it from >the rest of transmitted data? As well, wouldn't it solve the closed ports >issue? I'm sure some of my conclusions are based off of an incomplete understanding of the technologies involved, but I couldn't think of a better way to find out than to put my ideas out there. ___ 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:support-requ...@freenetproject.org?subject=unsubscribe
