Lucas Brasilino wrote:
So I suppose kernel frees that information after sending it to
userspace... right?
What information are you referring to?
The one you've said at your first reply: the information stored at
arp cache, ie, MAC <=> IP assigment.
Not at all. The arp cache in the kernel is still the source of the
linux IP stack IP<->MAC translation. Any memory used by that cache is
freed when the cache decides to do garbage collection, and thats
orthogonal to when it requests new IP<->ARP mappings. The sending of an
ARP solicitation is just something the kernel can do instead of sending
an ARP request out on the network. Think of a user space arp daemon as
being an L2 cache for MAC addresses to the kernels L1 cache (the real
ARP table).
I gonna sniff things around... I've never used netlink before.. just
common socket (and send/recv) syscall.. it's a good project to learn a
little more, since I really need an arp cache daemon. :)
John L. and I have been yapping about writing one as well. We'll post
if/when we get something good together.
Will this code CVS available ?
I've got a code here I wrote that implements a linked list API.
I'm wondering to use it to develop the arp cache... it's easy to use and
I think fits our needs.
It would be if we did it. Stephen Hemminger indicated to us however,
that the iproute2 utilities already contained a userspace ARP daemon, so
theres really no need for any of us to do this. You may want to check
that one out before building your own.
Neil
--
/***************************************************
*Neil Horman
*Software Engineer
*Red Hat, Inc.
*nhorman@xxxxxxxxxx
*gpg keyid: 1024D / 0x92A74FA1
*http://pgp.mit.edu
***************************************************/
-
: send the line "unsubscribe linux-net" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
