Conversation
Introduce lqos_network_devices actor + dir watcher and route lqosd + tools through public APIs.
- Emit unknown observations for existing entries when still unresolved\n- Downgrade watched queue miss to debug
- Rework Operation layout to avoid wide-table squeeze\n- Add responsive config table styling\n- Collapse min/max speed columns into down/up pairs
thebracket
added
enhancement
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Adds support for dynamic circuits.
Once you enable dynamic circuits in the config, and allow "unknown IP range creation" you can define ranges (e.g. 192.168.100.0/24 or 0.0.0.0 for everything), name them, and assign a default plan to any IP that appears in that range. This is intended for public wifi, tracking down unknown devices, simple small office setup and similar.
This is part 1 of 3 (but please merge it). The other two parts will update the API to use it (depends on this), and the final part will investigate (and implement if practical) RADIUS support.