quest for lower pings

#1

2c

12 Frags – +

http://esreality.com/post/2563765/re-quakelive-netcode/#pid2548581

long story short dudes found out in quakelive if u force to use less populated ports on a server u save 5-15 ping

i don't know source engine stuffs but maybe there is something similar? I looked and found nothing.

http://esreality.com/post/2563765/re-quakelive-netcode/#pid2548581

long story short dudes found out in quakelive if u force to use less populated ports on a server u save 5-15 ping

i don't know source engine stuffs but maybe there is something similar? I looked and found nothing.

#2

2c

8 Frags – +

i posted in that scripts thread but everyone was retarded

#3

2c

3 Frags – +

last resort bump

#4

ProfRoxas

-57 Frags – +

Please only bump threads if it's been at least 24 hours since the last post. Also, try not to double post. The edit post button is there for a reason.

#5

GOLDEN_NINJA_WARRIOR

38 Frags – +

ok dad

#6

Pythooon

16 Frags – +

ProfRoxasPlease only bump threads if it's been at least 24 hours since the last post. Also, try not to double post. The edit post button is there for a reason.

i laughed way too hard at this

[quote=ProfRoxas]Please only bump threads if it's been at least 24 hours since the last post. Also, try not to double post. The edit post button is there for a reason.[/quote]

i laughed way too hard at this

#7

Lunacide

25 Frags – +

http://i.imgur.com/7ioFJ1T.png

the dream is dead

[img]http://i.imgur.com/7ioFJ1T.png[/img]

the dream is dead

#8

kirby

-5 Frags – +

yeah op, jesus

#9

Arie

serveme.tf

6 Frags – +

AFAIK source server only binds to 1 port for players, so you can't connect to different ones.

#10

2c

11 Frags – +

in ireland they take this stuff more seriously... be culturally acceptive....

#11

2c

14 Frags – +

had to define:acceptive cause my retarded chrome gave me red squiggles

#12

2c

11 Frags – +

what if acceptive wasn't a word and I just used it my entire life and was wrong

#13

2c

10 Frags – +

gonna search if there's a more complete dictionary for chrome

#14

2c

9 Frags – +

http://i.imgur.com/u93WE1a.png

go ahead and check this everyone, goodnight and god bless.

[img]http://i.imgur.com/u93WE1a.png[/img]

go ahead and check this everyone, goodnight and god bless.

#15

Brock

5 Frags – +

bump

#16

Brock

4 Frags – +

oh wait is the thread over

#17

2c

5 Frags – +

well there appears to be no such command in my searching and everyone else's

#18

TechDude

16 Frags – +

TF2 servers are only accessible on one port.

This is typically 27015 (but can be changed for a given server). The dedicated only listens for connections on this port.

Now if you are interested in what ports are being used during gameplay you can use wireshark and inspect the packets being sent to the tf2 server: http://www.wireshark.org/

It's also possible that the server listens on 27015 but actually communicates to each client on a different port. Wireshark would show you this.

TF2 servers are only accessible on one port.

This is typically 27015 (but can be changed for a given server). The dedicated only listens for connections on this port.

Now if you are interested in what ports are being used during gameplay you can use wireshark and inspect the packets being sent to the tf2 server: http://www.wireshark.org/

It's also possible that the server listens on 27015 but actually communicates to each client on a different port. Wireshark would show you this.

#19

Magus

7 Frags – +

TechDudeTF2 servers are only accessible on one port.

This is typically 27015 (but can be changed for a given server). The dedicated only listens for connections on this port.

Now if you are interested in what ports are being used during gameplay you can use wireshark and inspect the packets being sent to the tf2 server: http://www.wireshark.org/

It's also possible that the server listens on 27015 but actually communicates to each client on a different port. Wireshark would show you this.

Techdude coming in hot.

[quote=TechDude]TF2 servers are only accessible on one port.

This is typically 27015 (but can be changed for a given server). The dedicated only listens for connections on this port.

Now if you are interested in what ports are being used during gameplay you can use wireshark and inspect the packets being sent to the tf2 server: http://www.wireshark.org/

It's also possible that the server listens on 27015 but actually communicates to each client on a different port. Wireshark would show you this.[/quote]

Techdude coming in hot.

#20

ukm

1 Frags – +

2clong story short dudes found out in quakelive if u force to use less populated ports on a server u save 5-15 ping

Thaaat doesn't make sense and isn't what happened in that thread.

There was a command in the original version of ql which forced the client to reconnect, and it happened to open the socket on a new ephemeral (i.e. arbitrary client-side) port due to a timing issue. They then found a way to replicate this behavior in the standalone version of ql which did not have that timing issue. This has nothing to do with the port the server is listening on (of which there is only 1). For some people, some of the time they found that changing the port their client uses would cause a small drop in latency. This is speculated to be due to some kind of port-based routing or QoS on one of the hops between the client and the server but they don't actually know.

[quote=2c]long story short dudes found out in quakelive if u force to use less populated ports on a server u save 5-15 ping[/quote]

Thaaat doesn't make sense and isn't what happened in that thread.

There was a command in the original version of ql which forced the client to reconnect, and it happened to open the socket on a new ephemeral (i.e. arbitrary client-side) port due to a timing issue. They then found a way to replicate this behavior in the standalone version of ql which did not have that timing issue. This has nothing to do with the port the server is listening on (of which there is only 1). For some people, some of the time they found that changing the port their client uses would cause a small drop in latency. This is speculated to be due to some kind of port-based routing or QoS on one of the hops between the client and the server but they don't actually know.

#21

Khaki

1 Frags – +

ukm2clong story short dudes found out in quakelive if u force to use less populated ports on a server u save 5-15 ping
Thaaat doesn't make sense and isn't what happened in that thread.

There was a command in the original version of ql which forced the client to reconnect, and it happened to open the socket on a new ephemeral (i.e. arbitrary client-side) port due to a timing issue. They then found a way to replicate this behavior in the standalone version of ql which did not have that timing issue. This has nothing to do with the port the server is listening on (of which there is only 1). For some people, some of the time they found that changing the port their client uses would cause a small drop in latency. This is speculated to be due to some kind of port-based routing or QoS on one of the hops between the client and the server but they don't actually know.

holy shit layman's terms for my caveman brain please

[quote=ukm][quote=2c]long story short dudes found out in quakelive if u force to use less populated ports on a server u save 5-15 ping[/quote]

Thaaat doesn't make sense and isn't what happened in that thread.

There was a command in the original version of ql which forced the client to reconnect, and it happened to open the socket on a new ephemeral (i.e. arbitrary client-side) port due to a timing issue. They then found a way to replicate this behavior in the standalone version of ql which did not have that timing issue. This has nothing to do with the port the server is listening on (of which there is only 1). For some people, some of the time they found that changing the port their client uses would cause a small drop in latency. This is speculated to be due to some kind of port-based routing or QoS on one of the hops between the client and the server but they don't actually know.[/quote]
holy shit layman's terms for my caveman brain please

#22

Khaki

1 Frags – +

sorry ukm i didn't mean to yell

#23

Deathy

2 Frags – +

TechDudeTF2 servers are only accessible on one port.

This is typically 27015 (but can be changed for a given server). The dedicated only listens for connections on this port.

Now if you are interested in what ports are being used during gameplay you can use wireshark and inspect the packets being sent to the tf2 server: http://www.wireshark.org/

It's also possible that the server listens on 27015 but actually communicates to each client on a different port. Wireshark would show you this.

Literally a tech dude

[quote=TechDude]TF2 servers are only accessible on one port.

This is typically 27015 (but can be changed for a given server). The dedicated only listens for connections on this port.

Now if you are interested in what ports are being used during gameplay you can use wireshark and inspect the packets being sent to the tf2 server: http://www.wireshark.org/

It's also possible that the server listens on 27015 but actually communicates to each client on a different port. Wireshark would show you this.[/quote]

Literally a tech dude

#24

downpour

0 Frags – +

this thread made me laugh pretty hard at work my boss looked at me funny thanks tehoreoz
also return of angry pete

#25

wareya

0 Frags – +

sounds like a driver problem
interesting