P2P Module

Overview

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.

How It Works

Peer-to-peer communication requires two steps. First, clients exchange their addresses and perform hole punching. Once hole punching is successful, clients can send and receive packets directly.

NAT Types

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.

NAT Type	Other Solutions	Diarkis
Full	○	○
Restricted	○	○
Port Restricted	○	○
Symmetric	✖︎	△

Fallback to Server Relay

The unique architecture of Diarkis P2P allows client devices to maintain a connection with the Diarkis server cluster. This ensures that even if a peer-to-peer connection cannot be established, communication can fall back from peer-to-peer to server relay, allowing all users to continue communication regardless of their network configuration.