From: Stephen Hemminger <stephen@networkplumber.org>
To: netdev@vger.kernel.org
Subject: Fw: [Bug 207063] New: vrf route oif problem
Date: Thu, 2 Apr 2020 08:49:23 -0700 [thread overview]
Message-ID: <20200402084923.4233e2ed@hermes.lan> (raw)
Begin forwarded message:
Date: Thu, 02 Apr 2020 14:15:58 +0000
From: bugzilla-daemon@bugzilla.kernel.org
To: stephen@networkplumber.org
Subject: [Bug 207063] New: vrf route oif problem
https://bugzilla.kernel.org/show_bug.cgi?id=207063
Bug ID: 207063
Summary: vrf route oif problem
Product: Networking
Version: 2.5
Kernel Version: 5.5.11
Hardware: All
OS: Linux
Tree: Mainline
Status: NEW
Severity: normal
Priority: P1
Component: IPV4
Assignee: stephen@networkplumber.org
Reporter: 1455793380@qq.com
Regression: No
Created attachment 288155
--> https://bugzilla.kernel.org/attachment.cgi?id=288155&action=edit
vrf route oif problem
first create vrf
#ip link add vrf-1 type vrf table 10
#ip link set dev vrf-1 up
then add default route and set local table
#ip route add table 10 unreachable default metric 4278198272
#ip rule add pref 32765 table local
#ip rule del pref 0
set slave interfaces
#ip link set dev ens19 master vrf-1
#ip link set dev ens20 master vrf-1
and then add ip
#ip a a 2.2.2.2/24 dev ens19
#ip a a 3.3.3.3/24 dev ens20
add default route
#ip route add default via 2.2.2.2 dev ens19 table 10 metric 300
#ip route add default via 3.3.3.3 dev ens20 table 10 metric 301
use command to test the route
#ip r g 5.5.5.5 oif ens20
but the result is 2.2.2.2 not 3.3.3.3
don't match the oif!!
I try with kernel vesion 5.5.11
--
You are receiving this mail because:
You are the assignee for the bug.
reply other threads:[~2020-04-02 15:49 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20200402084923.4233e2ed@hermes.lan \
--to=stephen@networkplumber.org \
--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 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.