Henning Rogge <[email protected]> wrote: >> This solves the issue of unexpected routing pathologies (the Homenet node >> is participating in the native Homenet routing protocol, and hence doesn't >> introduce any new pathologies), as well as that of flash and RAM usage (the >> Nest node isn't running any new software). It does cause sub-optimal >> routing, though, unless the specialised node is at the right place in the >> network.
> If Homenet assume any "lightweight nodes" (e.g. a Nest node) speak IP,
> then using ICMP might be an easy way to do this.
Yes, ICMP exactly does it.
ICMP ND exactly. Traffic to the nexthop (likely a LL address) fails to
resolve with ND, and that causes the link to go down, and the route to be
withdrawn. This is exactly how it always works today.
--
Michael Richardson <[email protected]>, Sandelman Software Works
-= IPv6 IoT consulting =-
pgpDDxCudMYwk.pgp
Description: PGP signature
_______________________________________________ homenet mailing list [email protected] https://www.ietf.org/mailman/listinfo/homenet
