All of lore.kernel.org
 help / color / mirror / Atom feed
From: Julian Anastasov <ja@ssi.bg>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] ip routing problems in 2.4.20
Date: Tue, 06 May 2003 11:42:01 +0000	[thread overview]
Message-ID: <marc-lartc-105222147607115@msgid-missing> (raw)
In-Reply-To: <marc-lartc-105213310523718@msgid-missing>


	Hello,

On Tue, 6 May 2003, Ard van Breemen wrote:

> Eh, just curious in how arp depends on routing... I've already
> seen how neigh/gc_thresh[123] can influence the reachability of a
> host, and that the routing cache can lock entries in the neigh
> table while they are being flushed, filling up the neigh table
> etc...

	When ARP packet is received the ARP code uses "input routing"
lookup (which can return cached entry) to determine what IP is
resolved. The result can be "local delivery", "forward", etc
but there are additional conditions that determine whether we
reply to this probe. In short, ARP follows the IPv4 routing
with additional checks.

	In your case I assume we already have cached
entry and without flushing it we can not provide actual/valid
lookup result. The rule is that if you care, after adding new
route you have to flush the cache. After adding IP addresses the
flush is automatically performed from the kernel but it is not
true for the routes.

Regards

--
Julian Anastasov <ja@ssi.bg>

_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/

      parent reply	other threads:[~2003-05-06 11:42 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-05 11:09 [LARTC] ip routing problems in 2.4.20 Ard van Breemen
2003-05-05 11:21 ` ulrich schwarz
2003-05-05 12:28 ` Ard van Breemen
2003-05-05 21:07 ` Julian Anastasov
2003-05-06 10:52 ` Ard van Breemen
2003-05-06 11:42 ` Julian Anastasov [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=marc-lartc-105222147607115@msgid-missing \
    --to=ja@ssi.bg \
    --cc=lartc@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.