Free ares p2p software for linux

c-ares project is a C library that resolves names asynchronously.
Enhancements:
- ares_save_options, ares_destroy_options, ares_process_fd, and ares_parse_ns_reply were added.
- The transaction IDs were made "secure".
- A few parsing issues and minor bugs were fixed.

NapShare project is a fully automated, multi network P2P client made to run 24/7 unattended.

Searching and automatic downloading happen without any user intervention. You supply a list of keywords and filters for the file types you want and it downloads overnight, automatically, also sharing whatever it gets. The automated "brain" tries to simulate searching and downloading like a human would.

Take a nap while it does the work!

Its a complete P2P client, with all the features. It connects to the Key Network and also interoperates with MUTE Network clients. It protects privacy by using a Virtual IP address and other software features.

Written using wxWindows/wxWidgets for multi-platform versions.

iptables-p2p is an iptables match module capable of matching various peer-to-peer networks. It works by examining the application-layer protocol.
This is how you install iptables-p2p:
1. Copy the iptables headers to an appropriate place (/usr/include) or install the iptables-dev package if your distro has one. (see Installing iptables headers)
2. Run make in order to compile iptables-p2p.
3. Insert the kernel/ipt_p2p.o module directly using insmod or copy it into your modules directory. If you are using a 2.6 kernel, the module is named kernel/ipt_p2p.ko.
4. Insert the iptables library libipt_p2p.so into the iptables lib directory (usually /lib/iptables).
Enhancements:
- 0.3.0a
- Fixed iptables-save/iptables-restore
- Fixed module versioning support

Hybrid Share is a User Friendly Application for Linux, Mac and Windows users, that allow you to Share file (and Talk) instantly with your friends...

What is Hybrid Share ?

Hybrid Share is a simple (User Friendly) Mono C#/Gtk# Application that allow Mac, Windows and Linux Users To Share Files. The Application is extensible via Plugins, so you can Talk with connected people, check your mailbox or other things that plugins could do.

What do you use if you have to share files with your friends ?

E-Mail or Instant Messaging are the first possible solution, but the E-Mail Size block and the slowing of the IM make this channels bad to share files. The NFS (Network File System) or other system like this, works only between similar system or are a little bit difficoult to configure, the same for ftp server.

So The Solution is Hybrid Share that is Portable and Easy to Use, It isnt the Best Application in The World, but it does a useful work.

What is the Difference with a Normal P2P ?

Hybrid Share has a core of P2P but is more like a traditional IM (Instant Messenger), like GTalk, MSN, Gaim, Adium and so on.... No Network Configuration is needed, Youve only to add your "buddies" (like an IM) and Drag File Into their folders...

Cutlass is a cross-platform system for secure peer to peer communication, oriented towards small groups. It provides IM and file transfer. A major design goal is to be easy to use, even by non-security conscious users. The Cutlass main goals are :

Easy enough to use for broad adoption
Coded using widely supported APIs, to be multiplatform
Secure by default, using encrypted channels
Useful for everyday Internet functionality. Transmit sound, files, text.
P2P as independent of central servers/failure points as possible.
Extendable (both in functionality and paranoia)
Not dependent on central servers

Cutlass is currently under development. The current version provides message, file and voice transmission, but grouping, directory services and connection forwarding are not yet implemented.

Cutlass was originally named DEFJAM (Distributed, Encrypted File Journalling And Messaging), and was the subject of a presentation at Notacon.

MooDriver is a library providing a C++ museekd "driver" class (Moo::Driver) MooDriver makes it easy to write museekd clients without having to deal with the museekd daemon and its protocol directly. museekd is a daemon which acts as a gateway to the SoulSeek P2P network.

AMI provides a full P2P network.

AMI is a universal P2P framework written in Java and XML. It allows people to communicate using plug-in AMI protocols. It can support any P2P protocol.

JXTA technology is a set of open protocols that allow any connected device on the network ranging from cell phones and wireless PDAs to PCs and servers to communicate and collaborate in a P2P manner.
JXTA peers create a virtual network where any peer can interact with other peers and resources directly even when some of the peers and resources are behind firewalls and NATs or are on different network transports.
The project goals are interoperability across different peer-to-peer systems and communities, multiple/diverse languages, systems, platform independence and networks, and ubiquity: every device with a digital heartbeat.
Main features:
Discovery:
- Pipes. An application is able to search for a named pipes created by other Peers.
- Groups. An application is able to discover a JXTA group and join it.
- Contents. Applications are able to discover application specific contents.
Create:
- Pipes. An application is able to create pipes - both point-to-point and propagate pipes.
- Groups. An application is able to create peer groups to limit the scope of discovery.
- Contents. Application specific contents.
Join Groups An application is able to join a given group as per JXTA spec.
Communicate An application is able to communicate with other JXTA users through JXTA pipes (unicast, propagate)
- Listed below are a few of the critical constraints imposed by cell phones and like devices. JXTA-J2ME is
- designed to provide P2P functionality within these limitations. Next generation devices may have a
- lesser constraints than the one currently-available.
- 50k MIDlet size Current cell phones have a total limit of about 123K for storing all MIDlet suites. In addition, Motorola phones currently limit each MIDlet to be no more than 50K and NTT DoCoMo phones limit MIDlets to 30K.
- Persistent storage on cell phones can be as little as 8K which is shared by all the MIDlets.
- Runtime heap is of the order of 32K - 64K
- Bandwidth is very limited and latency is high
- CPU power is very limited - around 20MHz.
- Battery life is very critical.
- Limited libraries MIDP-2.0
Enhancements:
- Backports of a number of bugfixes from JXTA JSE.
- This release no longer requires a persistent store for configuration files.