From: David Ahern <dsahern@gmail.com>
To: Hangbin Liu <liuhangbin@gmail.com>, David Ahern <dsahern@kernel.org>
Cc: davem@davemloft.net, netdev@vger.kernel.org
Subject: Re: [PATCH net] selftests: fib_rule_tests: Fix icmp proto with ipv6
Date: Tue, 30 Apr 2019 12:00:46 -0600 [thread overview]
Message-ID: <dac5b0ed-fa7e-1723-0067-6c607825ec31@gmail.com> (raw)
In-Reply-To: <20190430023740.GJ18865@dhcp-12-139.nay.redhat.com>
On 4/29/19 8:37 PM, Hangbin Liu wrote:
> An other issue is The IPv4 rule 'from iif' check test failed while IPv6
> passed. I haven't found out the reason yet.
>
> # ip -netns testns rule add from 192.51.100.3 iif dummy0 table 100
> # ip -netns testns route get 192.51.100.2 from 192.51.100.3 iif dummy0
> RTNETLINK answers: No route to host
>
> TEST: rule4 check: from 192.51.100.3 iif dummy0 [FAIL]
>
> # ip -netns testns -6 rule add from 2001:db8:1::3 iif dummy0 table 100
> # ip -netns testns -6 route get 2001:db8:1::2 from 2001:db8:1::3 iif dummy0
> 2001:db8:1::2 via 2001:db8:1::2 dev dummy0 table 100 metric 1024 iif dummy0 pref medium
>
> TEST: rule6 check: from 2001:db8:1::3 iif dummy0 [ OK ]
use perf to look at the fib lookup parameters:
perf record -e fib:* -- ip -netns testns route get 192.51.100.2 from
192.51.100.3 iif dummy0
perf script
next prev parent reply other threads:[~2019-04-30 18:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-29 17:30 [PATCH net] selftests: fib_rule_tests: Fix icmp proto with ipv6 David Ahern
2019-04-30 2:37 ` Hangbin Liu
2019-04-30 18:00 ` David Ahern [this message]
2019-05-07 8:20 ` Hangbin Liu
2019-05-08 19:38 ` David Ahern
2019-05-01 15:31 ` 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=dac5b0ed-fa7e-1723-0067-6c607825ec31@gmail.com \
--to=dsahern@gmail.com \
--cc=davem@davemloft.net \
--cc=dsahern@kernel.org \
--cc=liuhangbin@gmail.com \
--cc=netdev@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).