• Welcome to Valhalla Legends Archive.
 

UDP Plug

Started by gosumoo, February 13, 2004, 09:05 PM

Previous topic - Next topic

Soul Taker

Try it out guys, I just did... he's right.

Lenny

#31
Quote from: Soul Taker on February 21, 2004, 07:06 PM
Try it out guys, I just did... he's right.

At most, o.OV can be 1/2 right...Since he said this happens for 0x50 AND 0x1E

I have never tested with 0x1E, but for 0x50 this is not true....

So I also recommend o.OV try it with 0x50, to show that we are also right...

Edit: After looking at that post more carefully, I realized Soul Taker never specified what he tried.  I assume he was referring to o.OV's belief that with 0ms ping battle.net will not send 0x25 in channel.
The Bovine Revolution
Something unimportant

Live Battle.net:

WARNING: The preceding message may have contained content unsuitable for young children.

Dyndrilliac

o.Ov, for future posts, use the edit button, or put all your information in the same post.

Also, Ping has nothing to do with UDP Plug, so why is it being discussed? Why is anything not related to the UDP Plug being discussed in a  topic labeled "Chat Plug"?

For the sake of being on topic, I have tested each scenario mentioned - and found Arta to be correct, in all cases.
Quote from: Edsger W. DijkstraIt is practically impossible to teach good programming to students that have had a prior exposure to BASIC; as potential programmers they are mentally mutilated beyond hope of regeneration.

o.OV

#33
Quote from: Lenny on February 21, 2004, 05:44 PM
Quote from: o.OV on February 21, 2004, 04:11 PM
Quote from: Kp on February 21, 2004, 11:44 AM
Quote from: Arta[vL] on February 21, 2004, 04:11 AM
As far as I am aware, how you deal with the initial ping has absolutely no bearing on whether or not Battle.net sends you regular ping messages after logging on. It definitely has no bearing on whether or not you receive SID_NULL, as they are two completely different concepts - SID_NULL is designed to detect network failures, SID_PING is used to detect network latency.

Yes, but as above, failure to generate any outbound traffic (responding to SID_PING counts as outbound traffic) will eventually get you dropped.

I disagree.
I have remained Logged In for over 45 minutes without sending ANYTHING to battle.net.
All I have recieved are 0x00 every 2 minutes or so.
Failure to reply to 0x25 will get the user disconnected from battle.net.(InChannel)

"I have remained Logged In for over 45 minutes without sending ANYTHING to battle.net."

is inconsistent with

"Failure to reply to 0x25 will get the user disconnected from battle.net.(InChannel)"

How did you stay on for 45 minutes?


Yes !

Quote
"Failure to reply to 0x25 will get the user disconnected from battle.net"

In my case I never recieve 0x25 InChannel meaning there is nothing to reply to.
If the facts don't fit the theory, change the facts. - Albert Einstein

Lenny

How is the connection kept alive if you don't reply to anything battle.net sends you?

As Arta said, failure to generate any outbound traffic will get you dropped...
The Bovine Revolution
Something unimportant

Live Battle.net:

WARNING: The preceding message may have contained content unsuitable for young children.

o.OV

Quote from: Lenny on February 21, 2004, 08:13 PM
Quote from: Soul Taker on February 21, 2004, 07:06 PM
Try it out guys, I just did... he's right.

At most, o.OV can be 1/2 right...Since he said this happens for 0x50 AND 0x1E

I have never tested with 0x1E, but for 0x50 this is not true....

So I also recommend o.OV try it with 0x50, to show that we are also right...

Edit: After looking at that post more carefully, I realized Soul Taker never specified what he tried.  I assume he was referring to o.OV's belief that with 0ms ping battle.net will not send 0x25 in channel.

Heh. I'm not sure what you are doing differently..
but I get the same results as 0x1E.


2:48:13 AM  < ChrW$(1)
2:48:13 AM  < 50
2:48:13 AM  < 25
2:48:14 AM  > 25
2:48:14 AM  > 50
2:48:14 AM  < 51
2:48:14 AM  > 51
2:48:14 AM  < 14
2:48:14 AM  < 2D
2:48:14 AM  < 3A
2:48:15 AM  > 2D
2:48:15 AM  > 3A
2:48:15 AM  < A
2:48:15 AM  < C
2:48:15 AM  > A
2:48:16 AM  < 46
2:48:16 AM  < C
2:48:16 AM  > F
2:48:16 AM  > F
2:48:16 AM  > F
2:48:16 AM  > 46
2:51:42 AM  > 0
2:53:44 AM  > 0
2:55:44 AM  > 0
2:57:45 AM  > 0
2:59:46 AM  > 0

If the facts don't fit the theory, change the facts. - Albert Einstein

o.OV

#36
Quote from: Dyndrilliac on February 21, 2004, 08:43 PM
o.Ov, for future posts, use the edit button, or put all your information in the same post.

Also, Ping has nothing to do with UDP Plug, so why is it being discussed? Why is anything not related to the UDP Plug being discussed in a  topic labeled "Chat Plug"?

For the sake of being on topic, I have tested each scenario mentioned - and found Arta to be correct, in all cases.

I think you are doing the scenarios wrong as well.
Because if you performed my scenario correctly
you wouldn't be recieving 0x25.
Try voiding out 0x25 completely
since in none of my scenarios will you ever reply to it.
And 0x25 should only be sent immediately after 0x1E/0x50.

I only use modify if I'm adding on to the reply to the same person.

And there is nothing wrong with going off topic.
It happens all the time
if the forum admin
feels it should be on a new thread..
I'm sure they would move it.
Maybe they will. I dunno.
If the facts don't fit the theory, change the facts. - Albert Einstein

Dyndrilliac

Who cares as long as it works....
Quote from: Edsger W. DijkstraIt is practically impossible to teach good programming to students that have had a prior exposure to BASIC; as potential programmers they are mentally mutilated beyond hope of regeneration.

o.OV

Quote from: Dyndrilliac on February 22, 2004, 10:26 AM
Who cares as long as it works....

Quote
For the sake of being on topic, I have tested each scenario mentioned - and found Arta to be correct, in all cases.

With that attitude my guess is..
You didn't test any of the scenarios.
And if you did..
you didn't put effort into trying to simulate my PacketID log.

Less checkups from battle.net means less bandwidth usage
and 56k users won't drop as easily if they are lagging like mad.

And don't give me that 56k users should die BS :)
If the facts don't fit the theory, change the facts. - Albert Einstein

Soul Taker

I tried it the other night.  If you send 0x25 with 0x50, to get 0 ms ping, you won't recieve 0x25 intermittently while in chat.  I was expecting to prove him wrong but he's right.

o.OV

#40
Quote from: Lenny on February 22, 2004, 03:06 AM
How is the connection kept alive if you don't reply to anything battle.net sends you?

As Arta said, failure to generate any outbound traffic will get you dropped...

Kp said that NOT Arta.
And I just ran some tests on it..
the results were inconsistent.
I connected to battle.net with 0ms
disconnected my connection
(The first connection is still logged on despite the fact that I have disconnected)
acquired a new ip and reconnected to battle.net.
The first connection didn't drop on its own for about 2 minutes in my first test and 9 minutes on my second.

My guess is the 0x00 packets since that is the only traffic at all..
and its Incoming.

Quote
SID_NULL (0x00) has absolutely nothing to do with your latency. You can send it or not, Battle.net does not process it. Battle.net will send it to you regardless of whether you send it or don't. It's good practice to send it, because the game clients do.

Quote
SID_NULL is designed to detect network failures,
SID_PING is used to detect network latency.

And now is good time to share with the rest of bnet..
I am 56k and I can spoof 15/16ms lag.
It involves taking advantage of 0x00 to HELP spoof it.
If the facts don't fit the theory, change the facts. - Albert Einstein

Arta

Quote from: o.OV on February 22, 2004, 03:07 PM
It involves taking advantage of 0x00 to HELP spoof it.

You what?

HELP meaning /help? HELP is what? How do you use SID_NULL to change your latency?

What are you on about?

o.OV

#42
Quote from: Arta[vL] on February 23, 2004, 03:01 PM
Quote from: o.OV on February 22, 2004, 03:07 PM
It involves taking advantage of 0x00 to HELP spoof it.

You what?

HELP meaning /help? HELP is what? How do you use SID_NULL to change your latency?

What are you on about?

It's not so useful but I did it just because I knew it could be done.
:)

I use 0x00 to slightly increase the time
it takes for the server to process 0x25.

How many Nulls you send will vary depending on your connection speed.
I have both DSL and 56k..

For 56k I normally ping at 232ms.
I use about 725 Nulls

For DSL I normally ping at 62ms.
I use about 347 Nulls
(For me, 348 or more won't get me ipbanned
but I won't get a reply from battle.net..
If I could I would send more but I'm not clear on why B.net won't respond..
Perhaps it was sent too fast/too much)

This is why I used the term HELP..
because 0x00 is being used to AFFECT the outcome.
The first time I ever got 15ms was by accident
and it did not involve using 0x00.
If the facts don't fit the theory, change the facts. - Albert Einstein

Dyndrilliac

#43
You're saying your sending 0x00 to Bnet in order to create more time for the server to process the packets leading upto your response with 0x025, thus spoofing your ping higher than it normally would be?

That seems silly and moronic, seeing as you can just let the client sit idle (using functions(depending on your language), which means you will never get IP banned with this because your not mass sending) to increase the amount of time in the gap from the time you send 0x25 - which again proves 0x00 has NO EFFECT on ping whatsoever no matter how or why you use it. Get over it. you're wrong.
Quote from: Edsger W. DijkstraIt is practically impossible to teach good programming to students that have had a prior exposure to BASIC; as potential programmers they are mentally mutilated beyond hope of regeneration.

o.OV

Quote from: Dyndrilliac on February 23, 2004, 06:14 PM
You're saying your sending 0x00 to Bnet in order to create more time for the server to process the packets leading upto your response with 0x025, thus spoofing your ping higher than it normally would be?

That seems silly and moronic, seeing as you can just let the client sit idle (using functions(depending on your language), which means you will never get IP banned with this because your not mass sending) to increase the amount of time in the gap from the time you send 0x25 - which again proves 0x00 has NO EFFECT on ping whatsoever no matter how or why you use it. Get over it. you're wrong.

Did I even say I get ipbanned?

Why don't you try delaying the packet client side
while on 56k modem and see if you can get 15/16ms
while using 56k.

FYI, I have tested this already and I did try delaying it client side.
IT DOESN'T WORK!!

People like you don't seem to like testing things but instead..
you like to make critical statements
despite the fact that you lack knowledge on the matter.

And your theory doesn't disprove anything.
How do you explain the fact that I am a 56k user with 15/16ms lag?
You are saying 0x00 didn't play a vital role in it.
If anything you are proving that you are silly, moronic, and wrong.

You should really test your theories before replying again.
If the facts don't fit the theory, change the facts. - Albert Einstein

|