linux-admin.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Luca Ferrari <fluca1978@infinito.it>
To: linux-admin@vger.kernel.org
Subject: ip route refresh
Date: Fri, 30 Jul 2004 18:40:06 +0200	[thread overview]
Message-ID: <200407301840.06241.fluca1978@infinito.it> (raw)

Hi,
I've noted on different system that when an ip route changes, the kernel keeps 
the old one in a cache (I suppose) for a while. For example, if in 
you /etc/hosts you have an entry:
192.168.1.201 fluca fluca
and ping fluca it will try to connect to 192.168.1.201.
Now if you change the address and immediatly reping it, it will try again the 
old host for a while. After a minute the system should be able to use the new 
address. This also applies to routes.
Is there a way to force a cache-clear, thus modifications are immediatly 
visible?

Thanks,
Luca

-- 
Luca Ferrari,
fluca1978@infinito.it

             reply	other threads:[~2004-07-30 16:40 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-07-30 16:40 Luca Ferrari [this message]
2004-07-30 22:34 ` ip route refresh Glynn Clements
2004-07-31  8:13   ` Luca Ferrari
2004-07-31 17:28     ` urgrue
2004-08-01 20:48     ` Ahsan Ali
2004-08-02 12:10       ` Luca Ferrari
2004-08-06 11:20         ` Ahsan Ali

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=200407301840.06241.fluca1978@infinito.it \
    --to=fluca1978@infinito.it \
    --cc=linux-admin@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).