<div dir="ltr"><div class="gmail_extra"><br><div class="gmail_quote">On Wed, Nov 30, 2016 at 1:46 PM, Yisu Peng <span dir="ltr"><<a href="mailto:yisupeng@gmail.com" target="_blank">yisupeng@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">So, how is the kernel check
those staled arp entries? Or, what is the mechanism that the
kernel uses to find the out of date entries?</blockquote></div><br><div class="gmail_default" style="font-family:monospace,monospace">ok sure, well, each neighbor entry (struct neighbour) has a 'timer' (which is created during neighbor creation i.e. during neigh_alloc(...)). this timer gets 'serviced' by 'neigh_timer_handler(...)', which is the per neighbor garbage collector handler. </div><div class="gmail_default" style="font-family:monospace,monospace"><br></div><div class="gmail_default" style="font-family:monospace,monospace">when the state of the neighbor becomes NUD_FAILED, the neighbor is collected via invokation of 'neigh_release(...)' as indicated earlier.</div><br><div class="gmail_default" style="font-family:monospace,monospace">--</div><div class="gmail_default" style="font-family:monospace,monospace">kind regards</div><div class="gmail_default" style="font-family:monospace,monospace">anupam</div><br clear="all"><div><div class="gmail-m_-3442422875869384151gmail_signature"><div dir="ltr"><div><font face="monospace, monospace">In the beginning was the lambda, and the lambda was with Emacs, and Emacs was the lambda. </font></div></div></div></div>
</div></div>