-
Notifications
You must be signed in to change notification settings - Fork 473
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
fix(NSC): only set rp_filter to 2 if it is 1 #1791
Conversation
Also this doesn't work in all cases as I see, since this won't disable rp_filter on these in case all is set to 1 or 2: kube-router/pkg/controllers/proxy/linux_networking.go Lines 769 to 787 in 93498fb
|
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.
There's one linting error that needs correcting, and I left a request to add one more interface that I missed in our previous conversation, and I had one question.
I also deployed it to my test harness and while I haven't tested all of the boundary conditions for rp_filter values, I was able to confirm that it runs similar to how it ran before.
But other than that, this change looks really good! Thanks for putting this together for us!
I'm not totally sure if I understand this comment correctly, doesn't the last case set rp_filter to Also, just to be clear, this logic is setting that value for the interfaces found inside the container's network namespace in case that helps clarify anything for you. |
Okay, if it's inside the container that's not to be considered. Thanks for clarifying |
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 for the update! 2 more comments, but I think we're just about at the end here.
Setting rp_filter to 2 when it is 0 will override its status to be always enabled (in the loose mode). This behavior could break some networking solutions as it made packet admission rules more strict.
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.
LGTM!
Thanks so much for your contribution @dsseng!
Setting rp_filter to 2 when it is 0 will override its status to be always enabled (in the loose mode).
This behavior could break some networking solutions as it made packet admission rules more strict.
Reference: #1651 (comment) and subsequent