Hi all,
Is there anyone else running these COVR-C1213 (3x nodes) with COVR A in bridge mode, and wired backhaul?
I have observed a bit of "network spam" emanating from the D-Link COVR A unit.
Check this out:

* COVRA == 10.0.0.25
* misc devices == 10.0.0.X
This isn't in of itself "abnormal", it is reasonable for a device to ask for L2 MAC addresses for a given L3 target. (and to do so it sends an ARP broadcast request)
HOWEVER, what makes it unusual, is that these devices ARE in fact replying to the COVR unit, saying "here I am!", but the COVR unit ignores it and keeps asking again and again

...
Here's an isolated sequence with one client (also the one taking the packet capture):

What's ultimately worse about all of this, is that these devices are mostly on the wired-side of the network ... so why does the D-Link COVR unit even need to know about these devices all the time? And even if there is a reason, once it gets the ARP responses -- that should be the end of the chatter -- yet it continues.
I have contacted D-Link support about this, and they claim this is "normal" -- but I know it as a fact this is not good network device behaviour. (I've been in the networking industry/field for >15 years, and never seen a device behave like this -- and -- from what I know of the ARP protocol, this is not correct anyway);
Hoping to get feedback on this. Either "me too" or "same config but not happening to me", or "yes you are right this is wrong" or "actually this is fine/ok".