Gargoyle Forum

Posted: **Tue Apr 22, 2014 5:32 pm**

I was having an annoying problem with my router with default firmware that was giving me trouble while gaming. The router was having some delays to respond, and that could be seem with the ping command, as follows:

Code: Select all

Resposta de 192.168.0.1: bytes=32 tempo=1ms TTL=64
Resposta de 192.168.0.1: bytes=32 tempo=1ms TTL=64
Resposta de 192.168.0.1: bytes=32 tempo=1ms TTL=64
Resposta de 192.168.0.1: bytes=32 tempo=1ms TTL=64
Resposta de 192.168.0.1: bytes=32 tempo=1ms TTL=64
Resposta de 192.168.0.1: bytes=32 tempo=1ms TTL=64
Resposta de 192.168.0.1: bytes=32 tempo=1ms TTL=64
Resposta de 192.168.0.1: bytes=32 tempo=1ms TTL=64
Resposta de 192.168.0.1: bytes=32 tempo=1ms TTL=64
Resposta de 192.168.0.1: bytes=32 tempo=1ms TTL=64
Resposta de 192.168.0.1: bytes=32 tempo=1ms TTL=64
Resposta de 192.168.0.1: bytes=32 tempo=3ms TTL=64
Resposta de 192.168.0.1: bytes=32 tempo=1ms TTL=64
Resposta de 192.168.0.1: bytes=32 tempo=1ms TTL=64
Resposta de 192.168.0.1: bytes=32 tempo=1ms TTL=64
Resposta de 192.168.0.1: bytes=32 tempo=1ms TTL=64
Resposta de 192.168.0.1: bytes=32 tempo=1ms TTL=64
Resposta de 192.168.0.1: bytes=32 tempo=1ms TTL=64
Resposta de 192.168.0.1: bytes=32 tempo=1ms TTL=64
Resposta de 192.168.0.1: bytes=32 tempo=1ms TTL=64
Resposta de 192.168.0.1: bytes=32 tempo=1ms TTL=64
Resposta de 192.168.0.1: bytes=32 tempo=1ms TTL=64
Resposta de 192.168.0.1: bytes=32 tempo=4ms TTL=64
Resposta de 192.168.0.1: bytes=32 tempo=1ms TTL=64
Resposta de 192.168.0.1: bytes=32 tempo=1ms TTL=64
Resposta de 192.168.0.1: bytes=32 tempo=1ms TTL=64
Resposta de 192.168.0.1: bytes=32 tempo=1ms TTL=64
Resposta de 192.168.0.1: bytes=32 tempo=1ms TTL=64
Resposta de 192.168.0.1: bytes=32 tempo=1ms TTL=64
Resposta de 192.168.0.1: bytes=32 tempo=1ms TTL=64
Resposta de 192.168.0.1: bytes=32 tempo=1ms TTL=64
Resposta de 192.168.0.1: bytes=32 tempo=1ms TTL=64
Resposta de 192.168.0.1: bytes=32 tempo=75ms TTL=64
Resposta de 192.168.0.1: bytes=32 tempo=100ms TTL=64
Resposta de 192.168.0.1: bytes=32 tempo=32ms TTL=64
Resposta de 192.168.0.1: bytes=32 tempo=1ms TTL=64
Resposta de 192.168.0.1: bytes=32 tempo=174ms TTL=64
Resposta de 192.168.0.1: bytes=32 tempo=36ms TTL=64
Resposta de 192.168.0.1: bytes=32 tempo=1ms TTL=64
Resposta de 192.168.0.1: bytes=32 tempo=1ms TTL=64
Resposta de 192.168.0.1: bytes=32 tempo=1ms TTL=64
Resposta de 192.168.0.1: bytes=32 tempo=1ms TTL=64
Resposta de 192.168.0.1: bytes=32 tempo=1ms TTL=64
Resposta de 192.168.0.1: bytes=32 tempo=1ms TTL=64
Resposta de 192.168.0.1: bytes=32 tempo=1ms TTL=64
Resposta de 192.168.0.1: bytes=32 tempo=1ms TTL=64

As I couldn't solve that, I decided to try an alternative firmware, so I installed Gargoyle 1.6.1 on my wdr4300 v1.6 router, and I used the ping command to see the response time:

Code: Select all

Resposta de 192.168.1.1: bytes=32 tempo=52ms TTL=64
Resposta de 192.168.1.1: bytes=32 tempo=9ms TTL=64
Resposta de 192.168.1.1: bytes=32 tempo=12ms TTL=64
Resposta de 192.168.1.1: bytes=32 tempo=6ms TTL=64
Resposta de 192.168.1.1: bytes=32 tempo=1ms TTL=64
Resposta de 192.168.1.1: bytes=32 tempo=8ms TTL=64
Resposta de 192.168.1.1: bytes=32 tempo=173ms TTL=64
Resposta de 192.168.1.1: bytes=32 tempo=105ms TTL=64
Resposta de 192.168.1.1: bytes=32 tempo=4ms TTL=64
Resposta de 192.168.1.1: bytes=32 tempo=24ms TTL=64
Resposta de 192.168.1.1: bytes=32 tempo=3ms TTL=64
Resposta de 192.168.1.1: bytes=32 tempo=53ms TTL=64
Resposta de 192.168.1.1: bytes=32 tempo=8ms TTL=64
Resposta de 192.168.1.1: bytes=32 tempo=6ms TTL=64
Resposta de 192.168.1.1: bytes=32 tempo=137ms TTL=64
Resposta de 192.168.1.1: bytes=32 tempo=146ms TTL=64
Resposta de 192.168.1.1: bytes=32 tempo=143ms TTL=64
Resposta de 192.168.1.1: bytes=32 tempo=11ms TTL=64
Resposta de 192.168.1.1: bytes=32 tempo=24ms TTL=64
Resposta de 192.168.1.1: bytes=32 tempo=72ms TTL=64
Resposta de 192.168.1.1: bytes=32 tempo=33ms TTL=64
Resposta de 192.168.1.1: bytes=32 tempo=50ms TTL=64
Resposta de 192.168.1.1: bytes=32 tempo=6ms TTL=64
Resposta de 192.168.1.1: bytes=32 tempo=7ms TTL=64
Resposta de 192.168.1.1: bytes=32 tempo=13ms TTL=64
Resposta de 192.168.1.1: bytes=32 tempo=24ms TTL=64
Resposta de 192.168.1.1: bytes=32 tempo=1ms TTL=64
Resposta de 192.168.1.1: bytes=32 tempo=162ms TTL=64
Resposta de 192.168.1.1: bytes=32 tempo=71ms TTL=64
Resposta de 192.168.1.1: bytes=32 tempo=27ms TTL=64
Resposta de 192.168.1.1: bytes=32 tempo=1ms TTL=64
Resposta de 192.168.1.1: bytes=32 tempo=1ms TTL=64
Resposta de 192.168.1.1: bytes=32 tempo=1ms TTL=64

Seems worse to me, there's no way to solve that problem?

Posted: **Tue Apr 22, 2014 6:27 pm**

Hi what is your network setup like, swiches? what tipe of modem? wifi printer? Security Cameras? a naber / room mate on your wifi? all thees things could ad lag in to your network. just some things to think about.

Posted: **Tue Apr 22, 2014 6:35 pm**

tapper wrote:Hi what is your network setup like, swiches? what tipe of modem? wifi printer? Security Cameras? a naber / room mate on your wifi? all thees things could ad lag in to your network. just some things to think about.

No switches, just a Motorola modem from the ISP, have to see the exact model, a computer connected by cable to the router, but its off, and my desktop that is on the next room, ~2~3m from the router with the doors open, connected through wifi (wn722nc).

Thats the only things using the router. Theres no other wifi signal that my desktop can find except from my own.

Posted: **Tue Apr 22, 2014 6:49 pm**

hmm strange! So is your gaming PC using wifi to the router? Have you checked for any malwair? also you can try and change the Wireless Security, just encase the wifi card in your gaming PC is being funny as they sometimes can be. sorry if i sound funny i am just jotting thees things down as i think of them lol

Posted: **Tue Apr 22, 2014 7:08 pm**

I just thought is your GPU overclocked the reason i ask is that i had a 8800GTX once that wen running folding at home wood make my wifi dropout. weird i no! one more thing you can try is to change the cable between the router and modem. even if it's just to rool it out.

Posted: **Tue Apr 22, 2014 9:19 pm**

tapper wrote:hmm strange! So is your gaming PC using wifi to the router? Have you checked for any malwair? also you can try and change the Wireless Security, just encase the wifi card in your gaming PC is being funny as they sometimes can be. sorry if i sound funny i am just jotting thees things down as i think of them lol

Its now malware, I did a fresh windows install because of a bios update I did on my mobo, and that happens with my notebook too (so its not my wireless adapter too).
I let my router open, but the problem persists.

The cable wouldn't just affect if I was pinging the modem or some site?

Just found another problem that is not related to that and I'll have to address in the future, for some reason my linux (elementary OS) doesn't have access to the internet, even though it just connects with the router without any problem and I can access the routers page, and thats strange because I can access with any linux live usb.

Gargoyle Forum

Ping Spikes on wdr4300

Ping Spikes on wdr4300

Re: Ping Spikes on wdr4300

Re: Ping Spikes on wdr4300

Re: Ping Spikes on wdr4300

Re: Ping Spikes on wdr4300

Re: Ping Spikes on wdr4300