Gnutella is a decentralized Peer to Peer information exchanging network. At the moment you can publish and download files of any kind using the Gnutella network. For more information, visit the Wikipedia definition of Gnutella or the definition of gnutella on the infoAnarchy wiki.
We often refer to gtk-gnutella as GTKG or gtkg (because it's shorter). GTK comes from GTK+ which is the graphical toolkit used by gtk-gnutella.
At the moment you can try one or more of the following things if you are a user on a slow line (modem):
Since version 0.92, gtk-gnutella has implemented ultrapeers and leaf nodes. This divides servents on the gnet into leaf nodes, which connect only to ultrapeers, and ultrapeers, which connect to many leaf nodes and a small number of other ultrapeers (see What is a good number of connections?).
Ultrapeers must not be not firewalled, are expected to have long uptimes (more than two hours), and have sufficient surplus bandwidth to donate to the gnet. Ultrapeers forward queries from their leaf nodes and leaf nodes upload to their ultrapeers QRP tables which contain hashes of keywords that will match files shared by the leaf. When an ultrapeer gets a hit on a query routing table, it relays the query to the corresponding leaf node. The result is very low gnet traffic for each leaf node, freeing bandwidth for sharing and downloading (which still occur directly p2p.) Ultrapeers can also act as push-proxies for firewalled leaf nodes.
Gtk-Gnutella needs to receive an incoming connection to determine if you
can be reached from the outside. Until then, it's assumed that there's
a firewall which blocks the configured listening TCP port.
If you want to speed up the detection, use a web browser, telnet or similar
and connect to the listening port from the outside. If the connection is
refused or dropped, then you are very probably really unreachable due to a
firewall which blocks the port, a misconfigured NAT or similar. You might
want to try a different listening TCP port because some ISPs block the
default Gnutella port (6346).
See also,
Do I need to forward a port on my firewall?
.
You can run the Configure script in the following way to make it
use the default settings. It then behaves as calling the old
configure script from autoconf did back in the old days.
$ ./Configure -ders
You can set compile options on the command line too. Here is an example that will configure gtk-gnutella to
-O). Without this all the
parameters below won't have an effect.
-D gtkversion=1 -D remotectrl=y)
-Dccflags="-march=pentium -mmmx").
-Doptimize="-g -O0").
$ ./Configure -ders -O -D gtkversion=1 -D remotectrl=y -Dccflags="-march=pentium -mmmx" -Doptimize="-g -O0"
In leaf mode 3 ultrapeers, in ultrapeer mode 32/40 (minimum/maximum) ultrapeers and around 100 leaf nodes. The actual number should depend on the available bandwidth. If you have set "Prefer compressed connections," bandwidth used will be much lower. You should never use up all your bandwidth with gnet connections. Especially on an asymmetric cable/DSL connection you can easily starve your incoming traffic by producing too much outgoing traffic (TCP/IP issue). Use at most half of your outgoing bandwidth for gnet connections.
Since the adoption of "high outdegree" in version 0.95 you should have 32/40 connections to other ultrapeers. The number of leaf connections to use depends on your bandwidth and the speed of your cpu. As an absolute minimum an ultrapeer should connect to 20 leaf nodes and it's much better to connect to 100 or more. Watch the bandwidth odometers on the lower left of the gui and use the top command to keep track of cpu usage. Increase the number of leaf connections until you reach the maximum amount of bandwidth and system resources you wish to devote to this purpose.
The bandwidth control settings will help you further fine-tune gtk-gnutella's bandwidth usage.
You don't need to forward any ports for gtk-gnutella to work, but it
will perform much better if you do. If gtk-gnutella thinks you are
firewalled, it will not show any "push" results since
you wouldn't be able to download those anyway.
Even when people cannot connect directly to you, they can still download
files from your node using a push request.
You can configure the port gtk-gnutella listens on. The setting
Listen port is located in the Settings->Preferences->Network.
You can find instructions for most popular routers at http://www.portforward.com/routers.htm. Try http://www.canyouseeme.org/ to check your port forwarding.
Yes, starting with version 0.95 gtk-gnutella can also use UDP in addition to TCP.
The FC means "flow control".
In general, you should make sure that servents to which you are connected do
not flow control. Watch for the trailing [FC] indication at
the end of the Info string (you may need to drag the right
edge past the window to trigger the underlying scroll bar), or look at the
FC state in the Flags column. As a rule of thumb, if
you have more than one node flow-controlling at a given time, you don't have
enough outgoing bandwidth dedicated to gnet, and therefore you are harming
the network: either decrease the amount of connections, enable the
Prefer compressed connections option or raise the outgoing
bandwidth limit.
Try to do bandwidth limiting. If that doesn't help, maybe your provider throttles gnutella traffic. Try changing your gnutella port in the network settings of gtk-gnutella.
You can see the type and some of the settings of a connection here. Note push-proxies are implemented in 0.92.1c and later.
012345678AB (offset) NIrwqxZPFhT ||||||||||+ indicates a TLS-tunneled connection |||||||||+- hops flow triggered (h), or total query flow control (f) ||||||||+-- flow control (F), or pending data in queue (d) |||||||+--- we are push-proxy for node (P) or node is our push-proxy (p) ||||||+---- indicates whether Rx, Tx or both (Z) are compressed |||||+----- we sent our last-hop QRT to remote UP (X), or are sending one (x) ||||+------ we sent/received a QRT, or are sending/receiving one (q) |||+------- indicates whether node is writable ||+-------- indicates whether node is readable |+--------- connection type: (Incoming, Outgoing, Ponging) +---------- peer mode: Ultra, Leaf, or Legacy (a.k.a. Normal)
This indicates that the User-Agent name is possibly faked but it could be a false-positive caused by a bad clock on either side.
Sometimes, servents are discovered to have a bug or behaviour that is harmful to the gnet. For example, gtk-gnutella-0.92b had a bug that generated excessive queries which hammered on the GWebCache system. Such banning is exceptional, usually restricted to specific versions, and the servent's author is informed about the banning.
Versions of gtk-gnutella more than one year old are banned, since they lack features that are important to the rapidly evolving gnet's health and scalability. In addition, unstable versions are banned after 90 days.
Your HTTP proxy must support the method CONNECT because a normal GET
doesn't work with Gnutella connections. This is an extension to the HTTP
protocol and mainly supported by SQUID proxies. It's also often deactivated
because it might be considered a security problem by your provider. At the
moment, the proxy support - also for SOCKS - isn't very good. The developers
don't use proxies but if you think you can fix it, we would appreciate
your patches.
If your internet connection suffers from high latency it might help to increase the timeouts. Go to Settings->Preferences->User Interface and tick Expert mode. Now, you'll find a lot more settings to change when you go to Settings->Preferences->GnutellaNet.
In order to be promoted to ultra mode the following conditions must be met:
The number of results you get depends heavily on whether people are able to connect to you (see port forwarding) and on the number of connections to other hosts.
Click with right mouse button on a search result without a SHA1 and select "Drop results...->with the same urn:sha1" from the popup menu. That will drop all results with this SHA1 - in this case none - from your results. You'll miss a lot of spam.
Searches are now entered in the Search:
box in the sidebar.
A passive
search will return all the search results that
pass through gtk-gnutella. By
filtering these results,
passive searches can be useful.
If you are in ultra mode, many search
results are already passing through your node besides the ones for your own
searches. You can take advantage of this to make searches without generating
any extra gnet traffic. For example, on my ultrapeer with 200
leaf nodes, I opened a passive search and
filtered the results to display only hits with the name
eminem
. Within an hour or so I had about 1500 results.
Obviously, the more popular the search, and the more patient you are, the
more useful this technique is.
If you are in leaf mode, then the only search results that will pass through gtk-gnutella will be those from your own searches, so the above technique won't be useful. But there is another way to use passive searches that is only useful in leaf mode. For example, if you start a passive search and filter it to display only mp3 files, then all mp3 files from all your open searches will be conveniently aggregated in one search window. By opening more passive searches with different filters, you can display different file types in each.
This means that gtk-gnutella has that file recorded as complete in its
database. This database is usually located in
~/.gtk-gnutella/done.sha1 and ~/.gtk-gnutella/done.namesize.
At the moment, there is no way to remove or modify
an entry of that database from the gui, but you can edit the file with any
text editor while gtk-gnutella is not running. If you add or remove something
from one of the files, do the same to the other.
This means that gtk-gnutella wants to download a new file from a host, but
that host does not provide a SHA1 hash for the file. Since the file is new
(not yet partially downloaded), gtk-gnutella cannot do an overlap check to
verify that the file on the host is really the file you want. In such a case
it relies on the SHA1 provided by the remote host, but if no SHA1 is
supplied, then gtk-gnutella has no way of assuring that the file it wants to
download and the file on the remote server are really the same.
If you get annoyed by those messages you can activate the Optimistic
first chunk option in the Settings->Preferences->Download.
Check the Range column. This is called swarming. Gtk-Gnutella tries to get the file in chunks and will get it from multiple hosts in parallel, if possible.
Swarming describes the ability to download a single file from multiple hosts in parallel. Gtk-Gnutella will automatically try to find additional sources for any queued file using the download mesh and by monitoring routed results.
A chunk is another word for part of a file. When gtk-gnutella runs in swarming mode it will retrieve multiple chunks of a downloading file until it has downloaded the complete file. The Range column shows you which chunk you are currently downloading.
When you download a file from a host that supports the download mesh, it will tell you about additional sources for the requested file (provided it knows of any). Those will then be used for swarming
The push request is a facility to download files from hosts you cannot
connect to directly (because they are firewalled). Well, you cannot
connect to those hosts, but they probably can connect to you. To
tell a remote host to connect to your host so that you can download
a file from the remote host you send a push request to it.
If you download a file using a push request and you loose contact to
the host which originally returned the result for that file to you,
then the push route is lost and you can no longer download this
file.
Therefore push routes are quite fragile.
You can't make use of push requests when you are behind a firewall
(see port forwarding).
You probably haven't set up different directories for downloaded files, temporary files and bad files.
If you don't see a smiling yellow icon with sunglasses in the statusbar, you should try to change that. See the section about firewalls.
Otherwise if Gtk-Gnutella says it has only a few sources for the file (best seen in the fileinfo subtab in the downloads pane) then this can have two reasons:
You can try to search for the file again and see if you find another version which is more common. It's usually a good indication if the "#" shows a number for a file. The larger the number, the better are the chances that you can get it quickly.
It means that the file is received over a push route.
This shows the total amount of bytes uploaded for the file divided by the file size.
Set the environment variable GDK_USE_XFT to 0 and see whether
this helps. This turns off anti aliasing in Gtk2 which can use a lot of cpu.
The Gtk2 frontend is much slower than the Gtk1 frontend. So on a slow machine,
you should consider using the Gtk1 frontend.
Set the environment variable LC_CTYPE or LC_ALL to
an appropriate value for the encoding you use. For example, if you use
special German characters in your filenames, set it to
de_DE.ISO8859-1. The valid values depend on your operating
system; see the manpage setlocale(3) for details. Ideally, everyone would
use UTF-8 encoding which covers nearly all languages.