>> I'm probably missing something -- but where in the HNCP document does it
>> say that applied prefixes must be announced over the routing protocol?
>> I don't see it in Section 6.3.3.
> I'd say the role of HNCP and the routing protocol and what does what, is
> not really specified anywhere.
HNCP does specify when the router MUST speak RA and DHCPv4, and SHOULD
speak DHCPv6-PD, so I'd expect it to have similar requirements for
routing. It doesn't make a lot of sense to send RAs or perform prefix
delegation if you're not going to announce the prefix over the routing
protocol.
Markus, Stephen -- it's too late to change that, right? If so, no big
deal, we'll put it in the Homenet profile for Babel.
> Otoh, it's very natural for me that a routing protocol would do
> "redistribute connected" or at least do this for interfaces marked as
> "HNCP". From my testing before on the actual OpenWRT implementations as
> they are configured out of the box as I tested them, it seemed babel was
> doing "redistribute connected" for all interfaces,
The OpenWRT hnetd configuration redistributes everything, indeed. The
recommended shncpd configuration redistributes just hncpd routes:
redistribute local deny
redistribute proto 43 allow
("redistribute proto 43" is shncpd, "redistribute local" is locally
assigned addresses.)
(I'll go out on a limb, and argue that it's not HNCP's business to say
what the routing protocol does with non-Homenet routes -- it's hopefully
legal for a Homenet router to redistribute, say, RIPng into Babel --, so
both implementations are correct.)
-- Juliusz
___
homenet mailing list
homenet@ietf.org
https://www.ietf.org/mailman/listinfo/homenet
