Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
| toh:netgear:dg834g [2018/02/20 18:51] – ↷ Links adapted because of a move operation bobafetthotmail | toh:netgear:dg834g [2021/12/05 11:52] (current) – Brand name capitalization adjusted tmomas | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| - | ====== | + | ====== |
| + | |||
| + | {{section> | ||
| ===== Release Status ===== | ===== Release Status ===== | ||
| Line 15: | Line 17: | ||
| * Only WEP encryption is available in Wifi settings! not sure why - stock Netgear firmware supported WPA-PSK - need to check, may be a package install issue? | * Only WEP encryption is available in Wifi settings! not sure why - stock Netgear firmware supported WPA-PSK - need to check, may be a package install issue? | ||
| - | [http:// | + | [[http:// |
| - | [https:// | + | [[https:// |
| * Further upgrade(s) via web and sysupgrade command not supported, manual upgrade required, here’s how to do that at the device cmdline: < | * Further upgrade(s) via web and sysupgrade command not supported, manual upgrade required, here’s how to do that at the device cmdline: < | ||
| - | (NB .trx and .bin interchangeable) [doc: | + | (NB .trx and .bin interchangeable) |
| ===== Hardware Versions ===== | ===== Hardware Versions ===== | ||
| Line 30: | Line 32: | ||
| ==== Clones ==== | ==== Clones ==== | ||
| - | * [[toh/sphairon/turbolinkjdr454wb|Sphairon JDR454WB]] | + | * [[toh:sphairon:turbolinkjdr454wb|Sphairon JDR454WB]] |
| Line 37: | Line 39: | ||
| The ADAM2 bootloader in v3 is different, and cannot be patched as shown below. It does not seem to be needed anyway. Another important difference is that the bootloader does not allow FTP access nor interruption of the boot from the serial console, so recovery can only be done with the Windows recovery tool or the nftp.2 tool described below. | The ADAM2 bootloader in v3 is different, and cannot be patched as shown below. It does not seem to be needed anyway. Another important difference is that the bootloader does not allow FTP access nor interruption of the boot from the serial console, so recovery can only be done with the Windows recovery tool or the nftp.2 tool described below. | ||
| - | The old wiki has information for this particular model: [[oldwiki/ | + | The old wiki has information for this particular model: [[https:// |
| - | See also: http:// | + | See also: [[http:// |
| ===== Installation for v1 and v2 ===== | ===== Installation for v1 and v2 ===== | ||
| Line 76: | Line 78: | ||
| ==== Telnet to the Router ==== | ==== Telnet to the Router ==== | ||
| - | * Enable debug mode. Visit http:// | + | * Enable debug mode. Visit '' |
| * Telnet into your router < | * Telnet into your router < | ||
| telnet 192.168.0.1</ | telnet 192.168.0.1</ | ||
| Line 85: | Line 87: | ||
| ==== Obtaining your current Bootloader ==== | ==== Obtaining your current Bootloader ==== | ||
| - | * Enable debug mode. Visit http:// | + | * Enable debug mode. Visit '' |
| * Telnet into your router < | * Telnet into your router < | ||
| telnet 192.168.0.1</ | telnet 192.168.0.1</ | ||
| Line 123: | Line 125: | ||
| ==== Replace the restricted ADAM2 on the router ==== | ==== Replace the restricted ADAM2 on the router ==== | ||
| - | * Place the Modified mtd2.bin onto a web or FTP server (e.g http:// | + | * Place the Modified mtd2.bin onto a web or FTP server (e.g '' |
| * for this you can enable IIS on your PC to serve the directory containing the firmware files. Google for details on how to do this. | * for this you can enable IIS on your PC to serve the directory containing the firmware files. Google for details on how to do this. | ||
| * Don't forget to update the firewall on your PC to allow access to the relevant port. | * Don't forget to update the firewall on your PC to allow access to the relevant port. | ||
| Line 337: | Line 339: | ||
| - | See [[docs: | + | See [[docs:techref: |
| The onboard Flash Chip for V1 is a 4MB 29DL32BF-70PFTN when manipulating this chip from JTAG software such as TJTAG it may not be detected, in such cases masquerading as/forcing use of either the MBM29DL323BE or AM29LV320 chips will likely work (This has worked for the user Funkimunk, your mileage may vary). | The onboard Flash Chip for V1 is a 4MB 29DL32BF-70PFTN when manipulating this chip from JTAG software such as TJTAG it may not be detected, in such cases masquerading as/forcing use of either the MBM29DL323BE or AM29LV320 chips will likely work (This has worked for the user Funkimunk, your mileage may vary). | ||