On Thu, May 31, 2018 at 11:12:38AM +, Job Snijders wrote:
> On Wed, May 30, 2018 at 03:18:45PM +0200, Claudio Jeker wrote:
> > This adds a protection to handle aspaths overly large attributes in
> > bgpd. The main idea is to protect other bgp routes downstream for
> > hitting the limit with is
On Wed, May 30, 2018 at 03:18:45PM +0200, Claudio Jeker wrote:
> This adds a protection to handle aspaths overly large attributes in
> bgpd. The main idea is to protect other bgp routes downstream for
> hitting the limit with is often not well catched.
I am not sure this is sound logic. The BGP UP
Claudio Jeker(cje...@diehard.n-r-g.com) on 2018.05.30 15:18:45 +0200:
> Hi,
>
> This adds a protection to handle aspaths overly large attributes in bgpd.
> The main idea is to protect other bgp routes downstream for hitting the
> limit with is often not well catched.
> The limit is currently a bi
Hi,
This adds a protection to handle aspaths overly large attributes in bgpd.
The main idea is to protect other bgp routes downstream for hitting the
limit with is often not well catched.
The limit is currently a bit arbitarily set to 4096 - 1024 which is afaik
the same limit that bird uses.
Whi
