Skip to content
GitLab
Explore
Sign in
Register
Primary navigation
Search or go to…
Project
M
map-controller
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Wiki
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Snippets
Build
Pipelines
Jobs
Pipeline schedules
Artifacts
Deploy
Releases
Container registry
Model registry
Operate
Environments
Monitor
Incidents
Analyze
Value stream analytics
Contributor analytics
CI/CD analytics
Repository analytics
Issue analytics
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Terms and privacy
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
Multi-AP
map-controller
Commits
4aadf926
Commit
4aadf926
authored
1 year ago
by
Jakob Olsson
Browse files
Options
Downloads
Patches
Plain Diff
dpp: ethernet README
parent
3a0d136f
Branches
Branches containing commit
Tags
Tags containing commit
No related merge requests found
Pipeline
#123006
failed
1 year ago
Stage: static_code_analysis
Stage: compile_test
Changes
1
Pipelines
2
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
README.md
+24
-0
24 additions, 0 deletions
README.md
with
24 additions
and
0 deletions
README.md
+
24
−
0
View file @
4aadf926
...
@@ -711,6 +711,8 @@ improvement in the map-controller `status` UBUS API.
...
@@ -711,6 +711,8 @@ improvement in the map-controller `status` UBUS API.
## DPP Easy Connect
## DPP Easy Connect
### Wi-Fi QR Code based Onboarding
NOTE: The enrollee and the controller/configurator device must be operating at
NOTE: The enrollee and the controller/configurator device must be operating at
the same channel, as off channeling listening for DPP Chirp messages is
the same channel, as off channeling listening for DPP Chirp messages is
currently not supported.
currently not supported.
...
@@ -765,6 +767,28 @@ are not yet implemented, fronthaul configurations relies on AP-Autoconfiguration
...
@@ -765,6 +767,28 @@ are not yet implemented, fronthaul configurations relies on AP-Autoconfiguration
which does not support passing DPP AKMs. With this said, it is possible to onboard
which does not support passing DPP AKMs. With this said, it is possible to onboard
via DPP only AKMs and establish a connection.
via DPP only AKMs and establish a connection.
### Ethernet QR Code based Onboarding
DPP Ethernet onboarding is implemented leveraging
[
libdpp
](
https://dev.iopsys.eu/multi-ap/libdpp
)
.
For DPP Ethernet onboarding, no additional configuration sections needs to be
present, but map-controller must be compiled with the CLFAGS including
`USE_LIBDPP`
.
The credentials that are provisioned are picked up based on the backhaul
`ap`
sections in the map-controller configuration file.
To perform DPP Ethernet onboarding, the enrollees bootstrap information must
provided to the map-controller via its UBUS API
`dpp_enrollee_uri_eth`
:
```
ubus call map.controller dpp_enrollee_uri_eth '{"uri":"DPP:C:81/1,115/36;V:2;K:MDkwEwYHKoZIzj0CAQYIKoZIzj0DAQcDIgACcwPoTjXxtZ2IJAjyZeH1kECGHXGhxhEEyPzcnpFo2ms=;;"}'
```
Once provided, map-controller will be able to perform DPP Ethernet onboarding,
triggered by AP-Autoconfig Search and DPP Direct Encapsulated messages.
## UBUS APIs
## UBUS APIs
Map-controller offers a variety of UBUS APIs, most of them map to CMDU request
Map-controller offers a variety of UBUS APIs, most of them map to CMDU request
...
...
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment