technicolor.com

BRINGING OPENWRT TO MARKETOPENWRT SUMMIT 2017

Introducing Technicolor

We also design and manufacture equipment for

the Connected Home (routers, set-top-boxes …)

We are known for Entertainment

(film processing, special effects …)

And we work with OpenWrt/LEDE

2

3

Market Dynamics

Technicolor is not in the retail business – Our direct customers are ISPs

► Large scale operations: hundreds of products, tens of millions of homes

► Extensive and diverse set of requirements: triple play (Data, IPTV, VoIP), remote management …

► Access to component vendor’s proprietary code: physical layer (DSL, Wi-Fi, LTE), hardware accel …

► High quality expectations: uptime, Quality of Service …

► Robust software processes: traceability, release management, continuous integration …

Component Vendors

TechnicolorInternet Service

Providers

Subscribers (You!)

These market dynamics influence the way we work with OpenWrt/LEDE

4

Our customers using OpenWrt…One unified SW strategy lets customers share the benefits of interoperability and feature evolutions

Homeware deployed in 50+ customers from Australia to Gibraltar…

5

Why OpenWrt/LEDE?

Solid platform

• Provides the right functionality for a standard home router

• Modular and platform agnostic

• Easy to build upon to create your own router products

Accessible

• Well known throughout the community and the industry

• Anyone can get started, no red tape

• Common reference platform for third parties

Diverse ecosystem

• Platform of choice for new router software initiatives ranging from commercial to non-profit

• Innovation across boundaries

6

Our proposition with Homeware

Semicon Vendor SDK

User Applications

Voice TR-069GUI Analytics

TR-143

Network

Broadcom

QuantennaIntel

Annapurna

OpenWrt is the dominant

platform for gateway market

Vendor agnostic platform

approach

Unleash creativity for your

own applications or 3rd parties.

Qualcomm

Homeware quarterly releases, based on OpenWrt

One highly

customizable

release branch for all

customers, chipsets

and platforms

releasing 4 times per

year

• Build complexity solved

• Consistent quality

• Configurable and flexible

• Maximize reuse

• Bug fix coverage

• Fast security updates

Homeware

8

Enabling quality softwareDuring development Homeware is constantly verified with Continuous Integration

fully integrated with bug tracking system.

Each deliverable is fully validated on the target platform in the lab and the

customer network.

Development

On generic SW

Technology-facing testing

Functional testing

SW dev support testing

Typically in ‘generic’ CI setup

Typically automated

Validation

On customized SW

Customer facing testing

Scenario testing

From ‘User’ perspective

Typically in customer network

Typically manual

Field

Diagnostics in the field

Fast resolution

9

Focus on security

Security assessment on every quarterly release of Homeware

NOT ALLOWEDKnown critical vulnerabilities (CVSS > 7)

• Field deployment

• Field trials

TOLERATEDKnown critical vulnerabilities

• Lab trials

Enforced by the

Technicolor

Security Office

Vulnerabilities are being scored and assessed

Common Vulnerability Scoring System v3.0

10

Offering an SDKHomeware gives operators and their partners the tools that they

need to develop, to integrate and to deploy their applications

Linux Containers (LXC) = control groups + namespace isolation

• Control groups

• CPU

• Memory

• I/O

• Namespace isolation

• Processes

• Users

• File systems

• Network stacks

“Managing sparse resources”

“Improving security”

Compiler toolchain, APIs,

documentation, sample

apps, support services …

Package management

Remote management

App Store

Enabling life cycle management

TR-69 / TR157 Amendment II

Enables the gateway as an application platform

App 1

App 2

App 3

App 4

12

Combining Proprietary and Open Source SW

Open source50%

Technicolor35%

Component vendor

10%

Other5%

(Simplified package distribution of a Technicolor OpenWrt based router)

+ patches

► Base Linux system:

kernel, drivers …

► OpenWrt framework:

UCI, uBUS, procd …

► Standard networking:

Ethernet, IPv4, IPv6,

firewall, NAT, DHCP,

DNS, QoS …

► Various applications:

VPN, Samba, MQTT

…

► Managed services: IPTV, VoIP, WAN sensing …

► Remote management: TR-069, SNMP …

► Local management: Web UI, TR-064 …

► Value-added applications and services …

Specific kernel

extensions,

drivers, utilities

13

OpenWrt Contribution Strategy

Goal: achieving the right balance between software available in OpenWrt as open source, and software maintained in house

Reasons for Technicolor to contribute:

► Strengthen the community, increase adoption

► Stimulate new contributions, increase quality

► Reduce maintenance cost, avoid forking

Reasons for Technicolor not to contribute:

► Loss of competitive advantage

► Open source licensing constraints

► Effort to contribute and to maintain,low chance of adoption

Open source50%

Technicolor35%

Component vendor

10%

Other5%

+ patches

14

Past and Present ExamplesAdding new features

► GRE tunneling

► PPP Unnumbered

► IPinIP

► netifd link state propagation

► NTP server config via DHCP

► Procd firewall support

Making existing packages ready for field deployment

► 464xlat/map-t

► odhcp6c and odhcpd

Package upsteps, additional config options

► dnsmasq, nginx and ngx_lua, strongswan, curl, openssl, openssh, dropbear

Bug fixes

► ubus, procd, libubox, firewall3, Ldoc, luacheck

Unsuccessful contributions (*it happens!)

► MWAN

► TR-069 datamodel mapping framework

► https://github.com/dirkfeytons/transformer

► https://github.com/dirkfeytons/lua-tch

Potential future contributions

► WAN sensing

► Life Cycle Management

Thank you