P2P Module
Diarkis P2P enables direct client-to-client communication using NAT traversal and UDP hole punching, with server-relay fallback for seamless, low-latency data exchange.
Last updated
Was this helpful?
Diarkis P2P enables direct client-to-client communication using NAT traversal and UDP hole punching, with server-relay fallback for seamless, low-latency data exchange.
Last updated
Was this helpful?
Diarkis P2P enables direct communication between user devices without using a server as an intermediary.
The Diarkis server cluster functions as a client discovery point by utilizing NAT traversal technology.
In peer-to-peer communication, the server does not intervene for each packet exchange, allowing client devices to minimize network latency.
Diarkis P2P supports only the UDP network protocol and features a proprietary implementation of RUDP (Reliable UDP) to ensure packet delivery and order.
All packets exchanged between connected devices are encrypted, with encryption keys unique to the connection between the connected devices, ensuring secure communication.
Peer-to-peer communication requires two steps. First, clients exchange their addresses and perform . Once hole punching is successful, clients can send and receive packets directly.
In Diarkis P2P, the client SDK includes a hole punching feature, also known as NAT traversal. While NAT traversal is a common technology used in game console systems and many other networked applications, a key feature of Diarkis P2P is its ability to establish connectivity even with devices connected to Symmetric Cone-type routers, which typically cannot be reached using standard hole punching methods—though it is not guaranteed, Diarkis P2P increases the chances of successful communication.
Full
○
○
Restricted
○
○
Port Restricted
○
○
Symmetric
✖︎
△
Diarkis P2P is designed with a hybrid communication architecture that enables client devices to maintain a persistent connection to the Diarkis server cluster while simultaneously attempting to establish direct peer-to-peer (P2P) communication.
If a P2P connection cannot be established—due to NAT restrictions, firewall policies, or symmetric NAT configurations—Diarkis automatically triggers a fallback to server-relay mode, utilizing its built-in TURN-like functionality. This ensures uninterrupted, bidirectional packet delivery between clients, regardless of network topology.
By preserving both server and peer connectivity, Diarkis P2P guarantees resilient communication continuity, supports dynamic fallback routing, and maintains session integrity across varied client environments without manual intervention or custom NAT traversal logic.