OpenWrt with DD-WRT kernel. Is it possible?

For Developers
1

Hi,

I have a router with broadcom chip which works fine with DD-WRT. However, I prefer to use cli and web administration from OpenWRT (uci, luci).

Is it possible to build or repack an OpenWRT firmware to contain kernel and wireless firmware from DD-WRT?

Thanks

2

It might be, but that would require far more work than you probably are prepared to do, and I presume beyond your skillset (no offense - but if it were within your skillset, you would not have to ask probably).

It would not be worth it either way, UCI/LuCI is tied to mac80211 and related modern wireless tools, whatever DD-Wrt uses probably relies on ancient standards and kernels long phased out by now.

1 Like
3

I doubt it, DDWRT works with nvram and not with the configuration files and overlay.
So it needs a total rewrite which is not feasible.

(I use DDWRT and OpenWRT :slight_smile: )

4

DDWRT does not use old standards and most Broadcom routers are using Kernel 4.4 which is an SLTS release and still supported.

Maybe you are confusing it with Fresh Tomato which is still on Kernel 2.6?

5

So the proprietary broadcom drivers utilize cfg80211 instead of wext/ioctl for configuration now?

3 Likes
6

See jow's comment about that :slight_smile:.

  1. 4.4 is not supported anymore. At least not upstream by the kernel community. You can check that easily on https://kernel.org/.
  2. An LTS kernel merely implies it gets maintenance (bug fixes, security patches) for a more extended period, but it does not see backports in any meaningful way. So do not kid yourself: you are talking about an old kernel. And an unsupported one, in case of 4.4. 4.9 is the oldest supported LTS kernel at this point.
7

Kernel 4 4 is on SLTS:
See: https://wiki.linuxfoundation.org/civilinfrastructureplatform/start

2 Likes
8

SLTS is not maintained by kernel.org but by the civil infrastructure project. If you go to the CIP website, they even mention that 4.4 has been deprecated by its maintainer.

1 Like
9

dd-wrt is also struggling with Broadcom drivers for being closed source. Their forums advice to buy other brands, unless you refer to older Broadcom, which were supported at the time.

And regarding the OP, I also think it would be a huge effort to attempt a working mix of the two completely different implementations.