Post-Reply Pre-Login Ping (0x25 Ping Spoof => 0 Ping)

[FrOzeN]

Don't remember, remembered this from over a year ago.
Probably from someone who didn't send the KeepAlive packet.

[Eric]

However it's very hard to make it do this accurately, and by causing your ping to exceed 59999ms you won't establish a connection to Battle.net.

Battle.net stores user ping values in a doubleword which can be any numerical value from 0 to 4294967295.  Perhaps you failed to send the version check data before the hash values changed?

[shout]

However it's very hard to make it do this accurately, and by causing your ping to exceed 59999ms you won't establish a connection to Battle.net.

Battle.net stores user ping values in a doubleword which can be any numerical value from 0 to 4294967295.  Perhaps you failed to send the version check data before the hash values changed?

There may be a limit on how long logons can take. So you would need to keep the other packets going while holding off the ping packet. </speculation>

[FrOzeN]

However it's very hard to make it do this accurately, and by causing your ping to exceed 59999ms you won't establish a connection to Battle.net.

Battle.net stores user ping values in a doubleword which can be any numerical value from 0 to 4294967295.  Perhaps you failed to send the version check data before the hash values changed?

I was lazy testing this, I've never done it properally by making the code pause.
With StealthBot on Windows 98SE. I'd click 'Connect', then wait..
Once it said "[TimeStamp] [BNET] Connected!" I would suddenly click the Title bar and hold the mouse down counting to 59 before releasing. When holding the title bar down it pauses everything the program does. Once i'd release it would continue connecting giving me pings around 57,000ms.. I tried getting it as close to 60,000ms. Anytime that I exceeded 60 seconds it wouldn't connect. And the closest I got was 57,### so I fiqured 60 seconds was the maximum.

Also another story I remember, I had StealthBot set to give me 0 ms. During the connection my computer was LAGGING EXTREMELY BAD and somehow it gave me 16ms, the best i've ever got properally is 156ms so don't know how it happened but it did.

[Joe[x86]]

Code Select Expand

Public Sub Send0x50(bZeroPing As Boolean)
    With Buffer
        .InsertDWORD 0                              '(DWORD)      Protocol ID (0)
        .InsertDWORD GetDWORD(modINI.GetGameID)     '(DWORD)      Platform ID
        .InsertDWORD GetDWORD("68XI")               '(DWORD)      Product ID
        .InsertDWORD GetVerbyte(modINI.GetGameID)   '(DWORD)      Version Byte
        .InsertDWORD 0                              '(DWORD)      Product language
        .InsertDWORD 0                              '(DWORD)      Local IP for NAT compatibility*
        .InsertDWORD 0                              '(DWORD)      Time zone bias*
        .InsertDWORD &H1033                         '(DWORD)      Locale ID*
        .InsertDWORD &H1033                         '(DWORD)      Language ID*
        .InsertNTString "USA"                       '(STRING)     Country abreviation
        .InsertNTString "United States"             '(STRING)     Country
        .Push &H50
        If bZeroPing = True Then
            .InsertDWORD 0
            .Push &H25
        End If
        .Flush
    End With
End Sub

Public Sub Parse(Data As String)
    With Debuffer
        .Buffer = Data
        .RemoveVoid 1                               'Remove sanity byte
        Select Case .RemoveByte
            Case &H25
                Select Case modINI.PingValue
                    Case "-1"
                        'Nothing
                    Case Else
                        sckBnet.SendData Data
                End Select
            'Handle the rest of the packets here
        End Select
    End With
End Sub

[Securify]

Yet, not sure how but people have exceeded Battle.net pings over 60 seconds..

They still send the keepalive packet, which keeps the connection alive.

but there unstable and usually only last 2-10 minutes.

Where did you get that from?

You can either manually send it or not?  Not sure.  Maybe the user disconnected locally.

[R.a.B.B.i.T]

However it's very hard to make it do this accurately, and by causing your ping to exceed 59999ms you won't establish a connection to Battle.net.

Battle.net stores user ping values in a doubleword which can be any numerical value from 0 to 4294967295.  Perhaps you failed to send the version check data before the hash values changed?

I was lazy testing this, I've never done it properally by making the code pause.
With StealthBot on Windows 98SE. I'd click 'Connect', then wait..
Once it said "[TimeStamp] [BNET] Connected!" I would suddenly click the Title bar and hold the mouse down counting to 59 before releasing. When holding the title bar down it pauses everything the program does. Once i'd release it would continue connecting giving me pings around 57,000ms.. I tried getting it as close to 60,000ms. Anytime that I exceeded 60 seconds it wouldn't connect. And the closest I got was 57,### so I fiqured 60 seconds was the maximum.

I wrote a simple bot explicitly to test this.  I have successfully gotten over 1 million ping.  All you do is call Sleep() in the ms delay you want to have for a ping before sending the first 0x25 to Battle.Net (only when you recieve, do not send with 0x50), then sending following 0x25 responses normally.

[Warrior]

...thanks for repeating what I showed above?

[R.a.B.B.i.T]

Eh...I probably should have read the whole first page ;\