recognize quiet disconnects

[klucky]

Hello!
Sometimes wow disconnects in some kind of quiet mode. You dont get the disconnect message and will be able to run arround in the world and see the mobs which where near you when the dc happend. Is there any pointer or method with which i can recognize this kind of disconnect?
Thx for your help!
MFG Klucky

[Robske]

I suppose you could force Wow to send a 'CMSG_PING' packet and wait for the 'SMSG_PONG', although I'm not sure how these actually behave.

Anyway, I don't think I ever experienced such a disconnect without 'malicious' code being ran. (bots/hacks) So you might want to review that.

[Cypher]

Somewhere in the CG_CClientConnection (or w/e it's called) class there's an "IsConnected" boolean. (Or rather, there used to be. Not sure if there still is.)

[klucky]

this kind of disconnects especially happen on private servers .

i guess the "force Wow to send a 'CMSG_PING' packet and wait for the 'SMSG_PONG'" thing could work ... i will try this out ...

i think the "IsConnected" boolean will be 1 on this kind of disconnect cause else there would be an real disconnect or am i wrong?

008CD4C0 ServerLink__CMD_GRUNT_CONN_PING
008CBE00 ServerLink__CMD_GRUNT_CONN_PONG

mhh and how do i send a focre ping with this?

[Robske]

Somewhere in the CG_CClientConnection (or w/e it's called) class there's an "IsConnected" boolean. (Or rather, there used to be. Not sure if there still is.)

That crossed my mind, but from his description it seems that Wow is unaware of the 'disconnected' state (as he stays in the game world). So I doubt CClientConnection::IsConnected would work.

this kind of disconnects especially happen on private servers .

i guess the "force Wow to send a 'CMSG_PING' packet and wait for the 'SMSG_PONG'" thing could work ... i will try this out ...

mhh and how do i send a focre ping with this?

Send the packet yourself? http://arcemu.org/wiki/index.php?title=CMSG_PING

[ramey]

There's a connectionStatus offset of the NetClient class, which returns the current connection state. You should be able to reverse it really easy once you find it. There is also a Disconnect VMT function, which then you can force Disconnect, which works fine when connected and it disconnects you.

I'm having some problems dealing with this 'quiet' disconnect too. The connectionStatus does change however and you can recognise if you're quietly disconnected by checking that and if you're in game.

I'm just having problems with calling Disconnect VMT function because it boots to a ****ed up login screen for me.

Let me know if you find anythingz.

To Robske ^: It actually is aware, at least in the connectionStatus.

[klucky]

Mhh if i can recognize this quiet disconnects with connectionStatus offset it would be fine for me because i would completly restart wow then anyway. But atm i cant find this "connectionStatus offset" for 3.3.5a in http://www.mmowned.com/forums/world-...mp-thread.html.
This are the only things with connection which i found:
00465320 ClientConnection___ClientConnection
00465450 ClientConnection___scalar_deleting_destructor_
006B18C0 ClientConnection__CharacterAbortLogout
004650E0 ClientConnection__ClientConnection
00464410 ClientConnection__HandleAddonInfo
00464640 ClientConnection__HandleAuthResponse
00464780 ClientConnection__HandleCharacterLoginFailed
00464C10 ClientConnection__HandleCharEnum
00464730 ClientConnection__HandleClientCacheVersion
00464A40 ClientConnection__SendCharEnumOpcode
00464AB0 ClientConnection__SendPlayerLoginOpcode

but i dont know if they are the right ones.

[BoogieManTM]

If you're in-process I would personally check the socket itself. There's a few ways to do this, one being calling select() on the socket, and seeing if you get a FD_CLOSE, another would be to call getpeername(), if all is well it will return 0, otherwise there is a problem.

Also in process you could just hook wow's recv() function and monitor how often it is called. you should be getting packets consistently and any 5-10 second delay is likely a serious problem.

[ramey]

Mhh if i can recognize this quiet disconnects with connectionStatus offset it would be fine for me because i would completly restart wow then anyway. But atm i cant find this "connectionStatus offset" for 3.3.5a in http://www.mmowned.com/forums/world-...mp-thread.html.
This are the only things with connection which i found:
00465320 ClientConnection___ClientConnection
00465450 ClientConnection___scalar_deleting_destructor_
006B18C0 ClientConnection__CharacterAbortLogout
004650E0 ClientConnection__ClientConnection
00464410 ClientConnection__HandleAddonInfo
00464640 ClientConnection__HandleAuthResponse
00464780 ClientConnection__HandleCharacterLoginFailed
00464C10 ClientConnection__HandleCharEnum
00464730 ClientConnection__HandleClientCacheVersion
00464A40 ClientConnection__SendCharEnumOpcode
00464AB0 ClientConnection__SendPlayerLoginOpcode

but i dont know if they are the right ones.

They're functions, not offsets to a structure. Put some effort in and you'll find it easily.

[ddebug]

If you're in-process I would personally check the socket itself. There's a few ways to do this, one being calling select() on the socket, and seeing if you get a FD_CLOSE, another would be to call getpeername(), if all is well it will return 0, otherwise there is a problem.

Also in process you could just hook wow's recv() function and monitor how often it is called. you should be getting packets consistently and any 5-10 second delay is likely a serious problem.

this. I was going to recommend the same thing.

Anyway, klucky, I know what you're saying. That "disconnect" that doesn't "disconnect" the client (you can still move around in world; but you can't talk/use spells/etc...) still closes the tcp connection, but doesn't, for some strange reason, tell the client the server "disconnected" them (doesn't push them to the log-in selection screen). This makes me believe that it MUST be a bug within the client, moreso than anything else [not checking the state of the connection or whatever]. Therefore, I don't believe you will be able to retrieve the "IsConnected" status like Cypher recommended.

I'd say do Boogie's thang.

[andy012345]

Client expects realm server to kick them to back to character list in an event of a server crash.

In the event of your net dieing you'll lose connection to the realm server (now bnet) which causes "You have been disconnected from server.".

Do boogie's thing.

[Cypher]

That crossed my mind, but from his description it seems that Wow is unaware of the 'disconnected' state (as he stays in the game world). So I doubt CClientConnection::IsConnected would work.



Send the packet yourself? http://arcemu.org/wiki/index.php?title=CMSG_PING

Good point, I didn't actually read the first post, lol.