WIP: Allow routing on top of AP-client links, keep general and specific wifi settings separate, fix #415 #551
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…cific wifi options
…e' suffix on top of apname_mode.wifi_mode which is just 'ap'
…abeld and Batman-adv
|
I thought that rather than using the In that case I would not need to remove the hardcoded lan from mode/ap and mode/apname and neither I would need to remove tableMelt. |
G10h4ck
changed the title
|
Finally, clientbackbone is not useful and I rewrote the apbackbone part in #554, closing. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
LibreMesh by default creates 3 wireless interfaces on each radio and emploies the IEEE802.11s one for routing.
Up to now, access point-client wifi connections (AP-sta) was possible to use for routing with BMX6 as described in #426.
For the next release, BMX6 is not going to be included while Babeld will be.
The usage of AP-sta connections for the backbone can have the following advantages:
nearly every OpenWrt-supported router can be employed for a LibreMesh network; and the AP and client drivers are more tested than the IEEE802.11s drivers.
This PR allows the user to set up an AP interface (using interface specific configuration) out of the br-lan bridge removing the hardcoded setting
networkequal tolanfrom the mode/ap.lua and the mode/apname.lua scripts.This implies that an
option ap_network 'lua'and anoption apname_network 'lua'will have to be explicitly set in the configuration for having a normal usage. This was added to/etc/config/lime-defaults-factory.As implemented in eadcc14 and in db1c350, the general wireless configuration is also used as a default for the specific interface configuration, making impossible (I think) to not set the
option networkfor the specific interface configuration needed for the automatic setting of it by OpenWrt.For this reason, this has been removed.
The use of specific configuration will not keep any setting from the generic configuration for this radio, so that some users could have to update their configurations.
This has been reflected in lime-example file.
In lime-example, there is also an example of configuration for an AP with VLAN and Babeld + Batman-adv and also for a client with the same protocols.