Free peer to peer connection software for linux

PeerProtect is an addon for Jays firewall that generates a file which contains all IP addresses from the RIAA and MPAA, etc. and will protect peer-to-peer programs from them. The Database can be copied from PEERGUARDIAN or IPPREFIX.

Fast Messaging Peer to Peer (FM P2P) is a simple P2P program that forms a TCP-based overlay network by which a user may chat or share files.

Why name this FastMessaging when its anything but fast? Simply put, it is a reference to the underlying functioning of the application. TCUP, the protocol used to do the overlay network (the network we build ontop of an existing TCP/IP network) is message based.

We think it is Fast because there is no queueing or long searches. FastMessaging is built to construct moderately sized networks which have reasonably high responsiveness at the cost of global information sharing.

Perhaps thats not the best reasoning, but it works. Its just a name and the application needs a better name anyway. For now I just refer to it as FM.

JACK is a low-latency audio server, written for POSIX conformant operating systems such as GNU/Linux and Apples OS X.

Jack audio connection kit can connect a number of different applications to an audio device, as well as allowing them to share audio between themselves. Its clients can run in their own processes (ie. as normal applications), or can they can run within the JACK server (ie. as a "plugin").

JACK was designed from the ground up for professional audio work, and its design focuses on two key areas: synchronous execution of all clients, and low latency operation.

QoS Connection Tuning HOWTO is a document which explains how to tune network connection performance.

This enables you to get the maximum benefit out of your connection without lag and loss.

Connection Manager allows you to pre-configure all this, and use a single consistant interface to get connected to all of these various systems.
Do you have to log in to a lot of different systems? If you do, odds are that you have to use a variety of methods. You probably have some systems that require ssh and others that only support rdesktop. For some you may have to use vnc. Some may only support telnet. Connection Manager allows you to pre-configure all this, and use a single consistant interface to get connected to all of these various systems.
To install from the source distibution type (you probably will have to be root):
make install
To make rpms for rpm-based ditros type:
make rpm
Main features:
- Command Line Interface - Connection Manager will have a command line interface that allows for easy initiation of any connection. Some users, especially system administrators, will prefer this method of interaction
- Qt/KDE interface - Connection Manager will have a full featured graphical interface based on the Qt and KDE widgets. This interface will allow a user to manage their own connections, as well as maintain all of the various configuration files. You shouldnt have to use a text editor to edit configuration files unless you really want to
- Documentation - Connection Manager will be completely documented, including man pages, a user reference guide, and an administrator reference guide.
- Packaging - every effort will be made to make Connection Manager easy to install. Packages will be provided for a variety of platforms.
- Internationalization - Connection Manager will be designed and built so that it will be easy to add support for different languages.

Gtk2::Ex::MindMapView::Connection is a Perl module to draw connections between view items.

HEIRARCHY

Glib::Object
+----Gtk2::Object
+----Gnome2::Canvas::Item
+----Gnome2::Canvas::Shape
+----Gnome2::Canvas::Bpath
+----Gtk2::Ex::MindMapView::Connection

SYNOPSIS

use Gtk2::Ex::MindMapView::Connection;

This module is internal to Gtk2::Ex::MindMapView. Connections are instantiated by Gtk2::Ex::MindMapView. This module is responsible for drawing the connecting lines between Gtk2::Ex::MindMapView::Items onto the canvas.

The Gtk2::Ex::MindMapView::Connection is an observer. It registers with the view items so that it may be notified when a view items state changes.

INTERFACE

Properties

arrows (string : readable / writable)

Indicates whether arrows should be drawn. Possible values are: none, one-way, and two-way.

predecessor_item (Gtk2::Ex::MindMapView::Item : readable / writable)

The item at which this connection starts.

item (Gtk2::Ex::MindMapView::Item : readable / writable)

The item at which this connection ends.

Methods

INIT_INSTANCE

This subroutine is called by Glib::Object::Subclass as the object is being instantiated. You should not call this subroutine directly. Leave it alone.

SET_PROPERTY

This subroutine is called by Glib::Object::Subclass when a property is being set. You should not call this subroutine directly. Leave it alone. Instead call the set method to assign values to properties.

connect

Connect the Gtk2::Ex::MindMapView::Connection to the items it observes.

disconnect

Disconnect the Gtk2::Ex::MindMapView::Connection from the items it observes.

Check Your Network Address Translator for Compatibility with Peer-to-Peer Protocols.
If you are accessing the Internet from behind a Network Address Translator (NAT) of some kind, I would appreciate your help in surveying the behavior of different NATs, in terms of how and whether they support a certain technique for enabling peer-to-peer communication between NATted hosts (particularly when both endpoints are behind NATs). Down, you can understand what NAT is.
Suppose there are three communicating hosts: A, B, and C. Host A is a "well-known" Internet server with a permanent IP address, which acts as an "introducer" for the other two nodes. (For example, Host A might be a well-known ultrapeer or a game catalog server of some kind.) Host B, using Host As "introduction" services, would like to establish a direct peer-to-peer connection with host C. Both B and C, however, are behind (probably different) network address/port translators, and neither of them has exclusive use of any public IP address.
To initiate a peer-to-peer connection with host C, host B first sends A a message requesting an "introduction" to host C. A sends B a reply message containing Cs IP address and UDP port number as reported by host C, in addition to Cs IP address and UDP port number as observed by A. (If C is behind a NAT, then these two address/port combinations will be different.) At the same time, host A sends host C a message containing Bs IP address and UDP port numbers - again, both the ones reported by B and the ones observed by A, which will be different if B is behind a NAT.
Now B and C each know that they want to initiate a connection with each other, and they know each others public (NATted) as well as original IP addresses and UDP port numbers. Both B and C now start attempting to send UDP messages directly to each other, at each of the available addresses. If B and C happen to be behind the same NAT, then they will be able to communicate with each other directly using their "originally reported" IP addresses and UDP port numbers.
In the more common case where B and C are behind different NATs, the "originally reported" addresses will be useless because they will both be private IP addresses in different addressing domains. Instead, the IP address/UDP port combinations observed by A can be used in this case to establish direct communication. Although Bs NAT will initially filter out any UDP packets arriving from Cs public (NATted) UDP port directed at Bs public port, the first UDP message B sends to C will cause Bs NAT to open up a new UDP session keyed on Cs public port, allowing future incoming traffic from C to pass through the NAT to B. Similarly, the first few messages from B to C may be filtered out by Cs NAT, but will be able to start passing through the firewall as soon as Cs first message to B causes Cs NAT to open up a new session. In this way, each NAT is tricked into thinking that its respective internal host is the "initiator" of this new session, when in fact the session is fully symmetrical and was initiated (with As help) simultaneously in each direction.
Required NAT Behavior
There is one important requirement that the NATs must satisfy in order for this technique to work: the NATs must be designed so that they assign only one (public IP address, public UDP port) pair to each (internal IP address, internal UDP port) combination, rather than allocating and assigning a new public UDP port for each new UDP session. Recall that a "session" in Internet terminology is defined by the IP addresses and port numbers of both communicating endpoints, so host Bs communication with host A is considered to be one session while host Bs communication with host C is a different session. If Bs NAT, for example, assigns one public UDP port for Bs communication with A, and then assigns B a different public UDP port for the new session B tries to open up with C, then the above technique for peer-to-peer communication will not work because Cs messages to B will be directed to the wrong UDP port.
RFC 3022 explicitly allows and suggests that NATs behave in the former, "desirable" fashion, by maintaining a single (public IP, public port) mapping for a given (internal IP, internal port) combination independent of the number of active sessions involving this mapping. This behavior is not only good for compatibility with UDP applications, but it also helps to conserve the NATs scarce pool of public port numbers. Maintaining a consistent public port mapping does not adversely affect security in any way, either, because incoming traffic can still be filtered on a per-session basis regardless of how addresses are translated. There in fact appears to be no good reason not to implement the desirable behavior in a NAT, except perhaps for the implementation simplicity of naively allocating a new public port for every new session. Unfortunately, RFC 3022 does not require NATs to implement the desirable behavior, which has led me to wonder just how many real NATs actually do, and hence this page.
What NAT Check Does
The program natcheck.c is basically just a program that "pings" a well-known UDP port at two different servers that are publically accessible on the Internet. Both of these servers run the program natserver.c, with the command-line arguments "1" and "2" respectively. In addition, there a third "conspiring" server runs natserver with the command-line argument "3". Whenever each of the first two servers receives a UDP request, it not only sends a reply directly to the sender of that request, but also sends a message to the third server, which in turn "bounces" the reply back to the original client. The effect is that the client will receive not only solicited "ping" replies from the server the request was directed to, but also "unsolicited" replies from the third server.
To determine if the network address translator in use is implementing the desirable behavior of maintaining a single (public IP address, public port) mapping for a given (client IP address, client port), the client program natcheck.c basically just initiates a sequence of simultaneous pings to the first two servers (in case some of the requests or replies are lost in transit) and checks that the clients address and UDP port as reported by both servers is the same. If the NAT naively allocates a new public port for each new session, then the source port as reported by the two servers will be different, and its time to upgrade your NAT.
The replies echoed from the third server are used only to check whether the NAT properly filters out unsolicited incoming traffic on a per-session basis. Since the client never sends any messages to the third server, if the NAT is properly implementing firewall functionality, the client should never see the third servers echoed replies even after opening up active communication sessions with the first two servers.
Enhancements:
- The NAT Check client no longer attempts to guess whether you have Basic NAT or Network Address/Port Translation (NAPT). It turns to be quite difficult to test for this property reliably, because many NAPTs attempt to bind a private UDP port to a public port with the same port number if that port number is available, causing NAT Check to falsely report Basic NAT. The only way to test for this property reliably would be to run NAT Check on at least two client machines simultaneously, and since this property isnt terribly important to P2P apps its just not worth the trouble.
- The NAT Check client now tests for one additional NAT feature, which I call loopback translation. If a NAT supports loopback translation, it means that a host on the private network behind the NAT can communicate with other hosts on the same private network using public (translated) port bindings assigned by the NAT. Most NATs probably do not support this feature yet, but it may become increasingly important in the future where P2P clients may be located behind a common ISP-deployed NAT as well as individual home NATs. More details on loopback translation will appear in the next version of my Internet-Draft, to be released soon.
- The NAT Check client program now has a command-line option, "-v", which turns on verbose messages during the test.

BioCluster is a peer-to-peer clustering platform for Asterisk, the open source PBX, which allows Asterisk to be used as a full carrier-grade telephony solution. This project is meant to be installed on several machines together with Asterisk, turning them into a VoIP cluster.

While the BioCluster peer-to-peer protocol was initially designed to cater to Asterisk-based clustering solutions, the BioCluster framework is capable of being extended to support various forms of normally unclustered devices or software packages.