All of lore.kernel.org
 help / color / mirror / Atom feed
From: Petr Vorel <pvorel@suse.cz>
To: ltp@lists.linux.it
Subject: [LTP] [PATCH 1/3] test_net.sh: fix netns when defined LHOST_IFACES or RHOST_IFACES
Date: Thu, 22 Dec 2016 14:01:48 +0100	[thread overview]
Message-ID: <20161222130148.gn2j3vblabp4n446@dell5510> (raw)
In-Reply-To: <f18cb5f0-e5d9-68e8-45c7-262c987aca28@oracle.com>

Hi Alexey,

> On 12/22/2016 02:04 AM, Petr Vorel wrote:
> > Tested with:
> > TST_USE_NETNS=1 LHOST_IFACES=localpeer RHOST_IFACES=remotepeer \
> >    ./testscripts/network.sh -6

> Any good reason to do that?
Yes. Currently if you define LHOST_IFACES and/or RHOST_IFACES netns is defined for
ltp_ns_veth2 and ltp_ns_veth1, but then there are used new variables => it's not working.
Or have I overlooked something?

Kind regards,
Petr

  reply	other threads:[~2016-12-22 13:01 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-12-21 23:04 [LTP] [PATCH 1/3] test_net.sh: fix netns when defined LHOST_IFACES or RHOST_IFACES Petr Vorel
2016-12-21 23:04 ` [LTP] [PATCH 2/3] test_net.sh: delete netns before testing Petr Vorel
2016-12-22 11:08   ` Alexey Kodanev
2016-12-23 11:04     ` Petr Vorel
2017-01-09 12:09       ` Alexey Kodanev
2016-12-21 23:04 ` [LTP] [PATCH 3/3] test_net.sh: netns as default in tst_rhost_run Petr Vorel
2017-01-19 17:50   ` Petr Vorel
2017-01-20 16:14     ` Alexey Kodanev
2017-01-23  9:57       ` Petr Vorel
2016-12-22 10:47 ` [LTP] [PATCH 1/3] test_net.sh: fix netns when defined LHOST_IFACES or RHOST_IFACES Alexey Kodanev
2016-12-22 13:01   ` Petr Vorel [this message]
2016-12-22 14:15     ` Alexey Kodanev
2016-12-22 15:17       ` Petr Vorel
2016-12-22 17:55         ` Alexey Kodanev
2016-12-23 10:54           ` 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=20161222130148.gn2j3vblabp4n446@dell5510 \
    --to=pvorel@suse.cz \
    --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.