linux-admin.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: urgrue <urgrue@tumsan.fi>
To: Luca Ferrari <fluca1978@infinito.it>
Cc: linux-admin@vger.kernel.org
Subject: Re: ip route refresh
Date: Sat, 31 Jul 2004 20:28:54 +0300	[thread overview]
Message-ID: <20040731172854.GA751@cow2.intra.tumsan.fi> (raw)
In-Reply-To: <200407311013.07001.fluca1978@infinito.it>

> No, it's not, since I've experienced it also using direct addresses. I mean, 
> if you ping 192.168.1.201 the packets will follow a particular way. If you 
> change your kernel route (thru 'route') and try to ping immediately the same 
> host, the pakets will try to reach the host with the same way (if it is still 
> valid). 

Nevertheless these are two different mechanisms and two different "caches"
we're talking about. What route a packet takes is decided by a completely
different system as what IP an address maps to. iptables also has a kind of
"cache" but that doesn't mean it has anything to with /etc/hosts or routing.

For routes, try "ip route flush table cache" (this is from memory, but it
was something like that).

For name services, nscd is the only thing i can think of that might cause
the behaviour you described (/etc/hosts change not taking immediate effect).


  reply	other threads:[~2004-07-31 17:28 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-07-30 16:40 ip route refresh Luca Ferrari
2004-07-30 22:34 ` Glynn Clements
2004-07-31  8:13   ` Luca Ferrari
2004-07-31 17:28     ` urgrue [this message]
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=20040731172854.GA751@cow2.intra.tumsan.fi \
    --to=urgrue@tumsan.fi \
    --cc=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).