MN-700

From DD-WRT Wiki

(Difference between revisions)
Jump to: navigation, search
Revision as of 01:20, 21 September 2006 (edit)
Siafu (Talk | contribs)

← Previous diff
Revision as of 01:25, 21 September 2006 (edit) (undo)
Siafu (Talk | contribs)

Next diff →
Line 2: Line 2:
== Introduction == == Introduction ==
The [http://review.zdnet.com/Microsoft_MN_700_wireless_broadband_router/4507-3319_16-30540105.html|Microsoft MN-700] is essentially a rebadged Asus WL500G WRT. Out-of-the-box it runs a WinCE based firmware with a crippled bootloader that does not support Linux based firmwares (like DD-WRT). To run DD-WRT, a new bootloader must be installed through a hardware hack (until someone comes up with a WinCE killer like the vxworks killer for the Linksys WRT54G v5. The following links provide details regarding this hack:<br /> The [http://review.zdnet.com/Microsoft_MN_700_wireless_broadband_router/4507-3319_16-30540105.html|Microsoft MN-700] is essentially a rebadged Asus WL500G WRT. Out-of-the-box it runs a WinCE based firmware with a crippled bootloader that does not support Linux based firmwares (like DD-WRT). To run DD-WRT, a new bootloader must be installed through a hardware hack (until someone comes up with a WinCE killer like the vxworks killer for the Linksys WRT54G v5. The following links provide details regarding this hack:<br />
-* [http://www.liamm.com/?p=77 LiamM.com]+<blockquote>
-* [http://wl500g.info/showthread.php?t=1616 Microsoft MN700 Hack Project] AsusForums+*[http://www.liamm.com/?p=77 LiamM.com]
-* [http://www.techimo.com/forum/t157288.html TechIMO.com] version of LiamM's hack+*[http://wl500g.info/showthread.php?t=1616 Microsoft MN700 Hack Project] AsusForums
 +*[http://www.techimo.com/forum/t157288.html TechIMO.com] version of LiamM's hack
 +</blockquote>
For those who are wondering, the MN-500 has completely different hardware than the MN-700, so the instructions provided by the links above work for the MN-700 but not the MN-500. To date, it does not appear a similar hack for the MN-500 has been discovered yet. For those who are wondering, the MN-500 has completely different hardware than the MN-700, so the instructions provided by the links above work for the MN-700 but not the MN-500. To date, it does not appear a similar hack for the MN-500 has been discovered yet.

Revision as of 01:25, 21 September 2006

Contents

Introduction

The MN-700 is essentially a rebadged Asus WL500G WRT. Out-of-the-box it runs a WinCE based firmware with a crippled bootloader that does not support Linux based firmwares (like DD-WRT). To run DD-WRT, a new bootloader must be installed through a hardware hack (until someone comes up with a WinCE killer like the vxworks killer for the Linksys WRT54G v5. The following links provide details regarding this hack:

For those who are wondering, the MN-500 has completely different hardware than the MN-700, so the instructions provided by the links above work for the MN-700 but not the MN-500. To date, it does not appear a similar hack for the MN-500 has been discovered yet.

Installation

  1. Follow one (or a combination) of the hardware hack guides listed in the Introduction section above to get the WL500G Stock Firmware, Oleg's Custom Firmware, or OpenWRT installed and running on the MN-700.
  2. Put the WRT in "hardware restoration" mode (hold down the reset button while powering on the WRT and wait until the the power light steadily alternates between green and amber).
  3. Upload a DD-WRT firmware with the Asus Firmware Restoration tool.

Post Installation

Firmware SVN 3949 and later (post SP2) does not require any additional, post installation steps. Firmware versions prior to this build require some nvram variables to be manually reset before the firmware will function properly (changes made to the WRT will not survive a reboot and may cause the WRT to hang when booting with an amber power light).

  1. Boot the WRT after installing the firmware
  2. Reset the filter_services2 NVRAM variable by executing the following commands either by telneting to the WRT or using the Administration -> Commands interface:
nvram set filter_services2=
nvram commit

If the WRT continues to have problems with changes surviving a reboot, reset the remaining 6 filter_services nvram variables (filter_services1, filter_services2, ... filter_services7)

External Links