<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body style="overflow-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;"><div>Hi All,</div><div><br></div><div>I’m trying to implement a topology where multiple nodes have connections to one network. Let’s say there are three devices running babel:</div><div>A 10.0.0.1/24</div><div>B 10.0.0.2</div><div>C 10.0.0.3</div><div>and both B and C can route traffic to 10.1.0.0/16, and BIRD learns this route through the `kernel` protocol.</div><div><br></div><div>Now that both B and C announces 10.1.0.0/16 via babel, and it seems that BIRD does some kind of “first come first serve”, and A only sees the route via one of B or C.</div><div>Let’s say B comes online first and announces the route. Now C comes online. It doesn’t announce 10.1.0.0/16 to babel at all. The same behaviour is observed if I use ospf instead of babel.</div><div><br></div><div>My hypothesis is that when it synchronizes kernel with master4, it sees that 10.1.0.0/16 is already in master4 (<span style="caret-color: rgb(0, 0, 0); color: rgb(0, 0, 0);">announced by B)</span>, and so it doesn’t import this route from kernel to master4 at all(?)</div><div><br></div><div>What I am trying to do is to have both B and C announce this route, and let babel choose whether traffic from A for 10.1.0.0/16 should go to B or C based on its metric. Is this possible? or is it a really bad idea?</div><div><br></div><div>Thanks.</div>
<div><br></div>Best,<br>
<br><div>
<meta charset="UTF-8">Maiyun Zhang <font size="1">(he/him)</font>
</div>
<br></body></html>