On 2011-10-17 14:20, Marcin Mirosław wrote: > Hello, > i can't help you with "sorting problem" but i can see the real problem is > "i want to know which path will be used for given address ip". I suggest to > use iproute2, e.g.: ip r g <address_ip> > This is output: > # ip r g 4.5.6.7 > 4.5.6.7 via 88.198.102.193 dev eth0 src 88.198.102.195 To clarify, that's "ip route get <ip>". You can use shortcuts, but for examples for beginners that may not be wise. Another reason to use iproute2 ("ip") is that "route" is deprecated, and cannot display all of the things iproute2 now reveals. Such as multiple routes, metrics, or sources (such as from zebra/quagga). Finally, "ip rule" helps you to see policy routes like source-based routing. "route" cannot do any of that. Regards, Tyler -- "Never underestimate the bandwidth of a station wagon full of tapes hurtling down the highway. -- Andrew S. Tanenbaum -- To unsubscribe from this list: send the line "unsubscribe netfilter" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html