dhcpcd-discuss

Some more details about the TAHI test:

TAHI project (http://www.tahi.org/) has created an ipv6 compliance test
suite. These are run a specially configured BSD machine, sending and
receiving raw ipv6 packet to/from the target device. The following test is
part of 99 tests that validate rfc3315 compliance. "NUT" is the device
under test, and tn is the testing node, ie TAHI machine running the test
suite.

TEST PROCEDURE



       NUT      TN
        |       |
        |       |Initialize NUT(as a DHCPv6 client)
        |       |
        | ----> |*Solicit* (1*)
        | <---- |*Advertise*
        | ----> |*Request* (3*)
        | <---- |*Reply*
        |       |
        | ----> |*DAD NS* (5*)
        |       |
        | <---- |*Echo Request*
        | ----> |*Echo Reply* (7*)
        |       |


------------------------------
JUDGEMENT



  (1*)PASS: TN receives Solicit from NUT.
  (2*)PASS: TN receives Request form NUT.
  (7*)PASS: TN receives DAD NS from NUT.
  (7*)PASS: NUT should send Echo Reply to TN.

The test fails at the first step, when instead of



On Wed, Mar 23, 2016 at 5:03 PM, Shahid Mahmood <shahid.avaya@xxxxxxxxx>
wrote:

> Hi,
> I am running dhcpcd in ipv6 mode and testing with TAHI test suite for
> RFC3315.
> Has anyone done this?
>
> for me, the very first test failed:
>
> "Part A : Valid Reply message in response to Request"
>
> dhcpcd is sending out "Router Solicitation" message at startup, where as
> TAHI test (as per
> RFC3315) expecting a "Solicit" with XID message.
>
> dhcpcd started with:
> dhcpcd -6 eth0
>
> (This is an ARM based embedded device)
>
> dhclient e.g passes this test and sends out "Solicit XID:xx" right off the
> bat.
>
> Is there something I am missing?
>
> -shahid
>
>
>