Kernel protocol and different namespaces

[Maria Jan Matějka]

What about having the veth's in separate VRF's inside the netns's?

Do you need the full BGP features on the Unix socket, or just a pipe-like transport? Not promising now that I'll implement it soon, just trying to define the feature request, yet it should be quite easy to create. 

Maria

On June 7, 2019 6:00:14 PM GMT+02:00, Alexander Zubkov <green at qrator.net> wrote:
>On Fri, Jun 7, 2019 at 5:44 PM Toke Høiland-Jørgensen <toke at toke.dk>
>wrote:
>>
>> Alexander Zubkov <green at qrator.net> writes:
>>
>> > Hello,
>> >
>> > We want to use bird with different namespaces too, but proposed
>> > changes is not an option for us anyway because of somewhat
>proprietary
>> > kernel we are working with (there are some missing definitions for
>> > namespaces in headers and vanilla does not fit). So we are also
>> > thinking about several instances of bird as Maria Jan Matějka
>> > suggests. But we need to find some way to interconnect them. But we
>> > think creating a veth interface is not a best option for us.
>>
>> Why not?
>
>We do not want direct routing between namespaces. And also add some
>additional interfaces - it is a hardware switch, so it could disturb
>something. But may be not. This could be an option too. I just wrote
>that it could be not the best one. We have not tested yet, just
>considering possibilities.
>
>>
>> -Toke

-- 
Sent from my Android device with K-9 Mail. Please excuse my brevity.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://trubka.network.cz/pipermail/bird-users/attachments/20190607/4bc0887f/attachment.htm>