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

bgpd: Do not show TCP MSS if the socket is broken #15325

Merged

Conversation

ton31337
Copy link
Member

@ton31337 ton31337 commented Feb 7, 2024

Closes #15321

Just avoid calling for TCP MSS socket option if it's not in use.

Signed-off-by: Donatas Abraitis <[email protected]>
@frrbot frrbot bot added the bgp label Feb 7, 2024
@ton31337 ton31337 added this to the 10.0 milestone Feb 7, 2024
@ton31337
Copy link
Member Author

ton31337 commented Feb 7, 2024

@Mergifyio backport stable/9.1

Copy link

mergify bot commented Feb 7, 2024

backport stable/9.1

✅ Backports have been created

@donaldsharp donaldsharp merged commit fcf1ab9 into FRRouting:master Feb 8, 2024
11 checks passed
@ton31337 ton31337 deleted the fix/show_getsockopt branch February 8, 2024 15:36
ton31337 added a commit that referenced this pull request Feb 8, 2024
bgpd: Do not show TCP MSS if the socket is broken (backport #15325)
@SwimGeek
Copy link

SwimGeek commented Feb 9, 2024

Hi, is it safe to just ignore the 'sockopt_tcp_mss_get failed' log entries? Do we wait for version 9.1.1?

@ton31337
Copy link
Member Author

ton31337 commented Feb 9, 2024

Yes, it's safe, because it's just a noise for broken file descriptors (aka. non-established peers).

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.

FRR 9.1 sockopt_tcp_mss_get failed
3 participants