39340 is still stable after 2 days, 18:56,  load average: 0.26, 0.44, 0.35 (most of that time was at heavy load doing first-time syncs for two time machines)

wdr 4900 v2 ?

v1.x, using the MPC85xx trunk.

flippant,

What about Wifi connection?

I updated mine to the newest yesterday, and still got an issue with the wifi accesspoint drops out, and don't come alive again

Do you have a link to the version you are using?

Kasper

I got the newest trunk version a while ago. I'll check and see if I can find it.

My wi-fi is completely stable.

I think I got it straight off the web. Sorry.

I've just upgraded to OpenWrt Barrier Breaker r39457 and my Wifi wont start.

In Luci I see

Signal: 0 dBm / Noise: 0 dBm
0%    SSID: TP_5 | Mode: Client
Wireless is disabled or not associated

The config says its "Mode AP"...

Any ideas?

I've had some trouble getting both radios to work. I had to disassociate them from the interface, then set them up, and then put them back on the interface.

It's more a bug than anything else, especially if you're using Luci.

Thanks Flippant, I'm playing around with the settings now and have managed to get one of the radios back... I'll check to see if its the settings in the restore from the old settings.

The new install had Radio2 & 3 (SSID: OpenWrt) which seems to work if I manually issue:

/sbin/wifi up

Still going strong, with ~120gb of torrents downloaded, as well as two entire time machine backups done:

BusyBox v1.19.4 (2014-01-31 03:11:35 PST) 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, r39430)
 -----------------------------------------------------
  * 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@TheRouter:~# uptime
 12:58:58 up 4 days, 21:46,  load average: 0.05, 0.20, 0.26
root@TheRouter:~# 

Flippant, thanks, that's great to hear. Any ideas which commit(s) might have contributed to the resolution? Are you testing over wifi, or lan?

I'm using the wi-fi. There's nothing connected through Ethernet at the moment.

I have no idea what caused the sudden resolution of all my woes, but I'm happy that it's here.

Now, on the other hand, I am petrified to update.

All of you who report success with WDR4900 is that with v1 or is there anyone who have managed to get v2 working?

I'm currently (r39518) having two issues:

-- hostapd for second radio (2.4Ghz) dies on boot

[   36.273520] hostapd[2464]: unhandled signal 11 at 00000000 nip 1003cb04 lr 1003cf70 code 30001

A "wifi up" brings it up again fine afterwards, though

-- the 2.4Ghz radio stopped supporting channels 12 and 13, even when setting the regdomain to "DE" or with the world "00" regdb entry changed to support them. It's simply missing from the capabilities.

This has started some revisions ago, not sure yet exactly when.

Best Regards,
Olli

As a test, I've now patched the US regdb entry as well, and now both 12+13 are back and hostapd isn't crashing anymore.

Seems like CONFIG_ATH_USER_REGD is somehow being ignored/causing issues?

hi All

I bought a WDR 4900 ,( V1.3 EU )and setup it for my use like specific IP, virtual servers,.. but the features are bad...

to go from tp-link firmware  to openwrt, did you reset the router with the 30/30/30 method ?
I read http://wiki.openwrt.org/toh/tp-link/tl-wdr4900 it's not mentioned but ... feedbacks from experienced users is welcome :-)

best regards,
Brice

Running r39385 for some day now, with 2TB Harddisk at USB. uShare media server and Samba. I'm having no problems at all. My internet connection is 150 Mbit/s / 15 Mbit/s, running full speed with no freezes. It seems that OpenWRT has the major issues finally sorted out! :-)

@maxpayne911 to go from TP-Link firmware to OpenWRT, you can download the openwrt-mpc85xx-generic-tl-wdr4900-v1-squashfs-factory.bin file, and flash it via the normal way in the Web Interface of the TP-Link firmware. Be advised that you have no web interface installed by default in trunk releases. Hope it helps!

Is there a list of working packages???

http://downloads.openwrt.org/snapshots/ … x/packages

@marcos1988, thanks, that's encouraging to hear. Although browsing throw the changesets between r39365 (which was unstable for me, and froze/paused frequently) and r39385, I can't really see anything that should have fixed this for us.

Have you been testing over wifi or lan?

Hi,

I am on r39487, and I found that this revision suffers from performance problems.

When I run an iperf -c testdebit.info -i 2 -t 20 -r on my desktop behind the WDR4900, I get 200 Mbits upload and the router barely reaches 2% CPU load which is what's expected.

When iperf reaches the download part of the test, I "only" get 350Mbits and the router load rises to 80% or more. The culprits is for the most part ksoftirdq/0 (80% of cpu load) and 3-4 kworkers processes (3-9 % of cpu load each).

If I perform the same test without the router between my desktop and internet I get 900Mbits of download.

So it seems something is loading the cpu more than it should at high download rates.

I had the same results with an older revision dating back to september.

Does somebody know where this behavior could come from ?

Thanks Marcos...
I see this list earlyer...

Only all this package are not working.

An example tc is not working..

Or is there a other way to get a tc working?

No, it's not an issue.
All the routing in OpenWrt is made in software, so high cpu load by ksoftirqd is expected at high download rates. Many hi-end devices have an additional hardware to offload such traffic and allow higher throughput, and there's one in WDR4900 as well. However OpenWrt is lacking support for any hardware NAT offloading features. It's simply not supported at all. For all the capable devices. And no one is working on it. See ticket #11779.

They ARE working.

However those packages are automatically rebuilt by regular basis. If a package contains a kernel module, it will be marked as compatible ONLY with openwrt image it was built with. It means that if you flash your device with firmware built yesterday and then attempt to install a package with a kernel module which was built today then opkg will complain about package incompatibility.

Your options are as follows:
a.) You may flash new openwrt image and download ALL the packages from that build to your computer. Then install them from your computer, not from openwrt repository.
b.) You may flash new openwrt image and install all the packages you need from openwrt repository on the same day. If (when) you need to install a new package later, make a whole firmware upgrade along with it.
c.) Use an option for opkg to make it not check for compatibility of the packages you install. It will work most of the time (if kernel version doesn't change). However be prepared that you may break your openwrt installation so that failsafe mode might be required to restore your device.

21:52:19 up 10 days,  6:39,  load average: 1.36, 1.27, 0.84

Still going strong!

I migrated from tplink firmware to OpenWrt Barrier Breaker r39574 / LuCI Trunk (svn-r9953) ,
uptime  : 1d 16h 23m 6s

following Eximido post, I Grabbed all packages at the time as I updated to install package with same kernel version

I have an internet connection at arround 10 Mbit, no issue so far  with 1 laptop on wifi 5Ghz ( arround 17MB/sec), 2 on 2,4G (around 3/4 MB/Sec) for my wife & her sister
my gaming pc & my nas on  Cisco GB switch connected to the WDR 4900.

really, I like openwrt features ( firewall/settings applied without reboot/vlan support/multil ssid/etc..)
hope stability will stay as it is

Brice