Re: [B.A.T.M.A.N.] Migration to Batman

Mitar
2012-04-13T07:58:26Z

Hi!

On Fri, Apr 13, 2012 at 7:59 AM, Andrew Lunn <andrew@lunn.ch> wrote:
> This comes back to:
>
>     You need, in your head, a clear separation between L3 and L2.

:-)

OK, maybe I am getting a bit of hold on this. :-)

OK, so if we would like to provide a way for all nodes to also
announce their L3 subnets which are maybe behind them, we should run
additional L3 routing protocol between them so that they can exchange
information about those subnets and configure routes accordingly.
Which routing protocol are you proposing for such task? If I
understand it can be a really simple one, checking just when a node is
accessible and setting its announcements on all other nodes. There is
no need to think about link quality or anything else. If node is
accessible, set routes for its announced subnets to it. OK, one need
we would like is that it provides some routing filtering capabilities.
So that we could for example forbid to announce anything from
192.168/16. How does such protocol determine node availability?

Mitar