||This References may require cleanup to meet Wikipedia's quality standards. (January 2010)|
|Part of a series on|
|Development and societal aspects|
|Non-public file sharing|
|File sharing networks and services|
|By country or region|
Gnutella2, often referred to as G2, is a peer-to-peer protocol developed mainly by Michael Stokes and released in 2002. While inspired by the gnutella protocol, G2 shares little of its design with the exception of its connection handshake and download mechanics. It adopts an extensible binary packet format and an entirely new search algorithm. Furthermore, it has a slightly different network topology and an improved metadata system which helps effectively to reduce fake files, viruses (etc.) on the network.
In November 2002, Michael Stokes announced the Gnutella2 protocol to the Gnutella Developers Forum. While some thought the goals stated for Gnutella2, primarily to make a clean break with the gnutella 0.6 protocol and start over so that some of gnutella's less clean parts would be done more elegantly, to be impressive and desirable, other developers, primarily those of LimeWire and BearShare, thought it a "cheap publicity stunt" and discounted technical merits. Many still refuse to refer to the network as "Gnutella2" and instead refer to it as "Mike's Protocol" ("MP").
The Gnutella2 protocol still uses the old "GNUTELLA CONNECT/0.6" handshake string for its connections as defined in the gnutella 0.6 specifications, which was criticized by the GDF as an attempt to use the gnutella network for bootstrapping the new, unrelated network, while proponents of the network claimed that its intent was to remain backwards-compatible with gnutella to allow current gnutella clients to add Gnutella2 at their leisure.
The draft specifications were released on March 26, 2003, and more detailed specifications soon followed. G2 is not supported by many of the "old" gnutella network clients, however many Gnutella2 clients still also connect to gnutella. Many Gnutella2 proponents claim that this is because of political reasons, while gnutella supporters claim that the drastic changes don't have enough merit to outweigh the cost of deep rewrites.
Gnutella2 divides nodes into two groups: Leaves and Hubs. Most Leaves maintain two connections to Hubs, while Hubs accept hundreds of Leaf connections, and an average of 7 connections to other Hubs. When a search is initiated, the node obtains a list of Hubs if needed, and contacts the Hubs in the list, noting which have been searched, until the list is exhausted, or a predefined search limit has been reached. This allows a user to find a popular file easily without loading the network, while theoretically maintaining the ability for a user to find a single file located anywhere on the network.
Hubs index what files a Leaf has by means of a Query Routing Table, which is filled with single bit entries of hashes of keywords which the Leaf uploads to the Hub, and which the Hub then combines with all the hash tables its Leaves have sent it in order to create a version to send to their neighbouring Hubs. This allows for Hubs to reduce bandwidth greatly by simply not forwarding queries to Leaves and neighbouring Hubs if the entries which match the search are not found in the routing tables.
Gnutella2 relies extensively on UDP, rather than TCP, for searches. The overhead of setting up a TCP connection would make a random walk search system, requiring the contacting of large numbers of nodes with small volumes of data, unworkable. However, UDP is not without its own drawbacks. Because UDP is connectionless, there is no standard method to inform the sending client that a message was received, and so if the packet is lost, there is no way to know. Because of this, UDP packets in Gnutella2 have a flag to enable a reliability setting. When an UDP packet with enabled reliability flag is received, the client will respond with an acknowledge packet to inform the sending client that their packet arrived at its destination. If the acknowledge packet is not sent, the reliable packet will be retransmitted in an attempt to ensure delivery. Low importance packets which do not have the flag enabled do not require an acknowledge packet, reducing reliability, but also reducing overhead as no acknowledge packet needs to be sent.
Gnutella2 has an extensible binary packet format, comparable to an XML document tree, which was conceived as an answer for some of gnutella's less elegant parts. The packet format was designed so that future network improvements and individual vendor features could be added without worry of causing bugs in other clients on the network.
For file identification and secure integrity check of files it employs SHA-1 hashes. To allow for a file to be reliably downloaded in parallel from multiple sources as well as to allow for the reliable uploading of parts as the file is being downloaded (swarming), Tiger tree hashes are used.
To create a more robust and complete system for searching, Gnutella2 also has a metadata system for more complete labeling, rating, and quality information to be given in the search results than would simply be gathered by the file names. Nodes can even share this information after they have deleted the file, allowing users to mark viruses and worms on the network without requiring them to keep a copy.
Shareaza has the additional feature to request previews of images and videos, though currently no additional clients take advantage of this.
Differences from gnutella
Overall, the two networks are fairly similar, with the primary differences being in the packet format and the search methodology.
Gnutella's packet format has been criticized because it was not originally designed with extensibility in mind, and has had many additions over the years, leaving the packet structure cluttered and inefficient. Gnutella2 learned from this, and aside from having many of the added features of gnutella standard in Gnutella2, designed in future extensibility from the start.
While gnutella uses a query flooding method of searching, Gnutella2 uses a walk system where a searching node gathers a list of Hubs and contacts them directly, one at a time. However, as Hub organize themselves in so called "Hub clusters", where each Hub mirrors the information stored by its neighbours, the Leaf is returned the information of the entire Hub cluster (usually 7 Hubs). This has several advantages over the gnutella's query flooding system. It is more efficient, as continuing a search does not increase the network traffic exponentially, queries are not routed through as many nodes, and it increases the granularity of a search, allowing a client to stop once a pre-defined threshold of results has been obtained more effectively than in gnutella. However, the walk system also increases the complexity of the network and the network maintenance required, as well as requiring safeguards to prevent a malicious attacker from using the network for denial-of-service attacks.
There is also a difference in terminology: while the more capable nodes which are used to condense the network are referred to as Ultrapeers in gnutella, they are called Hubs in Gnutella2, and they are also used slightly differently in topology. In gnutella, the Ultrapeers generally maintain as many leaves as peer connections, while Gnutella2 Hubs maintain far more leaves, and fewer peer (Hub-to-Hub) connections. The reason for this is that the search methods of the various networks have different optimum topologies.
Free software Gnutella2 clients include:
- Adagio (Cross Platform), written in Ada, under the GPL.
- Gnucleus (Windows), written in C/C++, under the LGPL
- Gtk-gnutella (Cross Platform), written in C. Only supports leaf-mode connections to G2 .
- MLDonkey (Cross Platform), written in OCaml, under the GPL, however as of version 2.9.0, support is officially unmaintained and disabled in the binaries.
- Shareaza (Windows), multi-network, written in C++, under the GPL, currently +/- 93% network share
- Sharelin (Cross platform), written in C++, web-GUI
- G2CD (Linux/Unix/BSD) Hub mode only implementation of the Gnutella2 network.
- Quazaa (Cross platform) written in C++/QT4, under GPLv3. New client inspired by Shareaza.
Proprietary software implementations include:
- Foxy (Windows) Chinese GnucDNA-derived program, no interaction with any other G2 clients possible, free.
- Kiwi Alpha (Windows)
- Morpheus (Windows)
- TrustyFiles (Windows)
The following table compares general and technical information for a number of available applications supporting the G2 network.
|client||Chat||Handles big files (>4 GB)||UKHL||Unicode||UPnP port mapping||NAT traversal||Remote preview||Ability to search with hashes||Hub modus||Spyware/ Adware/ Malware-free||Other networks||Based on||OS||Other|
|MLdonkey||Currently no official support for the Gnutella2 plugin. Searching for new maintainer for this plugin.||-||Cross-platform|||
|Morpheus||Yes||No||No||No||Yes||No||No||Yes||No||No||gnutella,||GnucDNA||Windows||Development and hosting of the client has been stopped|
|Quazaa||No||No||No||Yes||No||IPv4to6 only||No||Yes||Yes||Yes||none yet||-||Cross-platform||Includes IRC chat, IPv6 support. Still in early stages of development.|
|Shareaza||Yes||Yes||Yes||Yes||Yes||No||Yes||Yes||Yes||Yes||gnutella,||-||Windows||Includes IRC support|
|Sharelin||No||Yes||Yes||No||No||No||No||Yes||No||Yes||N/A||-||Unix/Linux||Console application with WEB-GUI|
|TrustyFiles||No||No||No||No||No||No||No||Yes||No||removable in commercial version ($29)||eD2k, Overnet, BitTorrent, gnutella||GnucDNA (partial)||Windows||-|
- "Developer discussion of similarities between Gnutella and Gnutella2". The Gnutella Developer Forum. Retrieved 2006-05-10.
- "GDF Discussion on the Gnutella2 name". The Gnutella Developer Forum. Retrieved 2006-05-10.
- "Part of the Gnutella/Gnutella2 Flame War (1)". The Gnutella Developer Forum. Retrieved 2006-08-06.
- "Part of the Gnutella/Gnutella2 Flame War (2)". The Gnutella Developer Forum. Retrieved 2006-08-06.
- "Part of the Gnutella/Gnutella2 Flame War (3)". The Gnutella Developer Forum. Retrieved 2006-08-06.
- "Part of the Gnutella/Gnutella2 Flame War (4)". The Gnutella Developer Forum. Retrieved 2006-08-06.
- "Developer discussion on migration to Gnutella2". The Gnutella Developer Forum. Retrieved 2006-05-10.
- "Gnutella2 Network history". Gnutella2 Crawler g2paranha. Retrieved 2009-04-12.
- "Packet Structure". Gnutella2 Wiki. Retrieved 2007-11-07.
- "Gnutella2 Standard". Gnutella2 wiki. Retrieved 2007-11-07.
- "Simple Query Language and Metadata". Gnutella2 Wiki. Retrieved 2007-11-07.
- "Developer discussion of Gnutella and Gnutella2 packet formats". The Gnutella Developer Forum. Retrieved 2006-05-15.
- Uses its own "Foxy"-Network, which is half-poorly separated from the original G2 and known for network leakage into G2. Theoretically, the client is compatible to G2.
- It refers to client to client chat.
- Automatically configure port forwarding (requires Router with UPnP support)
- From searches and from downloads.
- Foxy Hubs are not compatible with any other Gnutella2 software and can only be connected by Foxy leaves.
- For testing purposes only Windows mode enabled in current version.
- gnutella and Gnutella2 plugins still available for downloading.
- supported via Teredo/Miredo
- Since version 220.127.116.11