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. -Ahsan On Sat, 31 Jul 2004 10:13:06 +0200, Luca Ferrari <fluca1978@xxxxxxxxxxx> wrote: > On Saturday 31 July 2004 00:34 Glynn Clements's cat walking on the keyboard > wrote: > > > Luca Ferrari wrote: > > > 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? > > > > 1. What does this have to do with routing? Unless I'm misunderstanding > > the above, this is a name-service issue. > > > > 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). > > > 2. Are you using nscd? If so, try "/etc/rc.d/init.d/nscd restart". > > No, I'm not using it. > > > > Thanks, > Luca > > -- > Luca Ferrari, > fluca1978@xxxxxxxxxxx > - > : send the line "unsubscribe linux-admin" in > the body of a message to majordomo@xxxxxxxxxxxxxxx > More majordomo info at http://vger.kernel.org/majordomo-info.html > - : send the line "unsubscribe linux-admin" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
