OpenWrt Funding, Round Two

Update September 29: Added additional suggested projects

Following up on the success of our initial round of funding, prpl Foundation, through the prplwrt PEG, is once again offering OpenWrt/LEDE developers an opportunity to submit OpenWrt/LEDE enhancement ideas to be funded by prpl Foundation and its members. Deadline for submissions is October 24, 2016


While all ideas with merit and value will be considered, some examples of projects that prpl is interested in funding include:

  • Adding support for hosting Docker on OpenWrt/LEDE
  • Improvements to the Boardfarm testing framework, including creating a standard server configuration for virtualizing Boardfarm tests, adding support for additional hardware or complex use-cases
  • Integration in OpenWrt of a vendor-neutral data plane abstraction layer, capable to exploit platform-specific HW / SW acceleration and offload capabilities with minimum impact on applications that can take advantage of them (example. ODP –
  • Integration in OpenWrt of a SW fast-path for acceleration of IPv4 /IPv6 packet routing, forwarding, tunneling and termination. (examples:  OFP – /; netmap –, relying preferably on the same data plane abstraction defined above
  • IoT support (standard protocols to aid IoT device onboarding, glue code to support disparate protocol translation, and remote device mgmt support for cloud-based provisioning, command, and control)
  • Application environment (including secure support for 3rd party post-loaded applications)
  • Provisioning/deployment support (so that end-users can be capable of new hardware self-install without having to be an experienced OpenWrt developer)
  • Auto-upgrade support (detect availability of new packages and enable end-users to automatically or manually accept updates)
  • Automated testing (daily build testing of many platforms against trunk)
  • Secure firmware upgrade (possibility to perform authenticity check of downloaded firmware image prior to applying the new image)
  • Power saving features
  • Remote management features (firmware upgrades)
  • Hardware- and/or software-based packet acceleration
  • Telephony support (VoIP, FXS/FXO, DECT/CAT-iq)
  • End-to-end QoS/QoE (IPTV support, HN discovery, LAN optimization, improved service continuity)
  • Carrier-grade access (VLANs, hybrid networking, vectoring, bonding, PHY firmware mgmt)

In addition, you can submit any idea you think has merit/value.

Funding Process

The new funding round for OpenWrt/LEDE projects will use the following process.

Submit a proposal on how to improve OpenWrt/LEDE , particularly in areas important to prpl Members

A proposal should include the following information:

  • Title
  • Summary description of the problem to be solved and reason why it should be solved.
    • Explain the value of the solution to downstream users and the community in general.
    • If your proposal doesn’t fit into one of the areas listed above, please explain why fixing the problem is important.
  • Describe your approach to solve the problem.
    • Include important technical details so that the community can properly evaluate the proposal.
  • Explain your qualifications to complete the problems
  • Make sure to explain why you feel this proposal will be accepted, maintained and used by the community over the long term.
  • If the solution REQUIRES inclusion into the main OpenWrt or LEDE repository, explain why you are confident that it will be accepted. If your solution needs to be in the main OpenWrt repository but probably won’t be accepted by the core OpenWrt team or LEDE committers, then work on community acceptance before you submit the proposal…
  • Timeline for implementation
  • Fixed-fee budget
    • A fixed-fee budget is one where you will receive a pre-determined sum for completion of the task, i.e. $x for completion of y

NOTE: there are limited project funds available. Smaller projects are more likely to be accepted than larger projects. Please consider this in your proposal.

Important considerations for your proposals

Your proposal should answer the following questions for the prpl funders who will evaluate them:

  • Will implementation of the project enhance the value of the community and/or improve the OpenWrt/LEDE project, and be aligned with the goals of prplwrt industry members?
  • Does the broader OpenWrt/LEDE community support the proposed solution? Or is there an important subset of the community which supports proposed solution?
  • Do core OpenWrt/LEDE team members support proposed solution?
  • Do prplwrt members support the proposed solution?
  • Does the implementer (or company/group) have a track record of delivering?
  • Is the proposed length of time for the project feasible?
  • Is the level of funding appropriate for the task to be accomplished?
  • Will the project be licensed under a free/open source software license? (use of an OSI or FSF-approved license is a requirement)

Proposal submission

Proposals must be submitted to the prpl Foundation by October 26. Each submitter should send their full proposal, including a fixed-fee budget, to openwrt-proposals (AT)

Additionally, we request that each submitter outline a summary of their proposal, minus information about the budget, by emailing the prplwrt list at openwrt (AT) announcing their submission. We encourage the community to provide thoughtful, courteous, and constructive feedback.

Answering questions

Prior to the prpl Technical Steering Committee (TSC) and the prpl Board of Directors deciding whether to fund a proposal, the submitter may be asked questions by prpl members and other members of the OpenWrt/LEDE community about their proposal. Answers to these questions help everyone better understand a proposal and the value of funding it.

Technical presentation and Q&A at a weekly prplwrt Meeting (October 29)

In addition to answering questions, to further improve the chances of being funded, submitters are encouraged to provide a short (five minute) presentation of their proposal at one of the prplwrt weekly meetings. If the weekly call is impossible to attend, prpl will try to schedule a special review meeting.

TSC and prpl Board funding decisions

The prpl Board and TSC will decide which projects to fund and then collaboratively work with submitters to develop a contractual agreement for funding the project.

The board and TSC will use their own judgment and the opinions of the community in their funding decisions. Everyone in the OpenWrt community is encouraged to share their opinions of proposals either on the prplwrt mailing list (openwrt (AT) or privately to prpl members or the TSC. If you don’t know who to contact, please email Kathy Giori, prplwrt Chair, at kathy.giori (AT)


If you have any questions about the process or making a submission, we’re here to help. Please either email the prplwrt mailing list at openwrt (AT), contact Kathy Giori, prplwrt Chair, at kathy.giori (AT) or Eric Schultz, prpl Community Manager at eschultz (AT), or ask here as a comment.

Smart Home Security Report

Study Finds Smart Home Tech Gaining in Popularity, Yet Still Woefully Insecure

Smart Home Security ReportSANTA CLARA, CA – Sep 20, 2016 – The non-profit prpl Foundation today unveiled its global study on the use of smart devices in a domestic setting entitled, “The prpl Foundation Smart Home Security Report.” The one-of-a-kind study, which was conducted through OnePoll, covers the proliferation of smart device use and security within the home. It surveyed 1,200 respondents across the US, UK, France, Germany, Italy and Japan to discover the measures people take to secure their smart homes and their attitudes about the security of devices.

Some key findings include:

  • The smart home isn’t coming; it’s already here and device adoption in certain cases has reached a tipping point
  • The smart home is woefully insecure due to users’ failure to follow best practices
  • Consumers prefer security to usability, and they’re prepared to take more responsibility if it means living in a safer home

Continue reading

OpenWrt Summit Sessions

Remember to register for OpenWrt Summit at

As the chair of the OpenWrt Summit Committee, I’m excited to announce the accepted sessions for this year’s OpenWrt Summit. Like last year, we had almost too many high-quality proposals but we tried to accept as many of them as possible. While we had a high bar to meet based on our sessions last year, I think this year’s OpenWrt Summit will meet or exceed last year’s. Even though every submission was unique in its own way, this year’s sessions seemed to fit into a number of categories: Continue reading

prpl @ Microchip MASTERs 2016

U.S. MASTERs 2016prpl Foundation, along with our members Imagination Technologies and Seltech, were excited to participate in Microchip MASTERs conference in Phoenix last week.

MASTERs is known as the “premier technical training conference for embedded control engineers”. We were thrilled to showcase our latest developments for this group: the porting of the prplSecurity™ framework to Microchip’s PIC32MZ controllers sporting the MIPS M5150 core.

Continue reading

IoT Evolution Wrap Up

UPDATE : Application Note posted at

Last week, the prpl Foundation took to the stage at IoT Evolution Expo in Las Vegas to present a workshop on the prpl Security Framework, during which we revealed a demonstration of the framework in practice. It was a series of firsts, as the use of the prplHypervisor™ was put into practice as well as prplPUF™ and prplSecureInterVM™.

Cesare Garlati, chief security strategist at prpl Foundation demonstrated the prplHypervisor™ on Thursday July 14th at 9AM, as part of a prplSecurity™ workshop on the IoT Developer track. The demo was a joint development effort of three key prpl members: Intrinsic-ID, Altran and the Pontifical Catholic University of Rio Grande do Sul (PUCRS).

Garlati showed three virtual machines connecting to the Internet and securely controlling a robotic arm. A MIPS M5150 CPU powers the PIC32 microcontroller to run the prplDSC_5023 hypervisor and thus securely isolates each application in its own virtual machine (VM). VM #1 receives commands from the Internet via Altran’s picoTCP listener, VM #2 authenticates the request via Intrinsic-ID’s implementation of the prplPUF™ API, and then relies authenticated valid command to VM #3, which is responsible for the real time control of the robotic arm via USB. The three VMs are completely separated and communicate within the system via the prplSecureInterVM™ communications APIs.

Continue reading