On Fri, Mar 10, 2017 at 05:19:11PM +0200, Lennert Buytenhek wrote:
> On Thu, Mar 09, 2017 at 05:53:51PM +0100, Ondrej Zajicek wrote:
>
> > > This patch implements the latter option, and this functionality is
> > > enabled by specifying two different remote AS numbers for a peer in
> > > the neighb
I don't know how I got on this email list. Please remove me.
From: Bird-users on behalf of Lennert Buytenhek
Sent: Friday, March 10, 2017 8:39:37 AM
To: Ondrej Zajicek
Cc: bird-users@network.cz; David Barroso
Subject: Re: [PATCH,RFC 1/3] BGP: Impl
On Fri, Mar 10, 2017 at 05:19:11PM +0200, Lennert Buytenhek wrote:
> * If rr_client is configured, both remote_as and remote_as2 must
> indicate eBGP (or remote_as must indicate eBGP and remote_as2 must
> not be set).
>
> * If rs_client is configured, both remote_as and remote_as2 must
> in
On Thu, Mar 09, 2017 at 05:53:51PM +0100, Ondrej Zajicek wrote:
> > This patch implements the latter option, and this functionality is
> > enabled by specifying two different remote AS numbers for a peer in
> > the neighbor statement. Instead of specifying:
> >
> > neighbor 1.2.3.4 as 12345;
On Thu, Mar 09, 2017 at 04:29:40PM +0200, Lennert Buytenhek wrote:
> This patch implements the latter option, and this functionality is
> enabled by specifying two different remote AS numbers for a peer in
> the neighbor statement. Instead of specifying:
>
> neighbor 1.2.3.4 as 12345;
>
>
When carrying out a BGP topology migration such as an AS renumbering
or an AS merge, which involves changing the local AS being reported
by one or both ends of a BGP session, being able to avoid the need
to reconfigure both peers at the same time can significantly reduce
the complexity of such a mi
