Hi,
as of my understanding ports for BFD session are not ephemeral; the port
is chosen statically when the daemon spawns (and even survives lost BFD
sessions).
Further, there is no RFC known to me that requests limitations on usable
port ranges for arbitrary outgoing connections in general--
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. ""; how
> 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 arbitra
