When I saw that the firmware was from 2013, I updated the latest 2019 version dd-wrt.v24-41027_NEWD-2_K2.6_mini-e900.bin
I extracted it from the same page, just different year, I thought they were all stable: ftp://ftp.dd-wrt.com/betas
The router now turns on, DHCP works assign ip, I can ping 192.168.1.1, I see the ddwrt wifi signal open. If I connect the wan port the internet works.
But it is impossible to access the configuration website http://192.168.1.1/ or https://192.168.1.1/
The page does not access either by cable or by wifi.
Try to update the firmware using TFTP either by command line, or by Windows GUI TFTP Utility. From Windows 10, Windows XP and Debian Linux.
I did it as indicated, in the period of the first ignition, I see that a LED enters programming mode and that both by command line and the application gui say that the file was transferred correctly, but when I turn off and on it remains the same.
Try this process to revert to different versions of ddwrt as well as the manufacturer's firmware. It does the programming process but it's not really reprogramming it.
I appreciate any help you can give me, the router is new.
I repeat, turn on everything seems to walk but the config page is not allowed to access. I did several reset 30-30-30
Note: Sorry for the syntax, I use google translator
When I saw that the firmware was from 2013, I updated the latest 2019 version dd-wrt.v24-41027_NEWD-2_K2.6_mini-e900.bin
[...]I see that a LED enters programming mode and that both by command line and the application gui say that the file was transferred correctly, but when I turn off and on it remains the same.
Try this process to revert to different versions of ddwrt as well as the manufacturer's firmware. It does the programming process but it's not really reprogramming it.
Can you login via telnet? If so (and the current build is still after 18 Apr 2018), try running*: nvram erase && reboot
Were you TFTP'ing various k2.6 mini e900 builds? If not, try that. If so, then do this:
-TFTP back to OEM firmware
-GUI reset (or hold button until the lights flash)
-flash DD from GUI again: 21676_NEWD-2_K2.6_mini-e900.bin
-GUI reset (or hold button until the lights flash)
-flash k3x from GUI: 33772_k3.x_mega-nv64k.bin (try the e900 trailed build if that fails)
-(set password and) login to telnet then run* `erase nvram && reboot`
*The `erase nvram` vs `nvram erase` difference is intentional.
Then manually set up, and run that for a couple weeks before trying latest builds. And always read the new build threads first; the E900 and E1200 series are finicky. _________________ #NAT/SFE/CTF: limited speed w/ DD#Repeater issues#DD-WRT info: FAQ, Builds, Types, Modes, Changes, Demo#
OPNsense x64 5050e ITX|DD: DIR-810L, 2*EA6900@1GHz, R6300v1, RT-N66U@663, WNDR4000@533, E1500@353,
WRT54G{Lv1.1,Sv6}@250|FreshTomato: F7D8302@532|OpenWRT: F9K1119v1, RT-ACRH13, R6220, WNDR3700v4
Pinging 192.168.1.1 with 32 bytes of data:
Response from 192.168.1.1: bytes = 32 time <1m TTL = 64
Response from 192.168.1.1: bytes = 32 time <1m TTL = 64
Response from 192.168.1.1: bytes = 32 time <1m TTL = 64
Response from 192.168.1.1: bytes = 32 time <1m TTL = 64
Ping statistics for 192.168.1.1:
Packages: sent = 4, received = 4, lost = 0
(0% lost),
Approximate round trip times in milliseconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms
C: \ Windows \ system32> telnet 192.168.1.1
Connecting to 192.168.1.1 ... Cannot open connection to host, on port 23: Connection failed
C: \ Windows \ system32>
Try updating the firmware using tftp.exe and tftp2.exe from the ddwrt and linksys pages, disabling firewall and antivirus from Windows 10 and Windows XP, and it still says "firmware update sucefull" does not work. I also did it from the Windows and Linux console. I did it with several versions DDWRT and with firmware versions of the manufacturer.
Joined: 08 May 2018 Posts: 14216 Location: Texas, USA
Posted: Tue Sep 17, 2019 20:17 Post subject:
Seems like there is and isn't an issue with reset to defaults with the latest build. But, you should be able to TFTP stock or and older build back to it. Ping, power, put.
Response from 192.168.1.1: bytes = 32 time <1m TTL = 64
Response from 192.168.1.1: bytes = 32 time <1m TTL = 64
Response from 192.168.1.1: bytes = 32 time <1m TTL = 64
Response from 192.168.1.1: bytes = 32 time <1m TTL = 64
Ping statistics for 192.168.1.1:
Packages: sent = 4, received = 4, lost = 0
(0% lost),
Approximate round trip times in milliseconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms
C: \> tftp -i 192.168.1.1 put dd-wrt.v24-21676_NEWD-2_K2.6_mini-e900.bin
Timeout
C: \>
It clearly does not respond.
But if I use TFTP when the router is initializing, and the wps LED is blinking I get the following:
Code:
C: \> tftp -i 192.168.1.1 put dd-wrt.v24-21676_NEWD-2_K2.6_mini-e900.bin
Transfer completed: 3548160 bytes in 16 seconds, 221760 bytes / s
C: \>
But the router remains the same, try this on all ports, and with different versions of the firm.
I think the next thing is to get a serial usb adapter and investigate that process. But I know all about it. I still don't understand much how it works.
The DHCP LAN ports work, the WAN port works, I have wifi SSID DDWRT open but I do not have access to 192.168.1.1 either by web or telnet or by lan or wifi.
If someone still has another idea, it is appreciated.
I'm from Argentina, thanks and sorry for my syntax.
The google translator must be horrible. =)
Joined: 08 May 2018 Posts: 14216 Location: Texas, USA
Posted: Tue Sep 17, 2019 22:29 Post subject:
You may have to TFTP stock firmware back onto the router first, perhaps, but serial recovery is also an option. If you have read the serial recovery wiki and found the correct pinout information for hooking up the serial adapter, then the process isn't too difficult.
If I use TFTP when the router has been on for several minutes and the wps LED is solid fixed, I get the following: [...]
It clearly does not respond.
Ya, that won't work.
elotrohernan wrote:
it still says "firmware update sucefull" does not work. I also did it from the Windows and Linux console. I did it with several versions DDWRT and with firmware versions of the manufacturer.
[...]
But if I use TFTP when the router is initializing, and the wps LED is blinking I get the following:
Code:
C: \> tftp -i 192.168.1.1 put dd-wrt.v24-21676_NEWD-2_K2.6_mini-e900.bin
Transfer completed: 3548160 bytes in 16 seconds, 221760 bytes / s
C: \>
But the router remains the same, try this on all ports, and with different versions of the firm.
If the OEM f/w doesn't work either, then yes you will need to use serial recovery. _________________ #NAT/SFE/CTF: limited speed w/ DD#Repeater issues#DD-WRT info: FAQ, Builds, Types, Modes, Changes, Demo#
OPNsense x64 5050e ITX|DD: DIR-810L, 2*EA6900@1GHz, R6300v1, RT-N66U@663, WNDR4000@533, E1500@353,
WRT54G{Lv1.1,Sv6}@250|FreshTomato: F7D8302@532|OpenWRT: F9K1119v1, RT-ACRH13, R6220, WNDR3700v4
