Unknown packets on 2015-10-29 #1049
Comments
|
I'm using the same client and we got ""massive"" random disconnections (30 ppl or so at the same time). Nevertheless, I dunno whether it is my hosting provider or my internet connection or a buggy OnTimer from custom script or the client itself. |
|
This could be due to some packet's we do not have yet. That is why this client is not yet marked as stable. |
|
As soon as I can isolate any factor, I will post it here. |
|
@RagnarokNova any input from your server on this? |
|
Console: http://i.imgur.com/qzoVTTg.png |
|
@admkakaroto could you monitor this and ask your users what they do, before they get kicked by the server? But I think we are on the right track already. |
Lemongrass3110
changed the title
|
@Lemongrass3110, I was talking to them, and no one knows for sure, the problem occurs in very different situations, one thing is quite certain, if the player is idle without performing any action, he has no problem with that. |
|
Could you uncomment this line, so that we at least get to know which data is sent: |
|
So far there are 6 possible causes, my players reported these situations: -- Disconnection while chatting. confirmed but unable to isolate any factor. I've got a myriad of screenshots, so far though I'm not posting them here to keep it readable. Unsupported packets (reason unknown): Invalid packet_len: Unknown packets (reason unknown): Other: (The player name was normal no weird characters or even spaces). |
|
Which clients do both of you use? |
|
I'm using: I will copy the packet_db for ver 54 I'm using. |
|
I use the standard package emulator, to the client 2015-10-29. Client 2015-10-29aRagexeRE or 2015-10-29aRagexe both with the same problem. |
|
@admkakaroto Have you received reports about disconnections while chatting, storing or selling using drag and drop method? |
|
@Darkelfen, yes, players have long claimed were talking and being disconnected, or are performing some instance or simply dropping items. |
|
I will update the information on the packets which caused disconnections. So far we have been monitoring the server for nearly 18 hours by now, and we got a myriad of disconnections. Isolated 1 factor. |
|
Spamming |
|
I have no problems with |
|
I've monitoring for nearly 48 hours by now, and I couldn't get a hold on 0x036b. Regarding the atcommand go, it was only caused in my PC w/win8.1; I've tried on a PC w/win-xp and I was unable to reproduce it. So maybe it is a problem related with win8 rather than the client itself. Regarding 1:1 whispers, I couldn't reproduce them, but I was disconnected while chatting and doing nothing else, so 1:1 whispers are triggering the disconnections but I couldn't isolate why or how yet. @secretdataz @admkakaroto guys, have you got any of these unsupported unknown packet issues? |
|
@Darkelfen, @Lemongrass3110, @secretdataz, any solution? |
|
I've monitored for nearly a week the unsupported/unknown packets errors in the console. As it's so time demanding, I've decided to stop monitoring. I got a massive amount of data which I'm unable to analyse nor isolate any factor causing the disconnections. In my post above I've updated the packets I was able to identify but 0x036b never appeared. |
|
having dc issue also using ragexe not ragexeRE |
|
[Warning]: clif_parse: Received unsupported packet (packet 0x5597, 42 bytes received), disconnecting session #11. |
|
|
[Warning]: clif_parse: Received unsupported packet (packet 0x04a1, 5 bytes received), disconnecting session #34. |
|
Please try to add those two commits to your server: What do these changes do? |
Lemongrass3110
changed the title
|
I compiled yet received these errors on the console: I'll try to do some tests. |
|
@admkakaroto Merge the updated test/issue1049 branch. It should compile now. |
|
This is the list of packet that occur for about 3-4 days in server. Can you check this out? |
|
"2015-10-29aRagexe" [Warning]: clif_parse: Received unsupported packet (packet 0x8480, 55 bytes received), disconnecting session #8. Example: |
|
I've started to monitor with the test commits added: @Badarosk0 I've tried to flood my chat and I couldn't replicate. As far as I know, chatting does cause disconnections but I don't know how. |
|
We added support for 2015-11-04 in 5e58149. You can grab the client from the 2015 Client Support topic. This will end up being an issue we can't resolve because it's specifically related to the October clients. |
|
2015-10-29 have this error |
|
Move to 2015-11-04, this issue can't be helped. |
|
With the new client players do not take more random dc, but when they talk very fast in general chat or be interacting with various NPC's by clicking one after the other they still take dc, see:
Client: 2015-11-04 |
|
Almost sounds like some integrated spam protection. |
|
I've also get a few disconnections with 2015-11-04 but considerably less than before. |
|
we should re-open this because the commit was reversed |
|
really |
|
There's no need. #1223 is open and is related to this. |
|
The issues are related. Both are at fault with the messaging system, now that we know what is causing the random crashes. Not just normal chat is at fault though which is why there are those random crashes though The packets above listed in this issue are just fine and serve no purpose into resolving this issue. It has been worked on and just needs testing now. It will be pushed to master soon! |
Hello good evening, the client 2015-10-29 is giving desconect the players randomly, but this only occurs if it is performing some task, whether walking, talking or anything like that, if the same stand there it does not take dc.
The text was updated successfully, but these errors were encountered: