public inbox for ltp@lists.linux.it
 help / color / mirror / Atom feed
From: Alexey Kodanev <alexey.kodanev@oracle.com>
To: ltp@lists.linux.it
Subject: [LTP] [RFC PATCH v2 2/3] network: Add tool for setup IP variables
Date: Tue, 4 Apr 2017 13:50:24 +0300	[thread overview]
Message-ID: <ae28eabb-494f-ef35-d983-e0685f98deaa@oracle.com> (raw)
In-Reply-To: <20170403123118.4p2xuzwzq34s46rv@x230>

On 03.04.2017 15:31, Petr Vorel wrote:
> ...
>> Hmm, what are '0xff0d' and '0xaa10' prefixes? The first one seems to be a
>> multicast group address...
> These are really random values, an easy way to get valid but unused value. Do you want
> different approach?
Hi Petr,

No, we shouldn't do that, at least using such prefixes.  The much safer
approach is to
use the private address ranges.

For IPv6 it's a unique local address, i.e. fd00::/8 prefix. We could
stick with default
one and use another one (may be random) in case we got overlap with the
predefined address, e.g.: "fd00:f00" and "fdaa:f00" (the same approach
as yours).

And for IPv4, e.g. 10.x/10.(x + 128).

> ...
>> And why this limitation is needed?
> I did it just to simplify the implementation.  IMHO both IPv4 and IPv6 require two nodes
> on the same physical network have the same prefix so I didn't consider this as a real
> limitation.
>
> But of course, there could be different prefixes, the smaller would be used as IPV6_NETWORK variable is
> used for both hosts. Do you want me to change it this way?

May be I misunderstood the 'prefix' variable there. If, for example,
10.20.0.1/22 and 10.20.1.1/22 would result into 10.20 prefix, then it's
fine,
network variable is "10.20" and host variables are "0.1" and "1.1".

Thanks,
Alexey


  reply	other threads:[~2017-04-04 10:50 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-03  7:14 [LTP] [RFC PATCH v2 0/3] Simplify network setup Petr Vorel
2017-04-03  7:14 ` [LTP] [RFC PATCH v2 1/3] gitignore: Prefixing filenames Petr Vorel
2017-04-03  7:14 ` [LTP] [RFC PATCH v2 2/3] network: Add tool for setup IP variables Petr Vorel
2017-04-03 11:29   ` Alexey Kodanev
2017-04-03 12:31     ` Petr Vorel
2017-04-04 10:50       ` Alexey Kodanev [this message]
2017-04-04 14:41         ` Petr Vorel
2017-04-03  7:14 ` [LTP] [RFC PATCH v2 3/3] network: Use tst_net_vars to set up variables Petr Vorel
2017-04-03 11:41   ` Alexey Kodanev

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=ae28eabb-494f-ef35-d983-e0685f98deaa@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox