GDN

Introduction

The Game Delivery Network (GDN) provides a service that allows users to access your game servers or other services through Mudfish relay servers.

If users are unable to connect to your game server or other services smoothly due to network-related reasons, it provides the ability to bypass them through a mudfish relay server. You can configure GDN settings at the following link.

Follow along

In this section, we'll show you how to configure GDN and how to do it with an example.

  1. First of all, you need to know the IP (or domain name) and port number of the server you're running, which we'll assume is the destination below.

    • Server IP: 1.1.1.1 (IPv4 address)
    • Server Port: TCP 53

  2. Connect to https://mudfish.net/gdn/dashboard, enter the "Relay Server Group" menu, and create one relay server group.

    1. Click the "Create" button in the upper right corner.

    2. In the "Group Name" field, enter a suitable name. For this example we'll use the group name "ABCD" group name "ABCD".

    3. "Route List" is where you select routing paths. GDN currently supports two different relay server modes: basic and advanced.

      Here, click the "Add Route" button, and then click the "Add" button with the following information.

      • Routing Mode: Basic
      • Source: MD Europe (Chisinau - MivoCloud) - PBE
      • Stopover: Disabled
      • Hostname: test

      The Hostname information can be any name in non-duplicate domain format.

    4. Press the "Create" button to create the relay server group.

  3. Now enter the "Resources" menu and create 1 resource as shown below.

    1. Click the "Create" button in the top right corner.

    2. Enter the resource information as shown below. The resource name below can be anything you want.

      • Resource name: VWXYZ Resource
      • Host Name: VWXYZ
      • Protocol: TCP
      • Port: 5353
      • Relay Server Group: ABCD
      • Destination IP: 1.1.1.1
      • Destination Port: 53
      • Use Proxy Protocol: Off

    3. Create the resource via the "Save" button.

All settings are complete. The above settings should result in the following.

  • The Mudfish relay server "MD Europe (Chisinau - MivoCloud) - PBE" is listening on TCP 5353.

  • When connecting to that TCP 5353, the connection is proxied to 1.1.1.1:53.

  • The domain vwxyd.resource.mudgd.net is automatically registered. When doing a DNS lookup for that domain, the Public IP of the "MD Europe (Chisinau - MivoCloud) - PBE" relay server will be responded.

    What if a relay server group contains multiple relay servers?

    Depending on your relay server group settings, a single relay server group can contain multiple Mudfish relay server routes. In this case, IPs answered by the domain vwxyd.resource.mudgd.net will automatically be answered by a relay server that is closer to the user.

    For more information on which relay server is selected, see the appropriate section below.

  • The domain test.route.mudgd.net is automatically registered. When you do a DNS lookup for that domain, the Public IP of the "MD Europe (Chisinau - MivoCloud) - PBE" relay server will be responded.

With this configuration, you can make a DNS request with the dig command and receive the response as shown below.

$ dig @vwxyd.resource.mudgd.net -p 5353 www.google.com +tcp

Settings menu

Relay Server Group

This menu lists the set relay server groups and allows you to create them.

Creating

This menu is used to create a relay server group. You will enter the following information.

  • Group name

    Specify an alias to identify the relay server group.

  • Route list

Add Route

Used to add a route to the route list. The following submenus exist

  • Routing Mode

    Choose how you want to set up the route. There are 2 modes, basic and advanced.

    • Basic mode is a route through a single mudfish relay server.

    • Advanced mode is a route that goes through 2 mudfish relay servers.

  • Source

    Specifies the mudfish relay server corresponding to the origin.

  • Stopover

    If you want to specify a mudfish relay server to be used for a stopover, you can do so here. Only available when the routing mode is set to "Advanced".

  • Hostname

    If you want to specify a hostname for this group, you can do so here. This hostname is registered in DNS and can be reached by domain instead of IP.

    This is optional, so you don't need to enter it.

Resources

A list of currently set resources and a menu to create a resource.

Create

You can create a GDN resource through this menu. To create a resource, you need to enter the following information.

  • Resource name

    Specify an alias to identify the resource.

  • Host name

    (Optional) You can define a host name for the resource. This host name will be registered in DNS, and the IP for the domain will be selected from the relay servers in the relay server group selected below that are close to the physical location of the accessor.

  • Protocol

    Specifies the protocol that the resource will use. You can select TCP / UDP.

  • Port

    Specifies the connection port for the resource. Users will connect through this connection port.

  • Relay Server Group

    Specifies the mudfish relay server group. Users will connect through these relay servers, which will proxy to the destination server. You can select multiple relay servers and choose whether to connect to a single relay server or a chain of two relay servers.

  • Destination IP / Domain

    Enter the IP / domain of the destination. The Mudfish relay server will attempt to connect to this destination IP / domain. It is common to enter the IP / domain of the game server. The connection method depends on the protocol selection above.

  • Destination Port

    Enter the port of the destination to connect to.

  • Use Proxy Protocol

    Specifies whether to use the Proxy Protocol. When this feature is enabled, the Mudfish relay server uses the Proxy Protocol to connect to the destination server. If the resource protocol is TCP, it sends the Proxy Protocol v1 header; if it is UDP, it sends the Simple Proxy Protocol header.

Pricing

The GDN feature is only available to users on a pay-as-you-go plan. Please note the following restrictions

  • Not available for subscription users.

  • Not available to mudfish alias accounts.

Please note that the "Resource Usage" plus "Traffic Fee" below is the actual usage price.

Resource Usage Fee

The resource usage fee is 490 KRW per month per relay server and is charged on an hourly basis. This means that you will be charged approximately 0.68 KRW credits per hour.

For example, if you have a relay server group of 5 mudfish relay servers on a single resource, your monthly resource usage fee would be

  • Monthly resource fee = 490 KRW * 5 units = 2,450 KRW

Traffic usage fee

Currently, it is priced at 135 KRW per 1 GB. For detailed traffic pricing, please refer to Plans or Pricing documents.

However, you should be aware of the following.

  • Traffic usage is based on the mudfish relay server, i.e. if you RX/TX 1 GB of data, the mudfish relay server will use twice as much, 2 GB.

  • The advanced mode of the relay server will use twice the traffic of the basic mode. For example, if you use 2 GB of data when set to basic mode, you will use twice as much when set to advanced mode. Advanced mode, the Mudfish relay server will use twice as much data, 4 GB.

Mudcat →