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.
Yeah, I figured that one out. I use iproute2 to build my routing table,
but never thought of using it to trace route paths as the "old" route
was more convenient - to me anyway.
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.
Yeah, that helped - thank you both! I think I also found a little
discrepancy while executing "ip rule list <number>" (wrong syntax,
obviously) - it shows me "'ip rule show' does not take any arguments."
error message. Should that be ""ip rule list" does not take any
arguments." instead?
I am still curious though why the sorting order in the old "route" has
changed from one kernel version to the next?
--
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
