CLIENT GAME BROADCAST MECHANISM CONFIGURATION ON THE ALIBABA SNOWCLOUD
Entertainment

CLIENT GAME BROADCAST MECHANISM CONFIGURATION ON THE ALIBABA SNOWCLOUD

snowcloud

Customer Requirements

When it comes to traditional client games, the architecture of the background server is typically quite intricate, and extensive communication over the network is required between snowcloud servers. When unicast communication is utilized, a server is required to be aware of the modifications that have been made to all other servers at any given moment. This reduces the overall elasticity of the design. Many client gaming servers continue to use UDP broadcast communication because it allows for flexible development and helps reduce the amount of host computing resources needed.

 

Basic Principles

L2 multicast and broadcast are not supported in the present classic network and VPC network environments of Alibaba Cloud. This is due to the fact that the underlying switches are L3 switches. You are able to use the unicast mode to simulate the multicast mode, which can help you meet the multicast and broadcast requirements of your clients.

 

Configuration Within The Microsoft Windows Environment

The server datapoint and the client udptomulti are the two components that make up the multicast utility in a Windows context. In order to send multicast packets, the server needs to be deployed on an ECS instance; on the other hand, the client needs to be installed on a snowcloud instance in order to receive multicast packets.

 

Installation

Utilizing the installation package, set up the Windows multicast agent on your computer. To install udptopoint-1.3.1.exe and udptomulti-1.1.1.exe, double-click their respective files. Install the server and the client by following the on-screen prompts. Their respective directories for the installation process are located in C:udptopoint and C:udptomulti.

 

Notes:

During the installation process, if the system determines that Winpcap has already been installed, you will have the option to either immediately cancel the installation or continue with the installation to overwrite the version that is currently installed.

If Winpcap is not already installed on your computer, clicking the Install button will do it.

 

Configuration

Setting up the Server’s Configuration

After successfully installing the multicast tool, execute the udptopoint.exe program. This will cause the multicast-to-unicast background service to begin running automatically. The next step is to go to Task Manager > Services in order to examine the present service’s operating state.

Using the configuration file entitled server cfg.json.txt, you are required to configure multicast groups on the server and add multicast members to the groups.

 

The Following Is A Description Of Each Parameter Found In The Configuration File:

  • Group IP is the multicast group’s corresponding IP address in snowcloud.
  • Group port is the multicast group port that starts the multicasting process on the server.
  • The server port is the communication port of the agent, and it is responsible for switching from the Multicast mode to the unicast mode.
  • Member array contains the IP addresses of the individuals who are part of the multicast group.
  • Send reload point cfg is a supplemental tool for the server that configures send reload point.
  • “Reload” and “list” are the only commands that can be executed at this time.
  • It is possible to reload the configuration file by using the reload command. After making changes to the configuration file, you should always run this command.
  • The list command is what’s used to display the information concerning the packets that the present agent system has either sent out or received.

 

Guidelines For Application:

  • At the terminal, you can either enter the reload or list command.
  • Setting up the Client Configuration

 

After the multicast tool has been installed properly, you will need to start the udptomulti.exe file in order to trigger the background program that converts multicast to unicast. The next step is to select Task Manager > Services, where you will be able to examine the current service’s operational state.

To configure the newly added multicast groups on the client, use the JSON array located in the client cfg.json.txt file that is located in the configuration directory.

 

Description:

  • server IP refers to the IP address of the source computer that is sending the multicast data.
  • server port refers to the port used for communication by the agent, specifically the unicast port.
  • group IP is the IP address of the multicast group, specifically the IP address of the multicast group whose behavior is going to be simulated once messages have been received.
  • group port is the application’s communication port; more specifically, it is the port of the multicast group that will need to be mimicked once the messages have been received.
  • send reload multi cfg is a tool that the client uses as an auxiliary function.
  • “reload” and “list” are the only commands that can be executed at this time.
  • It is possible to reload the configuration file by using the snowcloud reload command. After making changes to the configuration file, you should always run this command.
  • The list command is what’s used to display the information concerning the packets that the present agent system has either sent out or received.

 

Configuration In Linux Environment

Installation

The Linux multicast tool’s server and client components are combined into a single. RPM package for easy distribution. multicast use tool-1.0.1–1.x86 64. rpm is the name of the RPM package that is currently accessible (version 1.0.1).

To determine whether or not the RPM package was installed correctly. You can verify the installation status by using the command rpm-Q multicast use tool-1.0.3–1.el6.x86 64. After the RPM package has been successfully installed on the system. The server and client programs that make up the user-state multicast utility will be installed on the system automatically.

 

Configuration

Following a successful installation of the multicast tool, the client installation directory is located at /usr/local/bin, and the directory in which configuration files are stored is located at /etc/multicast/.

By entering the cd /usr/local/bin command, you will be able to reach the directory in which the client is kept.

The source /.bashrc command should be run.

 

Launching The Client And The Server In The Following Order:

  • Regarding the consumer: To manually start the client, execute the following command while logged in with root permissions: nohup multi admin -R > /dev/null &
  • With regard to the server: To begin the process of starting the server. Execute the following command while logged in as root: begin service on the multis monitored daemon

 

Put An End To The Client Or Server By Doing The Following:

  • To manually terminate the client, you must first discover the process’s PID using the ps aux|grep multi admin command and then terminate the process using the kill PID command.
  • Executing the service multis monitored stop command while logged in as root is required to terminate the server.
  • Make that everything is up and working by using the service multis monitor status.

 

Modifying The Server Configuration File For Specific Use Cases

Modify the server cfg.json.txt file located in the datapoint directory if you are using Windows. On a Linux system, edit the file located at /etc/multicast/server cfg.json.txt.

After you have finished making the changes, you need to use the reload tool. So that the changed configuration file may be loaded into the server software that is currently active:

  • Execute the following command on a Linux machine: server reload list and then type in the reload command.
  • In order to reload, you need to run the send reload point cfg command on Windows and then input the reload command.
  • If the message “connection rejected” appears, check to see if the datapoint service is functioning normally.

 

Adjust The Settings In The Client Configuration File

In order to demonstrate how to make changes to the client configuration snow cloud bachelor gulch file, the following will use snowcloud as an example. In order to customize the client configuration for Windows, edit the client cfg.json.txt file located in the datapoint directory. On a Linux system, edit the file located at /etc/multicast/client cfg.json.txt.

After you have finished making the changes, you need to use the reload tool so that the changed configuration file may be loaded into the server software that is currently active:

  • For Linux, enter the reload command after running the client reload list command, which may be found below.
  • To reload the configuration, open Windows Command Prompt and type send reload multi cfg followed by the reload command.
  • If the message “connection rejected” appears, check to see if the UDP multi-service is functioning normally.

 

Extra Notes Here And There

Caution: You need to make sure that the value of the Server port is the same on both the client and the server. Otherwise, there will be no possibility of receiving any packets.

The system generates log files. For Windows, the md cloud log.txt file will be generated in the C. Udptomulti directory and the server log.txt file will be generated in the C:udptopoint directory. On Linux, the client log.txt and server log.txt files that are located in the /etc/multicast/ directory will be created automatically.

You will be able to use the tool for packet capturing to test. The service once you have finished configuring the service. Wireshark is a program that is recommended for use on Windows systems. Whereas the tcpdump command is recommended for usage on Linux systems.

 

In The Event That There Is A Breakdown In Communication, Carry Out Troubleshooting By Performing The Following Steps:

  • On the server, you need to verify to see if the multicast packets are successfully transformed into unicast packets and then sent.
  • On the client, check to see if unicast packets are received in the correct manner and if the network connection is operating normally.
  • Verify that the client is capable of restoring multicast packets from unicast packets in the correct manner.

 

The Verification Of The Results

As a result of the transformation performed on the multicast tool, snowcloud instances running on the customer’s traditional network. Are now able to communicate with one another using the broadcast mode.

For more information, please visit sbxhrl.

Leave a Reply

Your email address will not be published.