On 03/06/2017 12:40 PM, Dean wrote:
On 03/06/2017 12:10 PM, Toke Høiland-Jørgensen wrote:
Dean Luga writes:
Hmm, I have been running babeld with source-specific routes for quite
some time and never run into this problem. Are you sure you didn't
botch
the netlink calls? ;)
I don't thi
On 03/06/2017 12:10 PM, Toke Høiland-Jørgensen wrote:
Dean Luga writes:
Hmm, I have been running babeld with source-specific routes for quite
some time and never run into this problem. Are you sure you didn't botch
the netlink calls? ;)
I don't think so, I even tested inserting the rout
Dean Luga writes:
> Hmm, I have been running babeld with source-specific routes for quite
> some time and never run into this problem. Are you sure you didn't botch
> the netlink calls? ;)
>
> I don't think so, I even tested inserting the routes with ip route
> without running bird. It was a d
>
> Hmm, I have been running babeld with source-specific routes for quite
> some time and never run into this problem. Are you sure you didn't botch
> the netlink calls? ;)
I don't think so, I even tested inserting the routes with ip route without
running bird. It was a documented behavior in net
Dean writes:
> There is already an implementation for that here
> (https://github.com/jech/babeld), if you want to check. I think this supports
> both IPV6_SUBTREES and policy routing, not sure.
I meant for the Bird Babel implementation. And yeah, that was what I was
referring to with policy rou
There is already an implementation for that here
(https://github.com/jech/babeld), if you want to check. I think this
supports both IPV6_SUBTREES and policy routing, not sure.
And I encountered another problem with IPV6_SUBTREES yesterday. Having
source constrained routes and normal routes in
Dean writes:
> Static routes can be added in the configuration file with a source
>
> address constraint. To match an entry in the routing table, you have to
> match both the source and destination address. The same thing as running
> the command:
>
> ip -6 route add 2001:db9:1::/64 from 2001:db9
On Sun, Mar 05, 2017 at 09:21:43PM +0100, Dean wrote:
> About the patch: it might be a little long, about 60 commits. And I
> started working last year, on BIRD 1.6.2, so some things might be
> different. Should I still just send each commit one by one here?
Generally, commits that are series of w
Static routes can be added in the configuration file with a source
address constraint. To match an entry in the routing table, you have to
match both the source and destination address. The same thing as running
the command:
ip -6 route add 2001:db9:1::/64 from 2001:db9:2::/64 dev eth0
Meaning
On Sun, Mar 05, 2017 at 07:39:57PM +0100, Dean wrote:
> Hello,
>
> I have been working on implementing SADR (Source Address Dependent Routing)
> in BIRD for the static and OSPFv3 protocols.
Interesting. How it works?
> What's the procedure for publishing the code? Should I put it on a
> reposito
Hello,
I have been working on implementing SADR (Source Address Dependent
Routing) in BIRD for the static and OSPFv3 protocols.
What's the procedure for publishing the code? Should I put it on a
repository online and send you a link?
Regards,
Dean
11 matches
Mail list logo
