WDR4300 timed out gargoyle

[eminem093]

Hello

I have instaled Gargoyle 1.5.10 to my new wdr 4300 rev 1.6

after instal my connection gets timed out

Strange my wdr1043nd working well with gargoyle

Pinging 192.168.1.1 with 32 bytes of data:
Request timed out.
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Request timed out.
Request timed out.
Reply from 192.168.1.1: bytes=32 time=3ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Request timed out.
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=2ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Request timed out.
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=2ms TTL=64
Reply from 192.168.1.1: bytes=32 time=3ms TTL=64
Reply from 192.168.1.1: bytes=32 time=2ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=2ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Request timed out.
Reply from 192.168.1.1: bytes=32 time=2ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=2ms TTL=64
Reply from 192.168.1.1: bytes=32 time=2ms TTL=64
Reply from 192.168.1.1: bytes=32 time=2ms TTL=64
Reply from 192.168.1.1: bytes=32 time=2ms TTL=64
Reply from 192.168.1.1: bytes=32 time=2ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=3ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=3ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Request timed out.
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=2ms TTL=64
Reply from 192.168.1.1: bytes=32 time=2ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=2ms TTL=64

This is what happens
The original firmware don't has this problem

Sorry for my english

Some help

Thanks

[BashfulBladder]

As I recall the original TP-Link firmware is 192.168.0.1. If you still have a DHCP lease, try to release it & renew.

[eminem093]

Hello


I was talking about fw gargoyle

I tried dd-wrt same issue

with openwrt trunk the timeout time is a bit more beter i mean its timing out less than with gargoyle.

the board rev is 1.3

on the case it says rev 1.6

it has green leds in stad off blue

any ideas

i think it's a driver problem for the lan chipset .

I hope its got fixed in the next fw.

I like gargoyle on my wr1043nd

Thanks

[BashfulBladder]

Sorry, I didn't see your pinging, only the timed outs

I have a computer connected with a 2m cable to a 4300 (1.2) which is connected via 40 or so feet of Cat5e to a 3600 (1.1):

• 64 bytes from 192.168.1.2: icmp_seq=0 ttl=64 time=0.535 ms
  64 bytes from 192.168.1.2: icmp_seq=1 ttl=64 time=0.299 ms
  64 bytes from 192.168.1.2: icmp_seq=2 ttl=64 time=0.308 ms
  64 bytes from 192.168.1.2: icmp_seq=3 ttl=64 time=0.307 ms
  64 bytes from 192.168.1.2: icmp_seq=4 ttl=64 time=0.318 ms
  64 bytes from 192.168.1.2: icmp_seq=5 ttl=64 time=0.328 ms
  64 bytes from 192.168.1.2: icmp_seq=6 ttl=64 time=0.309 ms
  64 bytes from 192.168.1.2: icmp_seq=7 ttl=64 time=0.307 ms
  64 bytes from 192.168.1.2: icmp_seq=8 ttl=64 time=0.310 ms
  64 bytes from 192.168.1.2: icmp_seq=9 ttl=64 time=0.320 ms
  64 bytes from 192.168.1.2: icmp_seq=10 ttl=64 time=0.298 ms
  64 bytes from 192.168.1.2: icmp_seq=11 ttl=64 time=0.306 ms
  64 bytes from 192.168.1.2: icmp_seq=12 ttl=64 time=0.292 ms
  64 bytes from 192.168.1.2: icmp_seq=13 ttl=64 time=0.314 ms
  64 bytes from 192.168.1.2: icmp_seq=14 ttl=64 time=0.300 ms
  64 bytes from 192.168.1.2: icmp_seq=15 ttl=64 time=0.307 ms
  
  64 bytes from 192.168.1.1: icmp_seq=0 ttl=64 time=0.371 ms
  64 bytes from 192.168.1.1: icmp_seq=1 ttl=64 time=0.284 ms
  64 bytes from 192.168.1.1: icmp_seq=2 ttl=64 time=0.291 ms
  64 bytes from 192.168.1.1: icmp_seq=3 ttl=64 time=0.288 ms
  64 bytes from 192.168.1.1: icmp_seq=4 ttl=64 time=0.287 ms
  64 bytes from 192.168.1.1: icmp_seq=5 ttl=64 time=0.316 ms
  64 bytes from 192.168.1.1: icmp_seq=6 ttl=64 time=0.323 ms
  64 bytes from 192.168.1.1: icmp_seq=7 ttl=64 time=0.310 ms
  64 bytes from 192.168.1.1: icmp_seq=8 ttl=64 time=0.314 ms
  64 bytes from 192.168.1.1: icmp_seq=9 ttl=64 time=0.294 ms
  64 bytes from 192.168.1.1: icmp_seq=10 ttl=64 time=0.296 ms
  64 bytes from 192.168.1.1: icmp_seq=11 ttl=64 time=0.257 ms
  64 bytes from 192.168.1.1: icmp_seq=12 ttl=64 time=0.257 ms
  64 bytes from 192.168.1.1: icmp_seq=13 ttl=64 time=0.308 ms
  64 bytes from 192.168.1.1: icmp_seq=14 ttl=64 time=0.316 ms
  64 bytes from 192.168.1.1: icmp_seq=15 ttl=64 time=0.272 ms

No timed outs, no dropped packats, but I'm not on 1.5.10 either

[eminem093]

As you cand see its meesing some segments this is a short log

PLS any help

root@OpenWrt:/# ping 192.168.1.197
PING 192.168.1.197 (192.168.1.197): 56 data bytes
64 bytes from 192.168.1.197: seq=2 ttl=128 time=1.831 ms
64 bytes from 192.168.1.197: seq=3 ttl=128 time=1.900 ms
64 bytes from 192.168.1.197: seq=4 ttl=128 time=1.876 ms
64 bytes from 192.168.1.197: seq=5 ttl=128 time=1.967 ms
64 bytes from 192.168.1.197: seq=6 ttl=128 time=1.865 ms
64 bytes from 192.168.1.197: seq=8 ttl=128 time=2.002 ms
64 bytes from 192.168.1.197: seq=9 ttl=128 time=2.031 ms
64 bytes from 192.168.1.197: seq=11 ttl=128 time=1.881 ms
64 bytes from 192.168.1.197: seq=12 ttl=128 time=2.021 ms
64 bytes from 192.168.1.197: seq=13 ttl=128 time=1.814 ms
64 bytes from 192.168.1.197: seq=14 ttl=128 time=2.177 ms
64 bytes from 192.168.1.197: seq=15 ttl=128 time=2.067 ms
64 bytes from 192.168.1.197: seq=16 ttl=128 time=2.553 ms
64 bytes from 192.168.1.197: seq=17 ttl=128 time=2.188 ms
64 bytes from 192.168.1.197: seq=18 ttl=128 time=1.983 ms
64 bytes from 192.168.1.197: seq=20 ttl=128 time=1.852 ms
64 bytes from 192.168.1.197: seq=21 ttl=128 time=2.123 ms
64 bytes from 192.168.1.197: seq=23 ttl=128 time=1.905 ms
64 bytes from 192.168.1.197: seq=25 ttl=128 time=1.915 ms
64 bytes from 192.168.1.197: seq=26 ttl=128 time=1.985 ms
64 bytes from 192.168.1.197: seq=27 ttl=128 time=2.143 ms
64 bytes from 192.168.1.197: seq=28 ttl=128 time=2.174 ms
64 bytes from 192.168.1.197: seq=29 ttl=128 time=2.126 ms

To revert back to original firmware without rs232 ttl link follow

setup local ip adres to 192.168.0.66 subnet 255.255.255.0

use tftp server "cisco tftp" used by me

use a original fw without the word boot in the name TL-WDR4300_V1_130319 this version is ok i tested

rename the bin file to wdr4300v1_tp_recovery

set tftp root directory where the file location is

now hold dows wps/reset buton left side on the router

power up the router stil holding the wps/reset buton when the wps symbol
light up let go of wps/reset boton

the router wil ask for fw from tftp server and wil reflash the fw by himsel

this is done by Uboot 1.1.4 june 17 2013

I don't know is this wil work for uboot version diferent then this test it.

Have fun.

by the way the router work as switch wery well so it a driver or switch init problem

please fix it the switch is AR8327N

Thanks