Search Results for "peers"

...These protocols can run over a variety of transports such as TCP, UNIX sockets, and even WebSocket. This pattern is useful for solving producer/consumer problems, including load-balancing. Messages flow from the push side to the pull side. If multiple peers are connected, the pattern attempts to distribute fairly. nanomsg is a socket library that provides several common communication patterns. It aims to make the networking layer fast, scalable, and easy to use. Implemented in C, it works on a wide range of operating systems with no further dependencies. The communication patterns, also called "scalability protocols", are basic blocks for building distributed systems.

No port forwarding, DMZ, and others are required, Trate allows other applications - almost all applications(VNC,WinSCP,BitTorrent,Filezilla,ssh,Web/Ftp etc) - to auto-create dynamic connections between two peers behind two separate NATs and firewalls.

Allow peers behind NATs to establish real unproxied TCP streams. Like STUN but for TCP.

The Statistically Unique and Cryptographically Verifiable Protocol (SUCVp) is used by two IPv6 Peers that used SUCV addresses (a.k.a. Cryptographically Generated Address, CGA or Crypto-Based Address, CBA) to bootstrap an IPsec Security Association.

A daemon that runs as a non-privileged user, sending updates of server status to a set of peers, which can keep state with rrdtool databases. You can specify information elements such as uptime, network counters (pps/bps), diskIO, load, and more.

Yavipind is a secure tunnel aka 2 peers securely forward­ing packets toward each other.It is what most people calls a VPN (virtual private network). It forwards any kind ofpacket (IPv4, IPv6 or other) sent over the virtual network interface (e.g. t

iSSL is a minimalistic cryptographical API that uses the ciphers RSA and AES to establish SSL-alike, secure encrypted communications between two peers communicating through a network socket, including session key generation and public key exchange.

The use of NAT devices all over the Internet has made peer-to-peer exchanges unreliable. The rise of IPv6 should repair this, but it will still not be reliable until all peers have implemented IPv6. Such IPv6 implementation could be arranged on the fly with a tunnel mechanism that does not rely on router co-operation or manual configuration. This specification details such a method of embedding IPv6 into UDP and IPv4. It employs embedded Router Solicitation to configure the tunnel's public IPv6 address, and Neighbor Discovery to try to find the remote peer over more efficient IPv4 routes.