Advertising and selling routers with OpenWrt/LEDE installed

Somewhat on subject,

CompexWRT is an Operating Systems designed for Compex brand of reliable and powerful embedded boards. It combines OpenWRT with the most advanced and updated Qualcomm Atheros wireless drivers. CompexWRT also includes a user-friendly LuCI web interface for configuring the router. OpenWRT is an extensible GNU/Linux distribution for embedded devices. It is built from the ground up to be a full-featured, easily modifiable operating system. It is powered by a Linux kernel that's more recent than most other distributions. The latest stable version of OpenWRT, 12.09 Attitude Adjustment, is used in CompexWRT. LuCI is a free, clean, extensible and easily maintainable web user interface for embedded devices. It has high performance, small installation size, fast runtimes, and good maintainability.

I don't know that I'd consider 12.09 "The latest stable version" but at least it gives hope that their cards are supported.

If someone can find the source-code links, I'd appreciate it!


They are using Qualcomms QSDK.
Thats pretty much it,that is why it is stuck at 12.09

They (Compex) use old version... new QSDK releases are based on more up to date kernel/LEDE/OpenWrt.

I was thinking about a different approach. When browsing Aliexpress, ZBT advertises that it will manufacture custom routers with orders of 500+. Firmware, logos, chipsets (qualcomm, mediatek) can be specified. It may be possible to start a project that would generate income for OpenWrt by providing a well-supported, no-hassel router.

It is better if entrepreneurs do their thing and make donations from their profit etc than volunteers trying to pretend to be entrepreneurs.


I'm currently looking at the GPL'd source for a Trendnet TEW-827DRU V2.0 It is OpenWrt (circa Kernel 3.10) based. Another recent post on a Comfast CF-WR617AC

I tried looking for a GPL'd source and only search hits described Comfast's failure to provide code. I looked at the OpenWrt donation page and did not find a list of corporate donors. Me thinks corporate donations are wishful thinking.

It is also telling to look at the posts regarding porting devices that come with OpenWrt/LEDE.

Personally, I trust the technical expertise of the project over any "entrepreneur".

You know the "etc" part might be they are contributing code back to the project.

Browse the linux kernel commits, it is littered with redhat, ibm, qualcomm, mediatek, amd, intel and realtek contributors. I'm pretty new to OpenWrt but have already been credited with contributing code and testing. My contributions were based on reviewing lines of existing code. Not once did I see a contribution from an employee of a router manufacturer.

Another example is OpenBSD, they list their financial contributors


There are manufacturers that provide GPL code for download or on request.

Do your research before purchasing and support appropriately.


True, but it's something that requires time to arrange things and quite a bit of money upfront, If someone volunteers to do that, please contact project members and see what they say about it.

if you think big brands aren't just buying hardware in bulk like that I have some news for you. For most sub-200 euro devices, they do that as there are basically no margins.

Most GL.Inet routers have been added to OpenWrt by the manufacturer's developers, even if they are not using company emails (especially lately, they started sending patches to the mailing list before the device is released). So it may not be obvious what was contributed by a manufacturer. Although in general the big brands don't really care.

Then again they are also known for their customer support people answering questions about doing electrical mods to their devices (i.e. things that 100% void any warranty) with partial schematics, so I concede that they are pretty unique.

Plus there is Gateworks and NXP developers sending for their own stuff.


I was thinking of using a reputable GoFundMe type service to handle the money/orders.
OpenWrt would pick the best supported chipsets in several categories:

  1. Low cost: mt7628 16/128 2.4/5.0Hz
  2. Midrange: dual core
  3. High end: arm with dual 5Hz radios

All would be upgrade-able via LuCi.

The cost of each device would include a 20% donation to OpenWrt and provide hardware for the developers who sign up to contribute.
OpenWrt would develop and host the firmware.

ZBT would manufacture, to the projects specs, imprint with a logo and flash with a basic OpenWrt firmware. ZBT would be responsible for the hardware warranty, OpenWrt for firmware bugs/vulnerabilities.

Not sure about the distribution; direct from ZBT or regional distributor.

I repeat, someone must devote time to decide what hardware is good or not, deal with manufacturers, ship orders and keep stuff stocked, and afaik none has volunteered to do that. It's something you are underestimating I guess, but it's not something you can just do "whenever you feel like it".

"Making the firmware" is more or less a non-issue as on such a device you know already everything from the start and control the bootloader's configuration, anyone of the basic "contributors"that has added a device in the past can do it.


There is nothing to stock, If the project reaches its goal, ZBT sets and runs the production one time. Late orders would be not be filled unless another production run minimum is met.
Only one prominent manufacturer advertises the capabilities that are needed. Although to keep them honest several bids should be obtained.

There are only 2 SoC manufacturers, that open source, for the lower end device, Mediatek (mt7628 or mt7621). The mt7620 is an older mt7628 that is not as energy efficient. These include a 2R2T 2.4 radio on chip. The 5.0 radio is an addon chip and there are several to choose from. The mt7615 is having some teething problems but older chips with a track record can be used.. The person handling MT76 development could make a recommendation. Qualcomm is the other - I'm not familiar with Qualcomm's offerings to make suggestions.

This is not a project for volunteers.
This is a full on business. You need to acquire warehousing and shipping facilities/services
You need to provide warranty, no you can't offload warranty to a manufacturer when you put your label on the device. You need to employ someone to deal with customers.

It is a great idea, But the way your going about it is wrong.

1 Like

When you open a case or irreversibly flash OpenWrt, you have voided your warranty anyway. The forum already deals, gratis, with users having problems with devices and actually is a more reliable source of flash dumps than any manufacturer. The available wikis are far more complete than any device manual I've seen. The GPL'd source is already available.

I agree, that It needs to be crystal clear for those that fund, the devices are specifically targeting OpenWrt users. The first thing most users will do is update and customize their packages.

Another hurdle comes to mind though and that is registering the device with the regulatory agencies, ie FCC. The FCC does not review the firmware, just the radiation and strength/specificity of the wireless bands. I have been able to find ZBT submissions to the FCC.

Oh my

What is the point of this excercise if your not offering warranty.

There is no shortage of products used and new that are supported by ooenwrt.

I don't see why this is required.

I don't understand your point.

While there is no warranty of ongoing support for any device under OpenWrt, those with insufficient resources are at great risk for “end of support”.

As quoted from the website, OpenWrt comes with no warranty. Here is why someone may want a device that is specifically built to run OpenWrt:

Here is a second example, a Cudy marketed device that has attractive specs
advertises OpenWrt compatibility. They specifically disclaim warranty support if you load OpenWrt.

In my opinion

Openwrt is not set up to run a business.

Consumers expect warranty.

Openwrt cannot endorse a commercial product or have product branded as openwrt. However a product can claim it supports openwrt and use the logo with condtions on documentation and marketing etc.

A business is welcome to do all the things you mentioned above but openwrt shouldn't.

A business is welcome to make a clone for openwrt and provide the support and testing before releasing updates to customers. Allowing warranty to be maintained.

A business is welcome to support openwrt and to ask for help when needed, or they may choose to hire a professional/expert .

In summary it needs to be a business.

If this is where openwrt wants to go then it needs to spin off a business first then do the things you mention.