network: Don't report deletion of cloned routes
authorRoy Marples <roy@marples.name>
Fri, 20 Sep 2019 09:09:46 +0000 (10:09 +0100)
committerRoy Marples <roy@marples.name>
Fri, 20 Sep 2019 09:09:46 +0000 (10:09 +0100)
commit4f4fafdebd80f00d3b2ae991d8e6b61b969c314c
tree608740c14b7380ddcab5f5b47da550446945ed81
parentcc382966241c52d6f74d7229a5aa87b61bd3b1e0
network: Don't report deletion of cloned routes

ARP and ND6 expiration works around one big timer vs timers
per address. As such, when expiry happens a flood of RTM_DELETE
messages can easily overflow the route(4) socket.

Now that RTM_MISS is reported for any unresolvable address via
these protocols, the reporting of the address expiring or being
maually deleted becomes questionable for any use cases pertaining
to it.

If we do want to report this in the future, we should move to
per address timers rather than one big timer.
sys/netinet/if_ether.c
sys/netinet6/nd6.c