giftd and gift-setup (ports?) for Apollon
- From: hawat.thufir@xxxxxxxxx
- Date: 18 Feb 2006 13:51:04 -0800
I'm getting the following error from Apollon:
'Connection error
The giFT daemon, which is responsible for connecting to the various
networks,
appears to be down and I don't seem to able to start it.
Probably your giFT installation is corrupted. Try starting giFT
manually by typing
"giftd" on the command line. If this gives errors, there's likely some
internal
error in giFT or in your giFT configuration. Refer to the giFT homepage
at
http://giftproject.org for help.'
running giftd at the moment gives something like:
[thufir@localhost ~]$ giftd
followed by a blank line, indicating to me that giftd is running.
After a few minutes of nothing, I hit CTRL-C to interrupt giftd. IIRC
giftd was saying that my gift-setup was probably incorrect, not sure
why it's now hanging.
Now, I have a wireless connection to a router, 802.11b, wi-fi, then the
router connects to a cable modem. So, that's a NAT situation, yes?
I'm wondering if I've got the ports correctly setup, or if it's
something else.
[thufir@localhost ~]$ gift-setup
*** WARNING ***
Previous configuration has been detected. This script is capable of
preserving that configuration and only adding from new available
templates.
If you choose no, all presently installed configuration modules will be
used
in place of any custom configuration you have. In the future, previous
configuration will be read and used as defaults, but this script does
not
currently have such a feature.
Would you like to preserve old configuration? [Yn] n
##############################################################################
Configuring giftd (/usr/share/giFT/giftd.conf.template):
##############################################################################
Boolean determining whether or not this file has been reviewed and is
complete. giFT will fail to start unless this is non-zero. This is
done
so that we can make sure you, at the very least, read through this
file.
Default: 0
/main/setup [0] 1
##############################################################################
Space separated list of hosts to allow connection to giFT's interface
protocol (running default on port 1213). This protocol is used for
GUIs
to communicate with giFT and could be considered a security risk to
allow
external connections.
The following special keywords are supported:
ALL - Synonym for 0.0.0.0/0
LOCAL - Synonym for 127.0.0.0/8 192.168.0.0/16 172.0.0.0/11
10.0.0.0/8
Bitwidth fields are optional.
Default: LOCAL
/main/hosts_allow [LOCAL]
##############################################################################
Port on which to listen for user interface connections. Unless you
have a
special need to talk to the client on a non-standard port, just accept
the
default.
NOTE:
If you change this value, you will also need to modify the ui.conf
configuration for the machine which will be making outgoing
connections
here.
/main/client_port [1213]
##############################################################################
Determines whether or not to follow symbolic links. If this value is
set
non-zero, symlinks will be traversed and a directory inode tracking
system
will be used to ensure that giFT does not descend the same directory
twice. If you do not have any symlinks or do not want them traversed,
set
this to 0 for a very minor efficiency gain.
Windows users: this setting has no effect.
Default: 1
/main/follow_symlinks [1]
##############################################################################
Colon separated list of protocol plugins to load by default. If
dynamic
library support is enabled, the plugin specified will be stat'd to
check if
it is a loadable path. If that fails, the fallback method is to
attempt to
construct the fully qualified path based on the configured environment.
NOTES:
Without dynamic library support, this plugin must have been compiled
into
your giFT binary. With, this plugin must exist in the installed
plugin directory. giFT -V will output this path to you, if you are
not
sure.
Protocol names are case sensitive, so use OpenFT, not Openft.
For example, to use the OpenFT and Gnutella protocols use:
OpenFT:Gnutella
Default: none
/main/plugins [OpenFT]
##############################################################################
Directory to store transfers while they are being operated on.
Temporary
state files are also kept here. It is recommended, but not required,
that
the incoming and completed directories are on the same partition
(drive).
Windows users: please use the following path specification:
incoming=/[drive]/dir1/dir2
For example, to refer to C:\Program Files\giFT\incoming, use:
incoming=/C/Program Files/giFT/incoming
Default (*nix): ~/.giFT/incoming
Default (Windows): /C/Program Files/giFT/incoming
/download/incoming [~/.giFT/incoming]
##############################################################################
Directory which will contain files after they have successfully
finished
downloading.
Default (*nix): ~/.giFT/completed
Default (Windows): /C/Program Files/giFT/completed
/download/completed [~/.giFT/completed]
##############################################################################
Maximum amount of uploads allowed from the same user at any given time.
It
is recommended that you keep this at 1 in order to prevent users from
unfairly queueing your connection.
Default: 1
/sharing/max_peruser_uploads [1]
##############################################################################
Determines whether or not to hide directories which contain a leading
dot.
These directories are commonly meant to be "hidden" and thus should not
be
submitted to the network. Selecting 0 here will submit all
directories.
On Windows files will additionally be checked for the hidden attribute
and
not shared if it is set and hide_dot_files is 1.
Default: 1
/sharing/hide_dot_files [1]
##############################################################################
Colon separated list of fully qualified paths you wish to share. These
directories will be recursed at giFT's startup and the files contained
within will be subjected to an MD5 hashing. The results will be cached
and
will only be recalculated on a per share basis when the size or
modification time in the cache and on disk disagree, or the file name
is
changed.
Sanity notice:
Do NOT share source directories! Remote nodes will refuse to index
your
shares if you are attempting to submit more than 64000 files.
Security notice:
Do not share directories which may contain sensitive information, such
as
~ ($HOME). Also note that any directories shared here will be
stripped of
all but the last path element when submitted to other nodes for
indexing,
effectively "hiding" the directory prefix.
Windows users: please use the following path specification:
/[drive]/dir1/dir2:/[drive]/dir3/dir4 ...
For example, to refer to C:\Program Files\giFT\shares and D:\shares,
use:
/C/Program Files/giFT/shares:/D/shares
Default: none
/sharing/root []
##############################################################################
Maximum amount of simultaneous uploads allowed. Setting this to 0 will
cause giFT to not limit outgoing transfers. Use shares_hidden to
disable
sharing.
Default: 0
/sharing/max_uploads [0]
##############################################################################
Whether we allow sharing. Setting this to 0 will allow sharing and
uploads
up to max_uploads. If this is 1 your shares will be hidden from the
world
and uploading will be denied. This may also be handled at run time via
your
GUI of choice.
Default: 0
/sharing/shares_hidden [0]
##############################################################################
Controls when giFT periodically rescans your shared directories for any
changes (new files, missing files, changed files, etc.) and
communicates
those changes to the underlying protocols. This parameter specifies
how
often (in seconds) you want that to happen.
For your reference
==================
0 turns off periodic auto-resync
3600 one hour
86400 one day
604800 one week
Default: 86400
/sharing/auto_resync_interval [86400] 3600
##############################################################################
Controls whether or not giFT should automatically share files that you
have
finished downloading. This feature significantly improves the
network's
abundance of files and helps ease the load on those sharing popular
files.
It's a Good Thing (TM), please leave it on.
Avoid setting your completed directories through sharing/root, as that
setting will duplicate recursion of the completed directory and cause
generally undesirable results.
Default: 1
/sharing/share_completed [1]
##############################################################################
Controls whether giFT ignores the incoming directory when sharing
files. If
this is 1 and the incoming directory is within one of the sharing roots
all
files in and below it will not be shared. This is what you want in all
known
universes. Should you find yourself running this software on a parallel
world where it is necessary to share the incoming files please make
sure it
doesn't affect us back here. Thank you.
Default: 1
/sharing/ignore_incoming [1]
##############################################################################
Bandwidth throttling allows giFT to have some basic control over your
bandwidth usage. This code operates in user space, and as a result can
not
guarantee perfect accuracy. If you wish to use this feature, please
consider using a more reliable kernel space option first. As always,
should be able to assist you there.
The following configuration switches control the maximum number of
bytes
per second allowed for the given stream direction. A setting of 0 will
disable throttling for that direction.
Default: 0
/bandwidth/downstream [0]
##############################################################################
/bandwidth/upstream [0]
##############################################################################
Wrote /home/thufir/.giFT/giftd.conf.
Configuring ui (/usr/share/giFT/ui/ui.conf.template):
##############################################################################
Host of the giFT daemon that is listening for interface connections.
If
unsure, use the default.
NOTE:
This currently does not support hostname lookup
/daemon/host [127.0.0.1]
##############################################################################
Interface port which the [possibly] remote giFT daemon is listening on.
You
should only need to change this if you have the daemon running on a
special
port.
/daemon/port [1213]
##############################################################################
Wrote /home/thufir/.giFT/ui/ui.conf.
Configuring OpenFT (/usr/share/giFT/OpenFT/OpenFT.conf.template):
##############################################################################
Node classification. This value is very important and will determine
your
potential role on the network. The following settings are allowed:
1 (USER)
Basic class that all nodes implicitly belong to. This node will
maintain
very few TCP connections on the network and perform almost no tasks
other
than to upload to other users. Users who do not have direct Internet
connections will be forced into this class.
3 (SEARCH)
Responsible for manging indexes of a large group of directly connected
children (run-time modifier for the USER class), responding to and
forwarding search requests from peers, as well as directing push
requests
so that indirectly connected users may still share files.
Please note that this class will require a much greater amount of both
local and network resources. If you select this, pay very close
attention
to the database environment settings several configuration options
down.
For reference, there are several fully functioning search nodes on
"average" broadband connections, such as 768/128kbit (my node *sigh*).
Keeping your node up-to-date is absolutely essential for this node
class.
Please check for regular updates and be sure that you are always
running
the latest version.
5 (INDEX)
Meta node used in favor of user nodes when attempting new connections
to
the network. This node class is also responsible for managing
statistics
information for the virtual clusters created by SEARCH nodes.
Reliability
is the largest requirement here.
If you're unsure it is highly recommended that you select 1 (the
default).
A setting of 7 will select both a SEARCH and INDEX node.
/main/class [1]
##############################################################################
Core listening port. OpenFT uses a compacted binary protocol for the
core
communication with other nodes. If this machine is unable to provide
both
port and http_port to the outside directly (blocked by either by a
firewall
or a NAT setup) you should select 0 here.
NOTE:
If you are unable to route this port (along with the HTTP port) you
will be
unable to download from other users with that same inability. You
will,
however, maintain the ability to upload to other non-firewalled users.
Selecting non-zero when the port is not available to the outside will
cause
very broken behaviour, namely search results will be extremely
unreliable.
Default: random (1215, 2215)
/main/port [1531] 0
##############################################################################
HTTP server port. OpenFT's implementation also makes use of HTTP for
all
file transfers. See above for more details. Please provide a valid
port
here regardless of your firewall state.
Default: random (2216, 3216)
/main/http_port [2496] 2216
##############################################################################
Arbitrary name you'd like to associate with your node. This field is
optional and it is NOT to be trusted. The name is not unique to the
network. Please do not choose useless aliases.
/main/alias [] ApollonThufirNode
##############################################################################
Maximum number of "active" nodes that are allowed connection at any
given
time. The default value (-1) is used to calculate a suitable value for
most search nodes based on their current max child configuration and
other
parameters. If you wish to take on additional connections, please note
that you must set your maximum file descriptor limit accordingly
(provided
that the internal setrlimit() call is unable to sufficiently increase
your
current limits). Consult your shell's manual regarding ulimits for
more
details.
/connections/max_active [-1]
##############################################################################
OpenFT offers a special configuration for users who wish to operate a
network from within a local area network (LAN). This mode causes giFT
to
reject authorization from any non-local address as well as advertising
it's
presence via the local UDP broadcast. If this switch is non-zero you
will
not be able to contact the main network.
/local/lan_mode [0]
##############################################################################
When LAN mode is enabled, this configuration switch is used to verify
which hosts are allowed connection to the core OpenFT port. It is
highly recommended that you just don't touch this, regardless of what
lan_mode's value is.
NOTE:
This switch provides a very crude loophole that could allow you to
create
a "private" OpenFT network between a list of known nodes. Using this
"feature" is going to be quite cumbersome as it is intended to be used
by developers only. You have been warned.
/local/hosts_allow [LOCAL]
##############################################################################
Wrote /home/thufir/.giFT/OpenFT/OpenFT.conf.
Configuring Gnutella (/usr/share/giFT/Gnutella/Gnutella.conf.template):
##############################################################################
Which port the Gnutella plugin uses. The default for the Gnutella
network
is normally 6346, but it is random for this plugin in order not to
interfere
with other Gnutella clients.
Unlike OpenFT, the Gnutella plugin uses a single port for both HTTP and
protocol communication. Similar to OpenFT, this port must be reachable
from
the outside Internet if you want to download from firewalled users.
Download
and search result performance is much better when this port is
reachable, as
quite a fair number of hosts on the Gnutella network are firewalled.
Default: random (3312, 4312)
/main/port [3820]
##############################################################################
Should the Gnutella plugin use an HTTP proxy server?
The Gnutella plugin will contact some websites over HTTP for finding an
initial list of nodes. If you need to go through a proxy server to
access
websites, the plugin will fail to connect to the Gnutella network
unless you
fill in your proxy server here. This should probably go away and be
replaced
by checking the 'http_proxy' environment variable instead. Please fix
me.
This field can be formatted as hostname:port, with an optional
'http://'
prefix and optional trailing slash. For example,
http://my.proxy.com:8080/
and my.proxy.com:8080 are valid.
Most people can probably leave this blank.
Default: none
/http/proxy []
##############################################################################
Wrote /home/thufir/.giFT/Gnutella/Gnutella.conf.
4 module(s) successfully processed.
[thufir@localhost ~]$ date
Sat Feb 18 16:34:36 EST 2006
[thufir@localhost ~]$
thanks,
Thufir
.
- Follow-Ups:
- Re: giftd and gift-setup (ports?) for Apollon
- From: hawat . thufir
- Re: giftd and gift-setup (ports?) for Apollon
- Prev by Date: Re: Repartition Windows disk.
- Next by Date: Re: Windows virus affects linux?
- Previous by thread: Repartition Windows disk.
- Next by thread: Re: giftd and gift-setup (ports?) for Apollon
- Index(es):
Relevant Pages
|
