From: Stephen Hemminger <stephen@networkplumber.org>
To: "Iremonger, Bernard" <bernard.iremonger@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>,
Stephen Hemminger <sthemmin@microsoft.com>
Subject: Re: [dpdk-dev] [PATCH v2 1/2] testpmd: use RFC values for Tx address and port
Date: Thu, 14 Jun 2018 08:56:18 -0700 [thread overview]
Message-ID: <20180614085618.7be877e6@xeon-e3> (raw)
In-Reply-To: <8CEF83825BEC744B83065625E567D7C260CB347E@IRSMSX108.ger.corp.intel.com>
On Thu, 14 Jun 2018 10:17:46 +0000
"Iremonger, Bernard" <bernard.iremonger@intel.com> wrote:
> Hi Stephen,
>
> > -----Original Message-----
> > From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Stephen
> > Hemminger
> > Sent: Monday, June 11, 2018 7:25 PM
> > To: dev@dpdk.org
> > Cc: Stephen Hemminger <stephen@networkplumber.org>; Stephen
> > Hemminger <sthemmin@microsoft.com>
> > Subject: [dpdk-dev] [PATCH v2 1/2] testpmd: use RFC values for Tx address
> > and port
> >
> > Change the IP address and UDP port used for testpmd Tx only test. The old
> > values overlap common NAT local networks; instead use reserved addresses
> > in IETF RFC 2544.
>
> The commit message should probably refer to RFC 863 too.
>
Ok. I forgot about RFC863. It is 1 page!
next prev parent reply other threads:[~2018-06-14 23:11 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-11 18:25 [dpdk-dev] [PATCH v2 0/2] testpmd: allow configure of Tx IP parameters Stephen Hemminger
2018-06-11 18:25 ` [dpdk-dev] [PATCH v2 1/2] testpmd: use RFC values for Tx address and port Stephen Hemminger
2018-06-14 10:17 ` Iremonger, Bernard
2018-06-14 15:56 ` Stephen Hemminger [this message]
2018-06-11 18:25 ` [dpdk-dev] [PATCH v2 2/2] testpmd: add ability to set tx IP and UDP parameters Stephen Hemminger
2018-06-14 10:30 ` Iremonger, Bernard
2018-06-18 19:31 ` Stephen Hemminger
2018-06-18 19:29 ` Stephen Hemminger
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=20180614085618.7be877e6@xeon-e3 \
--to=stephen@networkplumber.org \
--cc=bernard.iremonger@intel.com \
--cc=dev@dpdk.org \
--cc=sthemmin@microsoft.com \
/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).