RouterTech Firmware 2.96 (ar7rd-lite-1port) Download

Posted at November 2, 2024 by PCI-DB Team

RouterTech Firmware 2.96 (ar7rd-lite-1port) Description

Changelog

1. Busybox has been upgraded to v1.18.4.
2. User-configurable udp "SIP_EXPIRES" timeout for standard firmwares (wireless and non-wireless) only.
You can set "/proc/sys/net/ipv4/netfilter/ip_conntrack_udp_sip_expires" to the desired value (default=3600 [seconds]).
Example: "echo 7200 > /proc/sys/net/ipv4/netfilter/ip_conntrack_udp_sip_expires" will set the timeout value to 7,200 (seconds).
NOTE: this feature is not available in the 1350A wireless firmwares.
3. New 1-port firmware for the one-port 1350A wireless routers.
4. New facility for executing commands each time a WAN connection is made - by "RT_connect_x" entries in the environment ("x") stands for a number or some other distinguishing letter/number.
Example: setenv 'RT_connect_1 /nvram/refresh_web.sh' (this will run "/nvram/refresh_web.sh" (assuming that such a script exists) every time a WAN connection/reconnection is made).
5. Bug fixes to pptpd.
6. New scripts: "pptpdstart.sh" and "pptpd_stop.sh" - to start and stop the pptpd server respectively. The second script takes no parameters. Supply "--help" to "pptpdstart.sh" to see the syntax. See also the "pptpd_user_dir" environment variable, below.
7. New environment variable: "pptpd" - set to 1 to run pptpdstart.sh automatically when the router boots up.
8. New environment variable: "pptpd_user_dir" - points to the location of user configuration files for pptpd. The default is /nvram/pptpd/ (i.e., on your minix partition, if any). Use this variable to override the default - otherwise, you will need to run pptpdstart.sh manually, and to pass it the "--pptpd_user_dir" switch pointing to the relevant directory. Everything in this directory will be copied to the /var/tmp/ directory by pptpdstart.sh before starting the pptpd service. So you can have your own custom options.pptpd and pptpd.conf files there. If so, they will override the defaults supplied with the firmware. Your chap-secrets file MUST be in this directory.
9. The idle timeout for utelnetd (for telnet connections) is now configurable - by a "timeout" variable in "/var/tmp/utelnetd.conf" (default = 600 [seconds])
You can write the conf file manually;
Example: "echo timeout=3600 > /var/tmp/utelnetd.conf" will set the timeout to 1 hour. Set "timeout=0" for an indefinite timeout.
Or you can store the value in the "utelnetd_timeout" environment variable, in which case the firmware will create the conf file with the right value each time the router boots up
Example: "setenv utelnetd_timeout 7200"
10. The idle timeout for dropbear (for ssh connections) is now configurable - by a "timeout" variable in "/var/tmp/dropbear.conf" (default = 120 [seconds])
You can write the conf file manually;
Example: "echo timeout=600 > /var/tmp/dropbear.conf" will set the timeout to 10 minutes. Set "timeout=0" for an indefinite timeout.
Or you can store the value in the "dropbear_timeout" environment variable, in which case the firmware will create the conf file with the right value each time the router boots up
Example: "setenv dropbear_timeout 0"
11. New environment variable: "utelnetd_timeout" - to specify the idle timeout (in seconds) for telnet connections. Set to 0 (zero) for an indefinite timeout.
12. New environment variable: "dropbear_timeout" - to specify the idle timeout (in seconds) for ssh connections. Set to 0 (zero) for an indefinite timeout.
13. Got rid of the "ip_nat_mangle_udp_packet: undersized packet" error messages.
14. New script: "pppoe_bug_fix.sh" - to facilitate the fixing of pppoe problems that arise out of an invalid DSL MAC address in the router's environment.
15. The "Restart" button in the "System" menu has been removed. There was no point in having two ways of rebooting the router in the web admin. Use "Tools->Reboot Router" instead.

Disclaimer & Warning

1. Flashing custom firmwares onto a router is not for novices, as the process may well "brick" the router.
2. You must not flash this firmware onto your router unless you are very familiar with the PC-Tool (or similar) and are competent in using it to un-brick a router.
3. Please take this warning very seriously. If you are not adept at recovering bricked routers, and if you are not familiar with the PC-Tool, then do not install this firmware!
4. Do not even consider installing this firmware without first reading all the documentation supplied with the firmware. If you fail to observe this, then you are entirely on your own.
5. Do not even consider installing this firmware without first running the Router Upgrade Checker (RUC) and following whatever counsel it gives. If you fail to observe this, then you are entirely on your own.
6. Do not even consider installing this firmware unless you have first backed up your router's bootloader environment (i.e., /proc/ticfg/env) to your hard disk. If you fail to observe this, then you are entirely on your own.

Upgrading:

Before upgrading you must backup your router config as detailed above and reset to factory defaults.
Please remember to run the Router Upgrade Check BEFORE you upgrade!

If you choose to upgrade via the router's web interface, then you MUST observe the following
- First reset the router to factory defaults before trying to install this firmware.
- When upgrading via the web interface, (particularly for the 1350A wireless firmware) you must wait for at least 7 minutes for the new firmware to establish itself. Do not do anything to the router for at least 7 minutes from the moment the upgrade process starts, and do not interrupt the upgrade process.
- Once your router has been upgraded and be seen to be working you must reset to factory defaults again

Note: Before installing this firmware, you must, among other things (see the docs in the zip file for those other things) back up a copy of your router's current "/etc /led.conf" file. We only have a few LED configuration files, and the chances are that we do not have one suitable for your own router. If you do not keep a copy of the original contents of that file, then we have no way of knowing how your LEDs should be configured, and the LEDs will always be wrong. This will not affect the router's normal operation - but you the LEDs will not be reporting the correct operations.

NOTE:

- Non-wireless "Lite" firmwares for 1-port routers (contains both Adam2 and Pspboot firmware images). Use this if you want a lean firmware for your 1-port non-wireless router.

About Router Firmware:

Before you consider downloading this firmware, go to the system information page of the router and make sure that the currently installed version isn’t either newer or matching this release.

Due to the large variety of router models and different methods for upgrading the device, it is highly recommended that you read and, above all, understand the installation steps before you apply the new firmware, even if you are a power user.

In theory, these steps shouldn’t be much of a hassle for anyone, because manufacturers try to make them as easy as possible, even if they don’t always succeed. Basically, you must upload the new firmware to the router through its administration page and allow it to upgrade.

If you install a new version, you can expect increased security levels, different vulnerability issues to be resolved, improved overall performance and transfer speeds, enhanced compatibility with other devices, added support for newly developed technologies, as well as several other changes.

If you’re looking for certain safety measures, remember that it would be best if you perform the upload using an Ethernet cable rather than a wireless connection, which can be interrupted easily. Also, make sure you don’t power off the router or use its buttons during the installation, if you wish avoid any malfunctions.

If this firmware meets your current needs, get the desired version and apply it to your router unit; if not, check with our website as often as possible so that you don’t miss the update that will improve your device. 

  It is highly recommended to always use the most recent driver version available.

Try to set a system restore point before installing a device driver. This will help if you installed an incorrect or mismatched driver. Problems can arise when your hardware device is too old or not supported any longer.

Related RouterTech Drivers