Bird 2.0.0 and reconfiguring

Miłosz Oller milosz at sys-com.pl
Sun Dec 17 23:15:05 CET 2017


There is no way to setup two channels in one protocol definition? Or how 
can I do it?


inż. Miłosz Oller


W dniu 17.12.2017 o 21:55, Ondrej Zajicek pisze:
> On Sun, Dec 17, 2017 at 01:41:44PM +0100, Miłosz Oller wrote:
>> Hi
>>
>> How I must define bgp protocol as case 1?
>>
>> There can be only one source/neighbor ip.
> In case 1 there is only one BGP session / TCP connection and therefore one source/neighbor address.
>
>> W dniu 17.12.2017 o 03:26, Ondrej Zajicek pisze:
>>
>>> On Sat, Dec 16, 2017 at 04:25:50PM +0100, Miłosz Oller wrote:
>>>> Hi
>>>>
>>>> I fix it. Please tell me how I must define ipv6 session. There must be two
>>>> bgp protocols definitions?
>>> Hi
>>>
>>> That depends if yo want one BGP session with both ipv4 and ipv6 AFIs, or
>>> two independent BGP sessions, each for one AFI (like it was done with old
>>> BIRD).
>>>
>>> For the first case you need just one protocol (like in your example). For
>>> the second case (which is drop-in replacement for old BIRD) you have to
>>> define two BGP protocols, each with appropriate channel and
>>> neighbor/source addresses.
>>>
>>>
>>> Case 1:
>>>
>>>> protocol bgp bgp_cloudflare_waw {
>>>>       description "Cloudflare OpenPeering";
>>>> ipv4 { import all;
>>>>        export filter ipv4_export;
>>>> };
>>>> ipv6 { import all;
>>>>       export filter ipv6_export;
>>>> };
>>>>       local as 198611;
>>>>       neighbor 212.91.0.28 as 13335;
>>>>       source address 212.91.1.42;
>>>>    #   neighbor 2001:7f8:69::83 as 13335;
>>>> #    source address 2001:7f8:69::256;
>>>> }
>>> Case 2:
>>>
>>>> protocol bgp bgp_cloudflare_waw_4 {
>>>>       description "Cloudflare OpenPeering";
>>>>       ipv4 { import all;
>>>>           export filter ipv4_export;
>>>>       };
>>>>       local as 198611;
>>>>       neighbor 212.91.0.28 as 13335;
>>>>       source address 212.91.1.42;
>>>> }
>>>>
>>>> protocol bgp bgp_cloudflare_waw_6 {
>>>>       description "Cloudflare OpenPeering";
>>>>       ipv6 { import all;
>>>>           export filter ipv6_export;
>>>>       };
>>>>       local as 198611;
>>>>       neighbor 2001:7f8:69::83 as 13335;
>>>>       source address 2001:7f8:69::256;
>>>> }
>>
>
>


-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 4262 bytes
Desc: Kryptograficzna sygnatura S/MIME
URL: <http://trubka.network.cz/pipermail/bird-users/attachments/20171217/f2aa7b26/attachment.p7s>


More information about the Bird-users mailing list