[OpenWrt Wiki] TP-Link TL-WR1043ND

This page is read only. You can view the source, but not change it. Ask your administrator if you think this is wrong.
====== TP-Link TL-WR1043ND ======
One of the first cheap devices with an gigabit Ethernet switch. Advertised features: 3 removable omni antennas ([[wp>RP-SMA|RP-SMA connectors]]) and 24 dBm (251 mW, v1.x)/25 dBm (v2.x, v3.x) maximal TX power output. Note: Maximal TX power and available channels are limited in some countries!

^ HW v1.x ^ HW v2.x ^ HW v3.x ^ HW v4.x ^ HW v5.x ^
|  {{media:tplink:tl-wr1043:tl-wr1043nd-v1_profile.jpg?200|}}  |  {{media:tplink:tl-wr1043:tl-wr1043nd-v2_profile.jpg?200|}}  | {{media:tplink:tl-wr1043:tl-wr1043nd-v2_profile.jpg?200|}}  | {{media:tplink:tl-wr1043:tl-wr1043nd-v2_profile.jpg?200|}}|{{media:tplink:tl-wr1043:tl-wr1043nd-v2_profile.jpg?200|}}  |

===== Supported Versions =====
<!-- ToH: {
  "source": "json",
  "dom": "t",
  "paging": false,
  "rotate": true,
  "shownColumns": ["brand", "model", "version", "supportedcurrentrel", "oemdevicehomepageurl", "owrt_forum_topic_url", "deviceid"],
  "filterColumns": {"brand": "^TP-Link$", "model": "^TL-WR1043ND$|^TL-WR1043N$" }
} -->

++++Historic information|
^ Version/Model ^ S/N ^ Release Date ^ Bootloader Date ((U-Boot 1.1.4 if not stated otherwise.)) ((''grep U-Boot /dev/mtd0ro'')) ^ Supported since version ((The earliest OpenWrt release to be supported. Subsequent releases should be supported unless otherwise stated.)) ^ Model Specific Notes ^
| v1.0     | - | | | Backfire 10.03.1 | Similar, German WebUI |
| v1.1     | - | | | Backfire 10.03.1 | Similar to WR941ND.|
| v1.2     | - | | | Attitude Adjustment 12.09 | |
| v1.3     | - | | | Attitude Adjustment 12.09 | |
| v1.4     | - | | | Attitude Adjustment 12.09 | |
| v1.5     | - | | | Attitude Adjustment 12.09 | |
| v1.6     | - | | | Attitude Adjustment 12.09 | |
| v1.7     | - | | | Attitude Adjustment 12.09 | |
| v1.8     | - | 2010 | 2010-08-04 <sup><sub>(and probably other versions prior to 2012-02-02)</sub></sup> | Attitude Adjustment 12.09 | |
| ::: | - | | 2011-04-28 | Barrier Breaker 14.07 | |
| ::: | - | | 2012-02-02, 2012-03-31 <sup><sub>(and probably later versions)</sub></sup> | Attitude Adjustment 12.09 | |
| v1.9     | - | | 2012-03-31 | Barrier Breaker 14.07 | |
| v1.10    | - | | | Attitude Adjustment 12.09 | |
| v1.11    | - | | | Attitude Adjustment 12.09 | |
| v2.1     | - | | 2013-06-18 | [[http://downloads.openwrt.org/chaos_calmer/15.05.1/ar71xx/generic/|Chaos Calmer 15.05.1]]  |  |
| v3.0     | - | | - | [[http://downloads.openwrt.org/chaos_calmer/15.05.1/ar71xx/generic/|Chaos Calmer 15.05.1]] | Same HW as v2.x [[https://fccid.io/document.php?id=2644079|FCC ID: TE7WR1043NDV3]] |
| v4.0     | - | | 2016-03-03 | v4 Snapshot from 2017-02-19 was working without problems| New UI and HW changes. Got QCA9563 + 16MB internal flash (QCA9563+QCA8337N+25Q128FVSG+A3R12E40CBF-8E) [[https://fccid.io/TE7WR1043NDV4|FCC ID: TE7WR1043NDV4]] |
| v5.0     | - | | - | [[https://git.lede-project.org/?p=source.git;a=commit;h=673793d753717dc49e5a6f9b1bba52658cae63fc|Since commit 673793d753717dc49e5a6f9b1bba52658cae63fc]] | Model name shortened to TL-WR1043N |
++++


===== Hardware Highlights =====
<!-- ToH: {
  "source": "json",
  "dom": "t",
  "paging": false,
  "rotate": true,
  "shownColumns": ["model", "version", "cpu", "cpumhz", "flashmb", "rammb", "wlanhardware", "wlan24ghz", "wlan50ghz", "ethernet100mports", "ethernet1gports", "modem", "usbports"],
  "filterColumns": {"brand": "^TP-Link$", "model": "^TL-WR1043ND|^TL-WR1043N$" }
} -->

See paragraphs [[#Hardware]] or [[#Tags]] for more details.

===== Installation =====

<!-- ToH: {
  "source": "json",
  "dom": "t",
  "paging": false,
  "rotate": true,
  "shownColumns": ["model", "version", "supportedcurrentrel", "firmwareopenwrtinstallurl", "firmwareopenwrtupgradeurl", "firmwareoemstockurl"],
  "filterColumns": {"brand": "^TP-Link$", "model": "^TL-WR1043ND$" }
} -->
  - **If you have "Please choose a file to upgrade" message again and again, filename is probably too long and you have to rename image to for example ''firmware.bin''.**
  - [[docs:guide-user:installation:generic.flashing]] Now write this firmware-file onto the flash-chip of your device

:!: **''NOTE:''** In case you have a revision > v1.10 (but not v2.x), you need to flash an elder OEM firmware release first, and only then flash OpenWrt; tested and works [[http://forum.lowyat.net/topic/2481658/all|credits go to sayboon]] for his tutorial.



==== Installation on HW rev.5 ====

  * Normaly installing trought WEB interface
  * Or you can use TFTP server: Rename OpenWrt or original firmware to **WR1043v5_tp_recovery.bin** Set static IP of your PC to *192.168.0.66/24* Router will obtain IP 192.168.0.86 for a few seconds while loading, when reset button pressed at power On.
  * If something goes wrong you always can use UART

==== UART on HW rev.5 ====

Before soldering the connector
You need to solder the jumper between resistor and RX pin

{{:media:tplink:tl-wr1043:1043-v5-with-jumper.jpg?600|}}




==== Flash Layout ====
Please read the article [[docs:techref:flash.layout]] for a better understanding. It contains a couple of explanations. Then let's have a quick view at flash layout of this particular device:

^   TP-Link WR1043ND  Flash Layout stock firmware           ^^^^^^
^ Layer0       |                       m25p80 spi0.0: m25p64      8192KiB          |||||
^ Layer1       |  mtd0 **//u-boot//** 128KiB  |   mtd1 **//firmware//** 8000KiB  |||  mtd3 **//art//** 64KiB  |
^ mountpoint   |  none            |  /                               |||  none         |
^ filesystem   |  none            |  SquashFS                        |||  none         |
^   TP-Link WR1043ND  Flash Layout           ^^^^^^
^ Layer0       |                       m25p80 [[wp>Serial Peripheral Interface Bus|spi]]0.0: m25p64      8192KiB                                                                      |||||
^ Layer1       |  mtd0 **//u-boot//** 128KiB  |  mtd5 **//firmware//** 8000KiB                                      |||    mtd4 **//art//** 64KiB  |
^ Layer2       |                              |  mtd1 **//kernel//** 1280KiB  |  mtd2 **//rootfs//** 6720KiB                           ||          |
^ <color magenta>mountpoint</color>   |                              |                               |  <color magenta>''/''</color>                          ||          |
^ filesystem   |                              |                               |  [[docs:techref:filesystems#overlayfs|overlayfs]]           ||          |
^ Layer3       |                              |                               |  1536KiB        |  mtd3 **//rootfs_data//** 5184KiB     |          |
^ <color magenta>mountpoint</color>   |  //none//                    |  //none//                     |  <color magenta>''/rom''</color>  |  <color magenta>''/overlay''</color>   |  //none//  |
^ filesystem   |  //none//                    |  //none//                     |  [[docs:techref:filesystems#SquashFS]]  |  [[docs:techref:filesystems#JFFS2]]  |  //none//  |

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.

==== Firmware flashing ====

<WRAP center round info 60%>
This is an older device with multiple versions. These instructions have been written over the years and versions of devices. When following these instructions note that the IP address may be different for different versions of hardware and boot loader. 

Ensure that you are using the firmware version appropriate for your device.
</WRAP>

=== Flashing / Recovery using tftp only (without serial console) ===

If your device doesn't even boot (e.g. due to a bad flash), and your device is recent enough (circa 2011, v1.8+), you can use the device built-in auto tftp recovery process.

  * Connect the device (one of the LAN ports) to a host computer via an ethernet cable
  * Change the host computer IP address (manual or static) to 192.168.0.66
  * Install a tftp server. This is host computer OS specific.
    * On Mac OS X, you can start the built-in tftp server with ''$ sudo launchctl load -w /System/Library/LaunchDaemons/tftp.plist''
  * Download a desired firmware (openwrt *factory.bin or the original firmware wr1043nv1_*_boot*.bin) and rename the *.bin file to wr1043nv1_tp_recovery.bin in the tftpboot directory (if you use Tftpd check log viewer for read request from your router, to make sure your rename is correct. It's good to mention here that if you use tftpd64 on Windows 11 it's possible that the log viewer may be empty. The log viewer was empty in my case under Windows 11, so probably the tftpd64 author should update his program). The v4 file needs to be named wr1043ndv4_tp_recovery.bin.
    * On Mac OS X, copy the renamed file to /private/tftpboot/
  * Use a pin or paper clip to press down the reset button (in the hole besides the power adapter hole) and connect the power, while holding down the reset button for a few seconds
  * The LEDs should flash indicating firmware upload in progress.
  * The device will automatically boot to use the new firmware after flashing.

=== Flashing / Recovery using the serial console ===

If the tftp only approach doesn't work (due to an old bootloader) or you want to debug the boot process, you will need to attach to its serial console. Depending on your HW version, you will have **one or two options to transport the firmware** into the device: 1) using tftp, or 2) (v1.x only) using the serial connection itself for file transfer (using the Kermit protocol).

Requirements:
  * [[.tl-wr1043nd#Serial|Serial access]]
  * terminal program set to **115200 8N1**, no flow control
    * ''minicom --baudrate 115200 --device /dev/ttyUSB0 --8bit'' (I couldn't type the ''tpl'' command using this)
    * ''screen /dev/ttyUSB0 115200,cs8,-ixon'' (this worked for me)
  * the new //firmware.bin// file. In case you want revert to stock firmware, you need a stripped firmware file. See [[.tl-wr1043nd#Back to original firmware]].

To **enter the boot prompt**:

When you see something like this:
<code>
No valid address in Flash. Using fixed address
ath_gmac_enet_initialize: reset mask:c02200
Scorpion  ----> S17 PHY *
athrs17_reg_init: complete
: cfg1 0x80000000 cfg2 0x7114
eth0: ba:be:fa:ce:08:41
eth0 up
athrs17_reg_init_wan done
SGMII in forced mode
athr_gmac_sgmii_setup SGMII done
: cfg1 0x800c0000 cfg2 0x7214
eth1: ba:be:fa:ce:08:41
eth1 up
eth0, eth1
Setting 0x18116290 to 0x58b1a14f
is_auto_upload_firmware=0
Autobooting in 1 seconds
</code> 

Type 
<code>
tpl
</code>
during this 1 second period.

See this example for a ([[.tl-wr1043nd/flashlog|full console log]]) when using tftp.

== 1) Commands when using tftp (lan) for firmware transfer ==

The tftp server must be listening on 192.168.0.5:69 (configurable with ''setenv'' command; use ''printenv'' if not sure), and the router must be connected through one of the lan ports. The simplest tftp server to use is dnsmasq: ''<nowiki>dnsmasq --enable-tftp --tftp-root=/directory-containing-firmware.bin</nowiki>''.

**For v1.x hardware:**

<code>
tftpboot 0x81000000 firmware.bin
erase 0xbf020000 +7c0000 # 7c0000: size of the firmware (be aware that you may have a different size thus bricking your router)
cp.b 0x81000000 0xbf020000 0x7c0000
bootm 0xbf020000
</code>

**For v2.1 hardware:**

The tftp server must be listening on 192.168.1.100:69 (Version 2.1 with U-Boot 1.1.4 (Jul 17 2015 - 14:31:22))

<code>
tftp 0x80060000 firmware.bin
erase 0x9f020000 +${filesize}
cp.b 0x80060000 0x9f020000 ${filesize}
boot.m 0x9f020000
</code>

**For v3.x hardware:**

The TFTP server must be listening on 192.168.0.66, file requested will be wr1043v3_tp_recovery.bin.
<code>
TFTP from server 192.168.0.66; our IP address is 192.168.0.86
Filename 'wr1043v3_tp_recovery.bin'.
Load address: 0x80800000
Loading: #################################################################
</code>

== 2) Commands when using Kermit (serial console) for firmware transfer (v1.x hardware only)==

The tftp protocol is insecure and sometimes it doesn't work even if the console log suggests otherwise. In such cases you can also use a Kermit client to transfer the new image on the serial connection. It may take forever and a half (15-20min) to transfer the image, but it's easier and more secure than running a tftp server. These instructions assume you're using //**ckermit**// on a Linux system, but they will give you all you need to do the same on a Windows box.

Enter the boot prompt on the serial console (see above), and in your terminal program type:

<code>
erase 0xbf020000 +7c0000 # 7c0000: size of the firmware (be aware that you may have a different size thus bricking your router)
loadb 0x81000000
</code>

Then start //ckermit// (without any arguments) and run the following commands in it (or configure your Kermit client to these parameters):

<code>
set line /dev/ttyUSB0 # Just make sure you got the right USB interface
set speed 115200
set carrier-watch off
set handshake none
set flow-control none
robust
set file type bin
set file name lit
set rec pack 1000
set send pack 1000
set window 5
send firmware.bin # Make sure you include a proper path to the file. That's why I just kept it in /home/$user
</code>

After the 15-20min file transfer, the new firmware should be on your router and you can continue in the terminal:

<code>
cp.b 0x81000000 0xbf020000 0x7c0000
bootm 0xbf020000
</code>

=== Automated flashing with a script ===

FIXME Version 2.x with newest firmware (3.19.32) hast 192.168.0.1 as default IP and maybe differences in web interface. So this script needs adaption to work for 2.x devices.

Flashing hundreds of devices using the web interface can be a real pain. You can use this shell script to automate it:
<code bash>
#!/bin/bash

# Pass the firmware image file to be flashed as the first and only
# command line argument.
#
# The second curl call will time out, but it is expected. Once the
# script exits, you can unplug the ethernet cable and proceed to the
# next router, but do KEEP each router ON POWER until the new image is
# fully written! When flashing is done the router reboots
# automatically (as shown by all the leds flashing once).

curl \
  --user admin:admin \
  --user-agent 'Mozilla/5.0 (X11; Ubuntu; Linux i686; rv:12.0) Gecko/20100101 Firefox/12.0' \
  --referer 'http://192.168.1.1/userRpm/SoftwareUpgradeRpm.htm' \
  --form "Filename=@$1" -F 'Upgrade=Upgrade' \
  http://192.168.1.1/incoming/Firmware.htm > /dev/null

sleep 1

curl \
  --max-time 2 \
  --user admin:admin \
  --user-agent 'Mozilla/5.0 (X11; Ubuntu; Linux i686; rv:12.0) Gecko/20100101 Firefox/12.0' \
  --referer 'http://192.168.1.1/incoming/Firmware.htm' \
  http://192.168.1.1/userRpm/FirmwareUpdateTemp.htm >  /dev/null
</code>

==== Upgrading OpenWrt ====
-> [[docs:guide-user:installation:generic.sysupgrade]]

==== Back to original firmware ====
-> [[docs:guide-user:installation:generic.uninstall]]

{{page>meta:infobox:dangerous&noheader&nofooter&noeditbtn}}

With the WR1043ND router, there is a catch: the stock firmware is obtained from the OEM: http://www.tplink.com/en/support/download/?model=TL-WR1043ND

  * 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
  * 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:


The following method applies both for the V1, V2 and V3 since the bootloader is the same size.


An example of an image file with the word "boot" in it is ''wr1043nv1_en_3_9_17_up_boot(091118).bin''.

Cut the first 0x20200 (that is 131,584 = 257*512) Bytes from original firmware:
<code>
dd if=orig.bin of=tplink.bin skip=257 bs=512
</code>

You should transfer the firmeware image to the /tmp folder and revert back to original firmware (if availlable you can flash the firmware via the webinterface as well):

Via the safer method using sysupgrade (the `-n` makes sure that no leftover configs are preserved from openwrt):
<code>
sysupgrade -n /tmp/tplink.bin
</code>

Or alternatively use the mtd method:
<code>
mtd -r write tplink.bin firmware
</code>

This has been confirmed by [[https://forum.openwrt.org/viewtopic.php?pid=110583#p110583|supertom64]] (for the V1), and by [[https://forum.openwrt.org/viewtopic.php?pid=232448#p232448|akirkby]] (for the V2, flashing using the webinterface). Also confirmed Feb 29, 2020 by darkspot for V1 and TL-WR*V1_140319. Back to stock can be necessary to enable freifunk when coming from pure openwrt.

As of Apr 04 2020 is also confirmed to work on TL-WR1043ND V2 on OpenWRT 19.07.02 installation: upload the **stripped** firmware on LuCi and check the force option - the router will come back on 192.168.**0**.1.



===== Warnings / Gotchas =====

==== USB 3G Modems ====
| {{:meta:icons:tango:48px-emblem-important.svg.png?nolink}} | The TL-WR1043ND v1.x does **not** deliver enough power for most USB 3G modems, which can lead to erratic behavior such as dropped/failed connections. If a 3G USB modem is to be used, consider other routers with a USB port that delivers enough amperes (e.g. the [[:toh:buffalo:wzr-hp-ag300h|Buffalo WZR-HP-AG300H]]). |

=== USB 3G modems confirmed working with TL-WR1043ND v1: ===
  * Huawei E303  
  * Huawei E303c
  * Huawei E3131  
  * Huawei E3272
  * Huawei E3531
  * Huawei E3533 (via usb-tethering)
  * ZTE MF823L
  * ZTE MF190
  * ZTE MF193
  * ZTE MF626
  * ZTE MF667 (via usb-tethering, bad connection) 

=== USB 3G modems confirmed working with TL-WR1043ND v2: ===
  * TCT Mobile One Touch X500D
  * TCT Mobile X220L
  * ZTE MF632
  * Vodafone K3765 (Huawei)
  * Huawei E160E
  * Huawei E3531

==== Connection quality drops after a few hours, latency/ping/lag spikes ====

Still reproductible with release 15.05.1; gone in LEDE 17.01.4:
If wireless performance becomes awful after a few hours and ping times to the router over wifi increase up to half a second or more, there's a good chance you're experiencing [[https://dev.openwrt.org/ticket/12372]]

Restarting wireless with the "wifi" command makes the issue temporarily go away for the next few hours. Disabling ANI (Adaptive Noise Immunity) with the following command makes the issue go away until the next reboot
''
echo 0 >/sys/kernel/debug/ieee80211/phy0/ath9k/ani
''

For more details, including how to disable ANI at boot, see longer description of the same ANI issue on the [[toh:linksys:wrt160nl|Cisco WRT160NL]] page.

===== Basic configuration =====
After flashing, proceed with [[docs:guide-quick-start:checks_and_troubleshooting|Basic configuration]].\\
Set up your Internet connection, configure wireless, configure USB port, etc.

==== OEM firmware features ====
In case you want to have the same features with OpenWrt as the OEM firmware, look this up: [[toh:tp-link:tl-features|TP-Link OEM firmware features]]

===== Specific configuration =====
==== Interfaces ====

The OpenWrt default configuration of the [[docs:guide-developer:networking:network.interfaces|network interfaces]] is as follows:
^ Interface Name   ^ Description                ^ Default configuration   ^
| ''br-lan''       | LAN & WiFi                 | 192.168.1.1/24          |
| ''eth0''         | LAN ports (1 to 4) + WAN   | //none//                |
| ''wlan0''        | WiFi                       | //disabled//            |

==== Switch Ports (for VLANs) ====

Gigabit Media Independent Interface is the internal connection to the router itself. 
^ Port                                              ^ Switch port on v1.x   ^ Switch port on v2.x and v3.x         ^
| Internet (WAN)                                    | 0                     | 5                                    |
| LAN 1                                             | 1                     | 4                                    |
| LAN 2                                             | 2                     | 3                                    |
| LAN 3                                             | 3                     | 2                                    |
| LAN 4                                             | 4                     | 1                                    |
| [[wp>Gigabit Media Independent Interface|GMII]]   | 5 (marked as CPU)     | 0 (marked as CPU) Switch0 CPU Port   |
| :::                                               | -                     | 6 Switch0 CPU Port                   |

The v2.x and v3.x get the lan and wan interface not via eth0.1/eth0.2 but via eth0 (wan) and eth1 (lan).
The eth0 is in the same vlan as port 5 on the switch.
Because of that, port 6 on the v2.x, v3.x routers is an additional CPU port - used for wan traffic only.

Wan has VLAN 2, that shouldn't be touched, as you lose the WAN port. Start your VLANs from 3, attaching them to the eth1.x sub-interfaces.

See Schematics:

{{media:tplink:tl-wr1043:tl-wr1043nd-v2_schematics.png?600|}}


Some issues with 10.03.1-rc4 on Hardware Ver.1.8 see [[https://forum.openwrt.org/viewtopic.php?pid=123269#p123269|this post]] for workaround.

There is a problem with VLAN-IDs > 9 (at least on v1.4 with 10.03.1-RC6 r28680 and v1.8 with 12.09-rc1 r34185). Using a VLAN-ID > 9 makes the router inaccessible on this interface.

VLAN-IDs > 127 not working with Chaos Calmer r47335 on hardware version 2.1.

==== Port Mirroring ====
Port mirroring is supported since [[https://dev.openwrt.org/changeset/36847/|r36847 ]]

/etc/config/network
<code>

config switch
        option name 'switch0'
        option reset '1'
        option enable_vlan '1'
        option enable_mirror_rx '1'
        option enable_mirror_tx '1'
        option enable_monitor_isolation '1'
        option enable_mirror_pause_frames '1'
        option mirror_monitor_port '4'
        option mirror_source_port '3'
config switch_vlan
        option device 'switch0'
        option vlan '1'
        option ports '1 5t'
config switch_vlan
        option device 'switch0'
        option vlan '5'
        option ports '2 3'

</code>

The port numbers are shown here:\\
{{media:tplink:tl-wr1043:tl-wr1043nd_port-numbers.jpg?400}}

==== Use the WAN-Port as a LAN-Port  ====
**remove** to following lines, to remove the wan specific configuration (vlan and interface)

**V1.x**
/etc/config/network
<code>config interface 'wan'
	option ifname 'eth0.2'
	option proto 'dhcp'</code>
and
<code>config switch_vlan
	option device 'switch0'
	option vlan '2'
	option ports '0 5t'</code>

and **add** the port 0 to the existing Vlan
<code>config switch_vlan
	option device 'switch0'
	option vlan '1'
# add port 0 to the line below
	option ports '0 1 2 3 4 5t'</code>

**V2.x**
/etc/config/network
<code>config interface 'wan'
	option ifname 'eth0'
	option proto 'dhcp'</code>
and
<code>config switch_vlan
	option device 'switch0'
	option vlan '2'
	option ports '5 6'</code>

and **add** the port 5 to the existing Vlan
<code>config switch_vlan
	option device 'switch0'
	option vlan '1'
# add port 5 to the line below
	option ports '0 1 2 3 4'</code>

==== Use eth1.<VLAN ID> interface instead of eth0.<VLAN ID> for additional VLAN-s on v2.x, v3.x router hardware ====

As mentioned above for v2.x, v3.x: 
"Start your VLANs from 3, attaching them to the eth1.x sub-interfaces."
 
Additional VLAN ID-s must be tagged on CPU port and should be referenced as eth1.<VLAN ID> physical interfaces. To clarify, if multiple VLANs are used only one can be used untagged on switch ports (on CPU port) but it is not necessarily VLAN 1. 

**Note:** the default lan interace (VLAN 1) is preconfigured to use eth1 physical interface (cpu untagged in switch configuration). VLAN 1 can also be tagged on the CPU port but the interface must be changed to eth1.1 from eth1 accordingly.

**Note:** If we create an additional VLAN, a misleading eth0.<VLAN ID> interface option appears on "Physical Settings" tab in the GUI, but use "Custom interface" option and type eth1.<VLAN ID> (e.g.: eth1.3) instead!

==== Example: Add additional VLANs on v.2.x hardware ====

The following is an example where every port in the LAN switch is moved into its own VLAN, creating a five interface router (WAN + LAN x 4).

/etc/config/network

Each Port is a VLAN

Physical Port 1 is the WAN2

Adapt to your needs
<WRAP bootlog>
<nowiki>config interface 'loopback'
        option ifname 'lo'
        option proto 'static'
        option ipaddr '127.0.0.1'
        option netmask '255.0.0.0'

config globals 'globals'
        option ula_prefix 'fd30:0c4a:0bba::/48'

config interface 'lan1'
        option ifname 'eth1.1'
        option type 'bridge'
        option proto 'static'
        option ipaddr '192.168.1.1'
        option netmask '255.255.255.0'

config interface 'lan2'
        option ifname 'eth1.3'
        option proto 'static'
        option ipaddr '192.168.2.1'
        option netmask '255.255.255.0'
        option type 'bridge'

config interface 'lan3'
        option ifname 'eth1.4'
        option proto 'static'
        option ipaddr '192.168.3.1'
        option netmask '255.255.255.0'
        option type 'bridge'

config interface 'lan4'
        option ifname 'eth1.5'
        option proto 'static'
        option ipaddr '192.168.4.1'
        option netmask '255.255.255.0'
        option type 'bridge'

config interface 'wan'
        option ifname 'eth0'
        option proto 'static'
        option ipaddr '192.168.100.100'
        option netmask '255.255.255.0'

config interface 'wan6'
        option ifname '@wan'
        option proto 'dhcpv6'

config switch
        option name 'switch0'
        option reset '1'
        option enable_vlan '1'
        option enable_vlan4k '1'

config switch_vlan
        option device 'switch0'
        option vlan '1'
        option ports '0t 1'
        option vid '1'

#This should stay untouched
config switch_vlan
        option device 'switch0'
        option vlan '2'
        option ports '5 6'
        option vid '2'

config switch_vlan
        option device 'switch0'
        option vlan '3'
        option ports '0t 4'
        option vid '3'

config switch_vlan
        option device 'switch0'
        option vlan '4'
        option ports '0t 3'
        option vid '4'

config switch_vlan
        option device 'switch0'
        option vlan '5'
        option ports '0t 2'
        option vid '5'</nowiki>
</WRAP>\\


Another one (working) (v2.x) ready for modifications
<WRAP bootlog>
<nowiki>config interface 'loopback'
       option ifname 'lo'
       option proto 'static'
       option ipaddr '127.0.0.1'
       option netmask '255.0.0.0'

config globals 'globals'
       option ula_prefix 'fdf0:f161:7c60::/48'

config switch
       option name 'switch0'
       option reset '1'
       option enable_vlan '1'

config switch_vlan
       option device 'switch0'
       option vlan '11'
       option name 'LAN1, eth1.11'
       option ports '0t 4'

config switch_vlan
       option device 'switch0'
       option vlan '12'
       option name 'LAN2, eth1.12'
       option ports '0t 3'

config switch_vlan
       option device 'switch0'
       option vlan '13'
       option name 'LAN3, eth1.13'
       option ports '0t 2'

config switch_vlan
       option device 'switch0'
       option vlan '14'
       option name 'LAN4, eth1.14'
       option ports '0t 1'

config switch_vlan
       option device 'switch0'
       option vlan '2'
       option warning 'dont change this vlan number'
       option name 'wan, eth0'
       option ports '5 6'

config interface 'lan'
       option ifname 'eth1.11 eth1.12 eth1.13 eth1.14'
       option force_link '1'
       option type 'bridge'
       option proto 'static'
       option ipaddr '192.168.1.1'
       option netmask '255.255.255.0'
       option ip6assign '60'

config interface 'wan'
       option ifname 'eth0'
       option proto 'dhcp'

config interface 'wan6'
       option ifname '@wan'
       option proto 'dhcpv6'</nowiki>
</WRAP>\\

==== Failsafe mode ====
See [[docs:guide-user:troubleshooting:failsafe_and_factory_reset|OpenWrt Failsafe Mode]] for general information.

  * Power up your router. When the 'SYS' LED starts to blink, press the //QSS// push button repeatedly until the blinking of 'SYS' LED gets faster. **Done** = You made OpenWrt **boot into OpenWrt failsafe mode.** Proceed with [[docs:guide-user:troubleshooting:failsafe_and_factory_reset#in.failsafe.mode|In OpenWrt Failsafe Mode]]

==== WiFi: Using other country regulations ====
Per default the [[:docs:guide-user:network:wifi:wifi_countrycode|WLan-"Country Code"]] is set to US. That means users of OpenWrt worldwide are limited to Channel 1-11.

To unlock the specific channels of your country, it is possible to [[docs:guide-developer:toolchain:use-buildsystem|compile]] OpenWrt with "ATH_USER_REGD" set (recommended, and enabled by default in recent OpenWRT versions).

WARNING: Do this only if you know what you're doing! Using the wrong frequencies can result in interfering with other radio services.

==== Get the usb working ====

-> [[:docs:guide-user:storage:usb-installing]]\\
-> [[docs:guide-user:storage:usb-drives]]

On 14.07 the following packages were installed to let the usb work (Those are basically the packages described in the two pages linked above):
<file>
opkg update && opkg install block-mount fdisk kmod-usb-ohci kmod-scsi-generic kmod-usb-storage-extras kmod-usb-uhci kmod-usb2 e2fsprogs kmod-fs-ext4
</file>

===== Hardware =====
==== Info ====
TP-Link naming scheme is, that numbers behind the comma, refer to changes in the firmware only, the hardware is identical.

^ Type ^  HW ver. 1.x  ^  HW ver. 2.x  ^  HW ver. 5.x  ^
| **[[wp>Instruction set]]:**               |  [[wp>MIPS_instruction_set#MIPS32|MIPS32]]  |||
| **Vendor:**                               |  [[wp>Qualcomm Atheros]]  |||
| **[[docs:techref:bootloader]]:**           |  [[docs:techref:bootloader:uboot|U-Boot]] 1.1.4  ||
| **[[docs:techref:hardware:soc|System-On-Chip]]:**  |  AR9132 rev 2  |  QCA9558  |
| **[[docs:techref:hardware:cpu|CPU]]/Frq**          |  24Kc V7.4 400 MHz  |  74Kc V5.0 720 MHz  |
| **Target name**                           |  {{tagpage>ar71xx}}  |||
| **Flash-Chip:**                           |  [[https://web.archive.org/web/20221021210048/https://www.infineon.com/dgdl/Infineon-S25FL064P_64-Mbit_3.0_V_SPI_Flash_Memory-DataSheet-v11_00-EN.pdf?fileId=8ac78c8c7d0d8da4017d0ed4dcb1535c&utm_source=cypress&utm_medium=referral&utm_campaign=202110_globe_en_all_integration-files|ST 25P64V6P]]  |  [[http://www.nexflash.com/hq/enu/ProductAndSales/ProductLines/FlashMemory/SerialFlash/W25Q64FV.htm|Winbond 25Q64FV]]  |  [[https://www.winbond.com/resource-files/w25q128fv%20rev.m%2005132016%20kms.pdf|Winbond 25Q128FVSG]]  |
| **Flash size:**                           |  8192 KiB  |||
| **RAM:**                                  |  32 MiB  |  64 MiB  |
| **Wireless:**                             |  Atheros AR9103 2.4 GHz 802.11bgn  |  QCA9558 2.4 GHz 802.11bgn  | 
| **Wireless Power:**                       |  24 dBm (251 mW)  |  25 dBm(316 mW)  |
| **802.11n:**                              |  3 x 3 : 2  |  3 x 3 : 3  |
| **[[docs:techref:hardware:switch]]:**              |  [[http://realtek.info/pdf/rtl8366_8369_datasheet_1-1.pdf|RealTek RTL8366RB]]  |  [[http://wikidevi.com/files/Atheros/specsheets/AR8327_AR8327N.pdf|Atheros AR8327N-BL1A]]  |[[https://github.com/Deoptim/atheros/raw/master/QCA8337-datasheet.pdf|Qualcomm Atheros QCA8337-AL3C]]|
| **[[docs:techref:swconfig]]:**             |  [[https://dev.openwrt.org/browser/trunk/target/linux/generic/files/drivers/net/phy/rtl8366rb.c|yes, rtl8366rb]]  |  [[https://dev.openwrt.org/browser/trunk/target/linux/generic/files/drivers/net/phy/ar8216.c|yes, ar8216]]  |
| **USB:**                                  |  Yes 1 x 2.0 ([[wp>Open Host Controller Interface|OHCI]] platform; device name ''1-1'')  ||  No  |
| **Power:**                                |  12V DC 1.5A  ||  9V DC 0.85A  |
| **[[docs:techref:hardware:port.serial|Serial]]:**  |  [[#Serial|Yes]]  |||
| **[[docs:techref:hardware:port.jtag|JTAG]]:**      |  [[#JTAG|Yes]]   |  [[#JTAG|No?]]   |

==== Performance ====
  * [[docs:techref:hardware:performance|Filesystems & network performance]] results and [[docs:guide-user:perf_and_log:performance]] howto for help on measuring.
  * [[docs:guide-user:perf_and_log:benchmark.usb|USB Benchmarks]] results.

  * This router gets around 180 Megabits/s WAN to LAN throughput, tested using nuttcp.
  * Wan to Lan Throughput V1.x 122.7 Mbps [[http://www.smallnetbuilder.com/lanwan/router-charts/bar/74-wan-to-lan|http://www.smallnetbuilder.com/lanwan/router-charts/bar/74-wan-to-lan]]
  * Using 2 mikrotik routersOS x86 on a vmware machine, doing the bandwidth test through a wr1043n with openwrt 14.07 and basic network/firewall setup, got a stable speed of 210 Mbps (tcp, udp would be higher because easier to handle). 

==== Power ====

=== Power Consumption ===

With a cheap Wattmeter i measured 6.9 W idle and 9 W under load.

=== PSU (power supply) ===

My TL-WR1043ND DE (v1.0) came bundled with the following PSU:

{{media:tplink:tl-wr1043:tl-wr1043nd_dev10_psu.jpg?250}}

Specifications:
^  ^ TL-WR1043ND DE (v1.0) ^ TL-WR1043ND v2.1 ^
| **Brand/Model**         | Leader Electronics Inc / LEI F7 | TP-LINK Tech. co., ltd. |
| **Input**               |  100-240V~ (50/60Hz, 0.6A)  ||
| **Output**              |  12V 1.5A  ||
| **Measured output**     |  12.25V  |  12.40V (w/o load)  |
| The plug (on the router side) has the following specifications: |||
| **Outer diameter**      |  5.5mm  ||
| **Inner diameter**      |  2.1mm  ||
| **Length of the shaft** |  9.5mm  ||

I successfully used the ATX PSU (from my computer) to power the router.
All I did was buying a plug with above specifications and soldered a Molex-plug to the other end.

=== Powering with different Voltages ===
:!: ** WARNING: For sure you will lose your warranty if you run the router with too high voltage and I don't guarantee it will work for you. Your router might break, so only run it with too high voltage if you know what you are doing and you don't care if the router breaks. **

Because I wanted to run the router directly from solar and the 12V battery can have between 10.4V and 14.8V I tested the router with different voltages and it runs fine with voltages between 10V and 15V. Could not see any failures or loss in performance.

=== Power consumption on DC-Side ===

I have measured simultaneously voltage and current on the DC-side of the router with 2 analogue multimeters.

It looks like my AC-DC adapter is stabilized and delivers exactly 12 Volts.

  - Without LAN Connected, without any USB device, OpenWrt Running with WLAN 10dBm (b/g AP mode) : 250mA
  - With 1x100MBit LAN, 1xHuawei E1750 in idle (not connected) : 320mA
  - With HSDPA Connection active : 400mA

The HSDPA modem seems to draw a lot of power as soon as any data is transferred. In total i guess approx. 500mA. (Was NOT possible to measure exactly because my amperemeter is very slow...)


==== Photos ====

Photos of v1.X PCB:

{{media:tplink:tl-wr1043:tl-wr1043nd-v14_pcb.jpg?0x300|PCB Board TP-Link TL-WR1043ND v1.4}}
{{media:tplink:tl-wr1043:tl-wr1043nd-v16_pcb.jpg?0x300|PCB Board TP-Link TL-WR1043ND v1.6}}


Photos of v2.X PCB:

{{media:tplink:tl-wr1043:tl-wr1043nd-v21_pcb.jpg?0x300|PCB TP-Link TL-WR1043ND v2.1}}
{{media:tplink:tl-wr1043:tl-wr1043nd_images_board2.jpg?0x300|PCB TP-Link TL-WR1043ND v2.1}}

More photos of the v2 version: [[http://galeria.tech-blog.pl/TP-Link_TL-WR1043ND_v2/|TP-Link TL-WR1043ND v2]]

==== Opening the case ====

Note: This will void your warranty! 

The case of the WR1043N v1.x is composed of 4 pieces:

  * Top cover (white, with logo)
  * Bottom cover (white, with sticker)
  * Front (transparent, black)
  * Outer frame (black, vents on the sides)

There are only two screws at the back of the device, under the rubber feet. The rest of the case is kept together by two latches at the front of the device, and a system of guides and hooks in the front.

  - Remove the antennas.
  - Remove the rubber feet in the back and undo the screws.
  - Unscrew all three retaining nuts on the antenna connectors and carefully push them into the housing. If you find this hard to do, leave them in place: you'll have to pay attention and avoid pulling the outer frame, as there are wires running from the back of the device all the way to the front of the board.
  - Push one of the bottom screws back into place to lift the top cover, and keep it that way using a finger.
  - With the top slightly open, push the bottom cover away. Use a screwdriver if you can't reach it with your fingers.
  - If you have unscrewed the antenna connectors, now you can remove outer frame. Otherwise just carefully slide it  out of the way: this will expose the clips that keep the top and bottom covers together.
  - With a flathead screwdriver or similar tool, gently pry the two front clips apart. Each clip has two latches and is located near the corners, next to the black front. Put your screwdriver behind the latches and push it towards the ethernet ports.
  - Now the top cover can slide out the vertical guides on the black front.
  - The black front also has three plastic hooks that go into matching holes in the bottom cover. To remove it, pull the front away and then push it down.

Pictures can be found [[http://www.flickr.com/photos/19739482@N05/sets/72157624000636958/|here]]

The case of the WR1043N v2.x is composed of 2 pieces:

  * Top cover (black (bluish))
  * Bottom cover (gray)

1. Remove the four screws on the bottom cover.
2. Use a thin object to release the top cover from the bottom cover

==== Putting it back together ====

v1.x
  - Place the board on the bottom cover, so that the two plastic pins at the front keep it in place.
  - If you undid the antenna connectors, put them back in and tighten the nuts.
  - Place the outer frame behind the board and make sure it sits flush to the connectors.
  - Insert the hooks of the front into the holes in the bottom cover, don't push it in yet.
  - Make the top cover slide into the vertical guides on the front. Don't push it down yet.
  - Push the front towards the back so the hooks are engaged, then push down the top cover.
  - Fasten the screws and re-apply the rubber feet.

v2.x
  - Put the top cover back on
  - Press until it clicks back nicely to the bottom cover.
  - Put back the screws

==== Serial ====
-> [[docs:techref:hardware:port.serial]] general information about the serial port, serial port cable, etc.
How to connect to Serial Port:

Solder a header as shown in the picture or wires with a connector directly. The device uses TTL @ 3.3V and not a standard RS-232 Serial that operates between 3 and 15V, so do not try to connect it to a common serial adapter: you will certainly fry the serial circuit or even the whole board. There are plenty of USB to TTL and RS-232 to TTL available on the market, just be careful with the voltage: the standard is 5V and it may also damage your board. Look for the ones with 3.3V or with both voltages and a way to switch between them.

Don’t forget that the **TX pin** of the serial port must linked to the **RX pin** of the router and the RX to TX!

Bits per second: **115200**\\
Data bits: **8**\\
Parity: **None**\\
Stop bits: **1**\\
Flow control: **None**\\

{{media:tplink:tl-wr1043:tl-wr1043nd_serial_pinouts.jpg?500|Serial Pinouts}}

If you use the serial connection more often or want to have a permanent modification you can build a stereo audio jack at the back of the router and use the FTDI serial cable TTL-232R-3V3-AJ. As jumper wire you can recycle an old floppy drive power cable.

{{media:tplink:tl-wr1043:tl-wr1043nd_serjack.jpg?400|}}

=== Receive (RX) Disabled ===

Some revisions of v1.x require a jumper between the RX serial pin and the resistor R362 to enable serial writes. See this post for details:

[[https://forum.openwrt.org/viewtopic.php?pid=176448#p176448]]

If you find that the serial console will not accept write commands, check with a multimeter that you have continuity between RX and R362. 

If you don't have continuity you will need to jumper them, here is my working example:

{{media:tplink:tl-wr1043:tl-wr1043nd_rxjumper.png?400|}}

I went to the right hand side of the resistor for ease of soldiering, but there may be better solutions. 

I also noticed that the small hole just below R362 has continuity to the RX pin so that may provide a cleaner solution with a much smaller jumper. 

==== JTAG ====
-> [[docs:techref:hardware:port.jtag]] general information about the JTAG port, JTAG cable, etc.

{{media:tplink:tl-wr1043:tl-wr1043nd_jtagport.jpg?400|}}

JTAG Line:

[[http://forum.openwrt.org/viewtopic.php?pid=79931#p79931]]


Software:

Download EJTAG Debrick Utility 3.0.1

Backup:

Backup whole flash:

<code>
tjtag3.exe -backup:custom /fc:25 /window:bf000000 /start:bf000000 /length:00800000
</code>

Backup UBoot:

<code>
tjtag3.exe -backup:custom /fc:25 /window:bf000000 /start:bf000000 /length:00020000
</code>

Backup Firmware:

<code>
tjtag3.exe -backup:custom /fc:25 /window:bf000000 /start:bf020000 /length:00800000
</code>

<WRAP center round important 83%>At the moment it is **NOT** possible to **UNBRICK** the router by **JTAG** (no write access to flashrom). So be very careful not to overwrite the u-boot.</WRAP>



==== GPIOs ====
-> [[docs:techref:hardware:port.gpio]]

The AR913x platform provides 22 GPIOs. Some of them are used by the router for status LEDs, buttons and to communicate with the RTL8366RB. The table below shows the results of some investigation:

^        ^               ^            ^  Voltage level at GPIO in output-mode  ^^  gpioX/value in input-mode when GPIO is: ^^^
^  GPIO  ^  Common Name  ^  PCB Name  ^  gpioX/value=1  ^ gpioX/value=0         ^  Floating  ^  Pulled to GND  ^  Pulled to Vcc  ^
|      0 |               |  ->R713    |            3.3V |                    0V |          1 |               0 |        1 |
|      1 |  USB          |  D18=D9    |              0V |                  3.3V |          1 |               1 |        1 |
|      2 |  SYS          |  D19=D8    |              0V |                  3.3V |          1 |               1 |        1 |
|      3 |  RESET        |  SW6       |            3.3V |                    0V |          1 |               0 |        1 |
|      4 |               |            |                 |                       |            |                 |                  |
|      5 |  QSS          |  D31=D10   |            3.3V |                    0V |          0 |               0 |        1 |
|      6 |               |            |                 |                       |            |                 |                  |
|      7 |  QSS-Button   |  SW8=SW9   |            3.3V |                    0V |          1 |               0 |        1 |
|      8 |  Setting data direction to output and value to 0 causes hard reset of the SoC                         |||||||
|      9 |  WLAN         |  D11=D7    |              0V |                  3.3V |          1 |               1 |        1 |
|     10 |  P1-Tx        |            |   overriden by tty-kernel module       ||          1 |               0 |        1 |
|     11 |               |            |                 |                       |            |                 |                  |
|     12 |               |            |                 |                       |            |                 |                  |
|     13 |  P1-Rx        |            |            3.3V |                    0V |          0 |               0 |        1 |
|     14 |               |            |                 |                       |            |                 |                  |
|     15 | USB PSU OC CHK*   | ->R706     |            3.3V |                    0V |          1 |               0 |        1 |
|     16 | USB PSU EN*  | ->R708     |            3.3V |                    0V |          1 |               0 |        1 |
|     17 |               |            |                 |                       |            |                 |                  |
|     18 |  Data line of the RTL8366RB                                                                           |||||||
|     19 |  Clock line of the RTL8366RB                                                                          |||||||
|     20 |               |  GPIO20    |            3.3V |                    0V |          1 |               0 |        1 |
|     21 |  USB PSU EN** |            |                 |                       |            |                 |                  |

* USB power control for v1 hardware. GPIO 16 is for USB power enable and GPIO 15 is to check overcurrent, but resistors R706 and R708 must be soldered to use these GPIOs.
** USB power control for v2 hardware. GPIO 21 is for USB power enable, no hardware mods needed, works out of the box.

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 [[http://squidge.sourceforge.net/gpio/|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. 

==== LEDs ====
How to configure LEDs in general, see the LED section in the [[docs:guide-user:base-system:led_configuration]].

The WR1043ND has 10 LEDs:

^ LED name               ^ LED print   ^ Internal name              ^ Trigger              ^
| Power                  | PWR         | tl-wr1043nd:green:power    | N/A                  |
| System                 | SYS         | tl-wr1043nd:green:system   | ''heartbeat''        |
| Wireless LAN           | WLAN        | tl-wr1043nd:green:wlan     | ''netdev:wlan0''     |
| LAN Port 4             | 4           | unknown                    | N/A                  |
| LAN Port 3             | 3           | unknown                    | N/A                  |
| LAN Port 2             | 2           | unknown                    | N/A                  |
| LAN Port 1             | 1           | unknown                    | N/A                  |
| Wide Area Network      | WAN         | tl-wr1043nd:green:wan      | N/A                  |
| Universal Serial Bus   | USB         | tl-wr1043nd:green:usb      | ''ledtrig-usbdev''   |
| Quick Security Setup   | QSS         | tl-wr1043nd:green:qss      | User preference      |

ledtrig-usbdev is only available in attitude adjustment (Trunk) and in self-built Backfire images using [[https://dev.openwrt.org/ticket/9239|this set of patches]].

==== Buttons ====
-> [[docs:guide-user:hardware:hardware.button]]. For custom action on pressing button [[docs:guide-user:hardware:hardware.button#using.atheros.00-button.uci|the easy way]] with ''00-button'' script works nicely.

The TP-Link TL-WR1043ND has two buttons:
^ BUTTON                 ^ Event   ^ Backfire ID   ^ Attitude Adjustment ID   ^
| Reset                  | reset   | BTN_0         | reset                    |
| Quick Security Setup   | QSS     | BTN_1         | wps                      |

The QSS button is located at the front and can be easily pressed with a finger. The Reset button is located at the back and cannot be pressed with a finger, you need a small item (pen typically) to push it in.

//:!: Note: you don't need to configure or activate buttons to get the [[#failsafe_mode|Failsafe mode]] working, it will work by default.//

//:!: Note2: From versions 1.8 up to 2.x holding the reset button for more than 30' resets to OpenWrt initial settings.//

//:!: Note3: If you use current trunk version of OpenwRT then the reset button is controlled through /etc/rc.button/reset file. If you hold the button for longer than 5 seconds, then OpenWrt resets to initial settings. You can change the behaviour in this file: /etc/rc.button/reset//

===== Debricking =====
-> [[docs:guide-user:troubleshooting:generic.debrick]]

**NOTE:** If you accidentally bricked your router by overwriting the bootloader, try the following:
  - Desolder the Spansion SPI-Flash ([[http://www.spansion.com/Support/Datasheets/S25FL064P_00.pdf|here]] is the datasheet) from the board. I used tin foil to "mask" out everything else which I did not want to desolder and used a heat gun. It worked quite nice.
  - Find a way to connect the SPI flash to something with SPI interface.... I used a AVR microcontroller. {{:media:tplink:spi_flash1.pdf|Here}} you can download a pdf containing the layout for the adapter board I made to solder the Spansion SPI flash chip on, in order to connect it to the AVR. Attention, the PDF is mirrored and it is intended to manufacturing boards with the [[http://thomaspfeifer.net/direct_toner_pcb.htm | direct toner method]].
  - Write the bootloader into the flash. I got my bootloader out of another wr1043nd.
  - Solder the chip back into the router.
  - The router shall now be unbricked.

===== Bootloader Mods =====
  - you could read about [[docs:techref:bootloader]] in general and about [[docs:techref:bootloader:uboot|Das U-Boot]]/[[docs:techref:bootloader:uboot.config|Configuration of U-Boot]] in particular.
  - the uboot version you find on the 1043 is a fork of mainline U-Boot version 1.1.4 from 2005-12-17 [[ftp://ftp.denx.de/pub/u-boot/|see here]]. You can / you cannot FIXME take a current mainline version of uboot and simply cross-compile it for WR1043ND! TP-Link-Version: [[http://www.tp-link.com/support/gpl.asp]]. It contains the file ''u-boot-ap83.tar.bz2'' which is about 6,06 MiB in size, deflate this as well. The deflated source code will occupy about 37MiB of space, start with reading the ''README''.
  - also see [[ftp://ftp.denx.de/pub/u-boot/]] and compare the versions.
  - you may be able to cross compile the code with the OpenWrt [[wp>toolchain]] [[http://buildroot.org/|Buildroot]]. See [[docs:guide-developer:toolchain:start]] for guidance. But you may need to use other toolchain to crosscompile, like the ELDK (Embedded Linux Development Kit).
  - :!: **''Problem:''** you cannot test your bootloader, because for some obscure reason, you don't have write access to the flash via [[#JTAG]].

==== Making bootloader partition writable ====

=== Permanent method ===

Look at target/linux/ar71xx/files/arch/mips/ar71xx/mach-tl-wr1043nd.c (in trunk it's target/linux/ar71xx/files/drivers/mtd/tplinkpart.c)
<code c>
static struct mtd_partition tl_wr1043nd_partitions[] = {
  {
    .name   = "u-boot",
    .offset   = 0,
    .size   = 0x020000,
    .mask_flags = MTD_WRITEABLE,
  } , {
    .name   = "kernel",
    .offset   = 0x020000,
    .size   = 0x140000,
  } , {
    .name   = "rootfs",
    .offset   = 0x160000,
    .size   = 0x690000,
  } , {
    .name   = "art",
    .offset   = 0x7f0000,
    .size   = 0x010000,
    .mask_flags = MTD_WRITEABLE,
  } , {
    .name   = "firmware",
    .offset   = 0x020000,
    .size   = 0x7d0000,
  }
};
</code>
Remove the line 
<code c>
.mask_flags = MTD_WRITEABLE,
</code>
for the partition named "u-boot" to make it writeable.

=== Temporary method ===
<code>
opkg install kmod-mtd-rw
insmod mtd-rw i_want_a_brick=1
dd if=./FILE of=/dev/mtdX
</code>
==== Change MAC Address ====

  * Get the uboot image via the following command <code bash>cp /dev/mtd0ro /tmp/uboot.org</code>
  * Verify is a 1 to 1 copy (expect no output) <code bash>cmp -l /dev/mtd0ro /tmp/uboot.org</code>
  * Backup your original uboot <code bash>tar -czf /tmp/uboot.tar.gz -C /tmp uboot.org
ln -s /tmp/uboot.tar.gz /www/uboot.tar.gz</code> and download via http://192.168.1.1/uboot.tar.gz
  * At the offset 0x1FC00 you will usually find your mac address. <code bash>hexdump -n 6 -s 130048 -e '"%06.6_ax " 5/1 "%02X:" 1/1 "%02X""\n"' /tmp/uboot.org</code>
  * You can change it with an hex editor. I use [[http://www.dettus.net/dhex/ | dhex]]. Or use the following command <code bash>newmac=00:BA:AD:BE:EF:69
echo $newmac | awk -v FS="[: -]" '{for (i=1; i<=NF; i++) printf "%c", ("0x" $i)+0 }' | dd conv=notrunc bs=1 count=6 seek=130048 of=/tmp/uboot.org
mv /tmp/uboot.org /tmp/uboot.mod</code>
  * Double check your newly created, or spoof MAC Address: <code bash>hexdump -C -n 16 -s 130048 /tmp/uboot.mod
cmp -l /dev/mtd0ro /tmp/uboot.mod</code>
  * After changing the MAC and making the u-boot mtd flash portion writeable, you can write the modified uboot image back to flash: <code bash>mtd write /tmp/uboot.mod u-boot</code> where "uboot.mod" is the filename of your modified uboot image.
  * If the above command fails, you missing the custom firmware step, don't go any further.
  * After reboot a new radio1 will be created with default interface. To keep current settings and prevent radio1 creation <code bash>uci set wireless.radio0.macaddr=$newmac
uci commit wireless
reboot & exit
</code>
  * To get rid of wild radio1 after reboot, instead of the above prevention, get the cure: <code bash>uci set wireless.radio0.macaddr=$(uci get wireless.radio1.macaddr)
uci delete wireless.@wifi-iface[-1]
uci delete wireless.radio1
uci commit wireless
</code>
  * Your old MAC Address could be recovered from the sticker in the back of your router. Write it down securely, if in a hard to access location.

===== Hardware Mods =====
As a beginner, you really should inform yourself about [[docs:techref:hardware:soldering]] in general and then even obtain some experience!

==== 64MB RAM Mod for v1 model ====
<WRAP center round info 60%>
V2 Model uses DDR2 BGA chip: Zentel A3R12E40CBF
</WRAP>

The Device uses a DDR1 16Mbit x 16bit (16Mibit*16=256 mebibit. 256 mebibit/8=32MiByte) 400MHz chip. Replace it with any 32Mbit x 16bit chip. 333MHz instead of 400MHz also works fine. It's quite hard to find these chips. The best chance is to have a look at DDR-SODIMM. Since there are no 64Mbit x 16Bit DDR1 Chips available -> no 128 MB mod!

Working chips:
  * Hynix HY5DU121622DTP-D43 (From Mustang DDR-SODIMM 512 MB)
  * Hynix HY5DU121622CTP-J  (PC333 DDR RAM)
  * Infineon HYB25D512160BE (From Infineon DDR-SODIMM 512 MB)
  * EtronTech EM6AB160TSA-5G (PC400 200MHz)
  * Nanya NT5DS32M16BS-6K (From DDR-SODIMM 512 MB, 333MHz), update: restarting device fail every time, have to power un-replug. Plus the kernel still report 200MHz RAM speed, and this feels RAM overclocking. Changing to Hynix DDR400 fix the restarting hang bug.


**Additional list that may work:**

^      ^          ^ Type                  ^ ID Code                ^ Vendor    ^
| DDR  | 32Mx16   | PC400 TSOP Pb Free    | HY5DU121622DTP-D43-C   | Hynix     |
| DDR  | 32Mx16   | PC400 TSOP Pb Free    | H5DU5162ETR-E3C        | Hynix     |
| DDR  | 32Mx16   | PC400 Pb Free         | K4H511638G-LCCC        | Samsung   |
| DDR  | 32Mx16   | PC400 Pb Free         | K4H511638J-LCCC        | Samsung   |
| DDR  | 32Mx16   | PC400                 | A3S12D40ETP-G5         | Zentel    |
| DDR  | 32Mx16   | PC400                 | NT5DS32M16BS-5T        | Nanya     |
| DDR  | 32Mx16   | PC400 PB Free         | P3S12D40ETP-GUTT       | Mira      |
| DDR  | 32Mx16   | PC333 CL2.5 TSOP      | MT46V32M16TG-6T:F      | Micron    |
| DDR  | 32Mx16   | PC333 CL2.5 TSOP      | MT46V32M16P-6T:F       | Micron    |
| DDR  | 32Mx16   | PC333 PB Free TSOP    | EDD5116ADTA-6B-E       | Elpida    |
| DDR  | 32Mx16   | PC333 PB Free TSOP    | HYB25D512160CE-6       | Qimonda   |
| DDR  | 32Mx16   | PC333 PB Free TSOP    | HYB25D512160CEL-6      | Qimonda   |
| DDR  | 32Mx16   | PC333 PB Free TSOP    | HYB25D512160DE-6       | Qimonda   |

{{media:tplink:tl-wr1043:tl-wr1043nd_rammod-small.jpg?500|}}

<code>
root@OpenWrt:~# free
total used free shared buffers
Mem: 62104 17472 44632 0 1392
Total: 62104 17472 44632
</code>

This chip from Digikey should work too, if you aren't able to obtain a DDR-module: {{http://www.digikey.de/product-detail/de/AS4C32M16D1-5TCN/1450-1006-ND/4234565|Alliance Memory, Inc. AS4C32M16D1-5TCN}}

==== I²C GPIO Mod ====

An I²C-bus can easily be added using the GPIO-lines of the AR913x-SoC. So far, the only usable ones which have been confirmed to work are GPIO 0 (the unpopulated R713 located in the bottom right corner of the SoC, using the pad facing R714), GPIO 5 (the QSS-LED, easily soldered at D10,left pin with '+') and GPIO 20 (labeled on the pcb, next to the RAM chip, easily soldered from the bottom side). Using GPIO 0 and 20 may be the best choice, as they are not used, so there are no issues about removing the LED driver(bindings) or pcb components. If GPIO 5 has to be used, it should be used for SDA (it has less level changes than SCL). There are only two pull-up resistors of 4,7k-10k needed, which have to be soldered between the appropriate GPIO line and Vcc (found at the spot labeled TP3V3, about 2 cm above the WiFi-shielding). The common ground can be obtained from the TP_GND spot (between P1 and the flash chip). Remember this bus runs at 3.3V level, when connecting I²C-devices. \\
To improve signal integrity (in this case namely a solid logic low level on GPIO 5), you can replace R373 with a piece of wire and remove the LED D31. R373 seems to be the current limit resistor for the LED D31.
{{ media:tplink:i2c-gpio.png?400 }}

Make sure to install package kmod-i2c-gpio-custom.
To load the kernel module (with SCL=GPIO 0 and SDA=GPIO 20), do a:
<code>
insmod i2c-gpio-custom bus0=0,20,0
</code>
If your I2C-bus runs successfully, you can enable it on boot by creating a file in /etc/modules.d called "55-i2c-gpio-custom" with the options appropriate to your bus configuration. For example:
<code>
i2c-gpio-custom bus0=0,20,0
</code>

A more convenient way to add an I2C-bus to this router, without a modification of the internal hardware (and risking your warranty), is using the [[docs:guide-user:hardware:usb.i2c-tiny-usb|I²C Tiny-USB]] adapter. The downsides are, that it is not as cheap as the I²C-GPIO mod, and the longterm-stability is lower (temporary USB disconnects can occur randomly or due to EMI, but the I2C-subsystem is not designed for sudden disconnects). Remember this bus runs at 5V level, when connecting I²C-devices.

==== Flash Mod ====

Update (2020. 02. 24.):
The following instructions are working only with target: ar71xx, because ar71xx images automaticly correct the size of the overlay partition.
The new ATH79 target currently (and propably later) miss this feature.
Even updating modded unit result limited flash size (8Mb), and most propably lose of wifi (ART partition missplace).
At the end of the tutorial you can read updated information how to migrate to ATH79 target.
End of Update

You can install 16 MB flash Winbound 25Q128

Tested method on HW version 1, board version: 1.8:
The board has SOP16 (16 pin) flash chip pin layout, BUT under it also a SOP8 (discovered during the update process :) )

(I am windows guy mainly)

1. Backup "boot", and "ART" partition:
   list partitions:
   cat /proc/mtd

   backup:
   cat /dev/mtd0 > /tmp/mtd0.bin
   cat /dev/mtd4 > /tmp/mtd4.bin
   The 2 .bin file can be saved with winscp on windows, most easily.

2. Create "empty" file:
   You have to create image file, with the following layout:
   BOOT+"actual openwrt factory image"+"empty file"+ART
   The final image size have to match the size of the flash (16M),
   so you have to play with the size of the "empty file".
   
   under linux:
   dd if=/dev/zero bs=1 count=FILESIZE | tr "\000" "\377" > empty
   You HAVE TO set the FILESIZE

3. Create new flash file data (for flash programing):
   In windows:
   copy /B mtd0.bin+"actual openwrt factory image"+"empty file (wich means all FF)"+mtd4.bin final.bin

4. Flash with programmer.
   I had used one TL866II Plus.
   Don't buy "CH341A", it is garbage, voltages incorrect, ect.
   
5. Replace "U14" marked flash chip, and boot.
   The overlay partition size will autocorrect at the first boot.
   
6. Profit.

SSH was not worked until seting the interfeace (to "lan"). (?) 18.06.1 specific?

Wifi tested, working.

Best of luck!

7. Update: Second mod with one SOP8 pinout flash confirmed to work. (HW  version 1, Board version 1.8)

ATH97 migration update (2020. 02. 24):

As, you can read here:
https://forum.openwrt.org/t/using-release-ath79-19-07-0-kernel-and-packages-on-hardware-modded-tp-link-wr703n-16mb-64mb-without-snapshot-compilation/54310/7

Another great user ([[https://forum.openwrt.org/u/Tarask1n/summary|Tarask1n]]) of the openwrt forum had simmilar problems with the Tp-Link WR-703n unit.
Results of his great work, he created a script, which can patch the original kernel to utilize the full available flash (eg: 16M)

The patch can be reached from here (With absolutely no warranty, you have the full responsibility!)
https://1drv.ms/u/s!Agn0XLRpyDNbiMAf1ZuhQ_lfcGmkIg?e=PNttUU

To make this script work you need to have an - openwrt patched - lzma utility.
As a linux nooby (me), the easyest was (which was not easy), to clone the openwrt github repo, and compile/make menuconfig.
On Ubuntu 18.04 LTS i had a ton of dependency problems, and most of them was not an easy google search.

My succesful build was needed further editing of imagebuilder configuration files as the following:

Edited: openwrt-imagebuilder-19.07.1-ath79-generic.Linux-x86_64\target\linux\ath79\image\common-tp-link.mk
Add lines:

  define Device/tplink-16m
    $(Device/tplink)
    TPLINK_FLASHLAYOUT := 16M
    IMAGE_SIZE := 15872k
  endef

Edited: openwrt-imagebuilder-19.07.1-ath79-generic.Linux-x86_64\target\linux\ath79\image\generic-tp-link.mk

Search for:

  define Device/tplink_tl-wr1043nd-v1
    $(Device/tplink-8m)
    ATH_SOC := ar9132
    DEVICE_TITLE := TP-Link TL-WR1043N/ND v1
    DEVICE_PACKAGES := kmod-usb-core kmod-usb2 kmod-usb-ledtrig-usbport
    TPLINK_HWID := 0x10430001
    SUPPORTED_DEVICES += tl-wr1043nd
  endef
  TARGET_DEVICES += tplink_tl-wr1043nd-v1
  
Change it to (1 line change):

  define Device/tplink_tl-wr1043nd-v1
    $(Device/tplink-16m)
    ATH_SOC := ar9132
    DEVICE_TITLE := TP-Link TL-WR1043N/ND v1
    DEVICE_PACKAGES := kmod-usb-core kmod-usb2 kmod-usb-ledtrig-usbport
    TPLINK_HWID := 0x10430001
    SUPPORTED_DEVICES += tl-wr1043nd
  endef
  TARGET_DEVICES += tplink_tl-wr1043nd-v1

After build, i had:

16.253.928 byte long "...factory.bin" image    >>> This image was not tested!

 3.735.822 byte long "...sysupgrade.bin" image >>> This image was tested, and did proper ar71xx > ATH79 migration. Wifi was working, flash size was correct.
===== Other models with the same hardware =====

  * [[http://www.canyon-tech.com/archive/connectivity/wireless/CNP-WF514N3A|Canyon CNP-WF514N3A]] description and internal photos [[http://www.dd-wrt.com/phpBB2/viewtopic.php?t=148618|here]]
  * [[http://www.proware.com.cn/product-detail.asp?productId=1010195&t=4#info|Proware PW-RN611D/MH5-WR1043ND]] probably another clone...
  * [[:toh:tp-link:tl-wdr7500|TP-Link TL-WDR7500]] TP-Link TL-WDR7500 / TP-Link Archer C7 AC1750 (similar hardware to v2.1)
  * [[https://wikidevi.com/wiki/TP-LINK_TL-WR1045ND|TL-WR1045ND]] Looks similar to hardware V3
==== OpenVPN performance ====
This was done with an v5 version. (775MHZ)

<WRAP bootlog>
root@OpenWrt:~# iperf3 -c 10.4.20.10 -p 5201 -t 10
Connecting to host 10.4.20.10, port 5201
[  5] local 10.0.4.2 port 37506 connected to 10.4.20.10 port 5201
[ ID] Interval           Transfer     Bitrate         Retr  Cwnd
[  5]   0.00-1.00   sec  1.88 MBytes  15.7 Mbits/sec    0    142 KBytes       
[  5]   1.00-2.00   sec  1.88 MBytes  15.7 Mbits/sec    0    233 KBytes       
[  5]   2.00-3.00   sec  1.75 MBytes  14.7 Mbits/sec    0    326 KBytes       
[  5]   3.00-4.00   sec  1.88 MBytes  15.7 Mbits/sec    0    421 KBytes       
[  5]   4.00-5.00   sec  1.75 MBytes  14.7 Mbits/sec   18    339 KBytes       
[  5]   5.00-6.00   sec  1.75 MBytes  14.7 Mbits/sec    0    390 KBytes       
[  5]   6.00-7.00   sec  1.88 MBytes  15.7 Mbits/sec    0    430 KBytes       
[  5]   7.00-8.00   sec  2.00 MBytes  16.8 Mbits/sec    0    455 KBytes       
[  5]   8.00-9.00   sec  1.62 MBytes  13.6 Mbits/sec    0    469 KBytes       
[  5]   9.00-10.00  sec  2.12 MBytes  17.8 Mbits/sec    0    476 KBytes       
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval           Transfer     Bitrate         Retr
[  5]   0.00-10.00  sec  18.5 MBytes  15.5 Mbits/sec   18             sender
[  5]   0.00-10.26  sec  18.6 MBytes  15.2 Mbits/sec                  receiver

iperf Done.
</WRAP>\\

==== OEM bootlog from v5 ====
<WRAP bootlog>

< uBOOT should be here >
< GARBAGE from my raspi - Serial... >

20000-0x000000040000 : "u-boot"
[    0.480000] 0x000000040000-0x000000160000 : "uImage"
[    0.480000] 0x000000160000-0x000000ff0000 : "rootfs"
[    0.490000] mtd: partition "rootfs" set to be root filesystem
[    0.500000] 0x000000ff0000-0x000001000000 : "ART"
[    0.500000] flash_chrdev : flash_chrdev_init
[    0.640000] ag71xx_mdio: probed
[    0.650000] eth0: Atheros AG71xx at 0xb9000000, irq 4
[    1.230000] eth0: Atheros AR8327 switch driver attached.
[    4.150000] ag71xx ag71xx.0: eth0: connected to PHY at ag71xx-mdio.0:00 [uid=004dd036, driver=Atheros AR8216/AR8236/AR8316]
[    4.170000] TCP cubic registered
[    4.170000] NET: Registered protocol family 17
[    4.170000] Bridge firewalling registered
[    4.180000] 8021q: 802.1Q VLAN Support v1.8
[    4.180000] ### of_selftest(): No testcase data in device tree; not running tests
[    4.200000] VFS: Mounted root (squashfs filesystem) readonly on device 31:3.
[    4.200000] Freeing unused kernel memory: 180k freed
- preinit -
- regular preinit -
jffs2 not ready yet; using ramdisk
- init -
[    6.460000] liblog: module license 'unspecified' taints kernel.
[    6.460000] Disabling lock debugging due to kernel taint
[    6.730000] NET: Registered protocol family 10
[    6.870000] SCSI subsystem initialized
[    7.040000] Button Hotplug driver version 0.4.1
[    7.120000] PPP generic driver version 2.4.2
[    7.140000] tun: Universal TUN/TAP device driver, 1.6
[    7.150000] tun: (C) 1999-2004 Max Krasnyansky <maxk@qualcomm.com>
[    7.220000] PPP MPPE Compression module registered
[    7.230000] NET: Registered protocol family 24
[    7.330000] L2TP core driver, V2.0
[    7.340000] L2TP netlink interface
[    7.420000] IPv6 over IPv4 tunneling driver
[    7.460000] GRE over IPv4 demultiplexor driver
[    7.500000] GRE over IPv4 tunneling driver
[    7.550000] bonding: Ethernet Channel Bonding Driver: v3.7.1 (April 27, 2011)
[    7.670000] ip_tables: (C) 2000-2006 Netfilter Core Team
[    7.840000] nf_conntrack version 0.5.0 (960 buckets, 3840 max)
[    8.070000] PPPoL2TP kernel driver, V2.0
[    8.110000] PPTP driver version 0.8.5
[    8.480000] xt_time: kernel timezone is -0000
[    8.840000] nf_conntrack_rtsp v0.6.21 loading
[    8.860000] nf_nat_rtsp v0.6.21 loading
[    8.900000] Netfilter messages via NETLINK v0.30.
[    8.940000] ctnetlink v0.93: registering with nfnetlink.
[    9.200000] ssdk_plat_init start
[    9.200000] Register QCA PHY driver
[    9.320000] qca-ssdk module init succeeded!
[    9.470000] fuse init (API version 7.18)
reloadconfig() begin:
reloadconfig() end:
mergeconfigbycountry() begin
user has set country
mergeconfigbycountry() do nothing end
reload_profile() begin:
reload_profile() end:

Please press Enter to activate this console. [   12.190000] ADDRCONF(NETDEV_UP): eth0: link is not ready
GMT+00:00
Fri Jan  1 00:00:00 GMT 2016
[SWITCH DEBUG] Clear Port(0) PVID
[SWITCH DEBUG] Clear Port(1) PVID
[SWITCH DEBUG] Clear Port(2) PVID
[SWITCH DEBUG] Clear Port(3) PVID
[SWITCH DEBUG] Clear Port(4) PVID
[SWITCH DEBUG] Clear Port(5) PVID
[SWITCH DEBUG] Flush vlan entries.
[SWITCH DEBUG] Create VLAN VID=1
[SWITCH DEBUG] Add tagged port(0) to VLAN(1)
[SWITCH DEBUG] Add untagged port(1) to VLAN(1)
[SWITCH DEBUG] Add untagged port(2) to VLAN(1)
[SWITCH DEBUG] Add untagged port(3) to VLAN(1)
[SWITCH DEBUG] Add untagged port(4) to VLAN(1)
[SWITCH DEBUG] Set Port(0) PVID(1)
[SWITCH DEBUG] Set Port(0) ingress to secure
[SWITCH DEBUG] Set Port(1) PVID(1)
[SWITCH DEBUG] Set Port(1) ingress to secure
[SWITCH DEBUG] Set Port(2) PVID(1)
[SWITCH DEBUG] Set Port(2) ingress to secure
[SWITCH DEBUG] Set Port(3) PVID(1)
[SWITCH DEBUG] Set Port(3) ingress to secure
[SWITCH DEBUG] Set Port(4) PVID(1)
[SWITCH DEBUG] Set Port(4) ingress to secure
[SWITCH DEBUG] Create VLAN VID=4094
[SWITCH DEBUG] Add tagged port(0) to VLAN(4094)
[SWITCH DEBUG] Add untagged port(5) to VLAN(4094)
[SWITCH DEBUG] Set Port(0) PVID(4094)
[SWITCH DEBUG] Set Port(0) ingress to secure
[SWITCH DEBUG] Set Port(5) PVID(4094)
[SWITCH DEBUG] Set Port(5) ingress to secure
[SWITCH DEBUG] Set Port(0) PVID(0)
[   13.850000] device eth0 entered promiscuous mode
[   13.850000] ADDRCONF(NETDEV_UP): eth0.4094: link is not ready
[   14.220000] ADDRCONF(NETDEV_UP): lo: link is not ready
[   14.230000] ADDRCONF(NETDEV_UP): eth0: link is not ready
[   14.230000] ADDRCONF(NETDEV_UP): ip6tnl0: link is not ready
[   14.240000] ADDRCONF(NETDEV_UP): sit0: link is not ready
[   14.240000] ADDRCONF(NETDEV_UP): gre0: link is not ready
[   14.250000] ADDRCONF(NETDEV_UP): bond0: link is not ready
[   14.250000] ADDRCONF(NETDEV_UP): eth0.4094: link is not ready
[   14.370000] eth0: link up (1000Mbps/Full duplex)
[   14.380000] ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
[   14.400000] ADDRCONF(NETDEV_CHANGE): eth0.4094: link becomes ready
[   15.490000] ar8216_read_status_2991: eth0.4094 carrier off!
Loading defaults
Loading synflood protection
Adding custom chains
Loading zones
Loading forwardings
Loading rules
Loading redirects
Loading includes
Optimizing conntrack
Loading interfaces
Loading tpcmd
[   19.740000] device eth0 left promiscuous mode
[   19.750000] del ct event: 2 dev_name: eth0.4094
[   19.760000]  start clean up ct iterate..
[   19.770000] device eth0 entered promiscuous mode
[   19.800000] del ct event: 2 dev_name: eth0.1
[   19.800000]  start clean up ct iterate..
[   19.820000] device eth0.1 entered promiscuous mode
[   19.820000] br-lan: port 1(eth0.1) entered forwarding state
[   19.830000] br-lan: port 1(eth0.1) entered forwarding state
loading access_control
loading basic_security
[   20.640000] ar8216_read_status_2991: eth0.1 carrier off!
[   20.650000] ar8216_read_status_2991: eth0.4094 carrier off!
[   20.650000] br-lan: port 1(eth0.1) entered disabled state
[   23.050000]  start clean up ct iterate..
[   23.080000]  start clean up ct iterate..
conntrack v1.0.0 (conntrack-tools): connection tracking table has been emptied.
[   31.240000]  start clean up ct iterate..
Normal env generate
Flush nat forwarding chain
loading administration management
fw unload_local_mgnt
loading parental_control

 SSDK Init OK![   33.510000] enable:1
[   33.510000] bg task init successfull!
[   33.520000] host_helper_init start
[   33.530000] /proc/qca_switch/nf_athrs17_hnat is created
[   33.530000] /proc/qca_switch/nf_athrs17_hnat_wan_type is created
[   33.540000] /proc/qca_switch/nf_athrs17_hnat_ppp_id is created
[   33.540000] /proc/qca_switch/nf_athrs17_hnat_udp_thresh is created
[   33.550000] /proc/qca_switch/nf_athrs17_hnat_wan_ip is created
[   33.560000] /proc/qca_switch/nf_athrs17_hnat_ppp_peer_ip is created
[   33.560000] /proc/qca_switch/nf_athrs17_hnat_ppp_peer_mac is created
[   33.570000] /proc/qca_switch/nf_athrs17_hnat_wan_mac is created
[   33.570000] /proc/qca_switch/nf_athrs17_hnat_ppp_id2 is created
[   33.580000] /proc/qca_switch/nf_athrs17_hnat_ppp_peer_mac is created
[   33.590000] Adding ACL rules 15 - upnp_ssdp_add_acl_rules
[   33.610000] ACL is not yet enabled. Enabling...
[   33.620000] Adding ACL rules 7 - ipv6_snooping_solicted_node_add_acl_rules
[   33.670000] Adding ACL rules 11 - ipv6_snooping_sextuple0_group_add_acl_rules
[   33.720000] Adding ACL rules 13 - ipv6_snooping_quintruple0_1_group_add_acl_rules
[   33.770000] Hello, nat helper module for 1.1!
[   33.790000] register inet_notifier###

operate done.


 SSDK Init OK![   33.800000] enable:0
[   33.800000] unregister inet_notifier###
[   33.800000] /proc/qca_switch/nf_athrs17_hnat removed
[   35.790000] Goodbye, nat helper module!

operate done.

[   40.520000] ****Address of trace_timer :8240a610
[   40.860000] ath_hal: 0.9.17.1 (AR5416, AR9380, REGOPS_FUNC, WRITE_EEPROM, TX_DATA_SWAP, RX_DATA_SWAP, 11D)
[   40.920000] ath_rate_atheros: Copyright (c) 2001-2005 Atheros Communications, Inc, All Rights Reserved
[   41.000000] ath_dfs: Version 2.0.0
[   41.000000] Copyright (c) 2005-2006 Atheros Communications, Inc. All Rights Reserved
[   41.030000] ath_spectral: Version 2.0.0
[   41.030000] Copyright (c) 2005-2009 Atheros Communications, Inc. All Rights Reserved
[   41.050000] SPECTRAL module built on Oct 25 2016 11:22:49
[   41.110000] ath_tx99: Version 2.0
[   41.110000] Copyright (c) 2010 Atheros Communications, Inc, All Rights Reserved
[   41.300000] ath_dev: Copyright (c) 2001-2007 Atheros Communications, Inc, All Rights Reserved
[   43.490000] __ath_attach: Set global_scn[0]
[   43.500000] *** All the minfree values should be <= ATH_TXBUF-32, otherwise default value will be used instead ***
[   43.510000] ACBKMinfree = 48
[   43.510000] ACBEMinfree = 32
[   43.510000] ACVIMinfree = 16
[   43.520000] ACVOMinfree = 0
[   43.520000] CABMinfree = 48
[   43.520000] UAPSDMinfree = 0
[   43.530000] ATH_TXBUF=540
[   43.540000] Enterprise mode: 0x03bda000
[   43.540000]
[   43.540000] ART Version : -48.0.0
[   43.550000] SW Image Version : -48.0.0.0.0
[   43.550000] Board Revision :
[   43.560000] ar9300_attach: nf_2_nom -110 nf_2_max -60 nf_2_min -125
[   43.560000] SPECTRAL : get_capability not registered
[   43.570000] HAL_CAP_PHYDIAG : Capable
[   43.570000] SPECTRAL : Need to fix the capablity check for RADAR (spectral_attach : 231)
[   43.580000] SPECTRAL : get_capability not registered
[   43.590000] HAL_CAP_RADAR   : Capable
[   43.590000] SPECTRAL : Need to fix the capablity check for SPECTRAL
[   43.590000]  (spectral_attach : 236)
[   43.600000] SPECTRAL : get_capability not registered
[   43.610000] HAL_CAP_SPECTRAL_SCAN : Capable
[   43.610000] SPECTRAL : get_tsf64 not registered
[   43.620000] spectral_init_netlink 65 NULL SKB
[   43.620000] SPECTRAL : No ADVANCED SPECTRAL SUPPORT
[   43.620000] SPECTRAL :----- module attached
[   43.630000] Green-AP : Green-AP : Attached
[   43.630000]
[   43.640000] ath_get_caps[6169] rx chainmask mismatch actual 7 sc_chainmak 0
[   43.650000] ath_get_caps[6144] tx chainmask mismatch actual 7 sc_chainmak 0
[   43.660000] band steering initialized for direct attach hardware
[   43.660000] ieee80211_bsteering_attach: Band steering initialized
[   43.670000] ath_attach_dfs[12687] dfsdomain 1
[   43.690000] SPECTRAL : module already attached
[   43.690000] osif_wrap_attach:296 osif wrap attached
[   43.690000] osif_wrap_devt_init:916 osif wrap dev table init done
[   43.700000] ath_tx_paprd_init sc 82480000 PAPRD disabled in HAL
[   43.710000] wifi0: Atheros 956X: mem=0xb8100000, irq=47
[   43.720000] ath_pci: SmartAntenna-DRT-0.1 (Atheros/multi-bss)
[   44.510000] ath_attach_dfs[12687] dfsdomain 1
[   44.650000] wlan_vap_create : enter. devhandle=0x81c00380, opmode=IEEE80211_M_HOSTAP, flags=0x3
[   44.660000] wlan_vap_create : exit. devhandle=0x81c00380, opmode=IEEE80211_M_HOSTAP, flags=0x3.
[   44.670000] VAP device ath0 created osifp: (83253380) os_if: (8249c000)
[   44.700000] Set freq vap 0 stop send + 8249c000
[   44.700000] Set freq vap 0 stop send -8249c000
[   44.840000] Set wait done --8249c000
[   44.870000] WARNING: Fragmentation with HT mode NOT ALLOWED!!
[   44.890000] Set freq vap 0 stop send + 8249c000
[   44.890000] Set freq vap 0 stop send -8249c000
[   45.030000] Set wait done --8249c000
[   45.130000]
[   45.130000]  DES SSID SET=
[   45.140000]
[   45.140000]  DES SSID SET=TP-LINK_70AC
@@@@@@@@@@psk-mixed/tkip+aes
[   45.470000]  ieee80211_ioctl_siwmode: imr.ifm_active=131712, new mode=3, valid=1
[   45.480000]  DEVICE IS DOWN ifname=ath0
[   45.480000]  DEVICE IS DOWN ifname=ath0
[   45.750000] device ath0 entered promiscuous mode
[   45.940000] br-lan: port 2(ath0) entered forwarding state
[   45.940000] br-lan: port 2(ath0) entered forwarding state
[   45.960000] 8021q: adding VLAN 0 to HW filter on device ath0
[   46.760000] fast-classifier: starting up
[   46.760000] fast-classifier: registered
phyport start .......
[   48.730000] mlme_create_infra_bss : Overriding HT40 channel with HT20 channel
SETUP port (5) duplex: 1000 full autoneg: on!
loading qos
http://192.168.0.1/webpages/wan_error.html
192.168.0.1
http://192.168.0.1/webpages/wan_error.html
192.168.0.1
 3201 root      1772 S    /usr/sbin/crond -c /etc/crontabs -l 5


</WRAP>\\

===== Tags =====
{{tag>ath79 ar71xx AR9132 QCA9558 QCA9563 8Flash 16Flash 32RAM 64RAM 5Port GigabitEthernet 1NIC 1WNIC USB JTAG 802.11bgn ath9k 3Ant DetachableAntenna MIPS MIPS32 24Kc 74Kc JumboFrames vlan atheros-ap83 usb 1usb usb2.0}}
ath79 ar71xx ar9132 qca9558 qca9563 8Flash 16flash 32RAM 64RAM 5port gigabitethernet 1nic 1wnic usb jtag 802.11bgn ath9k 3ant detachableantenna mips mips32 24kc 74kc jumboframes vlan atheros-ap83 1usb usb2.0