Posted: Mon Jan 17, 2022 16:28 Post subject: Serial Flash version location
Trying out DD-WRT on my Belkin F5D7231-4 v1102. I see in the db for the model that the serial flash version needs to be used. Is that in a separate tree or am I missing something?
Joined: 08 May 2018 Posts: 14246 Location: Texas, USA
Posted: Mon Jan 17, 2022 19:38 Post subject:
Ping router IP; apply power to router; put firmware image via tftp client. OR, ping router IP; put firmware image via tftp client; apply power to router. Timing is everything. Per the wiki, firmware images are located in one of the following locations:
OK, this is maddening. Not my first rodeo. I've done a lot of Linksys router flashes but this is my first Belkin. Can get to the router homepage (192.168.2.1) can ping it but TFTP doesn't work. Never get an ACK back. I've done the 30/30/30 as well.
-d
daldrich$ ping 192.168.2.1
PING 192.168.2.1 (192.168.2.1): 56 data bytes
64 bytes from 192.168.2.1: icmp_seq=0 ttl=64 time=0.935 ms
64 bytes from 192.168.2.1: icmp_seq=1 ttl=64 time=1.042 ms
64 bytes from 192.168.2.1: icmp_seq=2 ttl=64 time=1.020 ms
64 bytes from 192.168.2.1: icmp_seq=3 ttl=64 time=1.055 ms
^C
--- 192.168.2.1 ping statistics ---
4 packets transmitted, 4 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 0.935/1.013/1.055/0.047 ms
daldrich$ tftp
tftp> connect 192.168.2.1
tftp> mode binary
tftp> verbose
Verbose mode on.
tftp> trace
Packet tracing on.
tftp> rexmt 1
tftp> timeout 60
tftp> put dd-wrt.v24_micro_generic.bin
putting dd-wrt.v24_micro_generic.bin to 192.168.2.1:dd-wrt.v24_micro_generic.bin [octet]
sent WRQ <file=dd-wrt.v24_micro_generic.bin, mode=octet>
sent WRQ <file=dd-wrt.v24_micro_generic.bin, mode=octet>
sent WRQ <file=dd-wrt.v24_micro_generic.bin, mode=octet>
sent WRQ <file=dd-wrt.v24_micro_generic.bin, mode=octet>
sent WRQ <file=dd-wrt.v24_micro_generic.bin, mode=octet>
…
sent WRQ <file=dd-wrt.v24_micro_generic.bin, mode=octet>
Joined: 08 May 2018 Posts: 14246 Location: Texas, USA
Posted: Tue Jan 18, 2022 0:22 Post subject:
Your pings are arriving after the bootloader / firmware is up (TTL=64); you are not getting the TTL=100 or TTL=128. It is strictly a timing issue. Which client OS are you using? I generally have been in the habit of putting an unmanaged switch between client and router, ping the "correct" IP address from client, put the file via whichever TFTP client, and immediately apply power.
