From: Ido Schimmel <idosch@mellanox.com>
To: "netdev@vger.kernel.org" <netdev@vger.kernel.org>
Cc: "davem@davemloft.net" <davem@davemloft.net>,
"roopa@cumulusnetworks.com" <roopa@cumulusnetworks.com>,
mlxsw <mlxsw@mellanox.com>, Ido Schimmel <idosch@mellanox.com>
Subject: [PATCH net-next 0/4] selftests: forwarding: Add tests for VXLAN routing
Date: Mon, 21 Jan 2019 13:22:51 +0000 [thread overview]
Message-ID: <20190121132231.25507-1-idosch@mellanox.com> (raw)
VXLAN routing allows hosts in different overlay networks (i.e.,
different VNIs) to communicate with one another.
Two popular routing models are asymmetric and symmetric routing.
In asymmetric routing the ingress VTEP routes the packet into the
correct VXLAN tunnel, whereas the egress VTEP only bridges the packet to
the correct host. Therefore, packets in different directions use
different VNIs - the target VNI.
In symmetric routing both the ingress and egress VTEPs perform routing
in the overlay network into / from the VXLAN tunnel. Packets in
different directions use the same VNI - the L3 VNI. Different tenants
(VRFs) use different L3 VNIs.
Patch #1 adds a test for asymmetric routing. Patches #2-#3 reuse the
topology and add test cases for ARP decapsulation and suppression.
Patch #4 adds a test for symmetric routing.
Ido Schimmel (4):
selftests: forwarding: Add a test for VXLAN asymmetric routing
selftests: forwarding: Add a test case for ARP decapsulation
selftests: forwarding: Add a test case for ARP suppression
selftests: forwarding: Add a test for VXLAN symmetric routing
.../net/forwarding/vxlan_asymmetric.sh | 567 ++++++++++++++++++
.../net/forwarding/vxlan_symmetric.sh | 551 +++++++++++++++++
2 files changed, 1118 insertions(+)
create mode 100755 tools/testing/selftests/net/forwarding/vxlan_asymmetric.sh
create mode 100755 tools/testing/selftests/net/forwarding/vxlan_symmetric.sh
--
2.20.1
next reply other threads:[~2019-01-21 13:22 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-21 13:22 Ido Schimmel [this message]
2019-01-21 13:22 ` [PATCH net-next 1/4] selftests: forwarding: Add a test for VXLAN asymmetric routing Ido Schimmel
2019-01-21 13:22 ` [PATCH net-next 2/4] selftests: forwarding: Add a test case for ARP decapsulation Ido Schimmel
2019-01-21 13:22 ` [PATCH net-next 4/4] selftests: forwarding: Add a test for VXLAN symmetric routing Ido Schimmel
2019-01-21 13:22 ` [PATCH net-next 3/4] selftests: forwarding: Add a test case for ARP suppression Ido Schimmel
2019-01-23 4:41 ` [PATCH net-next 0/4] selftests: forwarding: Add tests for VXLAN routing 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=20190121132231.25507-1-idosch@mellanox.com \
--to=idosch@mellanox.com \
--cc=davem@davemloft.net \
--cc=mlxsw@mellanox.com \
--cc=netdev@vger.kernel.org \
--cc=roopa@cumulusnetworks.com \
/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