netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: 吉藤英明 <hideaki.yoshifuji@miraclelinux.com>
To: Levente <leventelist@gmail.com>
Cc: netdev@vger.kernel.org, 吉藤英明 <hideaki.yoshifuji@miraclelinux.com>,
	yoshfuji@linux-ipv6.org
Subject: Re: IPv6 issue
Date: Thu, 26 Sep 2019 01:21:09 +0900	[thread overview]
Message-ID: <CAPA1RqCKr4TnqEGrn2Og2QmH94eNnAnRFBge3gtsM1XiQAYM-A@mail.gmail.com> (raw)
In-Reply-To: <CACwWb3BE7msW6=XADuG2Di4xYnoJq5qScc4Wsu4xOS=ycYPDww@mail.gmail.com>

Hi,


2019年9月26日(木) 0:25 Levente <leventelist@gmail.com>:
>
> Dear all,
>
>
> I don't know if this is the right place to ask, so please be gentle.
>
> I have a router running OpenWRT, and it fails the some test cases
> defined by the IPv6 forum.
>
> https://www.ipv6ready.org/docs/Core_Conformance_Latest.pdf
>
> It fails 1.2.3 / 1.2.4 / 1.2.5 / 1.2.8 test cases.
>
> My question is if there's any particular settings (either compile or
> running time) in the kernel that affects the outcome of these test
> cases?

You should look into the result in detail; how it fails.

>
> Other question is that is there any open source test program to test
> the kernel's IPv6 stack against this test specifications?
>

You could find some "Self Test" suites:
https://www.ipv6ready.org/?page=documents&tag=ipv6-core-protocols

--yoshfuji

>
> Thanks,
> Levente

  reply	other threads:[~2019-09-25 16:21 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-25 15:25 IPv6 issue Levente
2019-09-25 16:21 ` 吉藤英明 [this message]
  -- strict thread matches above, loose matches on Subject: below --
2008-05-09 11:34 IPV6 issue Bonitch, Joseph
2008-05-09 11:58 ` David Miller

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=CAPA1RqCKr4TnqEGrn2Og2QmH94eNnAnRFBge3gtsM1XiQAYM-A@mail.gmail.com \
    --to=hideaki.yoshifuji@miraclelinux.com \
    --cc=leventelist@gmail.com \
    --cc=netdev@vger.kernel.org \
    --cc=yoshfuji@linux-ipv6.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 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).