Somewhat related to this, I wrote this patchset last year: http://trubka.network.cz/pipermail/bird-users/2017-March/thread.html#11084 The idea was to let you configure two AS numbers that a remote peer can connect to us with, so that the remote peer can be reconfigured to use a different AS number without the local machine needing to reconfigured at the same time. (The converse case, where the local machine will reconnect with a secondary AS number if connecting with the primary AS number fails is more involved, and in my use case, I control both endpoints anyway, so this was sufficient.) If there's interest in this patchset I can dust it off and try resubmitting it. On Sun, Feb 18, 2018 at 01:25:37PM +0000, 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/...
I know it can be achieved by functions, but maybe there is already simplier way to get this done.
Best regards, Adam Król