OpenWrt Forum Archive

Topic: Developing Support for TPLINK WDR4900

The content of this topic has been archived between 4 Oct 2014 and 4 May 2018. Unfortunately there are posts – most likely complete pages – missing.

eximido wrote:

AR7161 could also be overclocked from its std 680MHz freq to 800MHz. IIRC in some mikrotik boards it comes with 800 MHz clock by default, but just the clock speeds are not the whole story. What I'm really interested in is whether hardware FPU (along with PPC architecture) will provide any significant performance benefits for the userspace software like php compared to MIPS SoCs running at the same clocks.

I am sure it would.
But developers will have to enable hardware float in the compile options.

hello good morning, what about this router.....  any news?

Well, as it appears at recent changeset #35733 by juhosg now we should be able to compile the openwrt firmware for wdr4900.

eximido wrote:

Well, as it appears at recent changeset #35733 by juhosg now we should be able to compile the openwrt firmware for wdr4900.

Bookmarked, very curious about these developments!

I'm also happy and expectant!

any update ??
very expectant !

Looks like there were no updates on this device in openwrt's trac for nearly three weeks. Meanwhile I've tried to build general firmware for mpc85xx devices since there's no separate target profile for wdr4900 yet. It compiled fine and if I'm right it theoretically should work with wdr4900 but I dunno whether it will in fact.

Can't check myself cause my wdr4900 is still on the way, international post service is ridiculously slow here.

Any news how long it takes that there is a precompiled image out?

(Last edited by stinger2k on 10 Mar 2013, 18:51)

I also compiled it and missed the target profile. So i'm afraid to flash it without knowing if it works.

In fact there's nothing to flash, because none firmware binary is created by default at all. But we're able to manually use mktplinkfw utility to create the firmware binary from kernel and rootfs files, which are created during general mpc85xx firmware compilation.
Still some clarification and explanation from juhosg, who was working on wdr4900 support, is required though.

Is that a problem if anyone can compile a flashable image with luci in it?
So if anyone can do this it would be great, fro, latest trunk...

I've asked juhosg a question regarding wdr4900 support status, and he says that there're still some problems with switch driver compability so that wired ports with current implementation are not operational yet. So openwrt still needs some futher development for running this device, unfortunately.

Great news: with the latest bunch of changesets (#36042 to #36051) wdr4900's switch in now fully supported and we are finally able to build firmware images for this device. Many thanks to juhosg!

Interested in finding a reliable US retailer for these. Please PM me if you can help (or steer me away from disasters).

So, as far as one can see, there will be no major functionality missing in openwrt for this, rather attractive looking spec device?  I guess I am impatient ... :-)

will hardware NAT supported ??
thx

yanzifans wrote:

will hardware NAT supported ??
thx

Currently it isn't, and probably it won't in the near future either.
Short explanation from ticket #11779 (regarding wdr4300):

here's why it's most likely not going to happen:

  • the source of the hw nat implementation is not included in the tarball

  • it requires some *extremely* nasty hacks in the netfilter source code

A call to TP-Link US today indicated that the WDR4900 is not available in the US through normal channels. They were not able to indicate what the configuration of a US model would be, but are expecting something in the May/June time frame.

I was wondering if someone already succeeded in building an OpenWrt trunk image for the TL-WDR4900.
As far as I could see, there's already support available for it since build r36051.

I tried building it several times, but I have never built an OpenWrt image before, so I would like to leave it to the experts, before bricking my device..

I've built my own image and successfully flashed it. I haven't had much time to test everything yet, but at a glance the device works smooth. The only thing that isnt working is wifi switch button, and WPS led (or what's that? the rightmost led) on the front panel is not controllable from corresponding /sys subsystem.

You can safely use only the WDR4900 profile in buildroot to make firmware with wired connections enabled and working. In order to enable wireless I had to manually select kmod-mac80211, kmod-cfg80211, kmod-ath9k and wpad-mini - although I dunno why, because it should be enabled by default as well. Probably that was some local bug in my buildroot due to switching&updating configs. Wireless-tools package could also come in handy. And, of course, if you need LuCI web-interface you'll need to enable its package as well - but I personally prefer cli only to configure the device.

I have dried to compile the trunk image on an virtual ubuntu installation. Everything worked fine as described in this wonderful tutorial: http://www.thepowerbase.com/2012/01/ope … to-finish/
But it always stops with an error "failed" after a half an hour of compiling...

@eximido: After compiling, I get a 16 MB factory image, which seems quite big for this device? I was expecting something like a 3 or 4 MB sized file.

Jeffrey87 wrote:

@eximido: After compiling, I get a 16 MB factory image, which seems quite big for this device? I was expecting something like a 3 or 4 MB sized file.

Thats ok - the device has 16MB flash onboard. Looks like the original tplink firmware updater requires firmware image to be exactly 16 MB, so factory image is padded to that size.

I too can confirm, that a stock firmware image works on the WDR4900 (got hardware version 1.3).
I installed luci and wpad-mini on it. So far I did only a rudimentary setup, but it seems that the WLAN (2.4 and 5 GHz) seems a bit "choppy". But the problem here could be my configuration.
I will have a closer look into getting this to work in the next few days.


BusyBox v1.19.4 (2013-03-21 17:05:50 CET) built-in shell (ash)
Enter 'help' for a list of built-in commands.

  _______                     ________        __
 |       |.-----.-----.-----.|  |  |  |.----.|  |_
 |   -   ||  _  |  -__|     ||  |  |  ||   _||   _|
 |_______||   __|_____|__|__||________||__|  |____|
          |__| W I R E L E S S   F R E E D O M
 -----------------------------------------------------
 BARRIER BREAKER (Bleeding Edge, r36099)
 -----------------------------------------------------
  * 1/2 oz Galliano         Pour all ingredients into
  * 4 oz cold Coffee        an irish coffee mug filled
  * 1 1/2 oz Dark Rum       with crushed ice. Stir.
  * 2 tsp. Creme de Cacao
 -----------------------------------------------------
root@openwrt:~# cat /proc/cpuinfo
processor    : 0
cpu        : e500v2
clock        : 799.999992MHz
revision    : 5.1 (pvr 8021 2151)
bogomips    : 99.99
timebase    : 49999999
platform    : Freescale P1014
model        : TP-Link TL-WDR4900 v1
Memory        : 128 MB

This is  neither here nor there, (and i don't know what good it does on this 2nd page of this thread) but one thing to note that makes the wdr4900 different than the wdr4300 is that on the 4900 the external antennas are only for 5ghz band.   
It has internal antennas for 2.4ghz. 

the 4300 antennas are dual band.   So... this can be either good or bad depending on what you want to do. Good because dual band external antennas are hard to find (at least currently) and you can mess with the 5ghz band without totally killing your 2.4.    Bad if you want to do something with the 2.4 band antennas because you can't. (unless you HW mod the thing presumably)

This is depicted on the tp-link site, so it's no secret, but was unexpected to me.   I assumed they just tweaked the radios to add a third stream on 2.4ghz.

(Last edited by vhrm on 22 Mar 2013, 21:06)