[Dibbler] DHCPv6 server negative tests failure

Ron, Omer1 omer1.ron at intel.com
Mon Jan 30 13:19:15 CET 2012


Hi,

All tests below had DHCPv6 server failure.
Please find on each test the received result vs. expected result

TEST 1:

    Verify server sends UseMulticast status code when client sends unicast Renew
the client send DHCPv6 Renew using the server's unicast address.
The server instead of sending status code of 5 'UseMulticast' send status code 'Success'

TEST 2:

    Verify server sends UseMulticast status code when client sends a unicast Request
the client send DHCPv6 Request using the server's unicast address.
The server instead of sending status code of 5 'UseMulticast' send status code 'Success'

TEST 3:

    Verify server sends Reply with lifetimes of 0 when client attempts to renew unknown address (relevant also for rebind message)
the client send DHCPv6 Renew with a valid IAID containing unknown address
IA IPv6 address is wrong , expecting the same IP send in the renew
IA Preferred lifetime is 4294967295, expecting 0
IA Valid lifetime is 4294967295, expecting 0

TEST 4:

    Verify server sends NotOnLink status code when client sends Request with invalid link address (relevant also for confirm message)
the client send DHCPv6 Request with an address not considered "on link"
Found unexpected status code Success (0), expecting NotOnLink (4)

Thanks,
Omer

From: dibbler-bounces at klub.com.pl [mailto:dibbler-bounces at klub.com.pl] On Behalf Of Ron, Omer1
Sent: Monday, January 30, 2012 12:30
To: dibbler at klub.com.pl
Subject: [Dibbler] DHCPv6 server negative tests failure

Hi,

Appreciate your comments on below fail tests:


TEST 1:

    Verify server sends UseMulticast status code when client sends unicast Renew

    Reference: IETF RFC 3315 Section 18.2.3 "Receipt of Renew Messages"

    When the server receives a Renew message via unicast from a client to
    which the server has not sent a unicast option, the server discards
    the Renew message and responds with a Reply message containing a
    Status Code option with the value UseMulticast, a Server Identifier
    option containing the server's DUID, the Client Identifier option
    from the client message, and no other options.

TEST 2:

    Verify server sends UseMulticast status code when client sends a unicast Request

    Reference: IETF RFC 3315 Section 18.2.1 "Receipt of Request Messages"

    When the server receives a Request message via unicast from a client
    to which the server has not sent a unicast option, the server
    discards the Request message and responds with a Reply message
    containing a Status Code option with the value UseMulticast, a Server
    Identifier option containing the server's DUID, the Client Identifier
    option from the client message, and no other options.

TEST 3:

    Verify server sends Reply with lifetimes of 0 when client attempts to renew unknown address (relevant also for rebind message)

    Reference: IETF RFC 3315 Section 18.2.3 "Receipt of Renew Messages"

    If the server finds that any of the addresses are not appropriate for
    the link to which the client is attached, the server returns the
    address to the client with lifetimes of 0.

TEST 4:

    Verify server sends NotOnLink status code when client sends Request with invalid link address (relevant also for confirm message)

    Reference: IETF RFC 3315 Section 18.2.1 "Receipt of Request Messages"

    If the server finds that the prefix on one or more IP addresses in
    any IA in the message from the client is not appropriate for the link
    to which the client is connected, the server MUST return the IA to
    the client with a Status Code option with the value NotOnLink.

Thanks,
Omer
---------------------------------------------------------------------
Intel Israel (74) Limited

This e-mail and any attachments may contain confidential material for
the sole use of the intended recipient(s). Any review or distribution
by others is strictly prohibited. If you are not the intended
recipient, please contact the sender and delete all copies.
---------------------------------------------------------------------
Intel Israel (74) Limited

This e-mail and any attachments may contain confidential material for
the sole use of the intended recipient(s). Any review or distribution
by others is strictly prohibited. If you are not the intended
recipient, please contact the sender and delete all copies.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://klub.com.pl/pipermail/dibbler/attachments/20120130/ac2067de/attachment-0001.html>


More information about the Dibbler mailing list