201 (edited by artteam 2013-08-09 07:04:42)

Re: Developing Support for TPLINK WDR4900

Horst_Tappert wrote:

On another note, has anybody already determined the maximum throughput of the WDR4900 as an OpenVPN client?
The raw benchmark published would lead me to believe that about double of the WDR4300's performance should be reached, i.e. close to the maximum of my connection, 60Mbit down and 6Mbit up.
I'd be interested in getting a confirmation of this.

I have 100M/5M DOWN/UP link connected to WDR4900
Using DH 1024, AES-256-CBC, TAP, UDP, LZO and 'redirect-gateway def1'- from remote location i'm getting ~4,4M stable link DOWN/UP with sys usage as below:

Mem: 41400K used, 85200K free, 0K shrd, 1620K buff, 9856K cached
CPU:  16% usr   6% sys   0% nic  67% idle   0% io   0% irq   9% sirq
Load average: 0.09 0.10 0.13
  PID  PPID USER     STAT   VSZ    %VSZ %CPU COMMAND
3143     1   root       R        3372   3%     18%    /usr/sbin/openvpn --syslog openvpn(la

Re: Developing Support for TPLINK WDR4900

Is anyone able to run openwrt on this model, and have it run stable with wifi performance at least close to the stock firmware?

I've tried r375 from the 26th June and I've tried r377 from yesterday morning, both give me horrible wifi performance (sometimes I get latency > 100ms & bandwith a few kb/s)
Also sometimes the router become completly unresponsive (but the lan switch still works, though no ssh & no luci till I power cycle)

I'm on stock-firmware again for now, because of those problems.

203 (edited by vanhaakonnen 2013-08-09 18:06:11)

Re: Developing Support for TPLINK WDR4900

As I described before - the following is working for me (without latency problems) with  LuCI Trunk (svn-r9875) OpenWrt Barrier Breaker r37709:

SSID1
- Channel: 44 (5.220 GHz)
- 40MHz 2nd Channel above
- NO(!) Force 40MHz mode. If I enable this my router crashes
- 17dBm
- WMM Mode
- WPA2-PSK  / CCMP-AES

SSID2
- Channel: 6 (2.437 GHz)
- 40MHz 2nd Channel above
- NO(!) Force 40MHz mode. If I enable this my router crashes
- 20dBm
- WMM Mode
- WPA2-PSK  / CCMP-AES

SSID3
- Channel: 6 (2.437 GHz)
- 40MHz 2nd Channel above
- NO(!) Force 40MHz mode. If I enable this my router crashes
- 20dBm
- WMM Mode
- WPA2-PSK  / CCMP-AES

Re: Developing Support for TPLINK WDR4900

I want to confirm the "unresponsive" crashes discribed here.
Since 4 Month i had used the device with an older trunk.
The r number is Lost but i am 100% sure it was kernel 3.8!
So maybe something to investigate here??
With that older build i never had such issues.
The VPN performance was totally great! There never was such a
Openwrt device in that price segment which has this VPN throughput.

I also tried it 5days without any wireless device enabled, no USB, nothing.
When i put heavy traffic over the switch (about 800mbits) you can count
from ten down till it becomes unresponsive. nothing in logread -f and dmesg
not possible then anymore.

Maybe someone has a serial console on it and can reproduce theese crashes.

205 (edited by vanhaakonnen 2013-08-11 09:39:07)

Re: Developing Support for TPLINK WDR4900

You're right. I was so sure it has to be something with the wlan 40MHz setting... If I put high troughput on my device it also crashes... (tested with netio) hmm

Please write your testing results also in the bug-report: https://dev.openwrt.org/ticket/14020

Re: Developing Support for TPLINK WDR4900

I'm still using r36353 (with kernel 3.8.7) with 100+ days of uptime. Wireless performance is nice and device is completely stable with no single crash over last months. Looks like something is definitely broken in newer revisions.

Re: Developing Support for TPLINK WDR4900

Is it possible to downgrade to the older version of the trunk and can I still use opkg to install new software or do we have to wait to get the problem fixed?

208 (edited by derdigge 2013-08-11 12:16:32)

Re: Developing Support for TPLINK WDR4900

You can Build an older Svn checkout.
BTW in which r has the Kernel changed?

@vanhakonnen
This Ticket was created by me wink

Re: Developing Support for TPLINK WDR4900

derdigge wrote:

You can Build an older Svn checkout.
BTW in which r has the Kernel changed?

r37472 is the last revision with 3.8 kernel.
Don't know whether the device is working fine there, though.

210 (edited by derdigge 2013-08-11 18:36:23)

Re: Developing Support for TPLINK WDR4900

I will Check that next week
Also i ordernd an usb2serial Adapter to have a Look at that error.
But i am pretty sure that the skills are missing to fix that on my own
In 3.10

Re: Developing Support for TPLINK WDR4900

Many of the Sources Downloadlinks were broken in r37472.
So after hunting all those tarballs here i have an Image r37472 with luci/samba/openvpn.
I can not test it on my own until Wednesday maybe someone can stress it with tcp traffic and see if it crashes.

http://www.file-upload.net/download-795 … y.bin.html

212 (edited by jkso 2013-08-12 22:18:17)

Re: Developing Support for TPLINK WDR4900

Thanks, I'll try and test.

EDIT: By the way. I now placed the device on some books on the edges so that it runs cooler. No hangup since then but I didn't test with much throughput, though.

Re: Developing Support for TPLINK WDR4900

I dont think that Heat is our Problem here.
The most People here and Those i am in private conversation
Confirmed that it crashes on High tcp throughput.

Re: Developing Support for TPLINK WDR4900

That´s why I posted my netio results to the bug-report. UDP is absolutely no problem.
I thought that it could be a problem with the firewall... but it also freezes with the firewall disabled.

Re: Developing Support for TPLINK WDR4900

@vanhaakonnen
Can you please try to Crash the Image from Post 211 here.
Please try netio method as you did in post 205. We need to isolate
The problem more ecxatly so the dev Ticket will cause any result some Day.

If we definitly know that kernel 3.8.13 doesent crash i can diff the kernelcode
Between this versions for mpc85xx and See what devs made here, to make our lifes so "easy" in
3.10 wink

Re: Developing Support for TPLINK WDR4900

sure smile

OpenWrt Barrier Breaker r37472 / LuCI Trunk (svn-r9881)
Kernel 3.8.13

>> NetIO with UDP and TCP are no problem. Nothing crashes <<

Is it possible that the device names or drivers has changed in the newer kernel versions? In 3.8.13 there are two "Generic 802.11 Wireless Controller". In the newest kernel I can see one "Generic MAC80211 802.11bgn" and another "Generic MAC80211 802.11an". Maybe there is a lot related to the drivers that has changed in the newer code...

Re: Developing Support for TPLINK WDR4900

Back on the the newest build (BARRIER BREAKER (Bleeding Edge, r37708)) it crashes again under load with tcp

Re: Developing Support for TPLINK WDR4900

vanhaakonnen wrote:

sure smile

OpenWrt Barrier Breaker r37472 / LuCI Trunk (svn-r9881)
Kernel 3.8.13

>> NetIO with UDP and TCP are no problem. Nothing crashes <<

Is it possible that the device names or drivers has changed in the newer kernel versions? In 3.8.13 there are two "Generic 802.11 Wireless Controller". In the newest kernel I can see one "Generic MAC80211 802.11bgn" and another "Generic MAC80211 802.11an". Maybe there is a lot related to the drivers that has changed in the newer code...

jep same here ~2h 800mbit fullspeed, no crash.
I build an Image(latest trunk) without any Wireless and i will test

Re: Developing Support for TPLINK WDR4900

If we have found out that r37472 is working stable, then it will be interesting to compile and test r37473, which is the first revision with 3.10 kernel. If it somehow will appear to work fine as well, then those crashes aren't directly related to kernel upgrade only.

220 (edited by derdigge 2013-08-15 22:57:04)

Re: Developing Support for TPLINK WDR4900

it definitly crashes since r37473.
Today i build both and testet twice.
I generate tcp traffic from a vlaned nas using gnu wget,
it crashes faster than using netio.

Clean Install of r37473 = tcptraffic .... crash -> reboot -> tcptraffic .... crash

Clean Install of r37472 = tcptraffic fo 30 Minutes .... stable -> reboot -> tcptraffic for 60 Minutes ..... stable

Clean Install of r37473 = tcptraffic .... crash -> reboot -> tcptraffic .... crash

Clean Install of r37472 = tcptraffic fo 30 Minutes .... stable -> reboot -> tcptraffic for 60 Minutes ..... stable

So thats definitly fact now.
Tommorrow i will try to find something inside kernelcode.
But i am definitly not the one you should ecxpect results here.
My skills are to low.....

221

Re: Developing Support for TPLINK WDR4900

My skills are even lower since I have to ask a total noob question:

How to downgrade? Can I just flash the "openwrt-mpc85xx-generic-tl-wdr4900-v1-squashfs-factory.bin" that derdigge built via LuCi's update mechnism?

Thanks in advance!

222 (edited by vanhaakonnen 2013-08-18 18:41:16)

Re: Developing Support for TPLINK WDR4900

You can always install a full factory image instead of an upgrade image.

Re: Developing Support for TPLINK WDR4900

Any news? Has someone tried to get the error message with a serial console cable?

Re: Developing Support for TPLINK WDR4900

I habe a serial cable here, but still not connected. I hope i find some time next week for that.

Re: Developing Support for TPLINK WDR4900

Curious what the error is.... had to check out at r37472  to make it stable