All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alexey Kodanev <alexey.kodanev@oracle.com>
To: ltp@lists.linux.it
Subject: [LTP] [PATCH 2/2] network/route: Rewrite route-change-gw into new API
Date: Wed, 27 Jun 2018 14:47:11 +0300	[thread overview]
Message-ID: <a5ed562e-4135-581c-aff0-65d7db4f210f@oracle.com> (raw)
In-Reply-To: <20180625140158.rvjasl7jq2m4blbc@dell5510>

On 25.06.2018 17:01, Petr Vorel wrote:
> Hi Alexey,
> 
>>> don't remember why the rewritten test is
>>> not using background traffic and not changing gateway anymore?
>> The current implementation was based on your suggestion for route-change-dst [1] (I'll
>> mention that in commit message), which uses ns-udpsender.  The other patch [2] is
>> changing gateway.
> 
>> Tests used ns-udpsender in previous implementation and we decided to keep it as  use
>> background traffic isn't sufficient enough [3].
> 
>> But ns-udpsender isn't good enough, as it doesn't check whether destination receive it [4].
>> And indeed you can pass it to any destination and it will not fail, e.g.:
>> ns-udpsender -f 4 -D 1.2.3.4 -p 1 -o -s 1472
> 
>> I guess we need to write another helper, which will listen for packets on remote side.
>> Any recommendations/ideas on it?
> 

It would be good to have this helper in order to extend the tests.
Not sure if it can be used other than here...

The other option is to configure a host on the other end as well,
so that we get responses, and use the standard tools.

> Ping, please.
> I suppose we want these gateway tests do the real client server communication even it's
> done on localhost, via tst_ipaddr_un().
> 
> I guess we want to keep UDP, as it's faster than TCP.
> So I'll create some server, which listens the packets, counts them and reports
> it.
> 
> 
> Kind regards,
> Petr
> 
> 
>> Kind regards,
>> Petr
> 
>> [1] http://lists.linux.it/pipermail/ltp/2017-August/005367.html
>> [2] https://lists.linux.it/pipermail/ltp/2018-May/008152.html
>> [3] http://lists.linux.it/pipermail/ltp/2017-July/005125.html
>> [4] http://lists.linux.it/pipermail/ltp/2017-August/005336.html


  reply	other threads:[~2018-06-27 11:47 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-17 10:35 [LTP] [PATCH 1/2] network/route: Rewrite route-change-dst into new API Petr Vorel
2018-05-17 10:35 ` [LTP] [PATCH 2/2] network/route: Rewrite route-change-gw " Petr Vorel
2018-05-18  9:53   ` Alexey Kodanev
2018-05-18 11:01     ` Petr Vorel
2018-06-25 14:01       ` Petr Vorel
2018-06-27 11:47         ` Alexey Kodanev [this message]
2018-07-04 15:35         ` Petr Vorel
2018-07-04 17:06           ` Alexey Kodanev
2018-05-18  9:36 ` [LTP] [PATCH 1/2] network/route: Rewrite route-change-dst " Alexey Kodanev
2018-05-18  9:40   ` Petr Vorel

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=a5ed562e-4135-581c-aff0-65d7db4f210f@oracle.com \
    --to=alexey.kodanev@oracle.com \
    --cc=ltp@lists.linux.it \
    /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.