Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision Next revisionBoth sides next revision | ||
| inbox:toh:askey:askey_rt4230w_rev6 [2021/01/16 21:59] – fix cover image danitool | inbox:toh:askey:rt4230w_rev6 [2024/02/12 08:58] – external edit | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| ====== Askey RT4230W REV6 / RAC2V1K ====== | ====== Askey RT4230W REV6 / RAC2V1K ====== | ||
| - | |||
| - | {{page> | ||
| {{media: | {{media: | ||
| Line 9: | Line 7: | ||
| **WARNING: | **WARNING: | ||
| - | **Note: | + | **Note: |
| - | + | ||
| - | ===== Experimental firmware ===== | + | |
| - | + | ||
| - | Experimental firmware and install instructions here: https:// | + | |
| ===== Hardware Highlights ===== | ===== Hardware Highlights ===== | ||
| - | ---- datatable ---- | + | <!-- ToH: { |
| - | cols | + | " |
| - | header | + | " |
| - | align : c,c,c,c,c,c,c,c,c,c,c,c,c | + | " |
| - | filter | + | |
| - | sort : Model | + | " |
| - | ---- | + | |
| + | } --> | ||
| ===== Installation ===== | ===== Installation ===== | ||
| - | ---- datatable ---- | ||
| - | cols : Model, Versions, Supported Current Rel, Firmware OpenWrt Install URL_url, Firmware OpenWrt Upgrade URL_url, Firmware OEM Stock URL_url | ||
| - | headers : Model, Version, Current Release, Firmware OpenWrt Install, Firmware OpenWrt Upgrade, Firmware OEM Stock | ||
| - | align : l,c,c | ||
| - | filter | ||
| - | ---- | ||
| - | ===== Tuning ===== | + | OpenWrt firmware: [[https:// |
| - | Enable Software flow offloading in Network > Firewall. | + | |
| - | This router has the same soc as the Netgear R7800, so thanks to [[https:// | + | For explanation of different images, see [[docs:guide-user: |
| - | To reach peak performance, | + | ==== Method 1: Installation over the network without serial access (Only works with non-SAC2V1K firmware) ==== |
| + | Method 1 doesn' | ||
| + | |||
| + | **WARNING: If you soft-brick your router, you will need to disassemble it to access the serial console in order to recover. You can use installation method 2 in that case.** | ||
| + | |||
| + | Stock non-SAC2V1K firmware: https:// | ||
| + | ==== Method 1A: Installation using web interface and SSH (only works with non-SAC2V1K firmware) ==== | ||
| + | This is the recommended install method. It does not require setting up a TFTP server and thus is quick and easy, it produces full backups of the router, and it installs dual OSes: main and recovery. The recovery OS will run automatically if the main OS ever gets corrupted, for example due to an interrupted sysupgrade. It also configures the router to attempt a TFTP boot if both OSes are corrupt. | ||
| + | |||
| + | Note that this method must be executed under the WSL (Windows Subsystem for Linux) if you are running Windows. | ||
| + | |||
| + | See instruction here: https:// | ||
| + | |||
| + | ==== Method 1B: Installation using web interface, SSH, and TFTP (only works with non-SAC2V1K firmware) ==== | ||
| + | // | ||
| + | |||
| + | Download the OpenWrt initramfs and sysupgrade (squashfs) images for your router. Install and set up a tftp server (see [[docs: | ||
| + | |||
| + | Connect a network cable between your computer and the blue (switch) port of the router. Configure your computer with static IP address '' | ||
| + | |||
| + | Login to stock router at '' | ||
| + | |||
| + | The router automatically reboots. Afterwards, you can ssh into the router with the username for your firmware from the [[https:// | ||
| + | |||
| + | From ssh, run these commands to configure a booting attempt via TFTP with fallback to stock firmware: | ||
| + | < | ||
| + | fw_setenv bootcmd 'set ipaddr 192.168.1.1; | ||
| + | fw_setenv bootdelay 2 | ||
| + | </ | ||
| + | |||
| + | Rename the OpenWrt initramfs image file '' | ||
| + | |||
| + | Reboot the router. The router will run as a TFTP client at '' | ||
| + | |||
| + | After you've confirmed your router is booted to OpenWrt in recovery mode, disable your computer' | ||
| + | |||
| + | ssh into OpenWrt and run this command to configure OpenWrt boot (autodetects flash size): | ||
| + | < | ||
| + | fw_setenv bootcmd 'set mtdids nand0=nand0; | ||
| + | </ | ||
| + | |||
| + | Next, use the OpenWrt sysupgrade image file and upgrade to sysupgrade OpenWrt firmware (using luci, etc.). See [[docs: | ||
| + | |||
| + | The router will reboot and, if all went well, you'll now have OpenWrt running. The router will have default address '' | ||
| + | |||
| + | ==== Method 2: Installation using serial access and TFTP (works with all firmware versions) ==== | ||
| + | Method 2: Install with serial access (Do this if something fails and you can't boot after using method 1) | ||
| + | Open the router and connect to the serial console. Instructions can be found here: https:// | ||
| + | |||
| + | Download the OpenWrt initramfs and sysupgrade (squashfs) images for your router. Install and set up a tftp server (see [[docs: | ||
| + | |||
| + | Connect a network cable between your computer and the blue (switch) port of the router. Configure your computer with static IP address '' | ||
| + | |||
| + | Rename the OpenWrt initramfs image file to '' | ||
| + | |||
| + | Interrupt U-Boot and run these commands to configure OpenWrt boot (autodetects flash size): | ||
| + | < | ||
| + | set bootcmd 'set mtdids nand0=nand0; | ||
| + | set bootdelay 2 | ||
| + | saveenv | ||
| + | </ | ||
| + | |||
| + | And run this command to boot once via TFTP: | ||
| + | < | ||
| + | set ipaddr 192.168.1.1; | ||
| + | </ | ||
| + | |||
| + | The router will run as a TFTP client at '' | ||
| + | |||
| + | Next, use the OpenWrt sysupgrade image file and upgrade to sysupgrade OpenWrt firmware (using luci, etc.). See [[docs: | ||
| + | |||
| + | The router will reboot and, if all went well, you'll now have OpenWrt running. The router will have default address '' | ||
| + | |||
| + | (Originally based on: github.com/ | ||
| + | |||
| + | ==== Installation of a recovery OS ==== | ||
| + | An secondary recovery OS (an initramfs OpenWrt image) can be installed on this device. The recovery OS will run automatically if the main OS ever gets corrupted, for example due to an interrupted sysupgrade. | ||
| + | |||
| + | See here for details: https:// | ||
| + | |||
| + | ===== Basic configuration ===== | ||
| + | -> [[docs: | ||
| + | Set up your Internet connection, configure wireless, configure USB port, etc. | ||
| + | |||
| + | ===== Specific Configuration ===== | ||
| + | |||
| + | ==== Network interfaces ==== | ||
| + | The default network configuration is: | ||
| + | ^ Interface Name ^ Description | ||
| + | | br-lan (eth1.1) | LAN & WiFi | 192.168.1.1/ | ||
| + | | wan (eth0.2) | ||
| + | | vlan1 (eth1.1) | ||
| + | | vlan2 (eth0.2) | ||
| + | | radio0 | ||
| + | | radio1 | ||
| + | |||
| + | ==== Switch Ports (for VLANs) | ||
| + | |||
| + | OpenWrt Switch port number 1 is the physical network port labeled Internet (WAN) on the device, numbers 2-5 are the Ethernet ports labeled 1-4 on the device, and number 0 and 6 are internal connections between the switch chip and the CPU (labeled " | ||
| + | |||
| + | By default, '' | ||
| + | |||
| + | ^ Port ^ Switch port ^ | ||
| + | | CPU (eth0) | ||
| + | | WAN | 1 | | ||
| + | | LAN 1 | 2 | | ||
| + | | LAN 2 | 3 | | ||
| + | | LAN 3 | 4 | | ||
| + | | LAN 4 | 5 | | ||
| + | | CPU (eth1) | ||
| + | ==== Performance tuning ==== | ||
| + | |||
| + | In **Network > Firewall > General Settings**, in section **Routing/ | ||
| + | |||
| + | **IMPORTANT: | ||
| + | |||
| + | < | ||
| + | Recent OpenWrt releases use the '' | ||
| + | |||
| + | < | ||
| + | root@OpenWrt: | ||
| + | performance | ||
| + | performance | ||
| + | </ | ||
| + | |||
| + | (Also, the referenced sysfs files (''/ | ||
| + | |||
| + | **OUTDATED INFORMATION FOLLOWS:** | ||
| + | |||
| + | This router has the same SoC as the Netgear R7800, so thanks to [[https:// | ||
| + | |||
| + | To reach peak performance, | ||
| < | < | ||
| Line 44: | Line 163: | ||
| echo 10 > / | echo 10 > / | ||
| </ | </ | ||
| + | </ | ||
| ===== Hardware ===== | ===== Hardware ===== | ||
| ==== Info ==== | ==== Info ==== | ||
| - | ^ Architecture | + | ^ Architecture |
| ^ Vendor | ^ Vendor | ||
| ^ Bootloader | ^ Bootloader | ||
| - | ^ System-On-Chip | + | ^ System-On-Chip |
| ^ Flash-Chip | ^ Flash-Chip | ||
| - | ^ Flash size | 512 MiB | | + | ^ Flash size | 512 MiB NAND, 32 KiB NOR | |
| ^ RAM | 1024 MiB | | ^ RAM | 1024 MiB | | ||
| - | ^ Wireless | + | ^ Wireless |
| - | ^ Ethernet | + | ^ Ethernet |
| ^ USB | 1x USB 3.0| | ^ USB | 1x USB 3.0| | ||
| ^ Serial | ^ Serial | ||
| - | ^ JTAG | + | ^ JTAG |
| + | |||
| + | ==== Different Revisions ==== | ||
| + | **NOTE:** Some Spectrum wireless routers have similar outward appearance, but different internal hardware. | ||
| + | * Sagemcom RAC2V1S, RAC2VS2S, RAC2V2S (Broadcom SoC, not supported by OpenWrt as of 2022) | ||
| + | * [[inbox: | ||
| - | ==== Different Revisions ==== | ||
| It seems like Askey has 5 revisions of the same router based off of the device trees extracted from the original firmware. Here's a list of differences that are known. The reference revision is rev 6 since that seems to be the most common and that's the one development has been happening on. The most accurate way to get the revision is to run `cat / | It seems like Askey has 5 revisions of the same router based off of the device trees extracted from the original firmware. Here's a list of differences that are known. The reference revision is rev 6 since that seems to be the most common and that's the one development has been happening on. The most accurate way to get the revision is to run `cat / | ||
| < | < | ||
| Line 66: | Line 190: | ||
| ^ Revision | ^ Revision | ||
| | REV 1 | ? | 177a | Quite a few gpio pins are different and the ethernet aliases have some differences. | Might boot but it's likely that it'll crash pretty quickly. | No | | | REV 1 | ? | 177a | Quite a few gpio pins are different and the ethernet aliases have some differences. | Might boot but it's likely that it'll crash pretty quickly. | No | | ||
| - | | REV 3 | ? | 177b | Has an extra led pin (gpio25) to lower the led brightness. There' | + | | REV 3 | ? | 177b | Has an extra led pin (gpio25) to lower the led brightness. There' |
| | REV 5 | ? | 177c | Has an extra led pin (gpio25) to lower the led brightness. Setting to high or low has no effect on rev 6. qca, | | REV 5 | ? | 177c | Has an extra led pin (gpio25) to lower the led brightness. Setting to high or low has no effect on rev 6. qca, | ||
| - | | REV 6 | 512MB | 177d | Reference Revision | | Yes | So far, this version has only been seen with the RAC firmware. | | + | | REV 6 | 512MB | 177d | Reference Revision | **Works with 22.03.x stable release** |
| | REV 10 | 256MB | 177e | Smaller flash. Missing usb3_dev_reset_quirk in device tree. | Seems to work fine. OpenWRT seems to automatically adapt to the smaller flash. | Yes | This version has been seen with both the SAC and RAC firmware. It also needs a slightly different bootcmd because of the smaller flash (bascally just replace 0x1A000000 with 0xDC00000)| | | REV 10 | 256MB | 177e | Smaller flash. Missing usb3_dev_reset_quirk in device tree. | Seems to work fine. OpenWRT seems to automatically adapt to the smaller flash. | Yes | This version has been seen with both the SAC and RAC firmware. It also needs a slightly different bootcmd because of the smaller flash (bascally just replace 0x1A000000 with 0xDC00000)| | ||