Bird 2 config syntax

[Douglas Fischer]

I'm not sure if that is the motivation on Bird...

But I think it could be related the fact that the protocolo that is used to
transport BGP Sessions does not defines protocols of the routes that are
being exchanged.
You cloud use a BGP session in v6 to exchange v6 routes, v4 routes or even
both.
The same is true if you are using a BGP session over v4.


Em ter., 21 de set. de 2021 às 10:26, Robert Sander <
r.sander at heinlein-support.de> escreveu:

> Hi,
>
> 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.
>
> Regards
> --
> Robert Sander
> Heinlein Consulting GmbH
> Schwedter Str. 8/9b, 10119 Berlin
>
> http://www.heinlein-support.de
>
> Tel: 030 / 405051-43
> Fax: 030 / 405051-19
>
> Zwangsangaben lt. §35a GmbHG:
> HRB 220009 B / Amtsgericht Berlin-Charlottenburg,
> Geschäftsführer: Peer Heinlein -- Sitz: Berlin
>


-- 
Douglas Fernando Fischer
Engº de Controle e Automação
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://trubka.network.cz/pipermail/bird-users/attachments/20210921/28a3a7aa/attachment.htm>