Dlink dir 100 page loading error

dlink dir 100 page loading error

When the router is being loaded, the LEDs are blinking If the error “The page cannot be displayed” (or “Unable to display the page”/“ Could not. D-Link DIR rev B1, WavePlus, 1 MiB1,, B 8, Kib
Dlink dir 100 page loading error - casual concurrence

D-Link DIR

From DD-WRT Wiki

Jump to: navigation, search

8 ETHERNET PORTS FOR UNLIMITED CONNECTIVITY TO ALL YOUR DEVICES

Delivering great wireless performance, network security and coverage, the D-Link Wireless N 8-Port Router (DIR) is ideal for building a powerful network. Designed to do the heavy-lifting and get your small business humming, 8 ports let you connect just about anything you can imagine, all at once - printers, laptops, desktops, security cameras, servers, storage drives - you name it, the DIR can handle it. It also serves as an excellent home router, since it's ideal for providing wired Internet connectivity for video, music, photos, and documents.

[edit]Pros of this hardware

  • Runs standard version of DD-WRT
  • Eight (8) wired ports, at 10/ speed.
  • New Harware. n WiFi
  • Easy to install DD-WRT
  • One USB Port
  • Great range, signal strength and stability

[edit]Cons of this hardware

  • The biggest knock about this router is it's frequent WIFI drops and lockups when using the stock firmware. Installing DD-WRT corrects this isssue.
  • No gigabit / speed LAN support.
  • No Wireless AC / IEEE ac.

[edit]Specifications

Power in ~V A, Power Out 5V A
PCB ver. A1
D-Link Firmware dated /11/26
CPU AR or AR @ Mhz(MIPS32 24Kc).
Wireless NIC AR
Ethernet Ports 1x WAN RJ 10/ Base T, 8x LAN RJ 10/ Base T
Switch chip RTLG
ROM size 8mb <= The D-Link official rom is mb
RAM 32MB
USB ports 1x USB, can connect to a USB hub, for more usb devices sharing.
USB 3G It support D-Link its own DWM 3G nic.
Antennas 2x antennas
FCC ID KA2IRA1
Wireless standards supported b (max. 11 Mbit/s), g (max. 54 Mbit/s), n (max. Mbit/s, GHz only)

[edit]Main board

This shows the main board for the DIR along with the location for the SERIAL and JTAG headers.
This shows the main board for the DIR along with the location for the SERIALand JTAGheaders.

Please note that is is pre-release firmware at the momment. Please read the support forum listed at the bottom of this page before loading it on you router to avoid bricking it.

[edit]Out-of-the-box factory firmware upgrade

To install dd-wrt on a stock D-Link DIR, you can flash it directly from the router's web admin page (yes, that is correct from D-Link's standard web interface). These are the steps to follow:

  1. Download the current firmware:
    1. NA (North America) - Factory-to-ddwrt r See Where do I download firmware? for links.
    2. AP (Asia Pasific) - Download the NA version of the firmware, then use a Hex Editor to modify the signature at the end of the file. Change AARRT to AARRT
    3. WW (Any place else in the world) - Download the NA version of the firmware, then use a Hex Editor to modify the signature at the end of the file. Change AARRT to AARRT
  2. Connect to the DIR using an Ethernet cable.
  3. Open http:/// in your web browser (Firefox recommended), which should open the DIR's administrative page from the standard D-link firmware.
    1. The D-link's default login details are user "admin", password is blank.
    2. Tools -> Firmware
    3. Click "browse" button -> select the "factory-to-ddwrt_sprers.eu" file -> click "Upload" button.
    4. Wait 2 or 3 minutes for the DIR to flash and do the update. You will see a status page that shows you the progress as it happens. After the flash & update is done, the router will reboot to dd-wrt, and the IP address will have changed to There is no need to reset.
  4. Open http:/// in web browser. This should open DD-WRT's web interface. Configure DD-WRT as desired.
  5. You're finished! No need to 30/30/30 hard reset, but you can reboot your router after several minutes. (I don't know if it has to build anything in NVRAM, but better safe than sorry.)

[edit]How to upgrade with new DD-WRT firmware

  1. Download the "dira-firmware" from one of the links from Where do I download firmware?, then pick a recent directory, then use the "dlink-dira" directory.
  2. Open the DD-WRT's web interface in your web browser. It's http:/// by default.
  3. Administration tab -> "Firmware Upgrade" button
  4. Click "browse" button -> select the "sprers.eu" file -> click "Upgrade" button. It will take about 2 minutes to upload and write the flash. Your browser will reload and let you know when it is done.
  5. It is probably a good idea to reboot after updating. That's it.

[edit]How to reset the Router to initial DD-WRT configuration

If you forget the username or password, or if the configuration becomes really messed up, you can always clear all the non-volitile parameters by doing a 'factory reset'. To do this, with the router already fully booted, press and hold the reset button for 5~6 seconds and release. The router will boot back up and answer to just as if it had just been flashed with DD-WRT.

[edit]How to restore to factory firmware

This has been tested by GottaBKD

  1. Download the original firmware from sprers.eu%/Firmware/DIRA1_sprers.eu
  2. Unplug everything from the router including power and any LAN/WAN cables
  3. Hold down reset button with a pin or bent paperclip for 10 seconds
  4. While still holding reset button down, plug router back in and hold down the reset button until the status light continually flashes orange
  5. Configure a Windows 7 computer with IP address in the , subnet , Gateway , DNS
  6. Plug ethernet cable into computer and a LAN port on the router, do not use WAN
  7. Open FIREFOX, I could only get this to work in FIREFOX, download it if you don't have it. CHROME and IE would not work, they just hang when it looks like they are working! I spent ages trying to get it to work in IE, then downloaded firefox and it worked first try.
  8. Type into firefox, this should bring up the emergency recovery page
  9. Click browse and select your firmware file
  10. Click send, and let it do it's magic, this may take a minute or 2, be patient, if it works your status light will turn green, you are supposed to get a page that says upload succeeded, I waited 5 minutes and it didn't happen. It still worked.
  11. Reset router by holding down reset button for 10 seconds, status light will go orange again but don't worry it is just rebooting.
  12. You should be good to go, open a new browser window and type and you should get the Dlink login page. If this doesn't work, try again from step 1

What follows are the steps needs to use storage devices connected to the routers USB port.

  1. Connect the USB device to the Router.
  2. Restart the router.
  3. Open the DD-WRT's web interface in your web browser. It's http:/// by default.
  4. Services -> USB
    1. Enable Core USB Support
    2. Enable USB Storage Support
    3. Enable Automatic Drive Mount
    4. Select Save, and then Apply
    • You can ignore the Status: Not mounted message

[edit]FTP Access

Once set up, you will be able to access all the mounted partitions by using ftp://

  1. Serices -> NAS
  2. Enable ProFTPD
  3. Select other settings and then select Save, and then Apply

[edit]File Sharing Access

Once set up, you can access your files using Universal Naming Convention (UNC) names; ex. \\\part1. Storage devices can be format as Fat16, Fat32, NTFS, and Ext2. The Ext3 drive format is not support, and will not mount.

  1. Serices -> NAS
  2. Add Share
  3. Select the Share's Path, enter and name, and indicate is it's public or not. If it's pubic you do not have to add users.
  4. Repeat 2 and 3 for each share
  5. Select Save, and then Apply
Image:Samba Share sprers.eu
  • If you plan to add user, do so after adding the shares.

Note: There is currently a limit of the size of Hard Drive that can be connected: 2TB and under only. Also formatting the drive as EXT2 will give you better performance over NTFS. Use the GParted Live image to reform your hard drive.

What follows are the steps needs to use printer devices connected to the routers USB port.

  1. Connect the USB device to the Router.
  2. Restart the router.
  3. Open the DD-WRT's web interface in your web browser. It's http:/// by default.
  4. Services -> USB
    1. Enable Core USB Support
    2. Enable USB Printer Support
    3. Select Save, and then Apply

[edit]Using the printer in Windows 7

  • Open Control Panel, Devices and Printers
  • Choose Add a printer, and then Add a Local Printer
  • select Create a new port, and choose Type of port: Standard TCP/IP Port. Click Next
  • Enter the IP address or your router: If you like you can give the port a name.
  • UNCHECK the checkbox to Query the printer and automatically select a driver use. Click Next. Now wait until the detection is done. It will say that the device is not found. Don't despair
  • Choose Custom and then click Settings
    • Make sure that Protocol Raw is selected and Port is entered. That will be proposed.
    • Leave all other settings also as they were and click OK
  • Click Next.
  • Choose the printer driver for your printer, then click Next
  • Give your printer a name, , then click Next
  • You don't have to share the printer. click Next
  • You can set it as default printer if your would like.
  • Click Finish

Don't forget that your routers default address is and its port is

  • Wireless Security WPA2 does not work with i Touches. Use WPA instead with AES or TKIP+AES encryption.
  • When mounting USB devices, an odd message is produced indicating Status: Not mounted. This can be ignored. Fixed in beta versions (since at least March ).
  • Can only load on the NA (North American) versions of the router. You need to Hex Edit the NA firmware to load elsewhere per the instructions.
  • The undocumented button on the right side, near the front is a WDS or Wireless Distribution System button. It's not used.
  • The WiFi Led doesn't light up. Not really a problem. Fixed in beta versions (since at least March ).
  • Support Thread: See Forum it's getting long.

Category: D-Link guides

0xe] === max[

D-Link DIR rev A

#Loading runtime image Imag Start Address =0xbe Find a 7zip self-decompressed kernel image, Just GO! Powered by Realtek RTLB SoC, rev 1 CPU revision is: ff00 Init MMU (16 entries) Primary instruction cache 0kB, linesize 0 bytes. Primary data cache 0kB, linesize 0 bytes. Linux version uc0 ([email protected]) (gcc version ) #1 Fri Apr 25 CST Determined physical RAM map: memory: @ (usable) NOFS reserved @ 0xbba0 On node 0 totalpages: zone(0): pages. zone(1): 0 pages.</code> zone(2): 0 pages. Kernel command line: root=/dev/mtdblock3 rootfstype=squashfs IRR(0)=c Calibrating delay loop BogoMIPS Memory: k/k available (k kernel code, k reserved, k data, k init, 0k highmem) Dentry cache hash table entries: (order: 2, bytes) Inode cache hash table entries: (order: 1, bytes) Mount cache hash table entries: (order: 0, bytes) Buffer cache hash table entries: (order: 0, bytes) Page-cache hash table entries: (order: 2, bytes) Checking for 'wait' instruction unavailable. POSIX conformance testing by UNIFIX NEW PCI DriverisLinuxCompliantEndianMode=False(Big Endian) [PCI] Reset Bridge Finish! No PCI device exist!! Linux NET for Linux Based upon Swansea University Computer Society NET Initializing RT netlink socket Starting kswapd pty: Unix98 ptys configured Serial driver version c () with MANY_PORTS SERIAL_PCI enabled Probing RTL home gateway controller Initialize RTLx ASIC and driver chip name: B, chip revid: 1 Initialize mbuf creating default 2 interfaceseth0 IRR(6)=c eth1 OK >>>now is rome running DQoS module initialization success! PPP generic driver version PPP BSD Compression module registered Amd/Fujitsu Extended Query Table v at 0x number of CFI chips: 1 cfi_cmdset_ Disabling fast programming due to code brokenness. Looking for mtd device mtd1: Found a mtd1 image (0x), with size (0x). Looking for mtd device mtd2: Found a mtd2 image (0x), with size (0x9daa0). Looking for mtd device mtd3: Found a mtd3 image (0xcdaa0), with size (0xfe). Creating 4 MTD partitions on "Physically mapped flash": 0xx&#;: "ldr" 0xx&#;: "alphafs" 0xxcdaa0&#;: "kernel" 0xcdaaxcbaa0&#;: "squashfs" NET4: Linux TCP/IP for NET IP Protocols: ICMP, UDP, TCP, IGMP IP: routing cache hash table of buckets, 4Kbytes TCP: Hash tables configured (established bind ) GRE over IPv4 tunneling driver ip_conntrack version ( buckets, max) - bytes per conntrack ip_tables: (C) Netfilter core team NET4: Unix domain sockets /SMP for Linux NET VFS: Mounted root (squashfs filesystem) readonly. Freeing unused kernel memory: k freed IRR(3)=c initial console created on /dev/ttyS1 Shell invoked to run file: /etc/rc Command: mount -t proc proc /proc Command: mount -t ramfs ramfs /var Command: mkdir /var/tmp Command: mkdir /var/ppp/ Command: mkdir /var/log Command: mkdir /var/run Command: mkdir /var/lock Command: mkdir /var/flash Command: #iwcontrol is required for RTL Wireless driver Command: #iwcontrol auth & Command: Command: #busybox insmod /lib/modules/uc0/kernel/drivers/usb/quickcam.o Command: Command: /bin/webs -u root -d /www -i /var/run/sprers.eu & [9] Command: Command: #ifconfig wlan0 up promisc Command: Command: Command: Execution Finished, Exiting Sash command shell (version ) /> System initializingCheck the crc=0xd,file_des->chksum=0xd! Config info: table total size[ 0x]! rtl_user_pid set to 9 WAN/LAN, Rx shift= runDNSProxy session 0 do not have dns server ip [16] cfg wan to dhcp client Set IGMP Default Upstream interface (eth0) SUCCESS!! [22] info, client (vpre) started [24] url filter default set to accept PPPoE Passthru disabled. Drop Unknown PPPoE PADT disabled. IPv6 Passthru disabled. IPX Passthru disabled. NETBIOS Passthru disabled. WebReset drule=0 moteAccessConfig ReadPPPoESessionInfo: idx=0 id = 0 ReadPPPoESessionInfo: idx=1 id = 0 /www/Status/st_sprers.eu: No such file or directory killall: neaps: no process killed pid failed [29] [31] get lan ip c0a enable 1 my host is =sprers.eu=buffer from user space=QoSEnable=0 DetectWanBand=0&#;! Find a pair, argumenit=QoSEnable, value=0!pBuf=DetectWanBand=0&#;! Find a pair, argumenit=DetectWanBand, value=0!pBuf=! tmpUpBW=0, tmpRsBW=0! get parameter: DQoS_enable= 0! get parameter: upLinkBandWidth=0 kbits! get parameter: VoIP reserved bandwidth=0 kbits! interface: eth1 config : /var/sprers.eu get vendor = ALPHA get model = DIR get version = v get secret = admin <== password for http login eth1: ip, mask, mac ec eth1 (ip) = , (netmask) = , adapter index 3 adapter hardware address ec Into Server listen!! nothing to monitor [35] info, server (vpre) started error, max_leases value () not sane, setting to 99 instead error, Unable to open /var/sprers.eu for reading auto ,en ,dir = /www dhcpc client deconfig ifCfgParam[0].ipAddr: ifCfgParam[0].ipMask: ifCfgParam[0].gwAddr: ifCfgParam[0].dnsPrimaryAddr: rtl_delNaptMapping: ret -6 rtl_delRoute(default): ret -3 rtl_delIpIntf: ret target SIOCDELRT: No such process

D-Link DIR - Multiple Vulnerabilities

Offensive Security The Exploit Database is maintained by Offensive Security, an information security training company that provides various Information Security Certifications as well as high end penetration testing services. The Exploit Database is a non-profit project that is provided as a public service by Offensive Security.

The Exploit Database is a CVE compliant archive of public exploits and corresponding vulnerable software, developed for use by penetration testers and vulnerability researchers. Our aim is to serve the most comprehensive collection of exploits gathered through direct submissions, mailing lists, as well as other public sources, and present them in a freely-available and easy-to-navigate database. The Exploit Database is a repository for exploits and proof-of-concepts rather than advisories, making it a valuable resource for those who need actionable data right away.

The Google Hacking Database (GHDB) is a categorized index of Internet search engine queries designed to uncover interesting, and usually sensitive, information made publicly available on the Internet. In most cases, this information was never meant to be made public but due to any number of factors this information was linked in a web document that was crawled by a search engine that subsequently followed that link and indexed the sensitive information.

The process known as “Google Hacking” was popularized in by Johnny Long, a professional hacker, who began cataloging these queries in a database known as the Google Hacking Database. His initial efforts were amplified by countless hours of community member effort, documented in the book Google Hacking For Penetration Testers and popularised by a barrage of media attention and Johnny’s talks on the subject such as this early talk recorded at DEFCON Johnny coined the term “Googledork” to refer to “a foolish or inept person as revealed by Google“. This was meant to draw attention to the fact that this was not a “Google problem” but rather the result of an often unintentional misconfiguration on the part of a user or a program installed by the user. Over time, the term “dork” became shorthand for a search query that located sensitive information and “dorks” were included with may web application vulnerability releases to show examples of vulnerable web sites.

After nearly a decade of hard work by the community, Johnny turned the GHDB over to Offensive Security in November , and it is now maintained as an extension of the Exploit Database. Today, the GHDB includes searches for other online search engines such as Bing, and other online repositories like GitHub, producing different, yet equally valuable results.

ETHERNET BROADBAND ROUTER

DIR

QUICK

INSTALLATION

GUIDE

INSTALLATIONSANLEITUNG

GUIDE D'INSTALLATION

GUÍA DE INSTALACIÓN

GUIDA DI INSTALLAZIONE

INSTALLATIEHANDLEIDING

INSTRUKCJA INSTALACJI

INSTALAČNÍ P&#x;ÍRUČKA

TELEPÍTÉSI SEGÉDLET

INSTALLASJONSVEILEDNING

INSTALLATIONSVEJLEDNING

ASENNUSOPAS

INSTALLATIONSGUIDE

GUIA DE INSTALAÇÃO

Ο&#x;&#x;&#x;ΌΣ &#x;Ρ&#x;&#x;ΟΡ&#x;Σ &#x;&#x;Κ&#x;Τ&#x;ΣΤ&#x;Σ&#x;Σ ΤΟ

VODIČ ZA BRZU INSTALACIJU

KRATKA NAVODILA ZA UPORABO

GHID DE INSTALARE RAPID&#x;

Table of Contents

loading

  Related Manuals for D-Link DIR

  Summary of Contents for D-Link DIR

ManualsLib

ManualsLib

This device is NOT RECOMMENDED for future use with OpenWrt due to low flash/ram.
DO NOT BUY DEVICES WITH 4MB FLASH / 32MB RAM if you intend to flash an up-to-date and secure OpenWrt version ( or later) onto it! See 4/32 warning for details.

1) This device does not have sufficient resources (flash and/or RAM) to provide secure and reliable operation.
This means that even setting a password or changing simple network settings might not be possible any more, rendering the device effectively useless. See OpenWrt on 4/32 devices what you can do now.

2) OpenWrt support for this device will end after
will be the last official build for 4/32 devices. After , no further OpenWrt images will be built for 4/32 devices. See OpenWrt on 4/32 devices what you can do now.

Version/Model S/N OpenWrt Version Supported Model Specific Notes
A1 - Kamikaze -
Bx - other hardware see DIR Rev.B

:!:NOTE: Because of Ticket OpenWrt &#;Backfire&#; wasn&#;t working. In r () this issue has been fixed. So avoid OpenWrt and use OpenWrt &#;Kamikaze&#;, a trunk version newer then r or the newest OpenWrt &#;Backfire&#;. Enjoy.

Before you install, you might need to back up the original firmware. It can be done in multiple ways, including but not limited to using UART and/or Telnet. The most important partition is Board/RadioCfg, which is physically located at last 64KiB of flash chip.

# cat /proc/mtd dev: size erasesize name mtd0: "spiflash" mtd1: ce "rootfs" mtd2: b "upgrade" mtd3: "rgdb" mtd4: "RedBoot" mtd5: "Board/RadioCfg" mtd6: "LangPack" mtd7: "flash"

Partition sizes correspond to DIR v_a firmware. While upgrade partition has multiple sections, only has got its own mtd device file.

Layer0 raw flash, mtd0 and mtd7, KiB
Layer1 mtd4

KiB
mtd2

KiB
mtd6

64 KiB
mtd3

64 KiB
mtd5

64 KiB
Layer2 No device

KiB
PackImg
header
32B
mtd1

KiB
empty
space
B
No device

KiB

When original firmware is flashed onto the router, first 96B are stripped, since it&#;s a header of some kind. The rest of it is written directly to partition. Knowing this allows restoring original firmware from an alternative firmware, such as OpenWrt. A command such as allows to prepare file suitable for writing directly onto mtd partition.

The data on the end of upgrade partition is likely remaining from past installation of some alt firmware and not used for anything.

First let&#;s have a quick view at the Flash Layout with the stock firmware and once OpenWrt has been installed onto the device. This helper understanding what mtd/sysupgrade does.
The D-Link DIR Rev.A1 uses this flash Layout:

Layer0 raw flash, KiB
Layer1 mtd0

KiB
mtd1

MiB
mtd3

MiB
“”,
mtd4

KiB
mtd5

KiB
mtd6

KiB
Layer2 mtd2

KiB
“”, JFFS2

:!: Notes: As opposed to other devices, there is no OpenWrt partition, so you cannot address it with . The explanation for this is, that the “FIS” (File Information System) must be adjusted every time the flash is written. Unfortunately, cannot do that, and thus cannot be used to do updates. Instead, is used for updates.

If you need to backup SPI flash you don&#;t need mtd2(rootfs_data) partition. You need to join 0,1,3,4,5,6 with cat command like:

cat /dev/mtd0 > /tmp/dir_full_sprers.eu cat /dev/mtd1 >> /tmp/dir_full_sprers.eu cat /dev/mtd3 >> /tmp/dir_full_sprers.eu cat /dev/mtd4 >> /tmp/dir_full_sprers.eu cat /dev/mtd5 >> /tmp/dir_full_sprers.eu cat /dev/mtd6 >> /tmp/dir_full_sprers.eu

Then you can save your SPI flash somewhere safe with:

scp /tmp/dir_full_sprers.eu [email protected]:/path

Some users have reported that the JFFS version of OpenWrt can remove the area of the flash. If you need to restore to the original firmware or to the emergency redboot web flash page at any point, instructions are here

Note My DIR takes ridiculously long to boot. I measured about 70 seconds after power connection has been established until I can connect to the bootloader and about seconds until I can telnet/ssh to the OpenWrt! Maybe this is normal, maybe I miss-configured the replacement bootloader at the first time installation. FYI.

In order to replace the original firmware with OpenWrt, you will need to replace the BootLoader as well. RedBoot is OpenSource software and we are going to replace the original one with a modified one here or from the DD-Wrt-Project. For the first time installation of OpenWrt on the D-Link DIR (Rev.A1) or on the Airlink ARW/ARW you need to obtain 4 files from the Internet and have a tfpd (i.e. daemon, not client) running.

First you should install a tfpt-daemon and change into its root directory. After installation it will be automatically started. In Ubuntu do:

sudo aptitude install tftpd-hpa cd /var/lib/tftpboot

Now download the four files directly into this directory. You only need sudo, because as a normal user you cannot write in here:

sudo wget sprers.eu%20WiSoc/Airlink%%20ARW/apram sudo wget sprers.eu%20WiSoc/Airlink%%20ARW/aprom sudo wget sprers.eu sudo wget sprers.eu

Let&#;s assume, you have only one NIC in you PC, while keeping you browser with this page open so you can read on, you will need to give yourself the IP Now before you proceed, due to compatibility issues, you need to create the ~/.telnetrc. It has to contain the following:

Connect your NIC to the -Port of the DIR and then restart the Router. While it reboots, after about 5 sec, there is a window of about 1 sec, during which you should be able to login to the original BootLoader of the DIR Simply repeat this, until success:

telnet

This is not a big deal, and you should be successful at first try. You will be presented with the original RedBoot prompt eagerly awaiting your input:

Now we will get and execute the modified (and temporary) RedBoot from the DD-Wrt-Project:

Redboot> load apram go

or split over two commands (if you get an error with the above)

Redboot> load apram Redboot> go

You will get no feedback and nothing has been written onto the flash yet, but the new temporary BootLoader should be running. To communicate with it, you need to change your own IP from to and reconnect the ethernet cable to one of the LAN-Ports of the Router. Then telnet to it:

The modified (and temporary) BootLoader awaits you.

Now you need to make things permanent. For this we will use the other file, the aprom:

DD-WRT>fis init About to initialize [format] FLASH image system - continue (y/n)? y *** Initialize FLASH Image System Erase from 0xbffexbfff . Program from 0xfx at 0xbffe . DD-WRT>ip_address -h IP: /, Gateway: Default server: DD-WRT>load -r -b %{FREEMEMLO} aprom Using default protocol (TFTP) Raw file loaded 0xxa, assumed entry at 0x DD-WRT>fis create -l 0x -e 0xbfc RedBoot An image named &#;RedBoot&#; exists - continue (y/n)? y Erase from 0xbfcxbfc Program from 0xxa at 0xbfc Erase from 0xbffexbfff . Program from 0xfx at 0xbffe . DD-WRT>fconfig bootp false bootp: Setting to false Update RedBoot non-volatile configuration - continue (y/n)? y Erase from 0xbffexbfff . Program from 0x80ffx at 0xbffe . DD-WRT>reset

The Router will reboot, it should take about a minute. You login again to the modified (but this time persistent) BootLoader, load and fis the OpenWrt-Images onto the flash and configure the BootLoader:

DD-WRT>fis init About to initialize [format] FLASH image system - continue (y/n)? y *** Initialize FLASH Image System Erase from 0xbffexbfff . Program from 0xfx at 0xbffe . DD-WRT>ip_address -h IP: /, Gateway: Default server: DD-WRT>load -r -b %{FREEMEMLO} sprers.eu Using default protocol (TFTP) Raw file loaded 0xxff, assumed entry at 0x DD-WRT>fis create -e 0x -r 0x sprers.eul7 Erase from 0xbfcxbfcf Program from 0xx at 0xbfc Erase from 0xbffexbfff . Program from 0x80ffx at 0xbffe . DD-WRT>load -r -b %{FREEMEMLO} sprers.eufs Using default protocol (TFTP) Raw file loaded 0xxff, assumed entry at 0x&#;&#; DD-WRT>fis create rootfs Erase from 0xbfcfxbffe Program from 0xx at 0xbfcf Erase from 0xbffexbfff . Program from 0x80ffx at 0xbffe . DD-WRT>fconfig boot_script_timeout 5 DD-WRT>fconfig boot_script true Run script at boot: true DD-WRT>fconfig Run script at boot: true Boot script: Enter script, terminate with empty line >> fis load -l sprers.eul7 >> exec >> Boot script timeout (ms resolution): 5 Use BOOTP for network configuration: false Gateway IP address: Local IP address: Local IP address mask: Default server IP address: Console baud rate: GDB connection port: Force console for special debug messages: false Network debug at boot time: false Update RedBoot non-volatile configuration - continue (y/n)? y Erase from 0xbffexbfff . Program from 0x80ffx at 0xbffe .&#;&#; DD-WRT>reset

And we are done. This time the reboot could take up to minutes, so be patient.

:!: If you don&#;t trust the script below (it loads some binary from some blog, use the step by step guideline above ;-)

For linux there is shell script called dirflash; it wraps the manual steps for replacing the original bootloader and/or flashing firmware images into a single command line. The script requires a tftp-daemon to be already running. See –help for further details. Usage:

For reflashing via the bootloader do: You have to compile by your own - Not enough memory to boot the openwrt. Example of configuration where device boot fine - No gui/www, no dhcp server, only ssh.

On tftp server, two files are needed:

sprers.eu sprers.eu

Connect to telnet to port

fis init ip_address -h load -r -b %{FREEMEMLO} sprers.eu fis create -e 0x -r 0x sprers.eul7 load -r -b %{FREEMEMLO} sprers.eu fis create rootfs

For reflashing via the bootloader do:

fis init ip_address -h load -r -b %{FREEMEMLO} sprers.eu fis create -e 0x -r 0x sprers.eul7 load -r -b %{FREEMEMLO} sprers.eufs fis create rootfs

If your router have already had DD-WRT installed, there will be a chance that the existing bootloader is MicroRedboot. In that case, the router boots rather fast, you cannot telnet to at start up. You will have to use Reset button to access Redboot. See sprers.eu for more detail.

If you have already followed this guide and your router is running OpenWrt, but because of some reason you still want to reflash using the bootloader you can access Redboot after seconds from powering the device up with the following command:

telnet

LUCI

  1. Go to System > Flash firmware

  2. Point to that you have downloaded

  3. Upload image

  4. Flash it

Terminal

  1. download the combined firmware from OpenWrt to your router:cd /tmp wget sprers.eu wget sprers.eu
  2. utilize : sysupgrade /tmp/sprers.eu

download sprers.eu to c:\ create a file on c:\ called sprers.eu, with the following content:

create a file on c:\ called sprers.eu with the following content:

start the bat file and power on the router…sprers.eu comes redboot

Architecture MIPS
Vendor Atheros
Bootloader redboot
System-On-Chip AR (MIPS 4KEc V)
CPU Speed Mhz
Flash chip Spansion FLAIF (V)
Flash size 4 MiB (32MBit)
RAM chip ESMT M12LA (SDRAM)
RAM size 16 MiB (MBit; 2M x 16 Bit x 4 Banks)
Wireless Integrated Atheros b/g
Ethernet IC Plus c
USB No
Serial Yes
JTAG Yes

→ JP1

speed ,n,8.

If you just see non-printable characters in the console, you may want to change baudrate. In some case, where MicroRedboot is install, the speed is

→ J6

The router follows the MIPS EJTAG Specification and has the same PIN information. But on the board the PINS are laid out as

1 - nTRST 2 - GND 3 - TDI 4 - GND 5 - TDO 6 - GND 7 - TMS
14 - VCC 13 - N/C 12 - N/C 11 - nSRST 10 - GND 9 - TCK 8 - GND

The default network configuration is:

Interface Name Description Default configuration
br-lan LAN & WiFi /24
eth LAN ports (1 to 4) None
eth WAN port DHCP
ath0 WiFi Disabled

To enable WiFi, you need to install packages and .

Numbers are Ports as labeled on the unit, number 4 is the Internet (WAN) on the unit, 5 is the internal connection to the router itself. Don&#;t be fooled: Port 1 on the unit is number 3 when configuring VLANs. vlan0 = eth, vlan1 = eth and so on.

Port Internet (WAN) LAN 1 LAN 2 LAN 3 LAN 4
Switch port 4 3 2 1 0

Assuming OpenWrt is already installed, log on the the device via SSH, then do:

Copy the file (with scp, for example) to your local computer and generate a MD5-checksum for it.

if it equals with B9DED01D3EDFAB2AF63FC22 it is probalby safe to go on. Load the file into a hex editor and

MD5 checksums:

Copy the modded sprers.eu back to the /tmp folder of your router and flash it back:

Reboot, then check CPU frequency:

There is a working mod to add a SD-card slot to your DIR Follow the instructions here.

[ ] Linux version ([email protected]) (gcc version (OpenWrt GCC ra6e11ccb13)) #0 Wed Aug 29 [ ] bootconsole [early0] enabled [ ] CPU0 revision is: (MIPS 4KEc) [ ] Determined physical RAM map: [ ] memory: @ (usable) [ ] Initrd not found or empty - disabling initrd [ ] Primary instruction cache 16kB, VIPT, 4-way, linesize 16 bytes. [ ] Primary data cache 16kB, 4-way, VIPT, no aliases, linesize 16 bytes [ ] Zone ranges: [ ] Normal [mem 0xxffffff] [ ] Movable zone start for each node [ ] Early memory node ranges [ ] node 0: [mem 0xxffffff] [ ] Initmem setup node 0 [mem 0xxffffff] [ ] On node 0 totalpages: [ ] free_area_init_node: node 0, pgdat ed20, node_mem_map [ ] Normal zone: 32 pages used for memmap [ ] Normal zone: 0 pages reserved [ ] Normal zone: pages, LIFO batch:0 [ ] random: get_random_bytes called from 0xa with crng_init=0 [ ] pcpu-alloc: s0 r0 d u alloc=1* [ ] pcpu-alloc: [0] 0 [ ] Built 1 zonelists, mobility grouping off. Total pages: [ ] Kernel command line: console=ttyS0, rootfstype=squashfs,jffs2 [ ] PID hash table entries: 64 (order: -4, bytes) [ ] Dentry cache hash table entries: (order: 1, bytes) [ ] Inode-cache hash table entries: (order: 0, bytes) [ ] Memory: K/K available (K kernel code, K rwdata, K rodata, K init, K bss, K reserved, 0K cma-reserved) [ ] SLUB: HWalign=32, Order=, MinObjects=0, CPUs=1, Nodes=1 [ ] NR_IRQS: [ ] clocksource: MIPS: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: ns [ ] sched_clock: 32 bits at 92MHz, resolution 10ns, wraps every ns [ ] Calibrating delay loop BogoMIPS (lpj=) [ ] pid_max: default: minimum: [ ] Mount-cache hash table entries: (order: 0, bytes) [ ] Mountpoint-cache hash table entries: (order: 0, bytes) [ ] clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: ns [ ] futex hash table entries: (order: -1, bytes) [ ] NET: Registered protocol family 16 [ ] Can&#;t analyze schedule() prologue at ebb8 [ ] clocksource: Switched to clocksource MIPS [ ] NET: Registered protocol family 2 [ ] TCP established hash table entries: (order: 0, bytes) [ ] TCP bind hash table entries: (order: 0, bytes) [ ] TCP: Hash tables configured (established bind ) [ ] UDP hash table entries: (order: 0, bytes) [ ] UDP-Lite hash table entries: (order: 0, bytes) [ ] NET: Registered protocol family 1 [ ] PCI: CLS 0 bytes, default 16 [ ] Radio config found at offset 0xf8 (0x1f8) [ ] Crashlog allocated RAM at address 0xf [ ] workingset: timestamp_bits=30 max_order=12 bucket_order=0 [ ] squashfs: version (/01/31) Phillip Lougher [ ] jffs2: version (NAND) (SUMMARY) (LZMA) (RTIME) (CMODE_PRIORITY) (c) Red Hat, Inc. [ ] io scheduler noop registered [ ] io scheduler deadline registered (default) [ ] Serial: / driver, 1 ports, IRQ sharing disabled [ ] serial ttyS0 at MMIO 0x (irq = 9, base_baud = ) is a A [ ] console [ttyS0] enabled [ ] bootconsole [early0] disabled [ ] arspiflash arspiflash Kbytes flash detected [ ] Searching for RedBoot partition table in spiflash at offset 0x3d [ ] Searching for RedBoot partition table in spiflash at offset 0x3e [ ] 6 RedBoot partitions found on MTD device spiflash [ ] Creating 6 MTD partitions on "spiflash": [ ] 0xx : "RedBoot" [ ] 0xx : "sprers.eul7" [ ] 0xxe : "rootfs" [ ] mtd: device 2 (rootfs) set to be root filesystem [ ] 1 squashfs-split partitions found on MTD device rootfs [ ] 0xdxe : "rootfs_data" [ ] 0xexef : "FIS directory" [ ] 0xefxf : "RedBoot config" [ ] 0xfx : "boardconfig" [ ] eth0: Atheros ARx: ef:8e, irq 4 [ ] IP17xx: Found IPC at [ ] libphy: arx_eth_mii: probed [ ] eth0: attached PHY driver [IC+ IP17xx] (mii_bus:phy_addr=) [ ] NET: Registered protocol family 17 [ ] q: Q VLAN Support v [ ] VFS: Mounted root (squashfs filesystem) readonly on device [ ] Freeing unused kernel memory: K [ ] This architecture does not have kernel memory protection. [ ] random: fast init done [ ] init: Console is alive [ ] init: - watchdog - [ ] kmodloader: loading kernel modules from /etc/modules-boot.d/* [ ] kmodloader: done loading kernel modules from /etc/modules-boot.d/* [ ] init: - preinit - [ ] eth0: link up (Mbps/full duplex) [ ] mount_root: jffs2 not ready yet, using temporary tmpfs overlay [ ] urandom-seed: Seed file not found (/etc/sprers.eu) [ ] procd: - early - [ ] procd: - watchdog - [ ] procd: - watchdog - [ ] procd: - ubus - [ ] random: ubusd: uninitialized urandom read (4 bytes read) [ ] random: ubusd: uninitialized urandom read (4 bytes read) [ ] random: ubusd: uninitialized urandom read (4 bytes read) [ ] procd: - init - [ ] kmodloader: loading kernel modules from /etc/modules.d/* [ ] Loading modules backported from Linux version wtgfefc2c [ ] Backport generated by sprers.eu vrcg86cf0e5d [ ] ath: EEPROM regdomain: 0x0 [ ] ath: EEPROM indicates default country code should be used [ ] ath: doing EEPROM country->regdmn map search [ ] ath: country maps to regdmn code: 0x3a [ ] ath: Country alpha2 being used: US [ ] ath: Regpair used: 0x3a [ ] ieee phy0: Selected rate control algorithm &#;minstrel_ht&#; [ ] ath5k: phy0: Atheros AR chip found (MAC: 0x90, PHY: 0x48) [ ] kmodloader: done loading kernel modules from /etc/modules.d/* [ ] urandom_read: 4 callbacks suppressed [ ] random: jshn: uninitialized urandom read (4 bytes read) [ ] random: jshn: uninitialized urandom read (4 bytes read) [ ] random: jshn: uninitialized urandom read (4 bytes read) [ ] jffs2_scan_eraseblock(): End of filesystem marker found at 0x0 [ ] jffs2_build_filesystem(): unlocking the mtd device [ ] done. [ ] jffs2_build_filesystem(): erasing all blocks after the end marker [ ] eth0: link up (Mbps/full duplex) [ ] br-lan: port 1(eth) entered blocking state [ ] br-lan: port 1(eth) entered disabled state [ ] device eth entered promiscuous mode [ ] device eth0 entered promiscuous mode [ ] br-lan: port 1(eth) entered blocking state [ ] br-lan: port 1(eth) entered forwarding state [ ] done. [ ] jffs2: notice: () jffs2_build_xattr_subsystem: complete building xattr subsystem, 0 of xdatum (0 unchecked, 0 orphan) and 0 of xref (0 dead, 0 orphan) found. [ ] overlayfs: upper fs does not support tmpfile. [ ] random: crng init done

How to add tags

ath25, 4Flash, 16RAM, bg, 1Ant, DetachableAntenna, FastEthernet, 1NIC, 1WNIC, 5Port, JTAG, MIPS, MIPS32, 4KEc

This website uses cookies. By using the website, you agree with storing cookies on your computer. Also you acknowledge that you have read and understand our Privacy Policy. If you do not agree leave the sprers.eu information about cookies

0 Comments

Leave a Comment