Skip to main content

SARD proxy requirements

Introduction article

Server requirements for the SARD proxy​

To support proxy work for up to 10000 CCU we require following configuration

  • Ubuntu 20.04
  • kernel 5.4.0-169-generic
  • Ram 16G
  • CPU 12( 3 socket 4 core)

Network setup​

note

Since we are not familiar with your particular network setup, this section outlines options we previously implemented for different game-titles. We are open to discuss tailor-made setup for your case

Basic scenario​

Firstly we will start with the basic scenario to provide a basic understanding of process running Basic scenario illustration In general process looks like

  1. Game Client sends a package to the game server, but SARD AC tracks it and routes to Proxy server instead
  2. There we change the source of the package to be the Proxy IP
  3. Data is sent to Game Server and it returns answer to SARD proxy
  4. Proxy changes the destination of the packet to the game client

This flow has an issue which may be crucial for live-ops of some games: Game server won't receive player's IP to address this we have solutions which will be described in next section

Using default gateway or policy based routing​

The problem of keeping player's IP address lies in inability to route outgoing traffic back to proxy, as a result game process wouldn't receive an answer from the expected source. Outgoing traffic problem illustration To address this issue we need to implement a solution for the data to be sent back to proxy. We propose one of the methods

  • Default gateway at game server level
  • Policy based routing at game server level or at the infrastructure level

Default gateway or pbr on game server level

Default gateway or pbr on infrastructure level