Comments

Currently it is possible to do just about everything with the arp table
from user space except treat an entry like you are using it. To that end
implement and a flag NTF_USE that when set in a netwlink update request
treats the neighbour table entry like the kernel does on the output path.
This allows user space applications to share the kernel's arp cache.
Signed-off-by: Eric Biederman <ebiederm@aristanetworks.com>
---
include/linux/neighbour.h | 1 +
net/core/neighbour.c | 6 +++++-
2 files changed, 6 insertions(+), 1 deletions(-)

From: ebiederm@xmission.com (Eric W. Biederman)
Date: Fri, 20 Feb 2009 12:23:43 -0800
> > Currently it is possible to do just about everything with the arp table> from user space except treat an entry like you are using it. To that end> implement and a flag NTF_USE that when set in a netwlink update request> treats the neighbour table entry like the kernel does on the output path.> > This allows user space applications to share the kernel's arp cache.> > Signed-off-by: Eric Biederman <ebiederm@aristanetworks.com>
Ok, no objections from me.
I'll apply this to net-next-2.6, thanks.
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html

David Miller <davem@davemloft.net> writes:
> Ok, no objections from me.>> I'll apply this to net-next-2.6, thanks.
Thanks
Eric
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html