AMP Release "Phobos" v2.6.2.6 Functionality Request After Update

[enix_lin]

This document is intended to serve as a basis for communication with the AMP software development team regarding issues encountered in a specific network environment.

Problem Description:

My server is configured with two network cards connected to two different routers to achieve traffic segregation.

• Network Configuration:

  • Network Card 1: IP address 192.168.1.152.

  • Network Card 2: IP address 192.168.2.152.

• Previous Operating Mode (Older Version):

  • In the older version of AMP, I was able to achieve traffic segregation with the following settings:

    • Game Instance: Server IP Address was set to 192.168.1.152.

    • Control Panel: Passthru IP Binding was set to 192.168.2.152.

  • Under this configuration, game and management traffic were properly segregated, and both could be successfully connected to from the external network.

  • It is important to note that, in this segregated state, when players used SFTP to transfer files, they utilized the bandwidth of 192.168.2.152, which did not impact the game running on 192.168.1.152, thus preventing lag and rollbacks.

• Current Issues (New Version):

  • After the AMP update, the previous Generic Config > Server IP Address option seems to be either missing or its behavior has changed.

  • In the new version, when I attempt to set Application IP Binding to 192.168.1.152, the server becomes inaccessible from the external network.

  • The only current workaround is to set Application IP Binding to 0.0.0.0, which allows the server to connect externally.

  • However, this 0.0.0.0 binding method disrupts my original traffic segregation setup.

Request:

My core request is: I hope the AMP software can restore the functionality of the older version, allowing users to bind different services (such as the game instance and control panel) to specific network card IPs (192.168.1.152 and 192.168.2.152) on the server, while ensuring these services remain accessible from the external network.

The current behavior of the Application IP Binding option in the new version, where it fails to work when set to a specific IP (192.168.1.152), may be a bug or a flaw in the configuration logic introduced after the software update.

Conclusion:

We have observed that the IP binding behavior in multi-NIC environments appears to have changed from the previous AMP version. When we attempt to precisely bind a service to a specific IP address, external connections are blocked. This represents a divergence from the functionality of the older version, which allowed for traffic segregation via specific IP addresses. We would appreciate it if the development team could investigate this issue and provide a solution that allows us to maintain the flexibility of network traffic segregation while ensuring all services can properly connect to the external network.