“TAGGED==MARKIERT”
TP-Link TL-WDR3600 (N600)
TP-Link TL-WDR3600 ist ein 802.11n Gigabit Ethernet und Funk Dualband Router. Sehr ähnliches Gerät -→TP-Link TL-WDR4300
Unterstüzte Versionen
Version/Model | Release Date | OpenWrt Version Supported | Model Specific Notes |
---|---|---|---|
1.1 | July 2012 | Attitude Adjustment 12.09 works fine (since trunk r33219) | Similar to TP-Link TL-WDR4300 |
1.2 | Attitude Adjustment 12.09 | LEDs blue | |
1.3 | Attitude Adjustment 12.09 + wifi patch, or trunk (r39392), | LEDs blue | |
1.4 | July 2013 | Attitude Adjustment 12.09 + wifi patch , or trunk (r39392) | LEDs now green, not blue |
1.5 | December 2013 | Chaos Calmer 15.05.1 (Search for 3600) |
Bekannte Fehler/Probleme
- 15.05 on 1.5 model: Router könnte hängen... occasional hangs under load nur nach längerem dauerbetrieb von einigen Wochen.
- 14.07 on 1.5 Model: unreliable reboots → Korrigiert in/seit r43777, Korrektur rück-übertragen für 14.07 in/seit r44065.
- 14.07: bezüglich VLAN switch driver bug → Korrigirt in/seit r42653
Info
Architecture: | MIPS MIPS 74Kc |
Vendor: | Qualcomm Atheros |
TP-LINK prod.page | N600 |
bootloader: | U-Boot |
System-On-Chip: | AR9344 (MIPS) |
CPU/Speed | 560 MHz |
Flash-Chip: | Spansion FL064KIF docs |
Flash size: | 8192 KiB |
RAM: | 128 MiB |
Wireless No1: | Atheros AR9340 2.4GHz 802.11bgn |
Wireless No2: | Atheros AR9582 5GHz 802.11an |
switch: | Atheros AR8327N Gigabit Switch |
USB: | Yes 2 x 2.0 (GL850G chip - 4 ports capable) |
Installation
See TP-Link TL-WDR4300 installation instructions.
Switch Ports (for VLANs)
Port | Switch port |
---|---|
CPU | 0 |
Internet (WAN) | 1 |
LAN 1 | 2 |
LAN 2 | 3 |
LAN 3 | 4 |
LAN 4 | 5 |
unknown | 6 |
Bei einigen Geräte Revisionen verweigert der Switch-Treiber die Konfiguration von “PORTS” mit “TAGGED” oder “UNTAGGED” VLANS. (Es wurde berichtet das auf Revision 1.5 der Switch TAGGED und UNTAGGED VLANS auf dem GLEICHENPORT ermöglicht.)
ES ist möglich verschiedenen VLANS an einem Port zu betreiben sind diese “TAGGED”:
root@OpenWrt:/# swconfig swconfig dev <dev> [port <port>|vlan <vlan>] (help|set <key> <value>|get <key>|load <config>|show) root@OpenWrt:/# swconfig dev switch0 help switch0: eth0(Atheros AR8327), ports: 7 (cpu @ 0), vlans: 128 --switch Attribute 1 (int): enable_vlan (Enable VLAN mode) Attribute 2 (none): reset_mibs (Reset all MIB counters) Attribute 3 (none): apply (Activate changes in the hardware) Attribute 4 (none): reset (Reset the switch) --vlan Attribute 1 (int): vid (VLAN ID (0-4094)) Attribute 2 (ports): ports (VLAN port mapping) --port Attribute 1 (none): reset_mib (Reset single port MIB counters) Attribute 2 (string): mib (Get port's MIB counters) Attribute 3 (int): pvid (Primary VLAN ID) Attribute 4 (string): link (Get port link information)
OpenWRT switch KONFIGURATION Eth0.1 = LAN et Eth0.2 = WAN
root@OpenWrt:/# swconfig dev switch0 vlan 1 show VLAN 1: vid: 1 ports: 0t 2 3 4 5 root@OpenWrt:/# swconfig dev switch0 vlan 2 show VLAN 2: vid: 2 ports: 0t 1
Tag von Port/Anschluss/Schnittstelle 5 zu VLANs 1 und 2 erfolgreich:
root@OpenWrt:/# swconfig dev switch0 vlan 1 set ports "0t 2 3 4 5t" root@OpenWrt:/# swconfig dev switch0 vlan 1 show VLAN 1: vid: 1 ports: 0t 2 3 4 5t root@OpenWrt:/# swconfig dev switch0 vlan 2 show VLAN 2: vid: 2 ports: 0t 1 root@OpenWrt:/# swconfig dev switch0 vlan 2 set ports "0t 1 5t" root@OpenWrt:/# swconfig dev switch0 vlan 1 show VLAN 1: vid: 1 ports: 0t 2 3 4 5t root@OpenWrt:/# swconfig dev switch0 vlan 2 show VLAN 2: vid: 2 ports: 0t 1 5t
Tag PORT/ANSCHLUSS/SCHNITTSTELLE 4 zu VLAN 1, und untag port 4 zu VLAN 2: Error, port 4 is removed from VLAN 1
root@OpenWrt:/# swconfig dev switch0 vlan 1 set ports "0t 2 3 4t 5t" root@OpenWrt:/# swconfig dev switch0 vlan 1 show VLAN 1: vid: 1 ports: 0t 2 3 4t 5t root@OpenWrt:/# swconfig dev switch0 vlan 2 show VLAN 2: vid: 2 ports: 0t 1 5t root@OpenWrt:/# swconfig dev switch0 vlan 2 set ports "0t 1 4 5t" root@OpenWrt:/# swconfig dev switch0 vlan 1 show VLAN 1: vid: 1 ports: 0t 2 3 5t root@OpenWrt:/# swconfig dev switch0 vlan 2 show VLAN 2: vid: 2 ports: 0t 1 4 5t root@OpenWrt:/#
''/etc/config/network'' SWITCH Ports/Schnittstellen einzeln Nutzbar
config interface 'loopback' option ifname 'lo' option proto 'static' option ipaddr '127.0.0.1' option netmask '255.0.0.0' config switch option name 'eth0' option reset '1' option enable_vlan '1' ## Port: internet config switch_vlan option device 'eth0' option vlan '2' option ports '0t 1' ## Port LAN1 config switch_vlan option device 'eth0' option vlan '1' option ports '0t 2' ## Port LAN2 config switch_vlan option device 'eth0' option vlan '3' option ports '0t 3' ## Port LAN3 config switch_vlan option device 'eth0' option vlan '4' option ports '0t 4' ## Port LAN4 config switch_vlan option device 'eth0' option vlan '5' option ports '0t 5'
TFTP auto recovery in revision 1.5
Mindestens seit Revision 1.5 beinhalted der Bootloader einiger Router einen “Wiederherstellungsbootloader” mit TFTP CLIENT. Um diese zu aktivieren drücke und halte den WPS/RESET Knopf wärend des Anschaltens bis die WPS LED zu leuchten beginnt. Verbinde den PC an mit Port/Anschluss/Schnittstelle 1 des Routers. MIt einem PAket Sniffer fällt nun auf, dass sich ein Gerät mit der Adresse 192.168.0.86 meldet, um nach einem Gerät/Server mit der Adrese 192.168.0.66 zu fragen (ARP-Request).
Beispiel für TCPDUMP
# tcpdump -ni eth0 arp ARP, Request who-has 192.168.0.66 tell 192.168.0.86, length 46
Stellen sie Ihren PC auf die gesuchte SERVER-Adresse ein Bsp.: -→ 192.168.0.66, netmask /24 (255.255.255.0).
# ip addr add dev eth0 192.168.0.66/24
Der Paketsniffer zeigt anschließend: der Router sucht nach einem Image -→ wdr3600v1_tp_recovery.bin
# tcpdump -npi eth0 udp IP 192.168.0.86.2195 > 192.168.0.66.69: 44 RRQ "wdr3600v1_tp_recovery.bin" octet timeout 5
Bennen sie das zu übertragene Image in das vom TFTP-Client des Routers gesuchte Format um. → generic.flashing.tftp
IFalls sie zurück zu einer Stock/TP-Link eigenen Firmware wollen beachten
sie kein boot
beinhaltendes Image zu Verwenden → back.to.stock.firmware.!!!!!!
# cp openwrt-ar71xx-generic-tl-wdr3600-v1-squashfs-factory.bin wdr3600v1_tp_recovery.bin # atftpd --no-fork --daemon .
Nach der Übertragung beginnt das beschreiben des Flash-Speichers umgehend und der Router wird anschließend automatisch neu gestartet. Dauer: ca. 1min
Wegen abweichungen diverser Firmware Versionen, kann es zu einem unterschiedlichen Verhalten kommen lese!:https://mail-archive.com/openwrt-devel%40lists.openwrt.org/msg32888.html. ←- Firmware aus beitrag hat ein Zeitfenster zwischen Boot des Recovery und Reset bei nichtgefundenem Firmware-Image.
Back to stock firmware
IN ENGLISH
With the TL-WR3600 router, there is a catch: the stock firmware is obtained from the OEM: http://www.tplink.com/en/support/download/?model=TL-WDR3600
- 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:
An example of an image file with the word “boot” in it is wdr3600v1_en_3_13_34_up_boot(130909).bin
.
Cut the first 0x20200 (that is 131,584 = 257*512) Bytes from original firmware:
dd if=orig.bin of=tplink.bin skip=257 bs=512
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:
sysupgrade /tmp/tplink.bin
Or alternatively you can use the mtd method:
mtd -r write /tmp/tplink.bin firmware
OEM TP-Link firmware for the TL-WDR3600 with the boot part removed to revert to the original OEM firmware:
- TL-WDR3600 V1 TL-WDR3600-V1-stripped.zip
- TL-WDR3600 V1 TL-WDR3600_V1_130320.zip
Useful Information about Stock Firmware
Updated versions of stock firmware have Firmware Recovery Mode. Recommend upgrading latest stock firmware before flashing to OpenWrt for the first time so you can utilise this if necessary.
Performance
See also performance.
Test in a simulated network
Scenario:
[samba server in a lan network offering a file of 3Gb] [one port connection (so max 1Gbit speed)] [switch 1Gbit ports] [one port connection (so max 1Gbit speed)] [mikrotik rb 750GL with routerOS 6.x as gateway2] [asus wl500gp v2 openwrt 12.09 as gateway2 limiting the wan/lan traffic to 1428 packets per second] [tplink wdr3600 , owrt 12.09, mwan3 for using 2 gw concurrently] [switch 1Gbit ports] [one port connection (so max 1Gbit speed)] [2 windows vm on a esxi server]
Both windows machines asked the same file to save it locally.
Results: the asus router was 40% idle, with the limit of packets reached ( ~ 15 Mbit/s ); the rb750Gl was completely used, idle less than 1% with a bandwidth of ~175 Mbit/sec and ~ 7.5K packets sent and ~ 17K packets received ; the tplink was 20% idle, with a total of ~ 190 Mbit/s , ~18K packets received and ~8K packets sent.
That is impressive, considering that the mikrotik solution is commercial and was expected to provide way more bandwidth (with way less firewall rules!), instead the openwrt solution is able to overload it even without the so 'blamed' hw accel https://dev.openwrt.org/ticket/11779 . Great job openwrt!
For whatever SOHO solution that has no so big traffic between two logical networks (for example, less than 50 Mbit on average), the wdr3600 plus openwrt and thirdy party software (mwan3) is a great solution even for business.
Flash Layout
0x000000000000-0x000000020000 | “u-boot” | /dev/mtdblock0 |
0x000000020000-0x000000120000 | “kernel” | /dev/mtdblock1 |
0x000000120000-0x0000007f0000 | “rootfs” | /dev/mtdblock2 |
0x000000600000-0x0000007f0000 | “rootfs_data” | /dev/mtdblock3 |
0x0000007f0000-0x000000800000 | “art” | /dev/mtdblock4 |
0x000000020000-0x0000007f0000 | “firmware” | /dev/mtdblock5 |
Serie U-Boot
WDR3600 v1.3 Start Log original U-Boot 1.1.4 (Jan 29 2013 - 16:09:44)
U-Boot 1.1.4 (Jan 29 2013 - 16:09:44) U-boot DB120 DRAM: 128 MB id read 0x100000ff flash size 8MB, sector count = 128 Flash: 8 MB Using default environment PCIe Reset OK!!!!!! In: serial Out: serial Err: serial Net: ag934x_enet_initialize... No valid address in Flash. Using fixed address wasp reset mask:c03300 WASP ----> S17 PHY * : cfg1 0x7 cfg2 0x7114 eth0: ba:be:fa:ce:08:41 athrs17_reg_init: complete eth0 up eth0 Autobooting in 1 seconds
Very quickly type tpl when the message Autobooting in 1 seconds appears
WDR3600 v1.3 U-boot help :
db12x> help ? - alias for 'help' bootm - boot application image from memory cp - memory copy erase - erase FLASH memory help - print online help md - memory display mm - memory modify (auto-incrementing) mtest - simple RAM test mw - memory write (fill) nm - memory modify (constant address) ping - send ICMP ECHO_REQUEST to network host printenv- print environment variables progmac - Set ethernet MAC addresses reset - Perform RESET of the CPU setenv - set environment variables tftpboot- boot image via network using TFTP protocol version - print monitor version
WDR3600 v1.3 U-boot printenv
db12x> printenv bootargs=console=ttyS0,115200 root=31:02 rootfstype=squashfs init=/sbin/init mtdparts=ath-nor0:256k(u-boot),64k(u-boot-env),6336k(rootfs),1408k(uImage),64k(mib0),64k(ART) bootcmd=bootm 0x9f020000 bootdelay=1 baudrate=115200 ethaddr=0xba:0xbe:0xfa:0xce:0x08:0x41 ipaddr=192.168.1.111 serverip=192.168.1.100 dir= lu=tftp 0x80060000 ${dir}u-boot.bin&&erase 0x9f000000 +$filesize;cp.b $fileaddr 0x9f000000 $filesize lf=tftp 0x80060000 ${dir}db12x${bc}-jffs2&&erase 0x9f050000 +0x630000;cp.b $fileaddr 0x9f050000 $filesize lk=tftp 0x80060000 ${dir}vmlinux${bc}.lzma.uImage&&erase 0x9f680000 +$filesize;cp.b $fileaddr 0x9f680000 $filesize stdin=serial stdout=serial stderr=serial ethact=eth0 Environment size: 686/65532 bytes
Restoration of original firmware (without modifying U-Boot). The firmware must be 8,126,464 octets which correspond to a firmware without U-Boot. Today, firmwares TP-Link : wdr3600v1_en_3_13_23_up(120820), wdr3600v1_en_3_13_26_up(130129) and wdr3600v1_en_3_13_31_up(130320) come without U-Boot. The version used in the example is wdr3600v1_en_3_13_31_up(130320) on the WDR3600 v1.3
db12x> setenv ipaddr 192.168.0.144 db12x> setenv serverip 192.168.0.11 db12x> tftp 0x80060000 wdr3600v1_en_3_13_31_up(130320).bin dup 1 speed 1000 Using eth0 device TFTP from server 192.168.0.11; our IP address is 192.168.0.144 Filename 'wdr3600v1_en_3_13_31_up(130320).bin'. Load address: 0x80060000 Loading: *################################################################# ################################################################# ################################################################# ################################################################# ################################################################# ################################################################# ################################################################# ################################################################# ################################################################# ################################################################# ################################################################# ################################################################# ################################################################# ################################################################# ################################################################# ################################################################# ################################################################# ################################################################# ################################################################# ################################################################# ################################################################# ################################################################# ################################################################# ################################################################# ############################ done Bytes transferred = 8126464 (7c0000 hex)
ATTENTION Only continue if the last line reads 8126464 (7c0000 hex)
db12x> erase 0x9f020000 +7c0000 First 0x2 last 0x7d sector size 0x10000 Erased 124 sectors db12x> cp.b 0x80060000 0x9f020000 0x7c0000 Copy to Flash... write addr: 9f020000 done db12x> reset
The router reboots
U-Boot 1.1.4 (Jan 29 2013 - 16:09:44) U-boot DB120 DRAM: 128 MB id read 0x100000ff flash size 8MB, sector count = 128 Flash: 8 MB Using default environment PCIe Reset OK!!!!!! In: serial Out: serial Err: serial Net: ag934x_enet_initialize... No valid address in Flash. Using fixed address wasp reset mask:c03300 WASP ----> S17 PHY * : cfg1 0x7 cfg2 0x7114 eth0: ba:be:fa:ce:08:41 athrs17_reg_init: complete eth0 up eth0 Autobooting in 1 seconds ## Booting image at 9f020000 ... Uncompressing Kernel Image ... OK Starting kernel ...
WDR3600 TP-Link Original Firmware Password
TL-WDR3600 login: root Password: ??? Login incorrect
shadow hash password file : root:$1$GTN.gpri$DlSyKvZKMR9A9Uj9e9wR3/:15502:0:99999:7:::
Login: root Password: sohoadmin
Bootloader Mods
Read about bootloader in general and about Das U-Boot in particular.
U-Boot 1.1.4 modification for routers
Forum member pepe2k made a modification of U-Boot 1.1.4 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 wr703n-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:
- Official repository on GitHub: U-Boot 1.1.4 modification for routers
- Discussion about this project on OpenWrt forum
- An article (in Polish) about one of the first version of this project on www.tech-blog.pl
Hardware
GPIO
Partially based on → tl-wdr4300_v1
Tested with hw version 1.5, BB r41181
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 |
16 | WPS Button | ||||||
17 | WiFi Switch |
Read button without hotplug
rmmod gpio_button_hotplug echo "16" > /sys/class/gpio/export echo "17" > /sys/class/gpio/export echo "in" > /sys/class/gpio/gpio16/direction echo "in" > /sys/class/gpio/gpio17/direction
cat /sys/class/gpio/gpio16/value cat /sys/class/gpio/gpio17/value
Hardware Modifications
USB Modification
The task was to make ext-root without using the default ports.
It turns out that the GL850G chipset used by the TP-Link in WDR3600/4300/4900 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. +5 V can be also taken from TP5 near the power switch. The Maplin part N75HL is perfect for adding these externally and can be mounted under one side once a small hole has been drilled in the case.