On Fri, Jul 20, 2018 at 12:47:35PM +0800, Antonio Quartulli wrote:
Unless somebody has any objection, I think we could consider as such also the "source IP/MAC" in an ARP request and apply the same logic.
Hrm, one potential downside just came to my mind...
A gateway for instance will frequently generate ARP Requests for various addresses. Sending a message to the three, poor nodes that happen to be the DAT candidates for the gateway IP might create a significant amount of messages to these nodes if we were triggering that for each ARP Request... And all those unicast messages would basically be redundant as the gateway IP/MAC pair will already be well populated in the DAT.
One solution would be to introduce rate limiting for global DAT cache updates... So basically introducing a third timeout for a DAT entry, next to the global and local DAT cache timeout split.