Linux dedicated regular LAN client timeout

[janzend]

I just put my home server back up and have been suffering form regular client timeouts since start - I'm unable to playthrough a clear quest without having issues, and then unable to complete them.

On disconnect the log displays something like this

2023-01-13T14:58:13 2584.393 INF Entity zombieArlene 1015 killed
2023-01-13T14:58:26 2597.097 INF [Steamworks.NET] NET: Connection closed: 12361197962439196
2023-01-13T14:58:26 2597.102 INF [NET] PlayerDisconnected EntityID=171, PltfmId='Steam_12361197962439196', CrossId='EOS_00021698ca123a58849a3817849c69e9', OwnerID='Steam_12361197962439196', PlayerName='PLAYER'
2023-01-13T14:58:26 2597.102 INF DynamicMusic: 171 successfully removed from Bloodmoon state cache
2023-01-13T14:58:26 2597.102 WRN Client disconnected from dy mesh: Id: 171 Total: 1
2023-01-13T14:58:26 2597.102 WRN Client disconnect complete for 171 Total: 0
2023-01-13T14:58:26 2597.102 INF Player set to offline: Steam_12361197962439196
2023-01-13T14:58:26 2597.104 INF Player disconnected: EntityID=171, PltfmId='Steam_12361197962439196', CrossId='EOS_00021698ca123a58849a3817849c69e9', OwnerID='Steam_12361197962439196', PlayerName='PLAYER'
2023-01-13T14:58:26 2597.106 INF GMSG: Player 'PLAYER' left the game
2023-01-13T14:58:26 2597.107 INF Exited thread NCSteam_Reader_Steam_12361197962439196_0
2023-01-13T14:58:26 2597.107 INF Exited thread NCSteam_Reader_Steam_12361197962439196_1
2023-01-13T14:58:26 2597.107 INF Exited thread NCSteam_Writer_Steam_12361197962439196_0
2023-01-13T14:58:26 2597.107 INF Exited thread NCSteam_Writer_Steam_12361197962439196_1
2023-01-13T14:58:26 2597.322 INF [Steamworks.NET] NET: Dropping client: 12361197962439196
2023-01-13T14:58:30 2601.128 INF [Steamworks.NET] NET: P2PSessionRequest from: 12361197962439196
2023-01-13T14:58:33 2604.778 INF Clearing all pools
2023-01-13T14:58:43 2614.034 INF Time: 42.51m FPS: 20.17 Heap: 2462.6MB Max: 2480.0MB Chunks: 359 CGO: 0 Ply: 0 Zom: 0 Ent: 0 (38) Items: 0 CO: 0 RSS: 3593.6MB
2023-01-13T14:58:46 2617.115 INF [Steamworks.NET] NET: Connection closed: 12361197962439196
2023-01-13T14:58:59 2630.395 INF [Steamworks.NET] NET: P2PSessionRequest from: 12361197962439196




I notice during play when zombies cease animation on kill and containers become unresponsive. I'm able to immediately reconnect - I haven't been able to get another player logged on remotely yet to see if they have the same experience.

I toyed with disabling combinations of LiteNetLib and SteamNetworking, and in some cases I get intermittent inability to connect, an error about being unable to initialize the servername or something similar, and removing the EOS line from platform.cfg

Does anyone have some additional threads I can pull?

 

[SylenThunder]

More information is needed.

What ports have you forwarded, and with what protocols on each port?

Put the full log on pastebin and link it here. I'm really tempted to just delete posts where people don't read instructions, and just post a wall of log.

Since this is a home server, your log should provide most of the information I need about the setup, but noting the process you used to set up the server may be helpful.

 

[janzend]

I have TCP/UDP 26900:26900 from internet to client

https://pastebin.com/Y10sHPX0 - I was under the impression that a wall of text from the log what less helpful than just the disconnect events, but ill keep that in mind for future issues. 

serverconfig.xml - https://pastebin.com/AkbwBEGw

I followed the following guide for server config with very little deviation, I had to go out and find some packages for running the application that were probably assumed in the config. https://steamcommunity.com/sharedfiles/filedetails/?l=german&id=360404397

I'm currently getting disconnected by the server, no longer a timeout issue. I notice client response issues like chests being unavailable or zombie pathing on their route after they die, then get a message that the server closed the connection. Happens around every 20 minutes or so to my client on lan, and internet clients as well. We are not affected at the same time

I'm running 

Intel(R) Xeon(R) CPU E5-2609 v3 @ 1.90GHz
16GB memory

 Ubuntu 22.04.1 LTS
 

Thanks for the review

 

[SylenThunder]

I have TCP/UDP 26900:26900 from internet to client

This is a big issue. You need TCP 26900, and UDP 26900-26903.

A couple of notes.  Your loot abundance of 125% doesn't really do anything. This is on numbered stacks, and you cannot have a quarter of an item. It's essentially the same as 100%. You'll want to stick to values of 100 here.
Landclaimsize needs to be an odd number. The default is 41. You have 40, and that may cause some issues. Remember, it's a cube with the LCB as the center block. So the default 41 is the LCB plus 20 blocks out from it in each direction. Keep that in mind when setting the value.

Other than that, it looks solid.

 

[janzend]

Thanks a lot, I only had 26900 previously while running on a windows VM, but I don't think that explains the disconnect with LAN clients. Is there any behavior being logged around the disconnects that may indicate a problem with anticheat or the network protocols. I'm not seeing any errors on the NIC and local connection is consistent, so I dont think theres an issue with the connection failing causing disconnect, but that the server is taking some action to remove clients. 

 

[SylenThunder]

Thanks a lot, I only had 26900 previously while running on a windows VM, but I don't think that explains the disconnect with LAN clients. Is there any behavior being logged around the disconnects that may indicate a problem with anticheat or the network protocols. I'm not seeing any errors on the NIC and local connection is consistent, so I dont think theres an issue with the connection failing causing disconnect, but that the server is taking some action to remove clients. 

The client gets the initial connection through 26900, however the primary traffic through LiteNetLib is handled by another port. So basically, you are connecting initially using Steam. However, when it passes to the optimized protocol that is closed and you get the disconnect. 

Also I missed this in the first pass, UNET hasn't existed for a while now. You can remove that from the config as it doesn't do anything. Just leave SteamNetworking disabled and open the ports. Or don't open the ports, and enable SteamNetworking. Though the latter will add a bit of latency to your connections.