dswd
/
vpncloud
mirror of https://github.com/dswd/vpncloud.git
1
0
Fork 0
Code Issues Releases Wiki Activity

Spec update

This commit is contained in:
Dennis Schwerdel 2015-11-20 13:58:11 +01:00
parent d3bcfbec5e
commit 594841da9b
2 changed files with 10 additions and 7 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

15
ethcloud.md
View File

@ -43,6 +43,11 @@ MAC tables. All frames without a tag will be treated as having tag `0`.
The peer-to-peer protocol will cause nodes to exchange information about their The peer-to-peer protocol will cause nodes to exchange information about their
peers. For nodes behind a firewall or a NAT, this can function as hole-punching. peers. For nodes behind a firewall or a NAT, this can function as hole-punching.
Ethcloud should be able to scale to a few thousand nodes with reasonable
management traffic (below 10 KiB/s for 10.000 nodes). However, such huge
networks will cause a lot of traffic due to broadcasts. At this point, a routed
approach should be preferred.
## NETWORK PROTOCOL ## NETWORK PROTOCOL
@ -83,11 +88,11 @@ of the packet:
Nodes are expected to request the peer list from the initial nodes they are Nodes are expected to request the peer list from the initial nodes they are
connecting to. After that, they should periodically send their peer list to all connecting to. After that, they should periodically send their peer list to all
of their peers to spread this information and to avoid peer timeouts. of their peers to spread this information and to avoid peer timeouts.
To avoid the cubic growth of management traffic, nodes should select a subset of To avoid the cubic growth of management traffic, nodes should at a certain
peers and send them a subset of their peer information. A reasonable number network size start sending partial peer lists instead of the full list.
would be the square root of the number of peers. The subsets can be selected A reasonable number would be the square root of the number of peers.
using round robin (making sure all peers eventually receive all information) The subsets can be selected using round robin (making sure all peers eventually
or randomly. receive all information) or randomly.
Nodes should remove peers from their peer list after a certain period of Nodes should remove peers from their peer list after a certain period of
inactivity or when receiving a `Close` message. Before shutting down, nodes inactivity or when receiving a `Close` message. Before shutting down, nodes

2
src/main.rs
View File

@ -16,8 +16,6 @@ use docopt::Docopt;
use ethcloud::{Error, Token, EthCloud}; use ethcloud::{Error, Token, EthCloud};
//FIXME: Send peer list in several packets when too large. The current behaviour panics at about
// 10000 peers.
//TODO: Implement IPv6 //TODO: Implement IPv6
//TODO: Encryption //TODO: Encryption
//TODO: Call close //TODO: Call close