<html><head></head><body>Thinking once more about it, with respect to the interfaces and so, the BGP transported over Unix socket seems to be quite simple feature to do.<br><br>I'll see what can be done with that.<br><br>Maria<br><br><div class="gmail_quote">On June 7, 2019 8:06:30 PM GMT+02:00, Alexander Zubkov <green@qrator.net> wrote:<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<pre class="k9mail">I'm not sure right now that its kernel supports vrf. Anyway, I know<br>there are some ways to connect them in terms of its current<br>possibilities. And we will do it one way or another. I just wanted to<br>propose a feature that could make such setups easier and probably is<br>not too hard to implement and does not brake internal things. I would<br>be also glad to hear from Jakub if it will help him too.<br>Of course bgp is not the only option here, it is just the most<br>familiar to me as a prtocol working over a stream socket and that<br>would keep communities etc. Pipe would be fine too, but it does not<br>have "on the wire representation" now, I suppose. And I am not sure<br>about things like - when the route is received, it is checked with<br>local interfaces etc. I think pipe skips most of this stuff. But I'm<br>not familiar with the internals of bird, just assuming what pros and<br>cons could be.<br><br>On Fri, Jun 7, 2019 at 7:21 PM Maria Jan Matějka <jan.matejka@nic.cz> wrote:<br><blockquote class="gmail_quote" style="margin: 0pt 0pt 1ex 0.8ex; border-left: 1px solid #729fcf; padding-left: 1ex;"><br> What about having the veth's in separate VRF's inside the netns's?<br><br> 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.<br><br> Maria<br><br> On June 7, 2019 6:00:14 PM GMT+02:00, Alexander Zubkov <green@qrator.net> wrote:<br><blockquote class="gmail_quote" style="margin: 0pt 0pt 1ex 0.8ex; border-left: 1px solid #ad7fa8; padding-left: 1ex;"><br> On Fri, Jun 7, 2019 at 5:44 PM Toke Høiland-Jørgensen <toke@toke.dk> wrote:<br><blockquote class="gmail_quote" style="margin: 0pt 0pt 1ex 0.8ex; border-left: 1px solid #8ae234; padding-left: 1ex;"><br><br> Alexander Zubkov <green@qrator.net> writes:<br><br><blockquote class="gmail_quote" style="margin: 0pt 0pt 1ex 0.8ex; border-left: 1px solid #fcaf3e; padding-left: 1ex;"> Hello,<br><br> We want to use bird with different namespaces too, but proposed<br> changes is not an option for us anyway because of somewhat proprietary<br> kernel we are working with (there are some missing definitions for<br> namespaces in headers and vanilla does not fit). So we are also<br> thinking about several instances of bird as Maria Jan Matějka<br> suggests. But we need to find some way to interconnect them. But we<br> think creating a veth interface is not a best option for us.<br></blockquote><br><br> Why not?<br></blockquote><br><br> We do not want direct routing between namespaces. And also add some<br> additional interfaces - it is a hardware switch, so it could disturb<br> something. But may be not. This could be an option too. I just wrote<br> that it could be not the best one. We have not tested yet, just<br> considering possibilities.<br><br><blockquote class="gmail_quote" style="margin: 0pt 0pt 1ex 0.8ex; border-left: 1px solid #8ae234; padding-left: 1ex;"><br> -Toke<br></blockquote></blockquote><br><br> --<br> Sent from my Android device with K-9 Mail. Please excuse my brevity.<br></blockquote></pre></blockquote></div><br>-- <br>Sent from my Android device with K-9 Mail. Please excuse my brevity.</body></html>