Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revisionLast revisionBoth sides next revision | ||
| toh:netgear:netgear_r6220 [2021/02/25 20:02] – [OEM easy installation (OpenWrt snapshot, 19.07 and newer)] badulesia | toh:netgear:r6220 [2024/05/15 21:12] – [Debricking / back to stock firmware] typo badulesia | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| - | ====== | + | ====== |
| /* This template is intended to be used via https:// | /* This template is intended to be used via https:// | ||
| Line 5: | Line 5: | ||
| /* USE https:// | /* USE https:// | ||
| - | The Netgear R6220 is a simultaneous dual band WIFI router with AC1200 WiFi - 300+867 Mbps (2.4 & 5 GHz) speeds. | + | The Netgear R6220 is a simultaneous dual band WIFI router with AC1200 WiFi - 300+867 Mbps (2.4 & 5 GHz) speeds. |
| - | The R6220 is based on the MT7621 and received official support since OpenWrt 18.06. | + | The R6220 is based on the MT7621 and received official support since OpenWrt 18.06. It supports software and hardware offloading since 22.03. |
| The R6230 is most likely internally identical to the R6220. OpenWrt installation has been achieved by treating the device as an R6220. Although success has been achieved on two units, the R6230 is not officially supported. | The R6230 is most likely internally identical to the R6220. OpenWrt installation has been achieved by treating the device as an R6220. Although success has been achieved on two units, the R6230 is not officially supported. | ||
| + | |||
| + | ⚠️ [[https:// | ||
| + | |||
| + | ⚠️ [[https:// | ||
| /*****/ | /*****/ | ||
| Line 17: | Line 21: | ||
| {{media: | {{media: | ||
| ===== Supported Versions ===== | ===== Supported Versions ===== | ||
| - | ---- datatable ---- | + | <!-- ToH: { |
| - | cols | + | " |
| - | headers | + | " |
| - | align : c,c,c,c,c,c,c | + | " |
| - | filter | + | " |
| - | filter | + | " |
| - | ---- | + | |
| + | } --> | ||
| ===== Hardware Highlights ===== | ===== Hardware Highlights ===== | ||
| - | ---- datatable ---- | + | <!-- ToH: { |
| - | cols | + | " |
| - | header | + | " |
| - | align : c,c,c, | + | " |
| - | filter | + | " |
| - | filter | + | |
| - | ---- | + | |
| + | } --> | ||
| ===== Installation ===== | ===== Installation ===== | ||
| - | ---- datatable ---- | + | <!-- ToH: { |
| - | cols | + | " |
| - | headers | + | " |
| - | align : c,c,c | + | " |
| - | filter | + | " |
| - | filter | + | " |
| - | ---- | + | |
| + | } --> | ||
| -> [[docs: | -> [[docs: | ||
| - | ==== OEM easy installation (OpenWrt | + | ==== OEM easy installation (OpenWrt 19.07 and newer, snapshot)==== |
| - | Apply factory OpenWrt image via OEM web-gui. If after flashing OpenWrt you still see the OEM ROM, flash OpenWrt again. Afterwards your router will definitely boot OpenWrt. | + | For security reason, it is recommanded to install |
| - | + | In Netgear | |
| - | After installation, | + | Select |
| - | * The wireless networks are disabled (normal default behavior of OpenWrt) nevertheless the wireless LED is still on. A reboot, or use of the wireless handswitch, restores the right LED status. This tiny bug is fixed in 21.02 snapshots | + | |
| - | * There is no default LED rules configurated, | + | |
| - | ==== Installation through telnet (OpenWrt 18.06)==== | + | |
| - | + | ||
| - | NOT RECOMMENDED : USE VERSION 19.07 INSTEAD | + | |
| - | + | ||
| - | **Note**: | + | |
| - | + | ||
| - | - Copy kernel.bin and rootfs.bin to a USB flash disk, plug to usb port on the router | + | |
| - | - Call the link: '' | + | |
| - | - You will see "Debug Enabled!" | + | |
| - | - telnet IP-address and login with " | + | |
| - | - ''ls / | + | |
| - | - '' | + | |
| - | - '' | + | |
| - | - '' | + | |
| - | - '' | + | |
| - | - '' | + | |
| - | - '' | + | |
| - | + | ||
| - | // Replace '' | + | |
| + | If you choose to install 19.07 (not recommanded for security reason), you'll noticed these tiny bugs: | ||
| + | * the wireless LED is still on while wireless networks are disabled (default behavior of OpenWrt). A reboot, or use of the wireless handswitch, restores the right LED status. | ||
| + | * There is no default LED rules configurated. | ||
| ==== OEM installation using the TFTP method ==== | ==== OEM installation using the TFTP method ==== | ||
| Line 99: | Line 88: | ||
| -> [[docs: | -> [[docs: | ||
| - | <WRAP BOX> | + | Upgrading can be done using LuCI or sysupgrade (in SSH) in the usual way. |
| + | Upgrading from 19.07 to an higher version requires a complete new setup due to DSA syntax. So don't keep settings and reconfigure from scratch. Upgrading from 21.02 to a higher version can be done while keeping settings. Refer to the release note of each version for general purpose compatibility. | ||
| - | FIXME These are generic instructions. Update with your router' | ||
| - | ==== LuCI Web Upgrade Process ==== | ||
| - | * Browse to '' | ||
| - | * Upload image file for sysupgrade to LuCI | ||
| - | * Wait for reboot | ||
| - | |||
| - | ==== Terminal Upgrade Process ==== | ||
| - | |||
| - | If you don't have a GUI (LuCI) available, you can alternatively upgrade via the command line. | ||
| - | There are two command line methods for upgrading: | ||
| - | |||
| - | * '' | ||
| - | * '' | ||
| - | |||
| - | <WRAP center round important 60%> | ||
| - | It is important that you put the firmware image into the ramdisk (/tmp) before you start flashing. | ||
| - | </ | ||
| - | |||
| - | === sysupgrade === | ||
| - | |||
| - | * Login as root via SSH on 192.168.1.1, | ||
| - | |||
| - | < | ||
| - | # Version 18.06.X | ||
| - | cd /tmp | ||
| - | wget http:// | ||
| - | sysupgrade -v / | ||
| - | |||
| - | # Version 19.07.X | ||
| - | cd /tmp | ||
| - | wget http:// | ||
| - | sysupgrade -v / | ||
| - | |||
| - | </ | ||
| - | <WRAP center round important 60%> | ||
| - | Since version 19.07.X, sysupgrade images now have the " | ||
| - | </ | ||
| - | |||
| - | |||
| - | === mtd === | ||
| - | |||
| - | If '' | ||
| - | |||
| - | * Login as root via SSH on 192.168.1.1, | ||
| - | |||
| - | FIXME The commands below are just an example. | ||
| - | < | ||
| - | cd /tmp | ||
| - | wget http:// | ||
| - | mtd write / | ||
| - | </ | ||
| - | |||
| - | :!: Flashing to the wrong mtd label or an invalid image file may **brick** your device.\\ | ||
| - | :!: DO NOT attempt to write files with the '' | ||
| - | |||
| - | </ | ||
| ===== Debricking / back to stock firmware ===== | ===== Debricking / back to stock firmware ===== | ||
| -> [[docs: | -> [[docs: | ||
| - | Debricking of the R6220 can be done by using the tool nmrpflash | + | Debricking of the R6220 can be done by using the **nmrpflash** program. It is somehow a '' |
| - | This tool can also be used to go back to stock firmware. For Windows users, ethernet cable must be connected to a switch or nmrpflash would fail to operate. | + | After uploading the file, the message '' |
| + | <code bash> | ||
| + | c: | ||
| + | Waiting for Ethernet connection. | ||
| + | Advertising NMRP server on net5 ... - | ||
| + | Received configuration request from xx: | ||
| + | Sending configuration: | ||
| + | Received upload request without filename. | ||
| + | Uploading R6220-V1.1.0.114_1.0.1.img ... OK (26892940 b) | ||
| + | Waiting for remote to respond. | ||
| + | Received keep-alive request (253). | ||
| + | Remote finished. Closing connection. | ||
| + | Reboot your device now. | ||
| + | </ | ||
| - | anecdotal info: | + | You can use the same method to install |
| - | My R6220 uses a different mac the first few seconds after boot. If nmrpflash does not work for you, start wireshark and sniff the first few packages after boot. Try directing nmrpflash at that mac and start it right as you powercycle the router | + | |
| - | :!: This process only works with OEM firmware, don' | + | if this fails try temporarily disabling the windows firewall while using nmrpflash, and remember to re-enable it after. |
| ===== Flash Layout ===== | ===== Flash Layout ===== | ||
| Line 182: | Line 128: | ||
| // Additional details to be added // | // Additional details to be added // | ||
| - | |||
| - | === Bad eraseblocks and resulting Wifi/MAC troubles in OpenWrt 18.06 === | ||
| - | |||
| - | In OpenWrt versions up to and including 18.06, the NAND driver intransparently shifted pages when encountering bad flash memory blocks. Depending on the actual location of the bad blocks, wifi calibration data and MAC addresses might have been read at incorrect locations, resulting in performance or stability issues. (For some time, this was incorrectly attributed to Netgear using different flash layout variations.) | ||
| - | |||
| - | If you find the following or similar in dmesg: | ||
| - | < | ||
| - | mt76x2e 0000: | ||
| - | mt76x2e 0000: | ||
| - | </ | ||
| - | your device is affected and there is a chance that you will encounter the aforementioned problems when running OpenWrt 18.06 or earlier. The wrong NAND driver behaviour [[https:// | ||
| ===== Failsafe mode ===== | ===== Failsafe mode ===== | ||
| -> [[docs: | -> [[docs: | ||
| Line 270: | Line 205: | ||
| ===== Hardware ===== | ===== Hardware ===== | ||
| ==== Info ==== | ==== Info ==== | ||
| - | ---- datatemplatelist dttpllist ---- | + | <!-- ToH: { |
| - | template: meta:template_datatemplatelist | + | " |
| - | cols | + | " |
| - | filter | + | " |
| - | filter | + | " |
| - | ---- | + | " |
| + | | ||
| + | } --> | ||
| ==== Photos ==== | ==== Photos ==== | ||