All of lore.kernel.org
 help / color / mirror / Atom feed
From: Matthieu Baerts <matthieu.baerts at tessares.net>
To: mptcp at lists.01.org
Subject: [MPTCP] Re: [PATCH mptcp-next v4 3/3] selftests: mptcp: add IPv4-mapped IPv6 testcases
Date: Mon, 21 Dec 2020 12:49:15 +0100	[thread overview]
Message-ID: <f0a0f5c3-c047-44f0-c4bf-3612a31b5515@tessares.net> (raw)
In-Reply-To: CA+WQbws31bk_d2JzL8-zGH+pZ5baYctfQKKvyy=SYev49TT3QQ@mail.gmail.com

[-- Attachment #1: Type: text/plain, Size: 2370 bytes --]

Hi Geliang,

On 21/12/2020 11:16, Geliang Tang wrote:
> Hi Matt,
> 
> Matthieu Baerts <matthieu.baerts(a)tessares.net> 于2020年12月19日周六 下午9:07写道:
>>
>> From: Geliang Tang <geliangtang(a)gmail.com>
>>
>> Here, we make sure we support IPv4-mapped in IPv6 addresses in different
>> contexts:

(...)

>> +# no subflow IPv6 to v4 address
>> +reset
>> +ip netns exec $ns1 ./pm_nl_ctl limits 0 1
>> +ip netns exec $ns2 ./pm_nl_ctl limits 0 1
>> +ip netns exec $ns2 ./pm_nl_ctl add dead:beef:2::10.0.3.2 flags subflow
> 
> dead:beef:2::10.0.3.2 is a invalid address, should we use dead:beef:3::2 here?

I used "dead:beef:2::10.0.3.2" on purpose just to have a valid and 
usable IPv4 address at the end of the v6 one. If we try to use the IPv4 
address at the end of this v6 one, we will send the SYN+MPJ to the 
correct host (no routing issue). With the previous version of this 
patchset (v3), this was creating a subflow with 10.0.3.2!

I should certainly add a new comment here.
Maybe you would prefer an additional test with "dead:beef:3::2" as well?

>> +run_tests $ns1 $ns2 "10.0.1.1"
> 
> We can drop the quotation marks here, only the IPv4-mapped address need
> the quotation marks.

Yes, I usually add quotes in Bash for each string but I see we didn't do 
that for the other tests, I will remove that!

> And add "0 0 0 slow" behind it, since the test need to slow down when use
> the IPv6 address.

Do I need to do that here as well even if we don't create v6 subflows?

>> +chk_join_nr "no JOIN with different families v4-v6" 0 0 0
> 
> This string is too long, it break the alignment of the output. Can we use
> "diff" here instead of "different"?

Good point, I didn't check that! I will short "different", good idea!

>> +
>> +# no subflow IPv4 to v6 address
>> +reset
>> +ip netns exec $ns1 ./pm_nl_ctl limits 0 1
>> +ip netns exec $ns2 ./pm_nl_ctl limits 0 1
>> +ip netns exec $ns2 ./pm_nl_ctl add 10.0.3.2 flags subflow
>> +run_tests $ns1 $ns2 dead:beef:1::1
> 
> Add "0 0 0 slow" here.

Same here, is it needed if we don't create any IPv6 subflow?

>> +chk_join_nr "no JOIN with different families v6-v4" 0 0 0
> 
> This string is too long too.

Will do in v5!

Thanks for the review!

Cheers,
Matt
-- 
Tessares | Belgium | Hybrid Access Solutions
www.tessares.net

             reply	other threads:[~2020-12-21 11:49 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-21 11:49 Matthieu Baerts [this message]
  -- strict thread matches above, loose matches on Subject: below --
2020-12-21 12:10 [MPTCP] Re: [PATCH mptcp-next v4 3/3] selftests: mptcp: add IPv4-mapped IPv6 testcases Geliang Tang
2020-12-21 10:16 Geliang Tang

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=f0a0f5c3-c047-44f0-c4bf-3612a31b5515@tessares.net \
    --to=unknown@example.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.