Re: [homenet] HNCP: interaction with routing protocol?

[Henning Rogge <[e-mail]>]

On Wed, Dec 16, 2015 at 6:31 PM, Juliusz Chroboczek
<[e-mail]> wrote:
>> hnetd does address configuration on interfaces, the routing protocol picks
>> this up because that's how it's configured...? Hnetd doesn't communicate
>> directly with the routing protocol at all, right? It just sets up the
>> landscape so the routing protocol can come and survey it and communicate
>> the contents.
>
> That's exactly right (and very well put).  That's what I tried to express
> in my talk at Prague -- it turns out that HNCP is a very clean design.
> (Except where it isn't, of course.)
>
> Hnetd and shncpd do that somewhat differently.  Hnetd assume that the
> routing protocol redistributes everything.  Shncpd has closer binding to
> the routing protocol, it marks its routes as "proto 43" and expects the
> routing protocol to redistribute just that; shncpd also occasionally
> inserts dummy "proto 43" routes into the kernel, just so that they get
> redistributed into the routing protocol.  The result is that shncpd
> produces somewhat cleaner (more aggregated) routing tables, at the cost of
> requiring special configuration of the routing protocol.

Just redistributing protocol 43 will also make you miss the default
route you get by DHCP from an uplink.

Henning Rogge