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:rt4230w_rev6 [2022/08/22 09:12] – [Installation] ulpian | inbox:toh:askey:rt4230w_rev6 [2024/02/12 08:58] – external edit | ||
|---|---|---|---|
| Line 11: | Line 11: | ||
| ===== 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 ===== | ||
| - | /* stable release */ | ||
| - | /* uncomment once stable release is available | ||
| - | ---- 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 : c,c,c | ||
| - | filter | ||
| - | ---- | ||
| - | */ | ||
| + | OpenWrt firmware: [[https:// | ||
| - | /* snapshot */ | + | For explanation of different images, see [[docs:guide-user:installation:before.installation|FAQ before installation]]. |
| - | /* delete once stable release is available */ | + | |
| - | ---- datatable ---- | + | |
| - | cols : Model, Versions, Supported Current Rel, Firmware OpenWrt snapshot Install URL_url, Firmware OpenWrt snapshot Upgrade URL_url, Firmware OEM Stock URL_url | + | |
| - | headers | + | |
| - | align : c,c,c | + | |
| - | filter | + | |
| - | ---- | + | |
| - | Method 1: Install | + | ==== Method 1: Installation over the network |
| - | Connect to one of the router's LAN ports | + | Method 1 doesn' |
| - | Download the [[https:// | + | **WARNING: If you soft-brick your router, you will need to disassemble it to access the serial console |
| - | [[https:// | + | |
| - | After a reboot, you should be able to ssh into the router with the username for your firmware | + | Stock non-SAC2V1K |
| + | ==== 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. | ||
| - | Run the following commands: | + | Note that this method must be executed under the WSL (Windows Subsystem for Linux) if you are running Windows. |
| - | fw_setenv ipaddr 10.42.0.10 #IP of router, can be anything | + | |
| - | fw_setenv serverip 10.42.0.1# #IP of tftp server that's set up in next steps | + | |
| - | fw_setenv bootdelay 5 | + | |
| - | fw_setenv bootcmd " | + | |
| - | Don't reboot the router yet. | + | See instruction here: https:// |
| - | Install | + | ==== Method 1B: Installation using web interface, SSH, and TFTP (only works with non-SAC2V1K firmware) ==== |
| + | // | ||
| - | Set a static ip on the ethernet interface of your computer | + | Download |
| - | Download | + | Connect a network cable between your computer and the blue (switch) port of the router. Configure your computer |
| - | Reboot the router. | + | Login to stock router |
| - | After OpenWrt boots, ssh into it (root user, no password) and run these commands: | + | |
| - | fw_setenv bootcmd " | + | |
| - | fw_setenv bootdelay 2 | + | |
| - | After this, find some way to flash the sysupgrade image (luci, sftp, flash drive, etc.) | + | The router |
| - | As the router reboots, | + | |
| - | The router will reboot and if all went well, you'll now have OpenWrt running. | + | |
| - | Method 2: Install with serial access (Do this if something fails and you can't boot after using method 1) (Works with RAC2V1K and SAC2V1K) | + | 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:// | Open the router and connect to the serial console. Instructions can be found here: https:// | ||
| - | Install and set up a tftp server | + | Download the OpenWrt initramfs and sysupgrade (squashfs) images for your router. |
| - | Set a static ip on the ethernet interface | + | Connect |
| - | Download | + | Rename |
| - | Connect the wan port of the router | + | Interrupt U-Boot and run these commands |
| + | < | ||
| + | set bootcmd 'set mtdids nand0=nand0; | ||
| + | set bootdelay 2 | ||
| + | saveenv | ||
| + | </ | ||
| - | Interrupt U-Boot and run these commands: | + | And run this command to boot once via TFTP: |
| - | | + | < |
| - | setenv ipaddr 10.42.0.10 (Can be any ip as long as it's in the same subnet) | + | set ipaddr 192.168.1.1; set serverip 192.168.1.2; tftpboot recovery.bin && bootm |
| - | setenv bootcmd " | + | </ |
| - | If you have a SAC2V1K router, use this bootcmd instead: | + | The router will run as a TFTP client at '' |
| - | setenv bootcmd " | + | |
| - | saveenv | + | |
| - | tftpboot | + | |
| - | bootm | + | |
| - | After OpenWrt boots, figure out a way to flash the sysupgrade file (luci, sftp, flash drive, etc.) | + | Next, use the OpenWrt |
| - | The router will reboot and if all went well, you'll now have OpenWrt running. | + | The router will reboot and, if all went well, you'll now have OpenWrt running. The router will have default address '' |
| - | credits: github.com/ | + | (Originally based on: github.com/ |
| - | ===== Tuning ===== | + | |
| - | Enable Software flow offloading in Network > Firewall. | + | |
| - | This router has the same soc as the Netgear R7800, so thanks | + | ==== 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. | ||
| - | To reach peak performance, | + | 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 109: | Line 163: | ||
| echo 10 > / | echo 10 > / | ||
| </ | </ | ||
| + | </ | ||
| ===== Hardware ===== | ===== Hardware ===== | ||
| Line 125: | Line 180: | ||
| ^ JTAG | ¿ | | ^ JTAG | ¿ | | ||
| - | ==== Different Revisions ==== | + | ==== 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: | ||
| 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 133: | Line 192: | ||
| | 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)| | ||