All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Tyler J. Wagner" <tyler@tolaris.com>
To: "Marcin Mirosław" <marcin@mejor.pl>
Cc: Mr Dash Four <mr.dash.four@googlemail.com>, netfilter@vger.kernel.org
Subject: Re: route sorting
Date: Mon, 17 Oct 2011 16:07:09 +0100	[thread overview]
Message-ID: <4E9C449D.2060907@tolaris.com> (raw)
In-Reply-To: <4E9C2BA6.6030507@mejor.pl>

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

  reply	other threads:[~2011-10-17 15:07 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-17 12:22 route sorting Mr Dash Four
2011-10-17 13:20 ` Marcin Mirosław
2011-10-17 15:07   ` Tyler J. Wagner [this message]
2011-10-17 15:37     ` Mr Dash Four
2011-10-17 19:32       ` Jan Engelhardt
2011-10-17 21:41       ` David Miller

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4E9C449D.2060907@tolaris.com \
    --to=tyler@tolaris.com \
    --cc=marcin@mejor.pl \
    --cc=mr.dash.four@googlemail.com \
    --cc=netfilter@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.