($INBOX_DIR/description missing)
 help / color / mirror / Atom feed
From: Petr Vorel <pvorel@suse.cz>
To: ltp@lists.linux.it
Subject: [LTP] [PATCH 2/2] network/README: Document ping dependencies
Date: Sat, 30 Mar 2024 19:08:18 +0100	[thread overview]
Message-ID: <20240330180818.246499-2-pvorel@suse.cz> (raw)
In-Reply-To: <20240330180818.246499-1-pvorel@suse.cz>

Signed-off-by: Petr Vorel <pvorel@suse.cz>
---
 testcases/network/README.md | 7 +++++++
 1 file changed, 7 insertions(+)

diff --git a/testcases/network/README.md b/testcases/network/README.md
index e1b1296d6..0b64df01e 100644
--- a/testcases/network/README.md
+++ b/testcases/network/README.md
@@ -88,6 +88,13 @@ Tests which use `tst_netload_compare()` test also performance. They can fail on
 overloaded SUT.  To ignore performance failure and test only the network functionality,
 set `LTP_NET_FEATURES_IGNORE_PERFORMANCE_FAILURE=1` environment variable.
 
+## Dependencies
+
+Some network tests which use `tst_ping()` function require `ping` with `-I` support,
+which is not supported by `ping` from [inetutils](https://www.gnu.org/software/inetutils/).
+Use `ping` from [iputils](https://github.com/iputils/iputils/) or from [BusyBox](https://busybox.net/)
+(configured with `CONFIG_FEATURE_IPV6=y` `CONFIG_FEATURE_FANCY_PING=y`).
+
 ## Debugging
 Both single and two host configurations support debugging via
 `TST_NET_RHOST_RUN_DEBUG=1` environment variable.
-- 
2.43.0


-- 
Mailing list info: https://lists.linux.it/listinfo/ltp

      reply	other threads:[~2024-03-30 18:09 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-30 18:08 [LTP] [PATCH 1/2] tst_net.sh: tst_ping(): check for ping -I support Petr Vorel
2024-03-30 18:08 ` Petr Vorel [this message]

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=20240330180818.246499-2-pvorel@suse.cz \
    --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 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 read-only IMAP folder(s) and NNTP newsgroup(s).