> > Hello! > > > > 1. CONFIG_ARPD > > > 2. echo 1 > /proc/sys/net/ipv4/neigh/<dev>/app_solicit > > > > > > > > > After this arp changes are reported to group RTMGRP_NEIGH. > > Not quite true, actually. It does not track expired entries. > The absence of an entry is detected only after it is requested again. > So, this thing is for user space resolution, not for monitoring. > > The absense of facility to monitor ARP tables is intentional. > Do you want to see what is there right now, dump. If you are not going > to help with resolution, content of highly dynmaic table is of no use for you. > Can you elaborate a little more ? I'm not sure why routing table and arp table should be treated differently. Each of the tables can have many thousands entries and both of them can be highly dynamic. - Jacob > Alexey > - : send the line "unsubscribe linux-net" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
