On Thu, Mar 09, 2017 at 05:36:54PM +0200, Lennert Buytenhek wrote:
> > Well, the simple way to avoid reconfiguration in this case is just to move
> > 'remote_as2' field at the end of bgp_config, like 'check_link' or 'bfd'.
>
> Well, e.g. if remote_as is 12345 and the currently established peer AS
On Thu, Mar 09, 2017 at 04:23:05PM +0100, Ondrej Zajicek wrote:
> > If we are using the secondary remote AS mechanism, we don't necessarily
> > need to restart an already established BGP connection if the remote AS
> > for a BGP session changes, as long as the AS number that the peer is
> > curren
On Thu, Mar 09, 2017 at 04:30:55PM +0200, Lennert Buytenhek wrote:
> If we are using the secondary remote AS mechanism, we don't necessarily
> need to restart an already established BGP connection if the remote AS
> for a BGP session changes, as long as the AS number that the peer is
> currently co
If we are using the secondary remote AS mechanism, we don't necessarily
need to restart an already established BGP connection if the remote AS
for a BGP session changes, as long as the AS number that the peer is
currently connected with is still in the list of AS numbers that we
accept from the pee
