Overclock.net › Forums › Software, Programming and Coding › Networking & Security › Wireless Latency Problems
New Posts  All Forums:Forum Nav:

Wireless Latency Problems

post #1 of 3
Thread Starter 
So here's some info, from pinging the default gateway
Warning: Spoiler! (Click to show)
Pinging 10.0.0.1 with 32 bytes of data:
Reply from 10.0.0.1: bytes=32 time=19ms TTL=64
Reply from 10.0.0.1: bytes=32 time=76ms TTL=64
Reply from 10.0.0.1: bytes=32 time=74ms TTL=64
Reply from 10.0.0.1: bytes=32 time=71ms TTL=64
Reply from 10.0.0.1: bytes=32 time=102ms TTL=64
Reply from 10.0.0.1: bytes=32 time=122ms TTL=64
Request timed out.
Reply from 10.0.0.1: bytes=32 time=673ms TTL=64
Reply from 10.0.0.1: bytes=32 time=82ms TTL=64
Reply from 10.0.0.1: bytes=32 time=369ms TTL=64
Reply from 10.0.0.1: bytes=32 time=324ms TTL=64
Reply from 10.0.0.1: bytes=32 time=1268ms TTL=64
Reply from 10.0.0.1: bytes=32 time=1352ms TTL=64
Reply from 10.0.0.1: bytes=32 time=931ms TTL=64
Reply from 10.0.0.1: bytes=32 time=682ms TTL=64
Reply from 10.0.0.1: bytes=32 time=59ms TTL=64
Reply from 10.0.0.1: bytes=32 time=147ms TTL=64
Reply from 10.0.0.1: bytes=32 time=47ms TTL=64
Reply from 10.0.0.1: bytes=32 time=174ms TTL=64
Request timed out.
Reply from 10.0.0.1: bytes=32 time=192ms TTL=64
Reply from 10.0.0.1: bytes=32 time=404ms TTL=64
Reply from 10.0.0.1: bytes=32 time=112ms TTL=64
Reply from 10.0.0.1: bytes=32 time=1012ms TTL=64
Reply from 10.0.0.1: bytes=32 time=1712ms TTL=64
Reply from 10.0.0.1: bytes=32 time=971ms TTL=64
Reply from 10.0.0.1: bytes=32 time=817ms TTL=64
Reply from 10.0.0.1: bytes=32 time=68ms TTL=64
Reply from 10.0.0.1: bytes=32 time=103ms TTL=64
Reply from 10.0.0.1: bytes=32 time=364ms TTL=64
Reply from 10.0.0.1: bytes=32 time=396ms TTL=64
Reply from 10.0.0.1: bytes=32 time=217ms TTL=64
Reply from 10.0.0.1: bytes=32 time=116ms TTL=64
Reply from 10.0.0.1: bytes=32 time=228ms TTL=64
Reply from 10.0.0.1: bytes=32 time=274ms TTL=64
Reply from 10.0.0.1: bytes=32 time=58ms TTL=64
Reply from 10.0.0.1: bytes=32 time=84ms TTL=64
Reply from 10.0.0.1: bytes=32 time=84ms TTL=64
Reply from 10.0.0.1: bytes=32 time=65ms TTL=64
Reply from 10.0.0.1: bytes=32 time=65ms TTL=64
Request timed out.
Reply from 10.0.0.1: bytes=32 time=400ms TTL=64
Reply from 10.0.0.1: bytes=32 time=883ms TTL=64
Reply from 10.0.0.1: bytes=32 time=79ms TTL=64
Reply from 10.0.0.1: bytes=32 time=1552ms TTL=64
Reply from 10.0.0.1: bytes=32 time=1092ms TTL=64
Reply from 10.0.0.1: bytes=32 time=188ms TTL=64
Reply from 10.0.0.1: bytes=32 time=108ms TTL=64
Reply from 10.0.0.1: bytes=32 time=72ms TTL=64
Reply from 10.0.0.1: bytes=32 time=200ms TTL=64
Reply from 10.0.0.1: bytes=32 time=32ms TTL=64
Request timed out.
Reply from 10.0.0.1: bytes=32 time=100ms TTL=64
Reply from 10.0.0.1: bytes=32 time=74ms TTL=64
Reply from 10.0.0.1: bytes=32 time=66ms TTL=64
Reply from 10.0.0.1: bytes=32 time=67ms TTL=64
Reply from 10.0.0.1: bytes=32 time=276ms TTL=64
Reply from 10.0.0.1: bytes=32 time=35ms TTL=64
Reply from 10.0.0.1: bytes=32 time=55ms TTL=64
Reply from 10.0.0.1: bytes=32 time=62ms TTL=64
Reply from 10.0.0.1: bytes=32 time=45ms TTL=64
Reply from 10.0.0.1: bytes=32 time=31ms TTL=64
Reply from 10.0.0.1: bytes=32 time=10ms TTL=64
Reply from 10.0.0.1: bytes=32 time=52ms TTL=64
Reply from 10.0.0.1: bytes=32 time=27ms TTL=64
Reply from 10.0.0.1: bytes=32 time=5ms TTL=64
Reply from 10.0.0.1: bytes=32 time=49ms TTL=64


And then not two seconds later, no network change to my knowledge
Warning: Spoiler! (Click to show)
Pinging 10.0.0.1 with 32 bytes of data:
Reply from 10.0.0.1: bytes=32 time=1ms TTL=64
Reply from 10.0.0.1: bytes=32 time=4ms TTL=64
Reply from 10.0.0.1: bytes=32 time=2ms TTL=64
Reply from 10.0.0.1: bytes=32 time=6ms TTL=64
Reply from 10.0.0.1: bytes=32 time=6ms TTL=64
Reply from 10.0.0.1: bytes=32 time=15ms TTL=64
Reply from 10.0.0.1: bytes=32 time=49ms TTL=64
Reply from 10.0.0.1: bytes=32 time=9ms TTL=64
Reply from 10.0.0.1: bytes=32 time=13ms TTL=64
Reply from 10.0.0.1: bytes=32 time=7ms TTL=64
Reply from 10.0.0.1: bytes=32 time=41ms TTL=64
Reply from 10.0.0.1: bytes=32 time=4ms TTL=64
Reply from 10.0.0.1: bytes=32 time=1ms TTL=64
Reply from 10.0.0.1: bytes=32 time=1ms TTL=64
Reply from 10.0.0.1: bytes=32 time=1ms TTL=64
Reply from 10.0.0.1: bytes=32 time=1ms TTL=64
Reply from 10.0.0.1: bytes=32 time=1ms TTL=64
Reply from 10.0.0.1: bytes=32 time=2ms TTL=64
Reply from 10.0.0.1: bytes=32 time=1ms TTL=64
Reply from 10.0.0.1: bytes=32 time=1ms TTL=64
Reply from 10.0.0.1: bytes=32 time=20ms TTL=64
Reply from 10.0.0.1: bytes=32 time=10ms TTL=64
Reply from 10.0.0.1: bytes=32 time=6ms TTL=64
Reply from 10.0.0.1: bytes=32 time=2ms TTL=64
Reply from 10.0.0.1: bytes=32 time=1ms TTL=64
Reply from 10.0.0.1: bytes=32 time=2ms TTL=64
Reply from 10.0.0.1: bytes=32 time=1ms TTL=64
Reply from 10.0.0.1: bytes=32 time=2ms TTL=64
Reply from 10.0.0.1: bytes=32 time=1ms TTL=64
Reply from 10.0.0.1: bytes=32 time=1ms TTL=64
Reply from 10.0.0.1: bytes=32 time=2ms TTL=64
Reply from 10.0.0.1: bytes=32 time=76ms TTL=64
Reply from 10.0.0.1: bytes=32 time=2ms TTL=64
Reply from 10.0.0.1: bytes=32 time=112ms TTL=64
Reply from 10.0.0.1: bytes=32 time=8ms TTL=64
Reply from 10.0.0.1: bytes=32 time=4ms TTL=64
Reply from 10.0.0.1: bytes=32 time=2ms TTL=64
Reply from 10.0.0.1: bytes=32 time=2ms TTL=64
Reply from 10.0.0.1: bytes=32 time=2ms TTL=64
Reply from 10.0.0.1: bytes=32 time=2ms TTL=64
Reply from 10.0.0.1: bytes=32 time=1ms TTL=64
Reply from 10.0.0.1: bytes=32 time=3ms TTL=64
Reply from 10.0.0.1: bytes=32 time=1ms TTL=64
Reply from 10.0.0.1: bytes=32 time=1ms TTL=64
Reply from 10.0.0.1: bytes=32 time=1ms TTL=64
Reply from 10.0.0.1: bytes=32 time=1ms TTL=64


So basically its useless, trying to play games is extremely frustrating (especially BF3) now you're going to say, "why are you playing on wireless" well the answer is, I don't have the money to have a jack installed in this room and have a run put in under the house and another jack where the modem is. So that's why i'm on wireless.

Card, D-Link DWA-556
Access Point is just some gibber comcast box

Any advice would be awesome
Edited by timma100 - 9/27/13 at 7:00pm
post #2 of 3
Are there a lot of other access points in your area?
Could you run something like InSSIDer to get a better view of your area?
Waiting on X399
(13 items)
 
  
CPUMotherboardGraphicsRAM
AMD Phenom II B57 @ X4 3.9 Gigabyte 790FXTA-UD5 Sapphire Radeon 290 8 GB G.Skill 2133 
Hard DriveCoolingOSKeyboard
250 GB 840 EVO Noctua NH-D14 Windows 10 Logitech K350 
PowerCaseMouseMouse Pad
Seasonic x750 Corsair 600T Logitech G100s Razer Goliathus Speed 
Audio
Plantronics Gamecom 788 
  hide details  
Reply
Waiting on X399
(13 items)
 
  
CPUMotherboardGraphicsRAM
AMD Phenom II B57 @ X4 3.9 Gigabyte 790FXTA-UD5 Sapphire Radeon 290 8 GB G.Skill 2133 
Hard DriveCoolingOSKeyboard
250 GB 840 EVO Noctua NH-D14 Windows 10 Logitech K350 
PowerCaseMouseMouse Pad
Seasonic x750 Corsair 600T Logitech G100s Razer Goliathus Speed 
Audio
Plantronics Gamecom 788 
  hide details  
Reply
post #3 of 3
Try moving either your AP or your computer a few centimeters. Sometimes it fixes timing issues that can happen on wireless.
#well
(19 items)
 
Lenovo L530
(8 items)
 
 
CPUMotherboardGraphicsRAM
Intel Core i7 4770k Gigabyte Z87X-UD4H XFX Radeon HD 6950 Corsair CMX8GX3M2A2000C9 
Hard DriveHard DriveOptical DriveCooling
Samsung EVO 840 Hitachi HDS722020ALA330 Generic DVD±RW Burner Noctua NH-D14 
OSMonitorMonitorKeyboard
Windows 8.1 Dell U2711 LG W2453 Ducky DK9008 Overclock.net Edition, Cherry MX B... 
PowerCaseMouseMouse Pad
Corsair TX850 Antec Three Hundred Corsair Raptor M40 QPAD HeatoN M 
AudioAudioAudio
E-MU Tracker|pre Beyerdynamic DT-770 250 Ohm AntLion ModMIc 
CPUGraphicsRAMRAM
Intel Ivy Bridge 3210M Intel HD 4000 Graphics Soldered Corsair Vengeance  
Hard DriveOptical DriveOSMonitor
500GB DVD-+RW Windows 7 Professional 1600x900 
  hide details  
Reply
#well
(19 items)
 
Lenovo L530
(8 items)
 
 
CPUMotherboardGraphicsRAM
Intel Core i7 4770k Gigabyte Z87X-UD4H XFX Radeon HD 6950 Corsair CMX8GX3M2A2000C9 
Hard DriveHard DriveOptical DriveCooling
Samsung EVO 840 Hitachi HDS722020ALA330 Generic DVD±RW Burner Noctua NH-D14 
OSMonitorMonitorKeyboard
Windows 8.1 Dell U2711 LG W2453 Ducky DK9008 Overclock.net Edition, Cherry MX B... 
PowerCaseMouseMouse Pad
Corsair TX850 Antec Three Hundred Corsair Raptor M40 QPAD HeatoN M 
AudioAudioAudio
E-MU Tracker|pre Beyerdynamic DT-770 250 Ohm AntLion ModMIc 
CPUGraphicsRAMRAM
Intel Ivy Bridge 3210M Intel HD 4000 Graphics Soldered Corsair Vengeance  
Hard DriveOptical DriveOSMonitor
500GB DVD-+RW Windows 7 Professional 1600x900 
  hide details  
Reply
New Posts  All Forums:Forum Nav:
  Return Home
  Back to Forum: Networking & Security
Overclock.net › Forums › Software, Programming and Coding › Networking & Security › Wireless Latency Problems