netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andrew Lunn <andrew@lunn.ch>
To: Ido Schimmel <idosch@mellanox.com>
Cc: netdev@vger.kernel.org, linux-kselftest@vger.kernel.org,
	davem@davemloft.net, shuah@kernel.org, jiri@mellanox.com,
	dsahern@gmail.com, roopa@cumulusnetworks.com,
	nikolay@cumulusnetworks.com, f.fainelli@gmail.com,
	vivien.didelot@savoirfairelinux.com, mlxsw@mellanox.com
Subject: Re: [PATCH net-next 01/14] selftests: forwarding: Add initial testing framework
Date: Mon, 26 Feb 2018 14:48:02 +0100	[thread overview]
Message-ID: <20180226134802.GC1195@lunn.ch> (raw)
In-Reply-To: <20180226085948.19368-2-idosch@mellanox.com>

> +                             br0
> +                              +
> +               vrf-h1         |           vrf-h2
> +                 +        +---+----+        +
> +                 |        |        |        |
> +    192.0.2.1/24 +        +        +        + 192.0.2.2/24
> +               swp1     swp2     swp3     swp4
> +                 +        +        +        +
> +                 |        |        |        |
> +                 +--------+        +--------+
> +

> +setup_prepare
> +setup_wait
> +
> +ping_test $h1 192.0.2.2
> +ping6_test $h1 2001:db8:1::2

How about putting 192.0.2.3/24 on br0, and pinging to/from
it. Otherwise you don't test the slow path. 

I would also suggest a much simpler first test.

> +                             
> +                              
> +               vrf-h1                                         vrf-h2
> +                 +                                              +
> +                 |                                              |
> +    192.0.2.1/24 +        + 192.0.2.2/24  192.0.3.1/24 +        + 192.0.3.2/24
> +               swp1     swp2                          swp3     swp4
> +                 +        +                            +        +
> +                 |        |                            |        |
> +                 +--------+                            +--------+

Ping from 192.0.2.1 to 192.0.2.2 and test there are 0 packets seen on
swp3 and swp4. I've seen DSA drivers get this wrong before, forgetting
to ensure ports are properly separated by default.

   Andrew

  reply	other threads:[~2018-02-26 13:48 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-26  8:59 [PATCH net-next 00/14] selftests: forwarding: Add VRF-based tests Ido Schimmel
2018-02-26  8:59 ` [PATCH net-next 01/14] selftests: forwarding: Add initial testing framework Ido Schimmel
2018-02-26 13:48   ` Andrew Lunn [this message]
2018-02-26  8:59 ` [PATCH net-next 02/14] selftests: forwarding: Add a test for FDB learning Ido Schimmel
2018-02-26 16:31   ` Petr Machata
2018-02-26 20:02     ` Ido Schimmel
2018-02-26  8:59 ` [PATCH net-next 03/14] selftests: forwarding: Add a test for flooded traffic Ido Schimmel
2018-02-26  8:59 ` [PATCH net-next 04/14] selftests: forwarding: Add a test for basic IPv4 and IPv6 routing Ido Schimmel
2018-02-26  8:59 ` [PATCH net-next 05/14] selftests: forwarding: Create test topology for multipath routing Ido Schimmel
2018-02-26  8:59 ` [PATCH net-next 06/14] selftests: forwarding: Test IPv4 weighted nexthops Ido Schimmel
2018-02-26  8:59 ` [PATCH net-next 07/14] selftests: forwarding: Test IPv6 " Ido Schimmel
2018-02-26  8:59 ` [PATCH net-next 08/14] selftests: forwarding: Add tc offload check helper Ido Schimmel
2018-02-26  8:59 ` [PATCH net-next 09/14] selftests: forwarding: Add MAC get helper Ido Schimmel
2018-02-26  8:59 ` [PATCH net-next 10/14] selftests: forwarding: Allow to get netdev interfaces names from commandline Ido Schimmel
2018-02-26  8:59 ` [PATCH net-next 11/14] selftests: forwarding: Introduce tc flower matching tests Ido Schimmel
2018-02-26  8:59 ` [PATCH net-next 12/14] selftests: forwarding: Introduce tc actions tests Ido Schimmel
2018-02-26  8:59 ` [PATCH net-next 13/14] selftests: forwarding: Introduce basic tc chains tests Ido Schimmel
2018-02-26  8:59 ` [PATCH net-next 14/14] selftests: forwarding: Introduce basic shared blocks tests Ido Schimmel
2018-02-26 13:35 ` [PATCH net-next 00/14] selftests: forwarding: Add VRF-based tests Andrew Lunn
2018-02-26 13:46   ` Jiri Pirko
2018-02-26 20:07   ` Ido Schimmel

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=20180226134802.GC1195@lunn.ch \
    --to=andrew@lunn.ch \
    --cc=davem@davemloft.net \
    --cc=dsahern@gmail.com \
    --cc=f.fainelli@gmail.com \
    --cc=idosch@mellanox.com \
    --cc=jiri@mellanox.com \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=mlxsw@mellanox.com \
    --cc=netdev@vger.kernel.org \
    --cc=nikolay@cumulusnetworks.com \
    --cc=roopa@cumulusnetworks.com \
    --cc=shuah@kernel.org \
    --cc=vivien.didelot@savoirfairelinux.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;
as well as URLs for NNTP newsgroup(s).