From: Stephen Suryaputra <ssuryaextr@gmail.com>
To: Levente <leventelist@gmail.com>, Captain Wiggum <captwiggum@gmail.com>
Cc: netdev <netdev@vger.kernel.org>
Subject: Re: IPv6 test fail
Date: Wed, 18 Dec 2019 16:00:28 -0500 [thread overview]
Message-ID: <CAHapkUgCWS4DxGVL2qJsXmiAEq4rGY+sPTROx4iftO6mD_261g@mail.gmail.com> (raw)
In-Reply-To: <CACwWb3CYP9MENZJAzBt5buMNxkck7+Qig9yYG8nTYrdBw1fk5A@mail.gmail.com>
I am curious: what kernel version are you testing?
I recall that several months ago there is a thread on TAHI IPv6.
Including the person who started the thread.
Stephen.
On Thu, Oct 24, 2019 at 7:43 AM Levente <leventelist@gmail.com> wrote:
>
> Dear list,
>
>
> We are testing IPv6 again against the test specification of ipv6forum.
>
> https://www.ipv6ready.org/?page=documents&tag=ipv6-core-protocols
>
> The test house state that some certain packages doesn't arrive to the
> device under test. We fail test cases
>
> V6LC.1.2.2: No Next Header After Extension Header
> V6LC.1.2.3: Unreacognized Next Header in Extension Header - End Node
> V6LC.1.2.4: Extension Header Processing Order
> V6LC.1.2.5: Option Processing Order
> V6LC.1.2.8: Option Processing Destination Options Header
>
> The question is that is it possible that the this is the intended way
> of operation? I.e. the kernel swallows those malformed packages? We
> use tcpdump to log the traffic.
>
>
> Thank you for your help.
>
> Levente
next prev parent reply other threads:[~2019-12-18 21:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-23 16:37 IPv6 test fail Levente
2019-12-18 21:00 ` Stephen Suryaputra [this message]
2020-01-29 22:31 ` Captain Wiggum
2020-01-30 12:06 ` Alarig Le Lay
2020-01-30 12:13 ` Levente
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=CAHapkUgCWS4DxGVL2qJsXmiAEq4rGY+sPTROx4iftO6mD_261g@mail.gmail.com \
--to=ssuryaextr@gmail.com \
--cc=captwiggum@gmail.com \
--cc=leventelist@gmail.com \
--cc=netdev@vger.kernel.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 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.