Saludos a todos.
Este material lo hice en inglés para un blog de varios países recopilando la información de Brainslayer y de Shadowandy. Lo integré porque se me presentó una serie de inconvenientes al momento de subir el ap61.ram, estos me sirvieron mucho para lograr actualizar de RedBoot a DD-WRT. También hago unas observaciones en los procesos que se encuentran entre paréntesis o resaltados que no se encontraban en los métodos originales.
Espero te sirva y puedas evitar convertir tu router en un "Brick".
Required
•Download ap61.ram, ap61.rom, linux.bin from DD-WRT on C:
•Install PumpKIN 2.6 TFTP Server.
•Download Putty (telnet client) on C:
NOTE: Before starting I recommend disable the antivirus, firewall and internet connection.
Create a file on C: named redboot.bat with the following content:
rem echo off
:start
rem ------------------------------------------------
ping 192.168.20.81 -n 1 -w 1 > NULL
IF ERRORLEVEL 1 goto start
rem putty
rem ------------------------------------------------
break
putty.exe telnet://192.168.20.81:9000 -m redboot.txt
exit
Create another file on C: named redboot.txt with the following content:
^C
GETTING INTO RedBoot
1.Configure your local (Ethernet) ip to 192.168.20.80 (static) and subnet mask: 255.255.255.0.
2.Unplug power cord and connect your lan cable to WAN port.
3.Execute C:redboot.bat. This begins to ping to the router.
4.Hold reset button and plug the power cord for 10 to 15 seconds.
5.RedBoot> should appear in Putty concole.
If RedBoot prompt doesn’t appear in Putty, repeat steps 2 to 4.
Now execute PumpKin, click on Option button, in TFTP filesystem root choice C: then Ok. Don’t close PumpKin, leave it running.
Let’s start !
LOADING IN THE TEMP BOOT LOADER
============================================================
RedBoot> load ap61.ram
Using default protocol (TFTP)
Entry point: 0×800410bc, address range: 0×80041000-0×800680d8
RedBoot> go
============================================================
It is normal to be disconnected from the telnet session.
Note: Do not reboot the router. Do not disconnect the power cord.
In some cases displays the following error:
============================================================
RedBoot> load ap61.ram
/releases/svn.porsche/redboot-ar231x/redboot-ar231x/redboot_cobra/ecos/packages/devs/eth/mips/ar531x/current/src/ae531xecos.c#390:ae531x_send AHB ERROR: AR531X_DEBUG_ERROR = 0000c34f
/releases/svn.porsche/redboot-ar231x/redboot-ar231x/redboot_cobra/ecos/packages/devs/eth/mips/ar531x/current/src/ae531xecos.c#393:ae531x_send AHB ERROR status_4 = 00000555
/releases/svn.porsche/redboot-ar231x/redboot-ar231x/redboot_cobra/ecos/packages/devs/eth/mips/ar531x/current/src/ae531xecos.c#390:ae531x_send AHB ERROR: AR531X_DEBUG_ERROR = 00000555
/releases/svn.porsche/redboot-ar231x/redboot-ar231x/redboot_cobra/ecos/packages/devs/eth/mips/ar531x/current/src/ae531xecos.c#393:ae531x_send AHB ERROR status_4 = 00000145
Using default protocol (TFTP)
TFTP timed out 1/15
Can't load 'ap61.ram': operation timed out
RedBoot>
============================================================
Do not worry about it, the router must be reboot automatically. If it doesn’t reboot try another PumpKing previous version
LOADING A NEW BOOT LOADER
Before proceeding, change your IP (Ethernet) to 192.168.1.2/255.255.255.0 and then telnet with Putty to the new address 192.168.1.1, port 9000. No longer need the file redboot.bat.
Should appear a new prompt in the console: DD-WRT>
NOTE: Never disconnect the power cord. Do not unplug the patch cord
Here we go:
============================================================
DD-WRT> fconfig -i
Initialize non-volatile configuration – continue (y/n)? y
Run script at boot: false
Use BOOTP for network configuration: true
Default server IP address:
Console baud rate: 9600
GDB connection port: 9000
Force console for special debug messages: false
Network debug at boot time: false
Update RedBoot non-volatile configuration – continue (y/n)? y
… Erase from 0xbffe0000-0xbfff0000: .
… Program from 0×80ff0000-0×81000000 at 0xbffe0000: .
DD-WRT> fis init
About to initialize
FLASH image system – continue (y/n)? y
*** Initialize FLASH Image System
… Erase from 0xbffe0000-0xbfff0000: .
… Program from 0×807f0000-0×80800000 at 0xbffe0000: .
DD-WRT> ip_address -h 192.168.1.2
IP: 192.168.1.1/255.255.255.0, Gateway: 0.0.0.0
Default server: 192.168.1.2
DD-WRT> load -r -b %{FREEMEMLO} ap61.rom
Using default protocol (TFTP)
Raw file loaded 0×80080000-0×800a8717, assumed entry at 0×80080000
DD-WRT> fis create -l 0×30000 -e 0xbfc00000 RedBoot
An image named ‘RedBoot’ exists – continue (y/n)? y
… Erase from 0xbfc00000-0xbfc30000: …
… Program from 0×80080000-0×800a8718 at 0xbfc00000: …
… Erase from 0xbffe0000-0xbfff0000: .
… Program from 0×807f0000-0×80800000 at 0xbffe0000: .
DD-WRT> reset
============================================================
Just wait 3 or 4 minutes to get in DD-WRT> with Putty.
Then
============================================================
DD-WRT> ip_address -h 192.168.1.2
IP: 192.168.1.1/255.255.255.0, Gateway: 0.0.0.0
Default server: 192.168.1.2
DD-WRT> fis init
About to initialize FLASH image system – continue (y/n)? y
*** Initialize FLASH Image System
… Erase from 0xbfc30000-0xbffe0000: …………………………………………………..
… Erase from 0xbffe0000-0xbfff0000: .
… Program from 0×80ff0000-0×81000000 at 0xbffe0000: .
DD-WRT> load -r -b 0×80041000 linux.bin
Using default protocol (TFTP)
Raw file loaded 0×80041000-0×803cffff, assumed entry at 0×80041000
DD-WRT> fis create Linux (Be patient in this case)
… Erase from 0xbfc30000-0xbffbf000: …………………………………………………
… Program from 0×80041000-0×803d0000 at 0xbfc30000: …………………………………………………
… Erase from 0xbffe0000-0xbfff0000: .
… Program from 0×80ff0000-0×81000000 at 0xbffe0000: .
DD-WRT> fconfig boot_script true
boot_script: Setting to true
Update RedBoot non-volatile configuration – continue (y/n)? y
… Erase from 0xbffe0000-0xbfff0000: .
… Program from 0×80ff0000-0×81000000 at 0xbffe0000: .
DD-WRT> fconfig boot_script_timeout 4
boot_script_timeout: Setting to 4
Update RedBoot non-volatile configuration – continue (y/n)? y
… Erase from 0xbffe0000-0xbfff0000: .
… Program from 0×80ff0000-0×81000000 at 0xbffe0000: .
DD-WRT> fconfig bootp false
bootp: Setting to false
Update RedBoot non-volatile configuration – continue (y/n)? y
… Erase from 0xbffe0000-0xbfff0000: .
… Program from 0×80ff0000-0×81000000 at 0xbffe0000: .
DD-WRT> fconfig
Run script at boot: true
Boot script:
.. fis load -l vmlinux.bin.l7 NOT NECCESSARY IN MY CASE
.. exec
Enter script, terminate with empty line
>> fis load -l linux
>> exec
>> (press enter here)
Boot script timeout (1000ms resolution): 4
Use BOOTP for network configuration: false
Gateway IP address:
Local IP address:
Local IP address mask:
Default server IP address:
Console baud rate: 9600
GDB connection port: 9000
Force console for special debug messages: false
Network debug at boot time: false
Update RedBoot non-volatile configuration - continue (y/n)? y
... Erase from 0xbffe0000-0xbfff0000: .
... Program from 0x80ff0000-0x81000000 at 0xbffe0000: .
DD-WRT> fconfig bootp_my_ip 192.168.1.1
bootp_my_ip: Setting to 192.168.1.1
Update RedBoot non-volatile configuration - continue (y/n)? y
... Erase from 0xbffe0000-0xbfff0000: .
... Program from 0x80ff0000-0x81000000 at 0xbffe0000: .
DD-WRT> fconfig bootp_my_ip_mask 255.255.255.0
bootp_my_ip_mask: Setting to 255.255.255.0
Update RedBoot non-volatile configuration - continue (y/n)? y
... Erase from 0xbffe0000-0xbfff0000: .
... Program from 0x80ff0000-0x81000000 at 0xbffe0000: .
DD-WRT> fconfig bootp_my_gateway_ip 0.0.0.0
bootp_my_gateway_ip: Setting to 0.0.0.0
DD-WRT> reset
============================================================
That's all guys !
The default username and password are “root” and “admin” or "admin" and "admin"(without the quotes) respectively. Enjoy your new DIR-300!
Note: Don’t worry if you can’t get an IP from your modem (through the DIR-300 on DD-WRT). It is a bug of DD-WRT. Just reset the modem and the router at the same time and then wait to connect.
NO OLVIDEN ENVIAR SUS COMENTARIOS !
Este material lo hice en inglés para un blog de varios países recopilando la información de Brainslayer y de Shadowandy. Lo integré porque se me presentó una serie de inconvenientes al momento de subir el ap61.ram, estos me sirvieron mucho para lograr actualizar de RedBoot a DD-WRT. También hago unas observaciones en los procesos que se encuentran entre paréntesis o resaltados que no se encontraban en los métodos originales.
Espero te sirva y puedas evitar convertir tu router en un "Brick".
FLASHING ROUTER D-LINK DIR-300 TO DD-WRT
Required
•Download ap61.ram, ap61.rom, linux.bin from DD-WRT on C:
•Install PumpKIN 2.6 TFTP Server.
•Download Putty (telnet client) on C:
NOTE: Before starting I recommend disable the antivirus, firewall and internet connection.
Create a file on C: named redboot.bat with the following content:
rem echo off
:start
rem ------------------------------------------------
ping 192.168.20.81 -n 1 -w 1 > NULL
IF ERRORLEVEL 1 goto start
rem putty
rem ------------------------------------------------
break
putty.exe telnet://192.168.20.81:9000 -m redboot.txt
exit
Create another file on C: named redboot.txt with the following content:
^C
GETTING INTO RedBoot
1.Configure your local (Ethernet) ip to 192.168.20.80 (static) and subnet mask: 255.255.255.0.
2.Unplug power cord and connect your lan cable to WAN port.
3.Execute C:redboot.bat. This begins to ping to the router.
4.Hold reset button and plug the power cord for 10 to 15 seconds.
5.RedBoot> should appear in Putty concole.
If RedBoot prompt doesn’t appear in Putty, repeat steps 2 to 4.
Now execute PumpKin, click on Option button, in TFTP filesystem root choice C: then Ok. Don’t close PumpKin, leave it running.
Let’s start !
LOADING IN THE TEMP BOOT LOADER
============================================================
RedBoot> load ap61.ram
Using default protocol (TFTP)
Entry point: 0×800410bc, address range: 0×80041000-0×800680d8
RedBoot> go
============================================================
It is normal to be disconnected from the telnet session.
Note: Do not reboot the router. Do not disconnect the power cord.
In some cases displays the following error:
============================================================
RedBoot> load ap61.ram
/releases/svn.porsche/redboot-ar231x/redboot-ar231x/redboot_cobra/ecos/packages/devs/eth/mips/ar531x/current/src/ae531xecos.c#390:ae531x_send AHB ERROR: AR531X_DEBUG_ERROR = 0000c34f
/releases/svn.porsche/redboot-ar231x/redboot-ar231x/redboot_cobra/ecos/packages/devs/eth/mips/ar531x/current/src/ae531xecos.c#393:ae531x_send AHB ERROR status_4 = 00000555
/releases/svn.porsche/redboot-ar231x/redboot-ar231x/redboot_cobra/ecos/packages/devs/eth/mips/ar531x/current/src/ae531xecos.c#390:ae531x_send AHB ERROR: AR531X_DEBUG_ERROR = 00000555
/releases/svn.porsche/redboot-ar231x/redboot-ar231x/redboot_cobra/ecos/packages/devs/eth/mips/ar531x/current/src/ae531xecos.c#393:ae531x_send AHB ERROR status_4 = 00000145
Using default protocol (TFTP)
TFTP timed out 1/15
Can't load 'ap61.ram': operation timed out
RedBoot>
============================================================
Do not worry about it, the router must be reboot automatically. If it doesn’t reboot try another PumpKing previous version
LOADING A NEW BOOT LOADER
Before proceeding, change your IP (Ethernet) to 192.168.1.2/255.255.255.0 and then telnet with Putty to the new address 192.168.1.1, port 9000. No longer need the file redboot.bat.
Should appear a new prompt in the console: DD-WRT>
NOTE: Never disconnect the power cord. Do not unplug the patch cord
Here we go:
============================================================
DD-WRT> fconfig -i
Initialize non-volatile configuration – continue (y/n)? y
Run script at boot: false
Use BOOTP for network configuration: true
Default server IP address:
Console baud rate: 9600
GDB connection port: 9000
Force console for special debug messages: false
Network debug at boot time: false
Update RedBoot non-volatile configuration – continue (y/n)? y
… Erase from 0xbffe0000-0xbfff0000: .
… Program from 0×80ff0000-0×81000000 at 0xbffe0000: .
DD-WRT> fis init
About to initialize
FLASH image system – continue (y/n)? y
*** Initialize FLASH Image System
… Erase from 0xbffe0000-0xbfff0000: .
… Program from 0×807f0000-0×80800000 at 0xbffe0000: .
DD-WRT> ip_address -h 192.168.1.2
IP: 192.168.1.1/255.255.255.0, Gateway: 0.0.0.0
Default server: 192.168.1.2
DD-WRT> load -r -b %{FREEMEMLO} ap61.rom
Using default protocol (TFTP)
Raw file loaded 0×80080000-0×800a8717, assumed entry at 0×80080000
DD-WRT> fis create -l 0×30000 -e 0xbfc00000 RedBoot
An image named ‘RedBoot’ exists – continue (y/n)? y
… Erase from 0xbfc00000-0xbfc30000: …
… Program from 0×80080000-0×800a8718 at 0xbfc00000: …
… Erase from 0xbffe0000-0xbfff0000: .
… Program from 0×807f0000-0×80800000 at 0xbffe0000: .
DD-WRT> reset
============================================================
Just wait 3 or 4 minutes to get in DD-WRT> with Putty.
Then
============================================================
DD-WRT> ip_address -h 192.168.1.2
IP: 192.168.1.1/255.255.255.0, Gateway: 0.0.0.0
Default server: 192.168.1.2
DD-WRT> fis init
About to initialize
FLASH image system – continue (y/n)? y
*** Initialize FLASH Image System
… Erase from 0xbfc30000-0xbffe0000: …………………………………………………..
… Erase from 0xbffe0000-0xbfff0000: .
… Program from 0×80ff0000-0×81000000 at 0xbffe0000: .
DD-WRT> load -r -b 0×80041000 linux.bin
Using default protocol (TFTP)
Raw file loaded 0×80041000-0×803cffff, assumed entry at 0×80041000
DD-WRT> fis create Linux (Be patient in this case)
… Erase from 0xbfc30000-0xbffbf000: …………………………………………………
… Program from 0×80041000-0×803d0000 at 0xbfc30000: …………………………………………………
… Erase from 0xbffe0000-0xbfff0000: .
… Program from 0×80ff0000-0×81000000 at 0xbffe0000: .
DD-WRT> fconfig boot_script true
boot_script: Setting to true
Update RedBoot non-volatile configuration – continue (y/n)? y
… Erase from 0xbffe0000-0xbfff0000: .
… Program from 0×80ff0000-0×81000000 at 0xbffe0000: .
DD-WRT> fconfig boot_script_timeout 4
boot_script_timeout: Setting to 4
Update RedBoot non-volatile configuration – continue (y/n)? y
… Erase from 0xbffe0000-0xbfff0000: .
… Program from 0×80ff0000-0×81000000 at 0xbffe0000: .
DD-WRT> fconfig bootp false
bootp: Setting to false
Update RedBoot non-volatile configuration – continue (y/n)? y
… Erase from 0xbffe0000-0xbfff0000: .
… Program from 0×80ff0000-0×81000000 at 0xbffe0000: .
DD-WRT> fconfig
Run script at boot: true
Boot script:
.. fis load -l vmlinux.bin.l7 NOT NECCESSARY IN MY CASE
.. exec
Enter script, terminate with empty line
>> fis load -l linux
>> exec
>> (press enter here)
Boot script timeout (1000ms resolution): 4
Use BOOTP for network configuration: false
Gateway IP address:
Local IP address:
Local IP address mask:
Default server IP address:
Console baud rate: 9600
GDB connection port: 9000
Force console for special debug messages: false
Network debug at boot time: false
Update RedBoot non-volatile configuration - continue (y/n)? y
... Erase from 0xbffe0000-0xbfff0000: .
... Program from 0x80ff0000-0x81000000 at 0xbffe0000: .
DD-WRT> fconfig bootp_my_ip 192.168.1.1
bootp_my_ip: Setting to 192.168.1.1
Update RedBoot non-volatile configuration - continue (y/n)? y
... Erase from 0xbffe0000-0xbfff0000: .
... Program from 0x80ff0000-0x81000000 at 0xbffe0000: .
DD-WRT> fconfig bootp_my_ip_mask 255.255.255.0
bootp_my_ip_mask: Setting to 255.255.255.0
Update RedBoot non-volatile configuration - continue (y/n)? y
... Erase from 0xbffe0000-0xbfff0000: .
... Program from 0x80ff0000-0x81000000 at 0xbffe0000: .
DD-WRT> fconfig bootp_my_gateway_ip 0.0.0.0
bootp_my_gateway_ip: Setting to 0.0.0.0
DD-WRT> reset
============================================================
That's all guys !
The default username and password are “root” and “admin” or "admin" and "admin"(without the quotes) respectively. Enjoy your new DIR-300!
Note: Don’t worry if you can’t get an IP from your modem (through the DIR-300 on DD-WRT). It is a bug of DD-WRT. Just reset the modem and the router at the same time and then wait to connect.
NO OLVIDEN ENVIAR SUS COMENTARIOS !