> That is true, but it is not limited to BGP peers, it also affects other
> issues like next hop validation. Unfortunately it is not easily fixable.
> It would require redesigning whole internal neighbor processing, which
> is something that we plan to do, but there are currently tasks with
>
On Wed, Feb 16, 2022 at 03:32:55AM +0100, Arsen Arsenović wrote:
> Good evening!
>
> When configuring BGP on a site BIRD fails to recognize whether an IP is
> directly connected. It appears to scan over the list of interfaces and
> check whether their subnets contain the target IP instead of
On Thu, Feb 17, 2022 at 01:09:33PM +0100, Christian Bruns wrote:
> Hi all,
>
> we experienced issues with non-functional BFD Sessions. Debugging yielded
> that bird does not use RFC compliant BFD Port ranges.
> RFC 5881 states: "" The source port MUST be in the range 49152 through
> 65535. "";
> On 17. Feb 2022, at 13:09, Christian Bruns wrote:
>
> providers like "Deutsche Telekom" apply strict filter for BFD and only allow
> RFC5881 compliant ports,
Hahaha ... *tips hat to Rüdiger Volk¹ in retirement*
¹) Oh! Just saw him on the Onsite registrant list for IETF-113 in Wien next
Hi all,
we experienced issues with non-functional BFD Sessions. Debugging
yielded that bird does not use RFC compliant BFD Port ranges.
RFC 5881 states: "" The source port MUST be in the range 49152 through
65535. ""; however, the port range is not restricted within bird and
thus using
