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.

Sign up for GitHub

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

Jump to bottom

bgpd: Print the real reason why the peer is not accepted (incoming) #18410

Merged
merged 1 commit into from
Mar 18, 2025
Merged

bgpd: Print the real reason why the peer is not accepted (incoming) #18410

merged 1 commit into from
Mar 18, 2025
+54 −25

Conversation

ton31337
Copy link
Member

Closes #18408

@ton31337
bgpd: Print the real reason why the peer is not accepted (incoming)
Loading
Loading status checks…
ace4b8f 
If it's suppressed due to BFD down or unspecified connection, we never know
the real reason and just say "no AF activated" which is misleading.

Signed-off-by: Donatas Abraitis <donatas@opensourcerouting.org>
@frrbot frrbot bot added the bgp label Mar 17, 2025
riw777
riw777 approved these changes Mar 18, 2025
View reviewed changes
Copy link
Member

@riw777 riw777 left a comment

Choose a reason for hiding this comment

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

looks good

@riw777 riw777 merged commit ad7e625 into FRRouting:master Mar 18, 2025
16 checks passed
@ton31337 ton31337 deleted the fix/print_the_real_reason_supressed_peer branch March 18, 2025 13:00
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@riw777 riw777

Assignees
No one assigned
Labels
bgp master size/M
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.

Bgpd log is misleading
2 participants
@ton31337 @riw777