• Please make sure you are familiar with the forum rules. You can find them here: https://forums.tripwireinteractive.com/index.php?threads/forum-rules.2334636/

Server random disconnects from private dedicated linux server

jazztickets

Member
Oct 31, 2022
5
1
I've been hosting a private passworded linux server for Killing Floor 2 for 5+ years now. It runs on a Lenovo laptop using Debian stable. We usually play during the 2XP events and seasons, although we haven't played for about a year now. We decided to play this season and have run into a new issue where 1 or 2 players get disconnected randomly throughout the match. The disconnect doesn't happen immediately though, usually someone calls out a player disconnecting because from their perspective the game's still running, except the zeds are just frozen. In some cases everyone gets disconnected and the server decides to switch to a completely new map immediately. I run a Mumble server and other game servers with no problems at all.

It's pretty much a vanilla set up with no custom maps, server takeover is disabled, and web admin interface enabled. Ports 7777 and 27015 are forwarded to the server.
There are 3 of us, playing on Windows 10/11 and we're all on the same fiber ISP.

It usually happens at least once before wave 15 on Spillway, but we've had trouble on other maps like ZED landing and die sector.

Another player hosted a Windows dedicated server just to see and the problem did not occur there. I have tried using Arch Linux and a completely different laptop to host and the problem still happens on that setup.

Here's a log file from last night with IP addresses replaced for privacy. We played zed landing for about 25 waves with no problem, then switched to spillway where the problem occurred within 10 waves. I believe around line 13955 is where 2 players got disconnected. It then switched to steam fortress.

One player has the Armory Season Pass, which is the only thing I can think of being different.

Has anyone seen this issue?
 

Attachments

  • Launch.log.txt
    986 KB · Views: 6
Your most likely issue is these lines:

[2120.01] DevNet: NotifyAcceptingConnection: Server TheWorld accept
[2120.01] NetComeGo: Open TheWorld 20.8.95.63
[2120.01] DevNet: NotifyAcceptingConnection: Server TheWorld accept
[2120.01] NetComeGo: Open TheWorld 20.8.95.63
[2120.01] DevNet: NotifyAcceptingConnection: Server TheWorld accept
[2120.01] NetComeGo: Open TheWorld 20.8.95.63
[2120.04] DevNet: NotifyAcceptingConnection: Server TheWorld accept
[2120.04] NetComeGo: Open TheWorld 20.8.95.63
[2120.04] DevNet: NotifyAcceptingConnection: Server TheWorld accept
[2120.04] NetComeGo: Open TheWorld 20.8.95.63
[2120.08] DevNet: NotifyAcceptingConnection: Server TheWorld accept
[2120.08] NetComeGo: Open TheWorld 20.8.95.63
[2120.08] DevNet: NotifyAcceptingConnection: Server TheWorld accept
[2120.08] NetComeGo: Open TheWorld 20.8.95.63
[2120.11] DevNet: NotifyAcceptingConnection: Server TheWorld accept
[2120.11] NetComeGo: Open TheWorld 20.8.95.63
[2120.11] DevNet: NotifyAcceptingConnection: Server TheWorld accept
[2120.11] NetComeGo: Open TheWorld 20.8.95.63
[2120.14] DevNet: NotifyAcceptingConnection: Server TheWorld accept
[2120.14] NetComeGo: Open TheWorld 20.8.95.63
[2120.14] DevNet: NotifyAcceptingConnection: Server TheWorld accept
[2120.14] NetComeGo: Open TheWorld 20.8.95.63
[2120.18] DevNet: NotifyAcceptingConnection: Server TheWorld accept
[2120.18] NetComeGo: Open TheWorld 20.8.95.63
[2120.21] DevNet: NotifyAcceptingConnection: Server TheWorld accept
[2120.21] NetComeGo: Open TheWorld 20.8.95.63
[2120.21] DevNet: NotifyAcceptingConnection: Server TheWorld accept
[2120.21] NetComeGo: Open TheWorld 20.8.95.63
[2120.21] DevNet: NotifyAcceptingConnection: Server TheWorld accept

And then disconnects after a timeout.

These are signs of your server used in an amplified volumetric DDoS attack, this particular IP is a target.

This has nothing to do with Windows/Linux.

Check this thread and act accordingly.

 
  • Like
Reactions: jazztickets
Upvote 0
Interesting! For some reason I thought those IPs might be from tripwire/steam, but DDoS makes sense. Since it's a completely private server I can just use iptables to allow only the IPs I want. I'll have to test it out next season when we play again.

I really wish there was an option to disable advertising the server on the public server list...
 
Upvote 0
Interesting! For some reason I thought those IPs might be from tripwire/steam, but DDoS makes sense. Since it's a completely private server I can just use iptables to allow only the IPs I want. I'll have to test it out next season when we play again.

I really wish there was an option to disable advertising the server on the public server list...
There is, although it's not documented to the best of my knowledge.

Also, if you implement it, it will decrease the probability, but not eliminate the risk, as UE3 game ports are discoverable by a direct internet scan, as opposed to relying on Steam APIs.
 
Upvote 0