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: Check if as_type is not specified when peer is a peer-group member #17603

Merged

Conversation

ton31337
Copy link
Member

@ton31337 ton31337 commented Dec 6, 2024

Closes #17602

Fixes this sequences:

```
neighbor pg4 peer-group
neighbor 127.0.0.4 peer-group pg4
neighbor 127.0.0.4 remote-as 65004

neighbor pg5 peer-group
neighbor 127.0.0.5 peer-group pg5
neighbor 127.0.0.5 remote-as internal
```

Fixes: 0dfe256 ("bgpd: Implement neighbor X remote-as auto")

Signed-off-by: Donatas Abraitis <donatas@opensourcerouting.org>
@ton31337
Copy link
Member Author

ton31337 commented Dec 6, 2024

@Mergifyio backport stable/10.2

Copy link

mergify bot commented Dec 6, 2024

backport stable/10.2

✅ Backports have been created

@Jafaral Jafaral merged commit f1a9b92 into FRRouting:master Dec 6, 2024
16 checks passed
@ton31337 ton31337 deleted the fix/bgp_peer_with_peer-group branch December 6, 2024 14:57
Jafaral added a commit that referenced this pull request Dec 6, 2024
bgpd: Check if as_type is not specified when peer is a peer-group member (backport #17603)
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.

#17542 introduces a regression breaking peer-group configs upon sequential config load
2 participants