-
Notifications
You must be signed in to change notification settings - Fork 2
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
feat: Support status
and wan
#39
Conversation
description: Connection status of the interface, true for connected. | ||
wan: | ||
type: boolean | ||
description: Indicate the interface worked as WAN or not (LAN). |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What is the main purpose of attribute wan
?
Bundle already has been defined all wan interfaces in json file
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
A WiFi interface may be in client mode or AP mode. The interface cannot be WAN if in AP mode.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think we could add another endpoints to let other bundles able to modify route priority/add/remove. In this case, wifi bundle should remove the interface which is in ap mode from routing list. Otherwise, route bundle restart will loose these information.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Route bundle depends on all network interface bundles, so it "will" loose all interfaces' information if it restart. The network manager we are thinking about is still under thinking...
We could discuss tomorrow for better method.
No description provided.