From: Alexey Kodanev <alexey.kodanev@oracle.com>
To: ltp@lists.linux.it
Subject: [LTP] [PATCH 1/3] lib/test_net.sh: add tst_ping() to check icmp connectivity
Date: Thu, 10 Mar 2016 10:23:14 +0300 [thread overview]
Message-ID: <56E120E2.8050107@oracle.com> (raw)
In-Reply-To: <20160310062208.GK2649@Leo.nay.redhat.com>
Hi,
On 03/10/2016 09:22 AM, Hangbin Liu wrote:
>>>
>>>> + if [ "$dst_addr" == "$(tst_ipaddr)" ]; then
>>>> + tst_rhost_run -c "$PING -I $src_iface -c $PING_MAX $dst_addr \
>>>> + -s $msg_size > /dev/null 2>&1"
>>>> + else
>>>> + $PING -I $src_iface -c $PING_MAX $dst_addr -s $msg_size > \
>>>> + /dev/null 2>&1
>>>> + fi
>>>> +}
>>> Do we actually need to run this command from remote host?
> I'm OK with both side. but the previous test run check_icmp_connectivity from
> remote.
>
> $LTP_RSH $RHOST ${LTPROOT}/testcases/bin/check_icmpv4_connectivity
>
> So how do you think.
If we're checking connectivity... it doesn't really matter,
but running it from remote host is not so convenient.
Thanks,
Alexey
next prev parent reply other threads:[~2016-03-10 7:23 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1457334114-10461-1-git-send-email-haliu@redhat.com>
[not found] ` <1457334114-10461-2-git-send-email-haliu@redhat.com>
2016-03-09 12:08 ` [LTP] [PATCH 1/3] lib/test_net.sh: add tst_ping() to check icmp connectivity Alexey Kodanev
2016-03-09 12:11 ` Alexey Kodanev
2016-03-10 6:22 ` Hangbin Liu
2016-03-10 7:23 ` Alexey Kodanev [this message]
2016-03-11 3:00 ` Hangbin Liu
2016-03-07 7:20 [LTP] [PATCH 0/3] networking/stress: add ip xfrm ipsec support Hangbin Liu
2016-03-07 7:20 ` [LTP] [PATCH 1/3] lib/test_net.sh: add tst_ping() to check icmp connectivity Hangbin Liu
-- strict thread matches above, loose matches on Subject: below --
2016-03-07 7:14 [LTP] [PATCH 0/3] networking/stress: add ip xfrm ipsec support Hangbin Liu
2016-03-07 7:14 ` [LTP] [PATCH 1/3] lib/test_net.sh: add tst_ping() to check icmp connectivity Hangbin Liu
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=56E120E2.8050107@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.