Primary Maintainer: Chandra Prakash ([email protected])
Secondary Maintainer: Niall Douglas ([email protected])
Reliable p2p network connections in Rust with NAT traversal. One of the most needed libraries for any server-less, decentralised project.
| Crate | Linux | Windows | OSX | Coverage | Issues |
|---|---|---|---|---|---|
 |
 |
 |
| API Documentation - master branch | SAFE Network System Documention | MaidSafe website | Safe Community site |
|---|
#Overview
![crusty] (https://github.com/maidsafe/crust/blob/master/img/crust-diagram_1024.png?raw=true)
This library will allow p2p networks to establish and maintain a number of connections in a group when informed by users of the library. As connections are made they are passed up and the user can select which connections to maintain or drop. The library has a bootstrap handler which will attempt to reconnect to any previous "direct connected" nodes.
TCP connections are always favoured as these will be by default direct connected (until tcp hole punching can be tested). TCP is also a known reliable protocol. Reliable UDP is the fallback protocol and very effective.
The library contains a beacon system for finding nodes on a local network, this will be extended using a gossip type protocol for multi hop discovery.
Encryption of all streams will also allow for better masking of such networks and add to security, this is done also considering the possibility of attack where adversaries can send data continually we must decrypt prior to handling (meaning we do the work). There are several methods to mitigate this, including alerting upper layers of such activity. The user of the library has the option to provide a blacklisting capability per session to disconnect such nodes 'en masse'.
_direct connected == Nodes we were previously connected to. TCP nodes or reliable UDP nodes that allow incoming connections (i.e. direct or full cone nat that has been hole punched). This library also supports fallback endpoints being passed at construction that will allow a fallback should nodes from previous sessions become unavailable.
##Nat traversal/Handling
Several methods are used for NAT traversal, UpNP, hole punching [See here for TCP NAT traversal] (http://www.cmlab.csie.ntu.edu.tw/~franklai/NATBT.pdf) and here for UCP/DHT NAT traversal etc. These methods will be added to by the community to allow a p2p network that cannot be easily blocked. By default this library spawns sockets randomly, enabling nodes to appear on several ports over time. This makes them very difficult to trace.
##Todo Items
- [#1132] (https://maidsafe.atlassian.net/browse/MAID-1132) Integrate UPnP
- [#1139] (https://maidsafe.atlassian.net/browse/MAID-1139) Remove Crust API’s start_listening2() and expose
get_own_endpoints() - [#1142] (https://maidsafe.atlassian.net/browse/MAID-1142) Add UTP protocol support to crust
- [#1136] (https://maidsafe.atlassian.net/browse/MAID-1136) Add a new event
NewBootstrapConnection - [#1140] (https://maidsafe.atlassian.net/browse/MAID-1140) Memory-mapped file I/O for bootstrap file
- Have ConnectionManager guarantee at most one connection between any two nodes
- Utp Networking
- Utp live port and backup random port selection
- Create send/rcv channel from routing to connections object
- Implement test for basic "hello world" two way communication
- Add connection established/lost messages to be passed to routing (via channel)
- Benchmark tx/rv number of packets
- Benchmark tx/rc Bytes per second
- NAT traversal See here for tcp NAT traversal
- Benchmark tx/rv number of packets
- Benchmark tx/rc Bytes per second
- Implement NAT hole punch (udp) for reliable udp
- Tcp hole punching as per paper
- Tracer tcp (TCP with magic in clear [unencrypted])
- Wireshark module for tracer TCP