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

bfdd: retain remote dplane client socket #17464

Merged
merged 1 commit into from
Nov 20, 2024

Conversation

mjstapp
Copy link
Contributor

@mjstapp mjstapp commented Nov 19, 2024

When using bfd in remote-dataplane client mode, don't close a new client socket if we're going to try to use it. It looks to me as if client-mode remote dataplane won't work without something like this?

When using bfd in remote-dataplane client mode, don't close
a new client socket if we're going to try to use it.

Signed-off-by: Mark Stapp <mjs@cisco.com>
@donaldsharp
Copy link
Member

@rzalamena can you take a look at this one?

@rzalamena
Copy link
Member

Just tried locally with libbfddp sample daemon and it fixes the client mode.

@rzalamena rzalamena merged commit bca9911 into FRRouting:master Nov 20, 2024
14 checks passed
@mjstapp
Copy link
Contributor Author

mjstapp commented Nov 20, 2024

@Mergifyio backport stable/10.2 stable/10.1

Copy link

mergify bot commented Nov 20, 2024

backport stable/10.2 stable/10.1

✅ Backports have been created

Jafaral added a commit that referenced this pull request Nov 21, 2024
bfdd: retain remote dplane client socket (backport #17464)
donaldsharp added a commit that referenced this pull request Nov 21, 2024
bfdd: retain remote dplane client socket (backport #17464)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants