From: Stephen Hemminger <stephen@networkplumber.org>
To: Hemant Agrawal <hemant.agrawal@nxp.com>
Cc: dev <dev@dpdk.org>
Subject: Re: [dpdk-dev] Query on the old patch: examples/l3fwd: use reserved IPv4/IPv6 addresses
Date: Tue, 5 Nov 2019 07:51:19 -0800 [thread overview]
Message-ID: <20191105075119.3303e891@hermes.lan> (raw)
In-Reply-To: <VI1PR0401MB25414FB8A03214BDCCD7DAF5897E0@VI1PR0401MB2541.eurprd04.prod.outlook.com>
On Tue, 5 Nov 2019 13:54:43 +0000
Hemant Agrawal <hemant.agrawal@nxp.com> wrote:
> Hi Stephen,
> In one of your old patch, you have changed the default IP addresses to the range of 192.18.0.0 citing RFC 5735.
> commit 37afe381bde4277f0078116b8d4d7a315c8e39b3
> Author: Stephen Hemminger <stephen@networkplumber.org>
> Date: Wed Apr 10 10:41:31 2019 -0700
> examples/l3fwd: use reserved IP addresses
>
> however, in the RFC, I see the range as 198.18.x.x. Was this deliberate ? Or, I am misreading?
>
> https://tools.ietf.org/html/rfc5735
> 198.18.0.0/15 Network Interconnect
> Device Benchmark Testing RFC 2544<https://tools.ietf.org/html/rfc2544>
>
>
> Regards,
> Hemant
>
Good catch, this is a typo in my patch.
198.18.0.0/15 - This block has been allocated for use in benchmark
tests of network interconnect devices. [RFC2544] explains that this
range was assigned to minimize the chance of conflict in case a
testing device were to be accidentally connected to part of the
Internet. Packets with source addresses from this range are not
meant to be forwarded across the Internet.
prev parent reply other threads:[~2019-11-05 15:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-05 13:54 Hemant Agrawal
2019-11-05 15:51 ` Stephen Hemminger [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=20191105075119.3303e891@hermes.lan \
--to=stephen@networkplumber.org \
--cc=dev@dpdk.org \
--cc=hemant.agrawal@nxp.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).