Could it not detect the IP address of the router though? I know you'd still have to have port forwarding set up but at least it would remove the need for needing to set up something like dyndns.
> -----Original Message----- > From: devl-admin at freenetproject.org [mailto:devl-admin at freenetproject.org] > On Behalf Of Matthew Toseland > Sent: 18 December 2002 19:53 > To: devl at freenetproject.org > Subject: Re: [freenet-dev] freenet.configuration > > On Wed, Dec 18, 2002 at 07:37:18PM -0000, Simon Porter wrote: > > Interesting. Thanks for that. With the ipAddress setting, will that > > become redundant with ARKs implemented. Would ARKs also work for people > > behind a NAT firewall (like me!)? > No. Running behind a NAT firewall requires manual configuration, and > always will, because you need to forward a port, and tell the node what > the outside address is. > > > > The other thing I'm not clear about is whether running a node in > > permanent mode would harm the network at all if the node isn't running > > 24hrs a day. I've always thought that it wouldn't because the network > > would just simple route around it. Every time I've asked this question > > in the past I just seem to have got flamed. > There have been improvements lately that should reduce the impact of > nodes being shut down frequently. > > > > Do you know who is responsible for the 'Freenet node properties' in the > > Windows client? It could do with some simplification for 'lusers' as you > > so amusingly refer to them as. > Probably oierw/Mathew Ryden. > > > > I'll keep a copy of this e-mail as it'll be very good as a reference for > > writing up documentation. Thanks. > > > > Simon > > > > > -----Original Message----- > > > From: devl-admin at freenetproject.org > > [mailto:devl-admin at freenetproject.org] > > > On Behalf Of Matthew Toseland > > > Sent: 18 December 2002 18:40 > > > To: devl at freenetproject.org > > > Subject: Re: [freenet-dev] freenet.configuration > > > > > > On Wed, Dec 18, 2002 at 09:04:56AM -0000, Simon Porter wrote: > > > > Yes but that's far from as user friend as a GUI config is. Most dumb > > > > users just scratch their head and go WTF? > > > It can be simplified significantly. > > > > > > $ CLASSPATH=freenet.jar:freenet-ext.jar java freenet.node.Main > > --config > > > Freenet Configuration > > > Running in simple mode. Some preferences will be skipped. > > > You can choose the default preferences by just hitting <ENTER> > > > > > > Setting: ipAddress > > > The IP address of this node as seen by the public internet. This is > > > needed in order for the node to determine its own node reference. > > > If you have a dynamic IP address, you may enter a host name in this > > > field (assuming you have a dynamic DNS service). If this is a > > > transient node, you can leave this blank. > > > ipAddress [] > > > this is no longer necessary except for people behind NATs... we > > > can make this expert mode. And update the comment. > > > > > > Setting: listenPort > > > The port to listen for incoming FNP (Freenet Node Protocol) > > connections > > > on. > > > listenPort [20299] > > > > > > there is no reason to expose this to the luser either. On the > > > other hand somebody who knows what he is doing would probably > > > prefer to see it... but it does cause a lot of confusion. I vote > > > to make this expert mode only too. > > > > > > Setting: clientPort > > > The port to listen for local FCP (Freenet Client Protocol) connections > > > on. > > > clientPort [8481] > > > > > > there is absolutely no reason for the luser to have to mess with > > > this > > > > > > Setting: fcpHosts > > > A comma-separated list of hosts that may connect to the FCP port > > > (clientPort). If left blank, only the localhost will be allowed. If > > you > > > set this, make sure localhost is included in the list or access won't > > > be allowed from the local machine. > > > May be given as IP addresses or host names. > > > fcpHosts [] > > > > > > here we have a bit of a dilemma; maybe we need a luser mode as > > > well as an expert mode > > > > > > Setting: transient > > > Transient nodes do not give out references to themselves, and should > > > therefore not receive any requests. Set this to yes if you cannot > > > receive incoming connections, or cannot keep the computer continuously > > > online. > > > transient [y/N] > > > > > > we will now default to permanent. only people whose nodes have > > > real connectivity problems should be transient. > > > > > > Setting: doAnnounce > > > If this is true, the node will automatically announce to all nodes in > > > the <seedFile> file, as specified by <announcementDelay>, etc. > > > doAnnounce [Y/n] > > > > > > this should definitely be expert mode only; it should also be > > > updated, announcementDelay no longer exists > > > > > > Setting: seedFile > > > A file containing one or more node references which will be > > incorporated > > > into the node's routing table on startup. A reference is only added > > if > > > there is no previously existing reference to that node. When this > > node > > > announces, it will announce to the nodes listed in this file. > > > seedFile [seednodes.ref] > > > > > > hmmm.... we should only ask this if there is no seednodes.ref > > > file, and any distribution should include it... again, I think > > > this should be expert or at least non-luser-mode > > > > > > Setting: storeSize > > > The byte size of each data store file. If there is more than one > > > file, the total size of the store is the product of the number of > > > files and <storeSize>. The maximum sized file that will be cached is > > > 1/200th > > > of this value, so we recommend the default 256MB, to cache the largest > > > common > > > file size on freenet, 1MB plus some headers > > > storeSize [268435456] > > > > > > this we do need to ask the user. The comment should be changed > > > to make it clear that you can use multipliers k, K, m, M, g, G, > > > t, T. A platform-specific daemon could poll the available disk > > > space and the used disk space, and keep freenet within certain > > > bounds including a % of available disk, dynamically updated... > > > but first we need the FCP store resize command. Once we have > > > that, we could perhaps have a default value for storesize of 20% > > > of available space on the partition we install on. Anyway, your > > > average linux user can surely understand this comment. > > > > > > Setting: bandwidthLimit > > > The maximum number of bytes per second to transmit, totaled between > > > incoming and outgoing connections. Ignored if either > > > inputBandwidthLimit > > > or outputBandwidthLimit is nonzero. > > > bandwidthLimit [100000] > > > > > > anyone who isn't a total luser will know what this means. > > > Unfortunately it is not generally possible to autodetect the > > > bandwidth of the local connections, so this will always be a > > > challenge to lusers. > > > > > > Setting: averageBandwidthLimit > > > The maximum number of bytes per second to transmit (averaged over a > > > week), totaled between > > > incoming and outgoing connections. Error to define it if any of > > > (average)inputBandwidthLimit > > > or (average)outputBandwidthLimit is nonzero. > > > averageBandwidthLimit [0] > > > > > > very very useful for people with limited-per-month > > > connections... > > > > > > Setting: logLevel > > > The error reporting threshold, one of: > > > Error: Errors only > > > Normal: Report significant events > > > Minor: Report minor events > > > Debug: Report events only of relevance when debugging > > > logLevel [normal] > > > > > > can people really not handle this? It should probably be > expert > > > > > > Setting: services > > > A comma delimited list of services that are run when the node starts. > > If > > > you don't know what this means, just accept the defaults. > > > services [mainport, distribution] > > > > > > definitely should be expert > > > > > > > > > That's all folks. > > > > > > > > > > > > > > > -----Original Message----- > > > > > From: devl-admin at freenetproject.org > > > > [mailto:devl-admin at freenetproject.org] > > > > > On Behalf Of Greg Wooledge > > > > > Sent: 18 December 2002 01:44 > > > > > To: devl at freenetproject.org > > > > > Subject: Re: [freenet-dev] freenet.configuration > > > > > > > > > > Anonymous (mtoseland at cableinet.co.uk) wrote: > > > > > > > > > > > what do you think about modify the configuration of freenet > > through > > > > the > > > > > web > > > > > > interface? > > > > > > > > > > I'm sure your patch to do this would be welcome. :) > > > > > > > > > > > and last but not least: we can have an updated configuration > > tool > > > > > > accordingly to the build of freenet.jar! > > > > > > > > > > We already have that. The configuration tool for everything > > *other* > > > > > than the Windows installer is called "java freenet.node.Main > > > > --config". > > > > > (That's precisely what the start-freenet.sh script runs.) > > > > > > > > > > -- > > > > > Greg Wooledge | "Truth belongs to everybody." > > > > > greg at wooledge.org | - The Red Hot Chili Peppers > > > > > http://wooledge.org/~greg/ | > > > > > > > > > > > > _______________________________________________ > > > > devl mailing list > > > > devl at freenetproject.org > > > > http://hawk.freenetproject.org/cgi-bin/mailman/listinfo/devl > > > > > > > > > > -- > > > Matthew Toseland > > > toad at amphibian.dyndns.org > > > amphibian at users.sourceforge.net > > > Freenet/Coldstore open source hacker. > > > Employed full time by Freenet Project Inc. from 11/9/02 to 11/1/03 > > > http://freenetproject.org/ > > > > > > _______________________________________________ > > devl mailing list > > devl at freenetproject.org > > http://hawk.freenetproject.org/cgi-bin/mailman/listinfo/devl > > > > -- > Matthew Toseland > toad at amphibian.dyndns.org > amphibian at users.sourceforge.net > Freenet/Coldstore open source hacker. > Employed full time by Freenet Project Inc. from 11/9/02 to 11/1/03 > http://freenetproject.org/ _______________________________________________ devl mailing list devl at freenetproject.org http://hawk.freenetproject.org/cgi-bin/mailman/listinfo/devl
