Skip to content
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

L2: avoid having one failure on responder disable l2 #1726

Merged
merged 3 commits into from Nov 29, 2022

Conversation

fedepaol
Copy link
Member

@fedepaol fedepaol commented Nov 29, 2022

If a responder fails to be set (i.e. ndp on a ipv4 only node), then the list of interfaces is not being built.
That results in l2 mode entirely not working. Here we make the mechanism a bit more robust by continuing on errors.

Fixes #1727

If a responder cannot be created on a given interface, it should not
prevent responders to be created on all the other interfaces. For this
reason here we continue instead of returning. This is even more sensible
with the interface selector mechanism, because returning won't allow the
list of interfaces to be filled and so the speaker will always skip.

Signed-off-by: Federico Paolinelli <fpaoline@redhat.com>
If the flag is set, we don't need to iterate over the interfaces to find
a match because it will always be the case.

Signed-off-by: Federico Paolinelli <fpaoline@redhat.com>
Copy link
Member

@oribon oribon left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

lgtm

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

A single interface failures makes l2 stop working
2 participants