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: Actually make --v6-with-v4-nexthops it work #16971

Merged

Conversation

ton31337
Copy link
Member

@ton31337 ton31337 commented Oct 2, 2024

Related: #16969

It was using `-v` which is actually a _version_.

Fixes: 0435b31 ("bgpd: Allow bgp to specify if it will allow v6 routing with v4 nexthops")

Signed-off-by: Donatas Abraitis <[email protected]>
@ton31337
Copy link
Member Author

ton31337 commented Oct 2, 2024

@Mergifyio backport stable/10.1 stable/10.0 stable/9.1

Copy link

mergify bot commented Oct 2, 2024

backport stable/10.1 stable/10.0 stable/9.1

✅ Backports have been created

@ton31337 ton31337 mentioned this pull request Oct 2, 2024
2 tasks
@ton31337 ton31337 added this to the 10.2 milestone Oct 2, 2024
@donaldsharp donaldsharp merged commit 46df84f into FRRouting:master Oct 2, 2024
13 checks passed
@ton31337 ton31337 deleted the fix/v6-with-v4-nexthops branch October 2, 2024 15:55
ton31337 added a commit that referenced this pull request Oct 3, 2024
bgpd: Actually make ` --v6-with-v4-nexthops` it work (backport #16971)
ton31337 added a commit that referenced this pull request Oct 3, 2024
bgpd: Actually make ` --v6-with-v4-nexthops` it work (backport #16971)
ton31337 added a commit that referenced this pull request Oct 7, 2024
bgpd: Actually make ` --v6-with-v4-nexthops` it work (backport #16971)
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