-
Notifications
You must be signed in to change notification settings - Fork 5
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
Improve netifyd network configuration #929
Labels
verified
All test cases were verified successfully
Milestone
Comments
This was referenced Dec 2, 2024
gsanchietti
added a commit
that referenced
this issue
Dec 3, 2024
Enhance interface filtering and ensure uniqueness in netifyd configuration #929
gsanchietti
added a commit
that referenced
this issue
Dec 5, 2024
Update exclusion logic and documentation for Netifyd #929
Testing image: 23.05.5-ns.1.3.0-92-g7ef1d292 |
Before adding the exclusion:
From
After added exclusion for
From
|
gsanchietti
added
verified
All test cases were verified successfully
and removed
testing
Packages are available from testing repositories
labels
Dec 5, 2024
Released on 23.05.5-ns.1.4.0 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
In accordance with Netifyd guidelines, modify the Netifyd configuration file, to limit the number of interfaces to inspect.
Actually every local interface (physical or logical) is added netifyd
internal_if
parameter.Keeping both physical and VLAN interfaces introduces redundancy and has a few negative impacts:
The following interfaces must be always be added to netifyd configuration:
Currentlyalso VPNs and hotspots interfaces are added to netifyd configuration, but there are mixed feelings about having them in netifyd configuration.
Proposed changes:
eth1
,tun*
,wg*
.The text was updated successfully, but these errors were encountered: