Open WrightBlue opened 4 years ago
I've connected TS3j to a 3.12.1 on Linux
server without issue; that server is watchtower'd and auto-updates on Docker. I'm wondering if there is a compatibility issue here. Is the behavior any different if you don't set a client version string? To start with, I figure we can begin by ruling out any version-specific behavior.
If I connect to an empty server in version 3.12.1 on Linux everything works, and if I connect to ts3.black (200+ users online) I get this error.
Given the user count, this seems a lot like a similar problem I found with compression in #12. Maybe the cryptography routines suffer from similar "large" packet bugs? Looking at your logs more closely, your packet ID's jump by 3 ID's or more semi-regularly... that's really odd. Granted, you could be dealing with out-of-order delivery and/or packet loss, but I'm seeing:
208 received
(209, 210, 211 missed)
212, 213 received
(214, 215 missed)
216, 217 received
(218, 219, 220 missed)
221 received
(222, 223 missed)
224, 225 received
(226 missed)
227, 228, 229, 230 received
(231, 232 missed)
233 received
(Did you remove those from your logs? If so, did those de-crypt OK?)
I'll have to take a deeper dive, specifically into the server you're on. When do the errors start? Is it at a specific point in the packet stream? Some of any "healthy" traffic you have would be helpful.
Tested on:
Code: