User Tools

Site Tools


d-link_dir-3001

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
Last revision Both sides next revision
d-link_dir-3001 [2012/02/11 09:49]
ispyisail
d-link_dir-3001 [2012/07/25 08:39]
ispyisail telnet should now work
Line 5: Line 5:
 WARNING: This document may contain errors which may result in damage to your router. USE AT YOUR OWN RISK. WARNING: This document may contain errors which may result in damage to your router. USE AT YOUR OWN RISK.
 </alertbox> </alertbox>
 +{{INLINETOC 2 4 }} 
 **Airlink101 AR430W** **Airlink101 AR430W**
  
 The D-link/Airlink is very similar to the La Fonera but only has 4MB of flash memory, it uses an atheros wireless device, and second you must access the RedBoot bootloader to install OpenWrt/Gargoyle. It is impossiable to install Gargoyle on a factory default DIR-300, so be warned that it is not as straightforward as with the other routers. The D-link/Airlink is very similar to the La Fonera but only has 4MB of flash memory, it uses an atheros wireless device, and second you must access the RedBoot bootloader to install OpenWrt/Gargoyle. It is impossiable to install Gargoyle on a factory default DIR-300, so be warned that it is not as straightforward as with the other routers.
  
-It appears that Dlink in there wisdom have changed the chipset of the DIR-300. **This procedure only works for revision A**+<alertbox> 
 +This how-to has been updated 25 July 2012 and now should work without the need for a serial connection 
 + 
 +</alertbox> 
 + 
 +It appears that Dlink in there wisdom have changed the chipset of the DIR-300.  
 + 
 +**This procedure only works for revision A**
  
 This procedure has been tested and works with This procedure has been tested and works with
Line 48: Line 55:
  
 back to the redboot enter: back to the redboot enter:
 +
   load ap61.ram   load ap61.ram
-  go+  go 
  
 Now a new temporarily bootloader should start. (on serial console it will display some warnings. but you don't need to worry about this) Now a new temporarily bootloader should start. (on serial console it will display some warnings. but you don't need to worry about this)
Line 58: Line 66:
  
  
-<shell> +  fis init 
-DD-WRT> fis init +  About to initialize [format] FLASH image system - continue (y/n)? y 
-About to initialize [format] FLASH image system - continue (y/n)? y +  *** Initialize FLASH Image System 
-*** Initialize FLASH Image System +  ... Erase from 0xbffe0000-0xbfff0000:
-... Erase from 0xbffe0000-0xbfff0000:+  ... Program from 0x807f0000-0x80800000 at 0xbffe0000:  
-... Program from 0x80ff0000-0x81000000 at 0xbffe0000: . + 
-DD-WRT> ip_address -h 192.168.1.2 +  ip_address -h 192.168.1.2 
-DD-WRT> load -r -b %{FREEMEMLO} gargoyle_1.0.14-atheros-vmlinux.lzma +  IP: 192.168.1.1/255.255.255.0, Gateway: 0.0.0.0 
-Using default protocol (TFTP) +  Default server: 192.168.1.2 
-Raw file loaded 0x80040800-0x801007ff, assumed entry at 0x80040800 + 
-DD-WRT> fis create -e 0x80041000 -r 0x80041000 vmlinux.bin.l7 +  load -r -b %{FREEMEMLO} ap61.rom 
-... Erase from 0xbfc30000-0xbfcf0000............ +  Using default protocol (TFTP) 
-... Program from 0x80040800-0x80100800 at 0xbfc30000............ +  Raw file loaded 0x80080000-0x800a8717, assumed entry  at 0x80080000 
-... Erase from 0xbffe0000-0xbfff0000:+ 
-... Program from 0x80ff0000-0x81000000 at 0xbffe0000: . +  fis create -l 0x30000 -e 0xbfc00000 RedBoot 
-DD-WRT> load -r -b %{FREEMEMLO} gargoyle_1.0.14-atheros-root.squashfs +  An image named 'RedBoot' exists continue (y/n)? y 
-Using default protocol (TFTP) +  ... Erase from 0xbfc00000-0xbfc30000: ... 
-Raw file loaded 0x80040800-0x802207ff, assumed entry at 0x80040800 +  ... Program from 0x80080000-0x800a8718 at 0xbfc00000 ... 
-DD-WRT> fis create rootfs +  ... Erase from 0xbffe0000-0xbfff0000:
-... Erase from 0xbfcf0000-0xbffb0000: ............................................... +  ... Program from 0x807f0000-0x80800000 at 0xbffe0000: . 
-... Program from 0x80040800-0x80220800 at 0xbfcf0000.............................. + 
-... Erase from 0xbffe0000-0xbfff0000: + 
-... Program from 0x80ff0000-0x81000000 at 0xbffe0000: . +  fconfig boot_script true 
-DD-WRT> fconfig +  fconfig boot_script_timeout 10 
-Run script at boot: true +  fconfig bootp false 
-Boot script: +  fconfig bootp_my_gateway_ip 192.168.1.
-Enter script, terminate with empty line +  fconfig bootp_my_ip 192.168.1.
->> fis load -l vmlinux.bin.l7 +  fconfig bootp_my_ip_mask 255.255.255.
->> exec +  fconfig bootp_server_ip 192.168.1.254 
->> +  fconfig console_baud_rate 9600 
-Boot script timeout (1000ms resolution): 10 +  fconfig gdb_port 9000 
-Use BOOTP for network configuration: true +  fconfig info_console_force false 
-Gateway IP address: 192.168.1.1 +  fconfig net_debug false 
-Console baud rate: 9600 + 
-GDB connection port: 9000 +  fconfig boot_script_data 
-Force console for special debug messages: false + 
-Network debug at boot time: false +  boot_script_data
-Update RedBoot non-volatile configuration - continue (y/n)? y +  .. fis load -l vmlinux.bin.l7 
-... Erase from 0xbffe0000-0xbfff0000:+  .. exec 
-... Program from 0x80ff0000-0x81000000 at 0xbffe0000: . +  Enter script, terminate with empty line 
-DD-WRT> reset+  >> fis load -l vmlinux.bin.l7 
 +  >> exec 
 +  >> 
 +  Update RedBoot non-volatile configuration - continue (y/n)? y 
 +  ... Erase from 0xbffe0000-0xbfff0000:
 +  ... Program from 0x80ff0000-0x81000000 at 0xbffe0000: . 
 +  DD-WRT> 
 + 
 +  DD-WRT> reset 
  
-</shell> 
  
 now the unit will reboot and the new bootloader will be executed and is waiting for your connection. now the unit will reboot and the new bootloader will be executed and is waiting for your connection.
d-link_dir-3001.txt · Last modified: 2015/09/01 21:34 by nworbnhoj