-
Notifications
You must be signed in to change notification settings - Fork 111
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(network): Configurable maximum connections per IP #7013
Conversation
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.
Thanks, looks great!
We might want to think about how to name the config files when we don't know if the next release will be 1.0.1 or 1.1.0. But that's not an issue for this PR to solve!
a262bf0
to
fa8e14a
Compare
Codecov Report
Additional details and impacted files@@ Coverage Diff @@
## main #7013 +/- ##
==========================================
- Coverage 77.44% 77.39% -0.06%
==========================================
Files 310 310
Lines 41609 41628 +19
==========================================
- Hits 32225 32218 -7
- Misses 9384 9410 +26 |
This new config could be a new user-visible feature. So if it merges, that would make the next release a minor version (1.1.0). This config is likely to be used in test environments. But we've also had production users say that they wanted node replication on internal networks or on the same machine, which would benefit from this config as well. Just checking to see if anyone wants to call it a debugging feature instead? (I don't mind either way, I'm just putting the question out there, so it's decided before the release.) |
Motivation
This could be helpful for integration testing.
Solution
maximum_connections_per_ip
field to zebra-network configzebrad/tests/common/configs
Review
Anyone can review.
Reviewer Checklist