Conversation
…#17074 The GUI has no way to set "bgp listen range", so dynamic BGP neighbors (MetalLB speakers, for example) can only be configured from the raw config page. The field lives on the peer group entry because a range is bound to a group. The group is also activated in the address family of each range, since bgpd ignores a listen range for a group that has no active address family.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The FRR package has no way to set
bgp listen range, so dynamic BGP neighbors (MetalLB speakers on a Kubernetes cluster, in my case) can only be configured from the raw config page.This adds a Listen Range field to the peer group entry on the BGP Neighbors form, since a range is only meaningful for a group. The non-obvious bit: the group also gets
neighbor <group> activatein the address family of each range, because bgpd will not create dynamic neighbors for a group with no active address family. Without it an IPv6 range, or any range underno bgp default ipv4-unicast, is silently ignored.Tested on 2.7.2 CE with pkg-frr 2.0.2_1, where the patch applies as is. Setting 192.168.120.16/28 on a group through the form put the listen range in the generated frr.conf and the four speakers in that range came up as dynamic members. Bad subnets, and a range on an IP neighbor, are rejected on save.
Redmine: https://redmine.pfsense.org/issues/17074