On Feb 18, Ondrej Zajicek wrote:
> When route is exported to a BGP peer, BIRD prepends ASN based on ASN of
> exporting BGP protocol instance. Therefore, only one ASN is prepended to
> AS path automatically. If you want to have both AS numbers in AS path,
> you would have to use filters.
This is n
On Sun, Feb 18, 2018 at 05:00:36PM +, Adam Król wrote:
> Is there any description how does AS path look like in that kind of
> configuration?
>
> Let's consider that scheme:
>
> PEER A<-> ISP (bird - one instance) <->
> PEER B
> AS 65499 <-> A
Is there any description how does AS path look like in that kind of
configuration?
Let's consider that scheme:
PEER A <-> ISP (bird - one instance) <-> PEER B
AS 65499<-> AS 65505 AS 65510<-> AS 65496
How side A see side B? B
On Feb 18, Alarig Le Lay wrote:
> You can choose the local AS on each BGP protocol instance, is it
> sufficient?
No, because this still required coordinating the exact time of the AS
change with each neighbor.
--
ciao,
Marco
signature.asc
Description: PGP signature
On dim. 18 févr. 13:25:37 2018, Adam Król wrote:
> Does BIRD have any support for AS migration mechanism as mentioned in
> RFC7705 https://tools.ietf.org/html/rfc7705? Something like
> https://www.cisco.com/c/en/us/td/docs/ios-xml/ios/iproute_bgp/configuration/xe-16/irg-xe-16-book/bgp-support-for-d
Does BIRD have any support for AS migration mechanism as mentioned in RFC7705
https://tools.ietf.org/html/rfc7705? Something like
https://www.cisco.com/c/en/us/td/docs/ios-xml/ios/iproute_bgp/configuration/xe-16/irg-xe-16-book/bgp-support-for-dual-as-configuration-for-network-as-migrations.html?
