From mboxrd@z Thu Jan 1 00:00:00 1970 From: Luca Ferrari Subject: Re: ip route refresh Date: Mon, 2 Aug 2004 14:10:27 +0200 Sender: linux-admin-owner@vger.kernel.org Message-ID: <200408021410.27425.fluca1978@infinito.it> References: <200407301840.06241.fluca1978@infinito.it> <200407311013.07001.fluca1978@infinito.it> <17daa85604080113482e90364b@mail.gmail.com> Reply-To: fluca1978@infinito.it Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <17daa85604080113482e90364b@mail.gmail.com> Content-Disposition: inline List-Id: Content-Type: text/plain; charset="us-ascii" To: linux-admin@vger.kernel.org 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