-
Notifications
You must be signed in to change notification settings - Fork 52
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
Allow to slave devices execute ifup-post. #109
base: main
Are you sure you want to change the base?
Conversation
Hello @k0ste,
What exactly can't be "tuned" in your case? Please, provide us with more information. Thank you. |
I provided example |
Hmm, can't you set most of the bits from your example via ETHTOOL_OPTS? The reason why we ask is that we would like to find a different way how to implement the behavior you want. Calling ifup-post here is not an option, it does much more than just calling ifup-local and this could definitely break someone else's setup. I would also like to avoid directly calling ifup-local here, because again I can imagine a use-case it could break. |
Nope, because sometimes (various of device) we need timeout between ethtool calls, when driver reloaded device. If we try do this jobs on MASTER interface (i.e. bond0) with switches that unsupported LACP rate fast (like Cisco Catalyst 29**) - possible break of LAG, due timeouts without any slave. With
But with
|
We already have ETHTOOL_DELAY which waits before calling ethtool, maybe we could also add it to the for loop. Something like:
|
But looking to your script, you do only one ethtool call per device, so the current ETHTOOL_DELAY should be working for you. |
Why you ignore |
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.
Calling ifup-post there could break existing setups. We should come with a solution that would offer to set the necessary settings without using ifup-local script.
I created issue #153, because don't see any movements about this PR. |
Well, I currently do not have any solution which would satisfy your needs and wouldn't break any existing user setups. Do you? :) |
Please, explain for me: how it break existing user setups? May be I don't understand something and will search another solution. |
Hello.
I find out that slave devices in bond LACP LAG can't be tuned via
ifup-local
. As I understand the exit after SLAVE key is for safety (ignore another options). So for save this behaviour I just added exec forifup-post
.Work of this patch tested on various baremetal servers. For example:
journal log: