-
Notifications
You must be signed in to change notification settings - Fork 16
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
New Features #25
base: master
Are you sure you want to change the base?
New Features #25
Conversation
Fix for Windows/Linux CRLF issues with shell scripts.
This reverts commit bf9b170.
Fixed the error when using multiple params in control net task which was caused by repeated `tc qdist add ...` commands being run for the same network interface.
Added packet duplication, packet corruption, packet reordering, and bandwidth limiting.
@cppforlife we added desired functionality from your previous future enhancements list. We are excited to contribute back to your repo with added functionality. Appreciate if you can please review and approve this PR. Please keep us posted on your thoughts and comments if any. Thanks |
@cppforlife just checking to see if you've any comments on this effort. |
@cppforlife any chance this will get merged? |
Hey @Eadword and @karunchennuri, Thanks for the PR and the huge feature set that it adds! It seems that @cppforlife isn't going spend significant time on this, so let me try to find time to look at this. One thing that makes it hard to look at the PR is that you are adding multiple features at the same time. Could you try to split this up into multiple PRs for the individual features you're adding?
This would make it much easier to test the corresponding functionalities and give feedback on the implementation. Sorry for the long wait, I certainly hope that we can merge this in 2019 ;) |
@voelzmo Thanks a lot. We can certainly do that. Also we have more other features we would love to add. Having said that given the fact PRs are taking time, is it ok if we create a new repo and credit this repo for true source of inspiration? Would love to know your thoughts on this please. We credited Turbulence here https://www.youtube.com/watch?v=KMiNuGIV0mY&t=13m06s in our last year's talk. We've plans to add more capabilities going forward, please let us know what is the best way we can get the PRs for current and new ones quickly now and in future. Will wait for you response. Thanks |
Hi @karunchennuri,
Sure, my assumption is you already have a fork of turbulence anyways. What would be your long-term plans for that repo? Would you want to keep it, or move back to this repo once your desired functionality is there?
Thanks for asking this! I think the best way is a twofold approach: First, open an issue to see if the features you're trying to implement make sense to a broader audience and potentially talk about how you're going to implement it. Secondly, open separate PRs for small increments, such that they can more easily be reasoned about and tested. Does this make sense? |
Hi @karunchennuri / @Eadword, i added additional features based on this PR within #27 Best, |
…ed by re-executions of the same command for working interfaces
Added:
Fixed:
The docs have been updated with changes as well, so please see the API docs for complete use information.