Re: Trace routing path

Anton Danilov <[email protected]> Wed, 27 Feb 2019 12:45:49 +0000
Newsgroups org.kernel.vger.lartc
Message-ID <CAEzD07L5omdszxcNtNLSrMcPaidDXWCzRaHBChsB8Byjx4XJmg@mail.gmail.com>
Hello.
You can resolve the actual routes with 'ip route get' command.
Something like this: ip -d route get <dst> from <src> iif
<input-interface>. It will show the table number if table is not main.
ip route get command also supports the filrewall mark specifing (ip -d
route get <dst> fwmark <mark-value>).

On Wed, 27 Feb 2019 at 05:06, Leroy Tennison <[email protected]> wrote:
>
> iptables has the TRACE functionality to trace through netfilter's path of execution for a specified ruleset, is there a trace functionality for routing?  Something which would show if an alternate routing table handled the routing rather than main?
>
>
> Leroy Tennison
> Network Information/Cyber Security Specialist
> E: [email protected]
> 2220 Bush Dr
> McKinney, Texas
> 75070
> www.datavoiceint.com
> This message has been sent on behalf
> of a company that is part of the Harris Operating Group of
> Constellation Software Inc. These companies are listed
> here
> .
> If you prefer not to be contacted by Harris
> Operating Group
> please notify us
> .
> This message is intended exclusively for the
> individual or entity to which it is addressed. This communication
> may contain information that is proprietary, privileged or
> confidential or otherwise legally exempt from disclosure. If you are
> not the named addressee, you are not authorized to read, print,
> retain, copy or disseminate this message or any part of it. If you
> have received this message in error, please notify the sender
> immediately by e-mail and delete all copies of the
> message.
>


-- 
Anton.