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
toh:netgear:dg834g [2015/12/30 16:48] – [Installation for v1 and v2] matchtoh:netgear:dg834g [2021/12/05 11:52] (current) – Brand name capitalization adjusted tmomas
Line 1: Line 1:
-====== Netgear DG834G ======+====== NETGEAR DG834G ====== 
 + 
 +{{section>meta:infobox:432_warning#infobox_for_dataentries&noheader&nofooter&noeditbutton}}
  
 ===== 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://oldwiki.openwrt.org/OpenWrtDocs(2f)WhiteRussian(2f)Configuration.html#head-f335c44d5b896564e2fb57831ceb0ab3958a668a] suggests that a package called “nas” is needed, but that does not exist in the backfire packages available from [http://downloads.openwrt.org/backfire/10.03/ar7/packages/] - however there are some “wpa-*” packages there. +[[http://oldwiki.openwrt.org/OpenWrtDocs(2f)WhiteRussian(2f)Configuration.html#head-f335c44d5b896564e2fb57831ceb0ab3958a668a]] suggests that a package called “nas” is needed, but that does not exist in the backfire packages available from [[http://downloads.openwrt.org/backfire/10.03/ar7/packages/]] - however there are some “wpa-*” packages there. 
-[https://forum.openwrt.org/viewtopic.php?id=24493] suggests that wpad-mini is needed for WPA and wpad for WPA Enterprise - yet to confirm that this works - doubtful as that topic refers to Broadcom chipsets so it may not work on TI AR7 ... [http://www.lizardking.biz/2010/03/qwest-actiontec-gt701-wg-ppoe-openwrt/] seems to reinforce +[[https://forum.openwrt.org/viewtopic.php?id=24493]] suggests that wpad-mini is needed for WPA and wpad for WPA Enterprise - yet to confirm that this works - doubtful as that topic refers to Broadcom chipsets so it may not work on TI AR7 ... [[http://www.lizardking.biz/2010/03/qwest-actiontec-gt701-wg-ppoe-openwrt/]] seems to reinforce 
  
   * Further upgrade(s) via web and sysupgrade command not supported, manual upgrade required, here’s how to do that at the device cmdline: <code>mtd -r write firmware.trx linux</code>   * Further upgrade(s) via web and sysupgrade command not supported, manual upgrade required, here’s how to do that at the device cmdline: <code>mtd -r write firmware.trx linux</code>
-  (NB .trx and .bin interchangeable) [doc:howto:installing#flashing.openwrt]+  (NB .trx and .bin interchangeable) [[doc:howto:installing#flashing.openwrt]]
  
 ===== 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/openwrtdocs/hardware/netgear/dg834gv3]]+The old wiki has information for this particular model: [[https://wiki.openwrt.org/oldwiki/openwrtdocs/hardware/netgear/dg834gv3]]
  
-See also: http://www.pitt-pladdy.com/blog/_20100424-103102+0100%20OpenWrt%20Take%202%20-%20native%20IPv6%20on%20DG834%20v3%20%28using%20AAISP%29/+See also: [[http://www.pitt-pladdy.com/blog/_20100424-103102+0100%20OpenWrt%20Take%202%20-%20native%20IPv6%20on%20DG834%20v3%20%28using%20AAISP%29/]]
  
 ===== Installation for v1 and v2 ===== ===== Installation for v1 and v2 =====
Line 47: Line 49:
 Successfully followed this procedure for a v1 model using Backfire 10.03 - note that on install openwrt changes the router IP to 192.168.**1**.1 so you need to reset your client interface, or re-do dhcp to reconnect. --- //match 2015/12/30 17:45// Successfully followed this procedure for a v1 model using Backfire 10.03 - note that on install openwrt changes the router IP to 192.168.**1**.1 so you need to reset your client interface, or re-do dhcp to reconnect. --- //match 2015/12/30 17:45//
 ==== Flash Layout ==== ==== Flash Layout ====
-Please see [[doc:techref:Flash.Layout]] for an overview of how the flash space is partitioned and accessed using [[doc:techref:MTD| MTD (Memory Technology Device)]]. Here the flash layout of the Netgear DG834G:+Please see [[docs:techref:flash.layout]] for an overview of how the flash space is partitioned and accessed using [[docs:techref:mtd| MTD (Memory Technology Device)]]. Here the flash layout of the Netgear DG834G:
  
 ^ Netgear DG834G  ^^^ ^ Netgear DG834G  ^^^
Line 70: Line 72:
   * update the relevant mtd special device on the router   * update the relevant mtd special device on the router
   * write openwrt to the relevant mtd firmware files   * write openwrt to the relevant mtd firmware files
-  * manually assign an ip address to the [[doc:techref:bootloader:adam2|Adam2]] bootloader+  * manually assign an ip address to the [[docs:techref:bootloader:adam2|Adam2]] bootloader
   * reboot the router and connect to the Adam2 ftp service   * reboot the router and connect to the Adam2 ftp service
   * transfer the updated firmware files to the router and write to the mtd special devices   * transfer the updated firmware files to the router and write to the mtd special devices
Line 76: Line 78:
  
 ==== Telnet to the Router ==== ==== Telnet to the Router ====
-  * Enable debug mode. Visit http://192.168.0.1/setup.cgi?todo=debug+  * Enable debug mode. Visit ''%%http://192.168.0.1/setup.cgi?todo=debug%%''
   * Telnet into your router <code>   * Telnet into your router <code>
 telnet 192.168.0.1</code> telnet 192.168.0.1</code>
Line 85: Line 87:
 ==== Obtaining your current Bootloader ==== ==== Obtaining your current Bootloader ====
  
-  * Enable debug mode. Visit http://192.168.0.1/setup.cgi?todo=debug+  * Enable debug mode. Visit ''%%http://192.168.0.1/setup.cgi?todo=debug%%''
   * Telnet into your router <code>   * Telnet into your router <code>
 telnet 192.168.0.1</code> telnet 192.168.0.1</code>
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://127.0.0.1/mtd2.bin)+  * Place the Modified mtd2.bin onto a web or FTP server (e.g ''%%http://127.0.0.1/mtd2.bin%%'')
     * 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 [[doc:hardware:port.jtag]] for more JTAG details.+See [[docs:techref:hardware:port.jtag]] for more JTAG details.
  
 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).
  • Last modified: 2015/12/30 16:48
  • by match