❦ 21 September 2021 15:23 +02, Robert Sander:
why is it not possible to define BGP sessions like this?
protocol bgp g60 { local as 64501; neighbor as 64499; ipv4 { import all; export all; }; local 192.0.2.4; neighbor 192.0.2.5; }; ipv6 { import all; export all; local 2001:db8::4; neighbor 2001:db8::5; }; };
It seems still necessary to write two bgp definitions separately for IPv4 and IPv6 repeating the AS numbers and name.
I see no benefit from the Bird 1.6 notation here.
With BIRD2, you can transport your IPv4 routes over an IPv6 BGP session. To not repeat stuff, you can use templates. -- Localise input and output in subroutines. - The Elements of Programming Style (Kernighan & Plauger)