All of lore.kernel.org
 help / color / mirror / Atom feed
From: Luca Ferrari <fluca1978@infinito.it>
To: linux-admin@vger.kernel.org
Subject: Re: ip route refresh
Date: Mon, 2 Aug 2004 14:10:27 +0200	[thread overview]
Message-ID: <200408021410.27425.fluca1978@infinito.it> (raw)
In-Reply-To: <17daa85604080113482e90364b@mail.gmail.com>

On Sunday 01 August 2004 22:48 Ahsan Ali's cat walking on the keyboard  wrote:

> Can you give some specific examples?
>
> I use linux extensively for routing and have never come across this.
>
> Show us exactly what you're doing and the route tables when you do it.

Well, I've noticed it first when I changed my router policies. From a computer 
I was telnetting a remote host on another subnet. The subnet was reached thru 
a Linux gateway connected to two routers (call them R1 and R2). In a first 
test R2 was down, so all the traffic was traveling over R1. When R2 was up, 
the traffic to the above subnet was redirected to the R2 router (i.e., I 
changed the 'route' policy of the gateway). Nevertheless, for a couple of 
minutes the traffic was going over R1.
Another issue I've noticed was an error on the /etc/hosts (different machine): 
I wrongly wrote  the address of an host, thus pinging it was a real ping to 
another machine. I correct the entry and re-do ping, but it was still pinging 
the wrong host. After a minute everything was working fine, but immediately 
it was not. I believe it could be an arp cache problem, as you suggested me.
Thanks,
Luca
-- 
Luca Ferrari,
fluca1978@infinito.it

  reply	other threads:[~2004-08-02 12:10 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
2004-08-01 20:48     ` Ahsan Ali
2004-08-02 12:10       ` Luca Ferrari [this message]
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=200408021410.27425.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 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.