Skip to content
GitLab
Explore
Sign in
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
b10a3240
Commit
b10a3240
authored
1 year ago
by
Jakob Olsson
Browse files
Options
Downloads
Patches
Plain Diff
README: add maxhop section and fix dscp_pcp list
parent
6763e581
Branches
Branches containing commit
No related tags found
1 merge request
!289
docs: update uci schema and docs
Pipeline
#133985
failed
1 year ago
Stage: static_code_analysis
Stage: compile_test
Changes
1
Pipelines
8
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
README.md
+18
-1
18 additions, 1 deletion
README.md
with
18 additions
and
1 deletion
README.md
+
18
−
1
View file @
b10a3240
...
...
@@ -360,7 +360,9 @@ config qos_rule 'qos_rule1'
option type 'dscp_pcp'
option output '8'
option always_match '1'
option dscp_pcp '1,2,3,4,5,6'
list dscp_pcp '58,1'
list dscp_pcp '58,2'
list dscp_pcp '10-21,5'
```
The
`output`
value determines the target PCP. If the rule has
`output`
...
...
@@ -788,6 +790,21 @@ ubus call map.controller dpp_enrollee_uri_eth '{"uri":"DPP:C:81/1,115/36;V:2;K:M
Once provided, map-controller will be able to perform DPP Ethernet onboarding,
triggered by AP-Autoconfig Search and DPP Direct Encapsulated messages.
## Control Depth of a Multi-AP Network
Limit the max number of Wi-Fi backhaul links that are allowed in "daisy-chained"
topology. By default the feature is disabled, which means that the EasyMesh
network is not limited to any number of Wi-Fi backhaul hops.
```
config controller 'controller'
option enabled '1'
...
option max_node_bh_hops '2' # number of allowed Wi-Fi hops
```
NOTE: Ethernet daisy-chains are still supported at any length, and forming a
daisy-chain with Eth to Wi-Fi is still possible.
## UBUS APIs
...
...
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