rbil.net]
> Sent: Saturday, May 06, 2017 1:17 PM
> To: Jakob Heitz (jheitz)
> Cc: Robert Raszuk ; grow@ietf.org
> Subject: Re: [GROW] [Idr] IETF LC for IDR-ish document
> (Default EBGP Route
> Propagation Behavior Without Policies) to Proposed Standard
>
> On Fri, May 0
On Fri, May 05, 2017 at 10:51:41PM +, Jakob Heitz (jheitz) wrote:
> Thanks Robert.
>
> I did it without using ios-regex or other time consuming string conversion
> stuff.
> Still, this method cannot scale to cover every one of several thousand AS
> neighbors that some ISPs have.
> IOS cannot
IETF LC for IDR-ish document
(Default EBGP Route Propagation Behavior
Without Policies) to Proposed Standard
Hi Jakob,
This is really great and exactly what I had in mind when proposed auto-policy
based on AS_PATH check. Can you commit it to IOS so it is build-in with a knob
to use ?
Cheer
Hi Jakob,
This is really great and exactly what I had in mind when proposed
auto-policy based on AS_PATH check. Can you commit it to IOS so it is
build-in with a knob to use ?
Cheers,
R.
On Sat, May 6, 2017 at 12:09 AM, Jakob Heitz (jheitz)
wrote:
> Even if violating router-os's are updated, l
Even if violating router-os's are updated, leaks will continue for a long time.
I hope I can help on the filtering side. No RFC or vendor code change required.
I wrote an app in C that takes the output of "show bgp" and creates
a set of route-policies that will prevent the leaks.
It looks at the a
