-
-
Notifications
You must be signed in to change notification settings - Fork 72
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[change] When adding a Wireless config, should it add an interface? #289
Comments
I ran into a situation in which the additional configuration in |
I don't think we can remove |
Avoid generating unnecessary config in /etc/config/network when defining wireless interfaces. Closes #289
Avoid generating unnecessary config in /etc/config/network when defining wireless interfaces. Closes #289
#298 should fix this. I am testing it. |
Avoid generating unnecessary config in /etc/config/network when defining wireless interfaces. Closes #289
Avoid generating unnecessary config in /etc/config/network when defining wireless interfaces. Closes #289
Scenario
Consider the following network configuration:
The goal is to create two SSIDs for each VLAN:
NetJSON Configuration
This configuration generates the following (showing only wireless-related settings):
Package Network
Package Wireless
When manually configuring in OpenWRT, it is simplified as follows:
Package Network
There's no config added in
network
Package Wireless
As observed, the manual configuration lacks the ifname attribute in the wireless package, and no interfaces are created in the network package. While the current configuration works, there's a consideration about simplifying the OpenWisp-generated config. Does this simplification make sense?
The text was updated successfully, but these errors were encountered: