[1.5.4][TL-WR1043ND] Incredibly huge ping times to router

[raz]

Hey mix,

I tried changing between channels 4-5-6, same results.
I tried switching between b/g/n, b/g, and only b, same result.

There's only me in my neighbourhood on channels 4-5-6.

It's getting more hectic:



Full garph

Even a reboot (can be seen in red) did not bring things under control.

I think I'll try a different Gargoyle revision..

[mix]

What is the significance of channels 4, 5 and 6? Only channel 1, 6 and 11 won't overlap. And if you are using 40Mhz channels, there is even more overlap going on. That little pause could be your router detecting interference and disabling the 20 Mhz secondary channel temporarily.

If this was me, I would disable the secondary channel and try channels 1 and 11 to see if the results are the same (even if 1 and 11 are being used by other routers).

Also, can you prove one way or another it's not just the wifi card in the computer you are using to produce that graph that is the problem? You have this same wifi problem with multiple computers right?

[HelderMF]

I have a TL-WR1043ND flashed with Gargoyle 1.5.4 and I've been experiencing the same latency spikes as raz is describing.

I'm using the same channel I used before, and tested with 20 and 40MHz.

Another thing I have noticed is that the maximum/standard transmission power is very HIGH!!! 35dBm. I changed it to 20dBm. Is this a real value? Or just another bug?

Regards,

HelderMF

[gmore]

Similar problem here.

can anyone tell me the difference between 1.3 and 1.5?

if 1.3 is more stable, i might try that.

I only got the 1043 after my asus refused to boot. the asus never had the spike problems before.

[smart]

This has just started, I presume that a reboot would fix things. Nevertheless, this definitely sounds like a major bug.

Code: Select all

Pinging 192.168.1.1 with 32 bytes of data:

Reply from 192.168.1.1: bytes=32 time=2052ms TTL=64
Reply from 192.168.1.1: bytes=32 time=2019ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1963ms TTL=64
Request timed out.
Reply from 192.168.1.1: bytes=32 time=807ms TTL=64
Reply from 192.168.1.1: bytes=32 time=2109ms TTL=64
Reply from 192.168.1.1: bytes=32 time=583ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1762ms TTL=64
Reply from 192.168.1.1: bytes=32 time=758ms TTL=64
Reply from 192.168.1.1: bytes=32 time=913ms TTL=64

Ping statistics for 192.168.1.1:
    Packets: Sent = 10, Received = 9, Lost = 1 (10% loss),
Approximate round trip times in milli-seconds:
    Minimum = 583ms, Maximum = 2109ms, Average = 1440ms

TL-WR1043ND, running Gargoyle 1.5.4

Memory usage: 14MB/28.8MB (48.6%)
Connections: 190/12288
CPU Load Averages: 0.00/0.00/0.00 (1/5/15 minutes)
Uptime: 2 days, 9 hours, 58 minutes


Nothing unusual in the logread, but dmesg spits this over and over:

Code: Select all

ath: Could not stop RX, we could be confusing the DMA engine when we start RX up
ath: DMA failed to stop in 10 ms
AR_CR=0x00000024
AR_DIAG_SW=0x42000020
DMADBG_7=0x00026020

Any clues?

Check your Network connection and implement any of the ping test tool or Whoisxy.com in to your code snippet and test ping again .