> 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). - : 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
