It's behaviour is: Closest match first. So if you have a package for 10.10.10.10 and your routing table says: Destination Gateway Genmask Flags Metric Ref Use Iface 10.0.0.0 192.168.1.1 255.0.0.0 UH 0 0 0 eth0 10.10.0.0 172.16.16.16 255.255.0.0 UH 0 0 0 eth1 The second one would be picked. It fits the description and the netmask is 'tighter' than the fist one. If, though, it would be: Destination Gateway Genmask Flags Metric Ref Use Iface 10.0.0.0 192.168.1.1 255.0.0.0 UH 0 0 0 eth0 10.0.0.0 172.16.16.16 255.0.0.0 UH 1 0 0 eth0 and you would be using a routing daemon, the first would be used, for it has a lower metric (=distance). The kernel makes no use of the metric value so if you would not use a routing daemon... Anyone? Serge. -----Original Message----- From: Allan McIntosh [mailto:amcintosh@atreuscorp.com] Sent: donderdag 28 september 2000 21:32 To: Linux-Networking Subject: routing question... Hey, Does any one know the order that linux parses it's routing table? Meaning does it parse host entries then network entries? or is there an order? If you do a `route -n` or `netstat -rn` it is listed in order of hosts then network then default gw but is this how it is parsed? Al - : send the line "unsubscribe linux-net" in the body of a message to majordomo@vger.kernel.org - : send the line "unsubscribe linux-net" in the body of a message to majordomo@vger.kernel.org
