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: Fix match peer when switching between IPv4/IPv6/interface #16022

Merged
merged 1 commit into from
May 20, 2024

Conversation

ton31337
Copy link
Member

No description provided.

Without this patch we MUST follow this sequence:

```
no match peer 10.0.0.1
match peer 2a01::1
```

Otherwise, both IPv4/IPv6 values are set/compiled, thus when printing the
configuration in show running, we see the first one (IPv4).

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

@Mergifyio backport stable/10.0 stable/9.1 stable/9.0

Copy link

mergify bot commented May 16, 2024

backport stable/10.0 stable/9.1 stable/9.0

✅ Backports have been created

@donaldsharp donaldsharp merged commit 0babb93 into FRRouting:master May 20, 2024
11 checks passed
@ton31337 ton31337 deleted the fix/match_peer branch May 20, 2024 14:02
donaldsharp added a commit that referenced this pull request May 20, 2024
bgpd: Fix `match peer` when switching between IPv4/IPv6/interface (backport #16022)
donaldsharp added a commit that referenced this pull request May 20, 2024
bgpd: Fix `match peer` when switching between IPv4/IPv6/interface (backport #16022)
donaldsharp added a commit that referenced this pull request May 20, 2024
bgpd: Fix `match peer` when switching between IPv4/IPv6/interface (backport #16022)
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.

None yet

2 participants