The Nagel Algorithm and Battle.net

[Eric]

Correct me if I'm wrong, but I'm pretty sure most Blizzard clients disable the Nagel Alg. while sending 0x25 and then re-enable it's sent.

My question is, while 0x25 is being sent back and forth, does the server follow the same procedure as the client? Or is the Nagel Algorithm always enabled/disabled server-side?

[iago]

I would imagine it is, it would be rather silly if it wasn't.  

For anybody who doesn't know, Nagel Algorithm, it is what causes packets to get stacked.  Disabling it (TCP_NODELAY) ensures packets are instantly sent out.

I couldn't find any references at wikipedia or mathworld, otherwise I would give those.

[MyndFyre]

yeah, I got a basic understanding of it when I did a google search.  Thanks though

[Adron]

Try looking at packet captures, see if the server ever sends another b.net packet in the same tcp packet?

[Tuberload]

I have recieved 0x25 clumped with other packets.

[Zakath]

Battle.net clumps packets all the time...

[Adron]

You've checked this in a real packet capture? You may receive them in the same recv even if b.net didn't send them together... Also, it's only about receiving 0x25 followed by another packet, not another packet followed by 0x25.

[tA-Kane]

I only know that the Nagel algorithm is evil for Battle.net bots. This thread's ID proves it!

</dumb joke>