From: Thomas Monjalon <thomas@monjalon.net>
To: Stephen Hemminger <stephen@networkplumber.org>
Cc: konstantin.ananyev@intel.com, bluca@debian.org, dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH] test/bpf_convert: do not require DNS lookup
Date: Wed, 10 Nov 2021 16:22:16 +0100 [thread overview]
Message-ID: <3072467.O75PRPML0V@thomas> (raw)
In-Reply-To: <20211109210403.114391-1-stephen@networkplumber.org>
09/11/2021 22:04, Stephen Hemminger:
> These tests are testing with strings with hostname (dpdk.org)
> and this makes test code do a DNS lookup. In container test
> runs, DNS is unavailable. Replace dpdk.org with the current
> IP and IPV6 addresses. Actual addresses don't matter the purpose
> of the test is to BPF code conversion, not any packets.
>
> Reported-by: Luca Boccassi <bluca@debian.org>
> Signed-off-by: Stephen Hemminger <stephen@networkplumber.org>
> ---
> --- a/app/test/test_bpf.c
> +++ b/app/test/test_bpf.c
> - "host dpdk.org and not (port 80 or port 25)",
> - "host dpdk.org and not port 80 and not port 25",
> + "host 92.243.24.197 and not (port 80 or port 25)",
> + "host 2001:4b98:dc0:43:216:3eff:feb6:2d88 and not port 80 and not port 25",
Wouldn't it be more appropriate to use reserved IP addresses?
next prev parent reply other threads:[~2021-11-10 15:22 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-09 21:04 Stephen Hemminger
2021-11-09 22:50 ` Luca Boccassi
2021-11-10 15:22 ` Thomas Monjalon [this message]
2021-11-10 16:18 ` [PATCH v2] " Stephen Hemminger
2021-11-14 23:39 ` Luca Boccassi
2021-11-24 18:51 ` Luca Boccassi
2021-11-15 3:41 ` Kalesh Anakkur Purayil
2021-11-15 23:23 ` [PATCH v3] " Stephen Hemminger
2021-11-15 23:29 ` [PATCH v4] " Stephen Hemminger
2021-11-15 23:29 ` [PATCH v5] " Stephen Hemminger
2021-11-16 13:31 ` David Marchand
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=3072467.O75PRPML0V@thomas \
--to=thomas@monjalon.net \
--cc=bluca@debian.org \
--cc=dev@dpdk.org \
--cc=konstantin.ananyev@intel.com \
--cc=stephen@networkplumber.org \
/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).