Game servers (lxc) cannot be listed and are unreachable for master servers

Mister J.

New Member
Oct 21, 2024
5
0
1
Hi all,

I successfully run 4 game servers (latest versions of Urban Terror, Unreal Tournament 2004, Xonotic & Warsow) that I can connect to with a client from the LAN and WAN by ip.

Since I changed server OS from ClearOS to initially NethServer 7, I am having problems getting listed.
Because someone advised me to solve this problem by simplifying my LAN setup (no double NAT), I changed to Proxmox and now I am running the game servers in Debian 12 based lxc containers (no firewall) with a dedicated OPNsense firewall box and a bridged router.

Old situation:
LAN (switch with clients) - Gateway server - (LAN) router & WiFi (WAN) - Internet

New situation:
LAN (switch with clients, Proxmox box & Access Point) - (LAN) OPNsense box (WAN) - router (bridged) - Internet

Because I do not have this 'in-game'- (see attachment) and online listing (see attachment) problem with UT2K4, I must assume that it's not something simple like a problem with port-forwarding, because those are identical.

But with Urban Terror, Xonotic & Warsow it's only possible to connect from the Internet by ip address and not with the 'in-game'- or online listings.
I already tried every trick in the book that I could find, but this doesn't work with these 3 games.
https://arena.sh (see attachment for Xonotic & -Warsow) and https://www.urbanterror.info (see attachment for UrT) also reports that these servers are unreachable for the master servers.

The problem I have with UT2K4 is that I can't figure out how to add my server to GameTracker.com (see attachment).
For unknown reasons it reports that one of the following criteria is true:
  • Server is not online
  • Entered the wrong Query Port
  • Server is firewalled
It seems that I can connect to the master servers, but they cannot connect to my server:
Code:
Log: MasterServerUplink: Resolved utmaster.openspy.net as 134.122.16.249
Log: MasterServerUplink: Connection to utmaster.openspy.net established.

UDP Ports:
7777 = Game port(n)+
7778 = Query-/Voice Chat port
7787 = Query port(n+10)
10777 = LAN Server port
28902 = Master Server port+
+ Default port (used on ClearOS)

Code:
[root@UT2K4 ~]# ss -tuln | grep -E '7777|7778|7787|10777|28902'
udp   UNCONN 0      0      192.168.100.142:7777       0.0.0.0:*
udp   UNCONN 0      0      192.168.100.142:7778       0.0.0.0:*
udp   UNCONN 0      0      192.168.100.142:7787       0.0.0.0:*+
udp   UNCONN 0      0      192.168.100.142:10777      0.0.0.0:*
udp   UNCONN 0      0      192.168.100.142:28902      0.0.0.0:*+
+ This port was not open by default.

Code:
[root@UT2K4 ~]# nmap -sU -p 7777,7778,7787,10777,28902 192.168.100.142
Starting Nmap 7.93 ( https://nmap.org ) at 2024-10-20 23:47 UTC
Nmap scan report for UT2K4.<domain>.nl (192.168.100.142)
Host is up.

PORT      STATE         SERVICE
7777/udp  open|filtered cbt
7778/udp  open|filtered interwise+
7787/udp  open|filtered popup-reminders
10777/udp open|filtered unknown
28902/udp open|filtered unknown+

Nmap done: 1 IP address (1 host up) scanned in 3.14 seconds
+ This port was not open by default.

Code:
[root@UT2K4 ~]# iptables -L -n
Chain INPUT (policy ACCEPT)
target     prot opt source               destination
ACCEPT     0    --  0.0.0.0/0            0.0.0.0/0            ctstate RELATED,ESTABLISHED+
ACCEPT     17   --  0.0.0.0/0            192.168.100.142      udp dpt:7777
ACCEPT     17   --  0.0.0.0/0            192.168.100.142      udp dpt:7778
ACCEPT     17   --  0.0.0.0/0            192.168.100.142      udp dpt:7787
ACCEPT     17   --  0.0.0.0/0            192.168.100.142      udp dpt:10777
ACCEPT     17   --  0.0.0.0/0            192.168.100.142      udp dpt:28902
DROP       0    --  0.0.0.0/0            0.0.0.0/0+

Chain FORWARD (policy ACCEPT)
target     prot opt source               destination
ACCEPT     17   --  192.168.100.142      0.0.0.0/0            udp dpt:7777
ACCEPT     17   --  192.168.100.142      0.0.0.0/0            udp dpt:7778+
ACCEPT     17   --  192.168.100.142      0.0.0.0/0            udp dpt:7787
ACCEPT     17   --  192.168.100.142      0.0.0.0/0            udp dpt:10777+
ACCEPT     17   --  192.168.100.142      0.0.0.0/0            udp dpt:28902

Chain OUTPUT (policy ACCEPT)
target     prot opt source               destination
+ This rule was not default.

When running these game servers in my old situation I did not have any of these problems.
Together with a friend of mine who has 35+ years of experience with Proxmox and OPNsense and myself having 20+ years of experience with hosting these game servers, we confirmed that all the server- and firewall settings are correct and should work.

Please advice,

Mister J.


My attempts to solve this on the OPNsense forum. >>
 

Attachments

  • arena.sh.jpg
    arena.sh.jpg
    49 KB · Views: 15
  • beta.openspy.net_en_server-list_ut2004.jpg
    beta.openspy.net_en_server-list_ut2004.jpg
    129.4 KB · Views: 13
  • GameTracker.jpg
    GameTracker.jpg
    213.8 KB · Views: 15
  • UrT.jpg
    UrT.jpg
    240.5 KB · Views: 13
  • UT2K4.jpg
    UT2K4.jpg
    416.7 KB · Views: 4
  • Portforward rules.jpg
    Portforward rules.jpg
    278.9 KB · Views: 3
  • WAN rules.jpg
    WAN rules.jpg
    217.9 KB · Views: 4
  • LAN rules.jpg
    LAN rules.jpg
    157.9 KB · Views: 5
  • Packet Capture.jpg
    Packet Capture.jpg
    127.7 KB · Views: 5
  • Automatically generated rules.jpg
    Automatically generated rules.jpg
    198.2 KB · Views: 4
Last edited:
The problems are still not solved and I would like some feedback to at least point me in the right direction before the end of the year.
 

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!