wlan and ping

  • Hey - turns out IRC is out and something a little more modern has taken it's place... A little thing called Discord!

    Join our community @ https://discord.gg/JuaSzXBZrk for a pick-up game, or just to rekindle with fellow community members.

May 10, 2003
2,884
0
Germany
yo, im using the wlan of my aunt whos living next to me (1 wall)

my ping is often fucked up. i tried pinging my wlan router and it gives me values between -5 (wtf) and 40.
is it normal that the ping is that unstable?oO
 

Attachments

  • Unbenannt.JPG
    Unbenannt.JPG
    83.3 KB · Views: 141
The wlan performance was already discussed several times already. Try SEARCH option ... it makes wonders sometimes ;)
 
overall: WLAN is suboptimal for gaming.
Use cable (if possible) or DLan


Well, you could try to change the WLAN channel.

//edit
Oh and just a hint:
with the command
Code:
ping 192.168.1.1 -t
you can ping continously :P
 
Last edited:
Is DLan that good?
well, like everything in the IT world: it depends.
How good the electricity cables of the apartment / house are and how those cables between this two rooms are connected.
Generally it provides better ping stability than WLAN.
 
Unstable ping times, including minus pings is a result of multicore time sync problems. Eg, if one core handles sending the packet, and the other one handles receiving it again, and the two not being synchronized properly, means that the packet could be received again with an earlier time stamp then it was sent with. Its the same thing that sometimes screws around with UT making it fast-slow-fast. I've seen the ping issue on AMD multiprocessor servers before, basically it means you can't trust those ping numbers at all.
 
yea, I really got an AMD multicore processor, thanks.

In the past I saw a fix for the time to be synchronized for amd cpus. They wont have another clock result for each core then. But that wont make the ping better and only give you in the best outcome better understandable ping times.
 
yea installed the newest driver:

Ping wird ausgeführt für 192.168.1.1 mit 32 Bytes Daten:

Antwort von 192.168.1.1: Bytes=32 Zeit=9ms TTL=64
Antwort von 192.168.1.1: Bytes=32 Zeit=10ms TTL=64
Antwort von 192.168.1.1: Bytes=32 Zeit=17ms TTL=64
Antwort von 192.168.1.1: Bytes=32 Zeit=4ms TTL=64
Antwort von 192.168.1.1: Bytes=32 Zeit=15ms TTL=64
Antwort von 192.168.1.1: Bytes=32 Zeit=8ms TTL=64
Antwort von 192.168.1.1: Bytes=32 Zeit=17ms TTL=64
Antwort von 192.168.1.1: Bytes=32 Zeit=7ms TTL=64
Antwort von 192.168.1.1: Bytes=32 Zeit=7ms TTL=64
Antwort von 192.168.1.1: Bytes=32 Zeit=1ms TTL=64
Antwort von 192.168.1.1: Bytes=32 Zeit=1ms TTL=64
Antwort von 192.168.1.1: Bytes=32 Zeit=1ms TTL=64
Antwort von 192.168.1.1: Bytes=32 Zeit=2ms TTL=64
Antwort von 192.168.1.1: Bytes=32 Zeit=4ms TTL=64
Antwort von 192.168.1.1: Bytes=32 Zeit=2ms TTL=64
Antwort von 192.168.1.1: Bytes=32 Zeit=4ms TTL=64
Antwort von 192.168.1.1: Bytes=32 Zeit=8ms TTL=64
Antwort von 192.168.1.1: Bytes=32 Zeit=3ms TTL=64
Antwort von 192.168.1.1: Bytes=32 Zeit=17ms TTL=64
Antwort von 192.168.1.1: Bytes=32 Zeit=1ms TTL=64
Antwort von 192.168.1.1: Bytes=32 Zeit=17ms TTL=64
Antwort von 192.168.1.1: Bytes=32 Zeit=5ms TTL=64
Antwort von 192.168.1.1: Bytes=32 Zeit=1ms TTL=64
Antwort von 192.168.1.1: Bytes=32 Zeit=1ms TTL=64
Antwort von 192.168.1.1: Bytes=32 Zeit=1ms TTL=64
Antwort von 192.168.1.1: Bytes=32 Zeit=1ms TTL=64
Antwort von 192.168.1.1: Bytes=32 Zeit=17ms TTL=64
Antwort von 192.168.1.1: Bytes=32 Zeit=17ms TTL=64
Antwort von 192.168.1.1: Bytes=32 Zeit=17ms TTL=64
Antwort von 192.168.1.1: Bytes=32 Zeit=4ms TTL=64
Antwort von 192.168.1.1: Bytes=32 Zeit=10ms TTL=64
Antwort von 192.168.1.1: Bytes=32 Zeit=17ms TTL=64
Antwort von 192.168.1.1: Bytes=32 Zeit=17ms TTL=64
Antwort von 192.168.1.1: Bytes=32 Zeit=17ms TTL=64
Antwort von 192.168.1.1: Bytes=32 Zeit=17ms TTL=64
Antwort von 192.168.1.1: Bytes=32 Zeit=17ms TTL=64
 
As i tatally agree that WLAn is shit for gaming my question is what rout and reciver do you use?

As i ping my wlan i get much better performance:
Antwort von 192.168.0.1: Bytes=32 Zeit=1ms TTL=64
Antwort von 192.168.0.1: Bytes=32 Zeit<1ms TTL=64
Antwort von 192.168.0.1: Bytes=32 Zeit<1ms TTL=64
Antwort von 192.168.0.1: Bytes=32 Zeit<1ms TTL=64
Antwort von 192.168.0.1: Bytes=32 Zeit<1ms TTL=64
Antwort von 192.168.0.1: Bytes=32 Zeit<1ms TTL=64
Antwort von 192.168.0.1: Bytes=32 Zeit<1ms TTL=64
Antwort von 192.168.0.1: Bytes=32 Zeit<1ms TTL=64
Antwort von 192.168.0.1: Bytes=32 Zeit<1ms TTL=64
Antwort von 192.168.0.1: Bytes=32 Zeit<1ms TTL=64
Antwort von 192.168.0.1: Bytes=32 Zeit<1ms TTL=64
Antwort von 192.168.0.1: Bytes=32 Zeit<1ms TTL=64
Antwort von 192.168.0.1: Bytes=32 Zeit<1ms TTL=64
Antwort von 192.168.0.1: Bytes=32 Zeit<1ms TTL=64
Antwort von 192.168.0.1: Bytes=32 Zeit<1ms TTL=64
Antwort von 192.168.0.1: Bytes=32 Zeit<1ms TTL=64
Antwort von 192.168.0.1: Bytes=32 Zeit<1ms TTL=64
Antwort von 192.168.0.1: Bytes=32 Zeit<1ms TTL=64
Antwort von 192.168.0.1: Bytes=32 Zeit<1ms TTL=64
Antwort von 192.168.0.1: Bytes=32 Zeit<1ms TTL=64
Antwort von 192.168.0.1: Bytes=32 Zeit=1ms TTL=64
Antwort von 192.168.0.1: Bytes=32 Zeit<1ms TTL=64
Antwort von 192.168.0.1: Bytes=32 Zeit<1ms TTL=64
Antwort von 192.168.0.1: Bytes=32 Zeit<1ms TTL=64

Ping-Statistik für 192.168.0.1:
Pakete: Gesendet = 24, Empfangen = 24, Verloren = 0 (0% Verlust),
Ca. Zeitangaben in Millisek.:
Minimum = 0ms, Maximum = 1ms, Mittelwert = 0ms

Maybe the following steps can help:
changing the channel
Disable encryption and make the network save via MAC adress
use a powered antenna
change the router and/or the reciver to some premium class models