Servers going down one after another?

I’ve checked with other server owners and this is spamming out server console then the servers go down and there is nothing we can do to bring it back up without forcing it. Please note the NET_GetLong spams hundreds of times with different IPs which makes me think its some sort of a DoS attack against the server itself.


NET_GetLong:  Split packet from 210.53.164.166:65480 with invalid split size (nu
mber 0/ count 0) where size 0 is out of valid range [564 - 1248 ]
NET_GetLong:  Split packet from 179.214.138.14:65463 with invalid split size (nu
mber 0/ count 0) where size 0 is out of valid range [564 - 1248 ]
NET_GetLong:  Split packet from 145.133.18.123:65481 with invalid split size (nu
mber 0/ count 0) where size 0 is out of valid range [564 - 1248 ]
NET_GetLong:  Split packet from 75.89.149.13:65464 with invalid split size (numb
er 0/ count 0) where size 0 is out of valid range [564 - 1248 ]
NET_GetLong:  Split packet from 195.88.46.223:61671 with invalid split size (num
ber 0/ count 0) where size 0 is out of valid range [564 - 1248 ]

If this is happening to anyone else let me know.

Glad it’s not just me. My server just went offline aswell, it’s in a restart loop.

That’s my console log.
I’ll go ahead and send the debug.log to Valve.

Well I’ve been talking to NFO support and they said other customers are having a similar problem and they’re working on setting up filters against it.

Ask if they might publicize the list of IP addresses to allow other people to block the connections as-well, because I host off of my own linux box so I’ll have to block manually.

The IPs have most likely been spoofed so they have to wait for another attack to capture it properly.

They’re spamming you with these:
https://developer.valvesoftware.com/wiki/Server_queries#Source_Server
(split packets)
The attacks using this method that i’ve seen have only sent oob packets, which shouldn’t be split from client to server. I think i’ve mentioned this before, but SS3 apparently blocks this.