Re: BGP Engines with support to "RTFilter address-family"

On Mon, 27 Feb 2023 at 22:20, Jeff Tantsura wrote: > FRR hasn’t implemented RFC4364 (nor planning to my knowledge (unless someone > comes and codes it ;-)) $ grep -P -r -i 'IANA_SAFI_.* = 1\d{2,}' frr frr/lib/iana_afi.h: IANA_SAFI_MPLS_VPN = 128, frr/lib/iana_afi.h: IANA_SAFI_FLOWSPEC = 133 No

Re: BGP Engines with support to "RTFilter address-family"

On Mon, 27 Feb 2023 at 22:20, Jeff Tantsura wrote: > FRR hasn’t implemented RFC4364 (nor planning to my knowledge (unless someone > comes and codes it ;-)) $ grep -P -r -i 'IANA_SAFI_.* = 1\d{2,}' frr frr/lib/iana_afi.h: IANA_SAFI_MPLS_VPN = 128, frr/lib/iana_afi.h: IANA_SAFI_FLOWSPEC = 133 No

Re: BGP Engines with support to "RTFilter address-family"

On Sun, 26 Feb 2023 at 21:48, Douglas Fischer wrote: > But I'm looking for an open-source engine that supports it. > > The official FRR documentation does not mention anything about RFC 4364, or > RTFilter address family. > So, I think FRR does not support RTFilter Constrained Route Distribution.

Re: AS9498 Bharti BGP hijacks

I would (from a peering perspective) see this as a configuration error where somebody/someone botched a configuration change in a specific network router. Partly because a) seeing as the reports is sequentially numbered, b) as - already pointed out - it is either /30 or /29. c) thou I'm puzzled ab