Forums Archived

This forum has been archived. No new posts can be made and no new users can sign up. It remains here for reference only.

Find the new forums here

Instances using TCP+UDP duplicating UDP rules instead

  • 343 Views
  • Last Post 15 February 2021
  • Topic Is Solved
AbhorrentJoel posted this 05 February 2021

OS Name/Version: Ubuntu 20.04.2 LTS (fresh install since a few days)

Product Name/Version: AMP (apt version 2.1.0.2 - upgraded from 2.1) - NOTE: I am using Docker for instances, but it seems to occur regardless.

Problem Description: When creating a new instances, AMP appears to be duplicating UDP ports in the case where TCP+UDP is specified.

I have two instances created, for Minecraft and 7 Days to Die, and the port is duplicated - 4 bottom rules:

root@[redacted]:~# ampinstmgr dumpports amp
[Info] AMP Instance Manager v2.1.0.2 built 03/02/2021 00:33
[Info] Release spec: Release - built by CUBECODERS/buildbot on CCL-DEV
[Info] TCP/2223 (AMP:ADS01:FileManagerPlugin.SFTP.SFTPPortNumber)
[Info] UDP/12820 (AMP:ADS01:ADSModule.Network.MetricsServerPort)
[Info] TCP/2224 (AMP:Minecraft01:FileManagerPlugin.SFTP.SFTPPortNumber)
[Info] TCP/2225 (AMP:SevenDays01:FileManagerPlugin.SFTP.SFTPPortNumber)
[Info] TCP/8766 (AMP:SevenDays01:SevenDaysModule.Server.WebServicePort)
[Info] TCP/27016 (AMP:SevenDays01:SevenDaysModule.Server.TelnetPort)
[Info] UDP/25565 (AMP:Minecraft01:MinecraftModule.Minecraft.PortNumber)
[Info] UDP/25565 (AMP:Minecraft01:MinecraftModule.Minecraft.PortNumber)
[Info] UDP/27015 (AMP:SevenDays01:SevenDaysModule.Server.ServerPort)
[Info] UDP/27015 (AMP:SevenDays01:SevenDaysModule.Server.ServerPort)

For example, the output from the firewall for the 7 Days to Die instance:

root@[redacted]:~# ufw status numbered | grep SevenDays01
[ 8] 2225/tcp                   ALLOW IN    Anywhere                   # AMP:SevenDays01:FileManagerPlugin.SFTP.SFTPPortNumber
[ 9] 8766/tcp                   ALLOW IN    Anywhere                   # AMP:SevenDays01:SevenDaysModule.Server.WebServicePort
[10] 27016/tcp                  ALLOW IN    Anywhere                   # AMP:SevenDays01:SevenDaysModule.Server.TelnetPort
[11] 27015/udp                  ALLOW IN    Anywhere                   # AMP:SevenDays01:SevenDaysModule.Server.ServerPort
[22] 2225/tcp (v6)              ALLOW IN    Anywhere (v6)              # AMP:SevenDays01:FileManagerPlugin.SFTP.SFTPPortNumber
[23] 8766/tcp (v6)              ALLOW IN    Anywhere (v6)              # AMP:SevenDays01:SevenDaysModule.Server.WebServicePort
[24] 27016/tcp (v6)             ALLOW IN    Anywhere (v6)              # AMP:SevenDays01:SevenDaysModule.Server.TelnetPort
[25] 27015/udp (v6)             ALLOW IN    Anywhere (v6)              # AMP:SevenDays01:SevenDaysModule.Server.ServerPort

Obviously, this results in it being impossible to connect where TCP is required. I have a feeling that it worked in AMP v2.1, yet I cannot confirm.

Steps to reproduce:

  • Install AMP v2.1 (with Docker) on a fresh Ubuntu 20.04.2 LTS install
  • Upgrade to AMP v2.1.0.2
  • Create instances for games which use TCP+UDP (7 Days to Die, Minecraft, etc.)

Actions taken to resolve so far:

  • Forced an upgrade of AMP instances using no-cache option
  • Removed ampinstmgr apt package, cleaned apt cache, and reinstalled
  • Deleted and created new instances

amp linux ubuntu firewall
Order By: Standard | Newest | Votes
AbhorrentJoel posted this 11 February 2021

Fixed in v2.1.0.6. Mentioned here.

Painwithin posted this 15 February 2021

This issue still seems to be apparent in 2.1.0.6 mine was working fine until updating now its duplicating UDP on ports "mainly game server ports".

AbhorrentJoel posted this 15 February 2021

It was working fine for me after the update to 2.1.0.6. I am not sure if it is necessary to create new instances in order for this to work - I would have guessed not, but cannot confirm.

Just ensure you have updated ampinstmgr via your distro's package manager, and preferably update AMP instances using the nocache option:

ampinstmgr --nocache upgradeall

I am currently on the Nightly build due to fixes applied to the Generic module, but it is seemingly all working fine for me there.

Live Chat Register to post
Categories
Search
Popular Tags
Hot Topics
Close