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