What is openwrt zip file on mac in downloads?

TP-Link TL-WDR has n Dual Band (concurrent) WiFi and Gigabit Ethernet. Advertised as Mbps it is Dual-Stream (2×2) on the GHz Band and Triple-Stream (3×3) on the 5 GHz Band. Same as the TL-WDR Released earlier this year in China.

Related to TL-WDR, which has only two instead of three antennas.

NOTE: The Ethernet switch in this device, ARN, is working fine with the OpenWrt default configuration. Some of the more advanced functions of the switch are not yet fully supported by the driver in

ALSO NOTE: The Ethernet switch lets WAN traffic through for a few seconds on bootup. This can be a problem.

If your wireless cannot be enabled when using wide channel modes, this may be due to the friendly neighbor “feature” that prohibits operation of such a mode and you may have to use the standard modes before wireless can be enabled.

• Download OpenWrt factory image as shown above
• Rename it to the format that the original firmware expects. Something like: wdrv1_en_3_14_3_up_boot().bin. Otherwise the page will show error messages like “please select a file to upgrade”.
• Connect your PC to a LAN port of the TP-link via ethernet.
• Login to the TP-link web administration webpage. (Default address is )
• Under &#;System Tools&#; select &#;Firmware Upgrade&#;. Browse to the previously downloaded *.bin file. Click Upgrade.
• Set your password and configure the router through the web UI. Basic Config

Note: Factory default IP address range is while OpenWrt uses by default. If you have trouble accessing your router after initial flash, check that you have a x IP address on your PC.

1. Download OpenWrt factory image as shown above
2. Look for www.cronistalascolonias.com.ar, unless your device was purchased in Israel. In that case, look for openwrt-ar71xx-generic-tl-wdrv1-ilwww.cronistalascolonias.com.ar
3. Rename the file (original firmware expects a specific format)
   1. The following filename will please the vendor&#;s web UI firmware update tool: wdrv1_en_3_14_3_up_boot().bin
   2. Otherwise the page will show error messages like “please select a file to upgrade,” or will not respond to clicking the upgrade firmware button.

Once installed, in order to use wifi, you need to activate wifi in the configuration, see wireless configuration.

NOTES

1. Recent (+) TP-Link firmware in the USA may be locked to prevent re-flashing. If you have such locked firmware, you can downgrade to use the original TP-Link firmware and flash OpenWrt from the web interface. You will need tools from dd-wrt to effect the downgrade: go to dd-wrt website and search the router database for wdr, then download the www.cronistalascolonias.com.ar file from the router database page. Unrar the file to extract the binary. Next, from www.cronistalascolonias.com.ar, select betas for the WDR, then select the most recent date (e.g), then find the latest wdrv1. Your path is reported as something like: Downloads › betas › › r › tplink_tl-wdrv1. Download the file www.cronistalascolonias.com.ar. This tool will install dd-wrt, and the revert tool will then install the original unlocked TP-Link firmware. To flash dd-wrt (dd-wrt reccomends IE/windows for this), login to the locked TP-Link router (admin/admin), and then use the “System Tool Update Firmware” to flash the www.cronistalascolonias.com.ar file. After the router has finished rebooting, the router has dd-wrt running at http://, and you are ready to revert to the unlocked TP-Link firmware. Browse to , assign an ID/PW, then navigate to Administration → Firmware Upgrade. Select the extracted www.cronistalascolonias.com.ar from your host&#;s download directory and click the Upgrade button, dd-wrt will be replaced with the original unlocked TP-Link firmware. Now browse to http://, hit reset on the router for 5+ seconds to revert the ID to admin/admin and reboot. The router is now running the old TP-Link unlocked firmware at the IP address , after the router reboots, browse to http:// and login with admin/admin. To install Openwrt firmware, browse to System Tools → Firmware Upgrade and select the new firmware file of your choice (e.g.: OpenWrt Designated Driver) and click Upgrade to flash the WDR with OpenWrt.
2. TP-Link&#;s firmware defaults to with username “admin” and password “admin”. After installation, OpenWrt defaults to and no assigned password.
3. Precompiled images do not activate the wireless feature by default (you will have to use Ethernet for the initial configuration).
4. Trunk images don&#;t have luci, you must install it manually, see www.cronistalascolonias.com.arials
5. For devices in Israel, try flashing the original image first, in most cases it will work just fine. Devices that require the Israeli firmware will show a warning on the Firmware Update page. If you see this warning, fallback to the “-il-” image. The Israeli firmware differs only in the Hardware ID, in order to enable flashing from the original firmware interface. There is no difference between the images otherwise. See this thread for details.
6. Images for the TP-Link are largely compatible with a simple modification to the header of the firmware image. The PCB for both models is identical, or close to identical. The third external antenna on the is on the PCB of the , but not connected to an external antenna.

WARNING: Do not flash the sysupgrade firmware via the vendor firmware web interface. Only the &#;factory&#; images should be flashed from the vendor firmware.

Pressing the WPS/Reset button during powerup makes the bootstrap loader enter the TFTP recovery mode. The procedure can be used to transfer a firmware image:

1. assign to your local network interface (the router uses )
2. publish a firmware image via tftp:
3. configure your tftp server. best if you can have some way of watching the log file so you can see if the router is requesting the file
4. turn on the router, wait until the second light from the left - the asterisk - starts flashing, hold down the WPS button on the back for a few seconds until the asterisk starts flashing faster
5. OR (some models are different) hold down the WPS button on the back and THEN power up the router. You will know it is attempting to transfer the file when the light furthest on the right lights up.
6. wait for the firmware transfer (about 20s), firmware flash (about 90s) and subsequent reboot (about 30s)

If OpenWrt is already installed and you wish to upgrade to a newer version, you have two methods available:

(prior to actual flashing given availability of a serial console it&#;s a nice idea to do dry runs, by ad-hoc RAM booting a www.cronistalascolonias.com.ar from a TFTP host server, via uboot “tftp” + “bootm”, served via WDR&#;s default www.cronistalascolonias.com.ar filename).

• Check memory usage with the free or top commands. The image can be up to 8MB, so only proceed if you have as much free RAM as the image size plus MB; this should not be a problem on a device with MB RAM.
• An easy way to free up some RAM is to delete the symlinks to /etc/modules.d/cfg, /etc/modules.d/mac, /etc/modules.d/2*-ath* and /etc/modules.d/[]*-* and reboot. Drop caches can be useful too:

• wget or scp the new firmware build to /tmp/

Alternately, you can follow the www.cronistalascolonias.com.arrade procedure. Don&#;t forget to populate your first.

For systems where OpenWrt mtd is not available, mtd-utils commands need to be used (subsequent commands boldly assume that it&#;s mtd5 which equals the “firmware” mtd partition name - cat /proc/mtd to verify!!):

(write operation will take about 5 minutes to complete)

Note that output of newer mtd-utils flash_eraseall recommends using “flash_erase <dev> 0 0” instead (did not test it).

Please read the article www.cronistalascolonias.com.ar for a better understanding. It contains a couple of explanations. Then let&#;s have a quick view at flash layout of this particular device:

ART = Atheros Radio Test - it contains mac addresses and calibration data for the wifi (EEPROM). If it is missing or corrupt, ath9k won&#;t come up anymore.

Power up your router. When the &#;SYS&#; light (asterisk symbol right of the power light) starts to blink, immediately push the WPS/Reset button on the back-left of the router for a short time (>1 sec). The &#;SYS&#; light should now start to blink very fast.

On a TL-WDR Ver and Barrier Breaker Bleeding Edge, r, the above instructions were not terribly successful. The only way that I was able to get the router into failsafe mode was to quickly and repeatedly press the WPS/Reset button starting before the front panel “star” LED started flashing. When that LED finally lit, it appeared to go directly into the rapid-flashing “failsafe” indication. If the WPS LED lights (rightmost, “yin-yang arrows”), it may be that you started clicking the button a little early in the boot sequence.

Years later, at least with OpenWrt/LEDE , the “magic moment” is the two seconds that the “on” LED starts flashing. As this is from the code, it likely applies to most similar models. (Confirmed on TP-Link Archer C7)

For what you can do in failsafe, go to the OpenWrt Failsafe Mode page.

DON&#;T TRY to flash wdr with wdr firmware and vice-versa!

Warning!
This section describes actions that might damage your device or firmware. Proceed with care!

The stock firmware is obtained from the OEM: www.cronistalascolonias.com.ar#Firmware As with the WRND router, there is a also a catch with the WDR!!

• in case the file name of this firmware file does not contain the word “boot” in it, you can simply revert back to original firmware. → www.cronistalascolonias.com.arall
• in case the file name of this firmware file does contain the word “boot” in it, you need to cut off parts of the image file before flashing it

An example of an image file with the word “boot” in it is or .

Cut the first 0x (that is , = *) Bytes from original firmware: (1* Vendor-info + * U-Boot)

If you want to find an image that does not contain the word “boot” from the OEM, try downloading smaller zip-files first. With status 12th October no such zip-files can be downloaded from the vendor&#;s website.

(Note: For 3_13_17 the File size should now be exactly: 8,, Bytes, for 3_14_3 the File size should be exactly 8,,).

Now the resulting file can be flashed via mtd or web interface (web interface-method is tested 12 Oct , works with 3_14_3)

Other caveats (from vendor web UI):

• If the firmware path is too short, it will fail with the incorrect error &#;firmware path too long&#;. For instance, flashing c:\www.cronistalascolonias.com.ar will not work.
• If the firmware path is too long, it will fail with the error &#;firmware path too long&#;.

Now follow → www.cronistalascolonias.com.arall

The stock firware (()) features a TFTP recovery client in bootloader. To activate it press and hold WPS/Reset Button during powering on until WPS LED turns on. Connect computer to LAN1. Using TCPdump, you should see ARP requests from router having address looking for address

Set up your computer to address , netmask /24 ().

Using TCPdump, you should now see request for new firmware image:

Rename factory image to given name and put it into TFTP server root. → www.cronistalascolonias.com.ar

In case you are flashing back original firmware, make sure original firmware image name does not contain word → Back to original firmware.

After downloading, the flashing starts immediately. After cca. 1 minute, the router reboots automatically.

If you want to de-brick/upgrade your router using TFTP you follow these steps:

Pre-requisits:

• serial RS connected from your machine to TL-WDR & terminal program (e.g. minicom, screen) set to 8N1, no flow control, 3,3V
• copy a working & full OpenWrt firmware image into your tftp server folder (e.g: www.cronistalascolonias.com.ar)

(in case you want to flash the original TPLink firmware it migth needed to delete the first Bytes from this firmware bevor flashing, plz check Video Flash Steps!)

• start a tftpd server on your local machine on LAN address /24 and connect your LAN-port to one of the routers LAN ports

Video Flash Procedure: How to debrick TL-WDR

Written Flash Procedure:

1. router should be unplugged & your serial line connected & terminal open & tftp server installed not yet running
2. copy your desired openwrt image for the tplink into your tftp server folder and rename it into www.cronistalascolonias.com.ar (to save some typing within the flash procedure)
3. first goal is to get the command prompt from the u-boot bootloader on your router
4. you should only plug in the serial into the router&#;s serial port AFTER it initialises for a split second after powering on BUT BEFORE Autobooting starts otherwise it might hang at the initialisation process
5. plug in your router and be ready to type & hit ENTER after you see the line :

1. in case you failed the right timing just reboot again until the prompt appears

1. now lets check what kind of parameters the u-boot loader expects (e.g file name of firmware via TFPT & Load Adress)
2. type & press ENTER …

1. as you can see, uboot expects a firmware image file name “www.cronistalascolonias.com.ar” at tftp server address
2. just change you local ip into and start your tftp server
3. start the uboots tftpclient to download the image from your local machine by typing: tftpboot 0x www.cronistalascolonias.com.ar + ENTER

1. the last line needs to show a size of otherwise your image is unsuitable
2. now we need to erase parts of the flash memory to be able to copy your fresh loaded firmware into it
3. just type in the promt and wait for the promt to come back

1. now just copy the image to the rigth place by typing

1. so .. you, in case your image is the correct one, your are just a single reboot away from having a working TL-WRD back on your desk
2. type or just un-plug and re-plug the power of your router and watch the boot process

WARNING: risk of frying your hardware. only do this when you understand basic electric engineering.

When the bootloader was trashed as well, and none of the above recovery methods work, you can de-brick the thing using flashrom, see www.cronistalascolonias.com.ar

If you don&#;t have one of those fancy SOIC clips, desolder the flash chip (google for SOIC desoldering for your favorite method)

The default network configuration is:

Numbers are Ports as labeled on the unit, number 1 is the Internet (WAN) on the unit, 0 is the internal connection to the router itself.

The switch ports may turn out to be not properly bridged in a default bootup config, causing connection failure. In this case you need to setup /etc/config/network or do manual swconfig setup - see switch for advice.

I ordered the switch ports to make it in order. port 1 is eth and wan port is eth, which is just another network

Remove the 4 screws on the bottom of the case.

The top is clipped to the bottom of the case at 9 attachment points: 3 on each side of the case, 1 on the back, and 2 on the front. Each attachment point consists of two pins which fit into holes in tabs which protrude from the other half of the case. All of the tabs are on the bottom of the case, with the exception of the case back, where the single tab is in the center of the top of the case.

One method known to work, once, is to start at one of the rear corners. The corner by the ethernet ports seems to work best. Gently flex the case and slightly separate the top from the bottom at the corner by lifting on, or inserting a fingernail or other thin object into, the crack above the antenna. While doing this insert the tip of a knife blade (upward, given the geometry as the unit normally sits) into the crack between the two halves along the side of the case toward the rear. This will force the pins in the top of the case outward, flex the tab protruding from the bottom of the case inward, and free the pins from the tab. If necessary the knife tip may be levered slightly toward the case interior after insertion. Due to the force separating the top of the case from the bottom near the antenna, the pins should pop out of the tab located on the case side near the rear, lift slightly upward, and remain free.

Continue to free the other tabs, first working from the rear corner toward the front of the case, then across the front of the case, and finally from the front of the case toward the rear along the opposite side. The two halves of the case will then separate without having to work at freeing the last attachment point at the rear of the case.

With care, this method leaves no marks on the case.

Serial console is available on the J1 () connector, v signals.

DO NOT CONNECT VCC. Use only TX/RX/GND.

To break bootstrap sequence, type &#; during the 1-second boot delay.

Factory firmware login credentials are not known at this time (it&#;s not root/5up as with other tp-link models).

Below is an image of the PCB with the serial TTY console shown, in addition the JTAG pin location is shown as well. Both has all its pins labled as well.

→ www.cronistalascolonias.com.ar general information about the JTAG port, JTAG cable, etc.

How to connect to the JTAG Port of this specific device: See picture above.

The TL-WDR DE (v) comes bundled with the following PSU:

Specifications:

The WDR/ consume about 3 W with both radios enabled and idle. Each connected ethernet cable adds about W.

→ www.cronistalascolonias.com.ar The ARx platform provides 30 GPIOs. Some of them are used by the router for status LEDs, buttons and other stuff. The table below shows the results of some investigation:

To make the GPIOs available via sysfs, the required ones have to be exported to userspace, as it is explained on a page of the Squidge-Project. Kernel modules occupying that resource need to be removed before (e.g. “leds-gpio” and “gpio-buttons”). In output-mode, voltage levels of the GPIOs were measured against GND, after the value 1 or 0 had been written to /sys/class/gpio/gpioX/value. In input-mode, the value of the file /sys/class/gpio/gpioX/value was read when the GPIO was floating (initial state), pulled to GND or pulled to Vcc.

The 5GHz LED seems not to be controlled via GPIO.

Tested with |http over nginx|←wan-|wdr|←lan-|Client|

WARNING: risk of frying your hardware. only do this when you understand basic electric engineering.

The task was to make ext-root without using the default ports.

It turns out that the GLG chipset used by the TP-Link in WDR// models can handle up to four ports.

Analysing the router&#;s PCB it appears that pins 8(D-), 9(D+), 11(D-) and 12(D+) are unused. Aditionaly each factory USB port has separate power section.

GND is at the TP7 pin point. +5 V was taken directly from the MOSFET.

Internally, the device generates + V, + V and + V (just for USB). All voltage regulators will work from V - V. This makes the device capable of running from USB power (e.g. a power bank).

You have to open the case and remove (bridge) the input diode, which you will find directly in between the power connector and the input capacitors. Care: There are no thermal reliefs so you need a quite powerful soldering station. Unsolder the SMD diode, place a wire across the pads and solder that.

As the V regulator is only specified for V (with absolute maximum of 16 V), you will lower the allowed input voltage by this modification. Running directly of the car 12 V (up to V while charging) is outside the limits when the diode is removed and on the edge when diode is in place.

USB devices connected to the USB port on the WDR/ may not work when the device is powered with less than V.

Forum member pepe2k made a modification of U-Boot for Qualcomm Atheros SoCs based devices (the project is still being developed, so new devices and SoCs will be supported in the future). Up to date information, binary images and sources can be found on official GitHub repository.

This modification started from wrn-uboot-with-web-failsafe project, but supports more devices, all modern web browsers, has a lot of improvements and other modifications (like U-Boot NetConsole, custom commands, overclocking possibilities etc.).

More information:

(for , at least)

Changing variables through &#; doesn&#;t seem to make the changes stick, unfortunately.

The following kernel log was capture on a WDR running (trunk):