[1.1.91] Invalid packet received from IP ADDR

[clincha]

I've recently deployed a Factorio server. When I connect to the server I can play for about 20 seconds to 2 minutes and then then the client disconnects. I couldn't see anything in the server logs until I enabled verbose logs then when the disconnect happened I saw this message repeating over and over again when the client was having issues:

Code: Select all

  48.515 Info UnparsedNetworkMessage.cpp:91: Invalid packet (type ClientToServerHeartbeat) received from IP ADDR:({10.1.2.103:46388}): unknown sender
  48.531 Info UnparsedNetworkMessage.cpp:91: Invalid packet (type ClientToServerHeartbeat) received from IP ADDR:({10.1.2.103:46388}): unknown sender
  48.565 Info UnparsedNetworkMessage.cpp:91: Invalid packet (type ClientToServerHeartbeat) received from IP ADDR:({10.1.2.103:46388}): unknown sender
  48.565 Info UnparsedNetworkMessage.cpp:91: Invalid packet (type ClientToServerHeartbeat) received from IP ADDR:({10.1.2.103:46388}): unknown sender
  48.581 Info UnparsedNetworkMessage.cpp:91: Invalid packet (type ClientToServerHeartbeat) received from IP ADDR:({10.1.2.103:46388}): unknown sender
  48.598 Info UnparsedNetworkMessage.cpp:91: Invalid packet (type ClientToServerHeartbeat) received from IP ADDR:({10.1.2.103:46388}): unknown sender
  48.615 Info UnparsedNetworkMessage.cpp:91: Invalid packet (type ClientToServerHeartbeat) received from IP ADDR:({10.1.2.103:46388}): unknown sender
  48.648 Info UnparsedNetworkMessage.cpp:91: Invalid packet (type ClientToServerHeartbeat) received from IP ADDR:({10.1.2.103:46388}): unknown sender
  48.648 Info UnparsedNetworkMessage.cpp:91: Invalid packet (type ClientToServerHeartbeat) received from IP ADDR:({10.1.2.103:46388}): unknown sender
  48.681 Info UnparsedNetworkMessage.cpp:91: Invalid packet (type ClientToServerHeartbeat) received from IP ADDR:({10.1.2.103:46388}): unknown sender
  48.681 Info UnparsedNetworkMessage.cpp:91: Invalid packet (type ClientToServerHeartbeat) received from IP ADDR:({10.1.2.103:46388}): unknown sender
  48.698 Info UnparsedNetworkMessage.cpp:91: Invalid packet (type ClientToServerHeartbeat) received from IP ADDR:({10.1.2.103:46388}): unknown sender
  48.731 Info UnparsedNetworkMessage.cpp:91: Invalid packet (type ClientToServerHeartbeat) received from IP ADDR:({10.1.2.103:46388}): unknown sender
  48.748 Info UnparsedNetworkMessage.cpp:91: Invalid packet (type ClientToServerHeartbeat) received from IP ADDR:({10.1.2.103:46388}): unknown sender
  48.748 Info UnparsedNetworkMessage.cpp:91: Invalid packet (type ClientToServerHeartbeat) received from IP ADDR:({10.1.2.103:46388}): unknown sender
  48.781 Info UnparsedNetworkMessage.cpp:91: Invalid packet (type ClientToServerHeartbeat) received from IP ADDR:({10.1.2.103:46388}): unknown sender
  48.798 Info UnparsedNetworkMessage.cpp:91: Invalid packet (type ClientToServerHeartbeat) received from IP ADDR:({10.1.2.103:46388}): unknown sender
  48.815 Info UnparsedNetworkMessage.cpp:91: Invalid packet (type ClientToServerHeartbeat) received from IP ADDR:({10.1.2.103:46388}): unknown sender
  48.815 Info UnparsedNetworkMessage.cpp:91: Invalid packet (type ClientToServerHeartbeat) received from IP ADDR:({10.1.2.103:46388}): unknown sender
  48.848 Info UnparsedNetworkMessage.cpp:91: Invalid packet (type ClientToServerHeartbeat) received from IP ADDR:({10.1.2.103:46388}): unknown sender
  48.848 Info UnparsedNetworkMessage.cpp:91: Invalid packet (type ClientToServerHeartbeat) received from IP ADDR:({10.1.2.103:46388}): unknown sender
  48.881 Info UnparsedNetworkMessage.cpp:91: Invalid packet (type ClientToServerHeartbeat) received from IP ADDR:({10.1.2.103:46388}): unknown sender
  48.881 Info UnparsedNetworkMessage.cpp:91: Invalid packet (type ClientToServerHeartbeat) received from IP ADDR:({10.1.2.103:46388}): unknown sender
  48.898 Info UnparsedNetworkMessage.cpp:91: Invalid packet (type ClientToServerHeartbeat) received from IP ADDR:({10.1.2.103:46388}): unknown sender
  48.915 Info UnparsedNetworkMessage.cpp:91: Invalid packet (type ClientToServerHeartbeat) received from IP ADDR:({10.1.2.103:46388}): unknown sender
  48.948 Info UnparsedNetworkMessage.cpp:91: Invalid packet (type ClientToServerHeartbeat) received from IP ADDR:({10.1.2.103:46388}): unknown sender
  48.965 Info UnparsedNetworkMessage.cpp:91: Invalid packet (type ClientToServerHeartbeat) received from IP ADDR:({10.1.2.103:46388}): unknown sender
  48.981 Info UnparsedNetworkMessage.cpp:91: Invalid packet (type ClientToServerHeartbeat) received from IP ADDR:({10.1.2.103:46388}): unknown sender
  48.998 Info UnparsedNetworkMessage.cpp:91: Invalid packet (type ClientToServerHeartbeat) received from IP ADDR:({10.1.2.103:46388}): unknown sender
  49.015 Info UnparsedNetworkMessage.cpp:91: Invalid packet (type ClientToServerHeartbeat) received from IP ADDR:({10.1.2.103:46388}): unknown sender

Bug first found in game version: Factorio 1.1.87 (build 61545, linux64, headless)
System info: CPU: AMD Ryzen 5 3600 6-Core Processor, 8 cores, RAM: 32447 MB

I've tried the following:
- Change the network interface that the traffic is coming in on
- Disable the firewall on the host
- Disable any firewall rules on the router (Ubiquity Dream Machine)
- Update the game
- Changed out the host
- wired the client (server is already on a wired connection)

Worth noting that the server is running in a Kubernetes cluster using the image clincha/factorio on Docker Hub. I was previously using the image from factoriotools/factorio-docker but I needed to enable verbose logging so I forked it and modified it. I'm hitting the issue in both images.

I'm stumped at this point and not really sure how to continue debugging. Does anyone have any suggestions for me to try out?

The server is open at clinch-home.com:34197 (185.23.254.226:34197) if you want to give it a test yourself.

Logs for the server and the client are attached to the post.

factorio-server.log

Server log file

(195.03 KiB) Downloaded 23 times

factorio-current.log

Client log file

(9.68 KiB) Downloaded 22 times

iperf-results.txt

iperf results

(1.23 KiB) Downloaded 21 times

Thanks in advance,
clincha

[clincha]

I've got a packet capture for the pod that was experiencing the issue. I'm not sure what normal traffic is supposed to look like so I'm struggling to read it. If anyone is able to see an issue with the packets I would appreciate some guidance. Just needs Wireshark to open it.

https://drive.google.com/file/d/1RZRBI5 ... drive_link

Joined: 16:09:42
Error: 16:10:08
Error end: 16:10:29

I've noticed is that the packet length drops from 14 bytes to 10 just as the issue starts happening. I wonder if the packet is being chopped off at some point. There is also some ICMP packets just before the error so that could be interfering

Thanks in advance,
clincha