Scribd
Upload
533 views37 pages

PrplMesh An Open Source Implementation of The Wi Fi Alliance® Multi AP Specification Arnout Vandecappelle EssensiumMind PDF

Uploaded by

Icaro Posdata
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
533 views37 pages

PrplMesh An Open Source Implementation of The Wi Fi Alliance® Multi AP Specification Arnout Vandecappelle EssensiumMind PDF

Uploaded by

Icaro Posdata
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 37

Arnout

prplMesh: Vandecappelle
Open-source Implementation Essensium/Mind

of the spec underlying


Wi-Fi CERTIFIED EasyMesh™
Overview
●
Multiple acess points problem
●
Wi-Fi CERTIFIED EasyMesh™
●
prplMesh architecture
●
Security
●
Missing features
Multiple access points in house
Insufficient coverage
Multiple access points in house
Insufficient coverage
→add access point
Multiple access points in house
Insufficient coverage
→add access point
→setup complexity
Multiple access points in house
More access points
→more complexity
Multiple access points in house
More access points
→more complexity
→interference
Multiple access points in house
More access points
→more complexity
→interference
→suboptimal use
https://www.wi-fi.org/discover-wi-fi/wi-fi-easymesh
Wi-Fi Alliance Multi-AP specification
underlies Wi-Fi CERTIFIED EasyMesh
Multi-AP
implementation

OEM product

Wi-Fi CERTIFIED
EasyMesh™
Wi-Fi Alliance Multi-AP specification
●
Based on IEEE 1905.1
– ethertype 0x893A version 0 CMDU type CMDU
Message ID frag ID flags header
– fixed multicast
type length value
address
value type length
– device “AL MAC” length value type TLVs
address length value
0 0
Wi-Fi Alliance Multi-AP specification
●
Based on IEEE 1905.1
– Topology discovery
– Onboarding (push-button)
Wi-Fi Alliance Multi-AP specification
●
Based on IEEE 1905.1
●
New CMDUs and additional TLVs
●
Extended onboarding procedure
●
Capability / metric collection
●
Configuration, channel selection, steering
●
Controller and Agent roles
WFA Multi-AP architecture

Agent
Controller
Agent
Agent

Agent
WFA Multi-AP Discovery

Agent
Controller
Agent
Agent

Agent
WFA Multi-AP Metrics

Agent
Controller
Agent
Agent

Agent
WFA Multi-AP Steering

Agent
Controller
Agent
Agent

Agent
WFA Multi-AP Onboarding

Agent
Controller
Agent
Agent Search

Agent
WFA Multi-AP Onboarding

Agent
Controller
Agent
Agent Response

Agent
WFA Multi-AP Onboarding

Agent
Controller
Agent
Agent WSC

Agent
WFA Multi-AP Onboarding

Agent
Controller
Agent
Agent WSC

Agent
WFA Multi-AP WPS

Agent
Controller
Agent
Agent

Agent
Implementation stakeholders
●
Chip vendors start implementing Multi-AP
●
OEMs want to use different chips
without changing their software
●
Carriers want interoperability and
manageability
prpl Foundation
●
An open-source, community-
driven, collaborative, non-profit
foundation
●
Working on standards, APIs and
software for IoT, embedded
devices and the smart society of
the future
●
International membership of 30+
member organizations, and 200+
active engineers
prpl combines standardisation
& open source
●
High-level API
A single API for
on-device software
●
Low-level API
A single API for
chipsets and SoCs
prplMesh Multi-AP implementation
●
Open source reference implementation for Linux
●
Agent ready for Wi-Fi CERTIFIED EasyMesh™
●
Controller as differentiator
●
Match with prpl APIs, add carrier manageability
●
Contracted Essensium/Mind for implementation
Path to certification

prplMesh

OEM product

Wi-Fi CERTIFIED
EasyMesh™
BroadBand Forum and Multi-AP
●
Delivers IEEE 1905.1a stack
https://github.com/BroadbandForum/1905.1a
●
Define architecture and interface for carrier management
– QoS
– metrics acquisition for diagnostics
– ...
●
Define additional test plans
prplMesh architecture
1905.1
Control Data model
Multi-AP

Platform
Drivers
integration
prplMesh Data Model
remote
local device
device

radio radio radios


phy0 phy1

AP AP Backhaul
SSID2 BSSes
SSID1 SSID1
prplMesh Data Model
remote
local device
device

radio radio radios


phy0 phy1
addAP() addAP() addAP()
→cfg80211 →vendor driver →Multi-AP
+ hostapd + forked hostapd CMDUs
OpenWRT platform integration
access persist AP creation metrics/control
ubus socket nl80211

prpl hostapd UCI


hostapd cfg80211
API API rpcd

/etc/config netifd
Stretch goal: unified AP interface
access persist AP creation/metrics/control
ubus socket nl80211

prpl hostapd UCI


hostapd cfg80211
API API rpcd

/etc/config
Security
Multi-AP messaging is protected against out-of-
network eavesdropping through utilization of
encryption feature(s) of its underlying network
connectivity.
A Multi-AP interface is considered authenticated
when the underlying networking technology
encryption mode has been successfully configured.
Missing features
●
Specification of NAT/firewall/VLAN rules
●
Separate networks (guest, fon)
●
Quality of Service
●
End-to-end authentication / encryption
●
Controller election
Router with multiple bridges
●
lan: wired LAN ports, PSK Wi-Fi
●
wan: NATed from other bridges
●
guest: open Wi-Fi, isolated
●
dmz: PSK Wi-Fi, firewalled
License: Attribution-ShareAlike 3.0 Unported
(CC BY-SA 3.0)

You might also like