Index: [Article Count Order] [Thread]

Date: Tue, 20 Dec 2005 17:19:55 +0900
From: "haoda" <haoda@64translator.com>
Subject: [dhcptest:00035] Re: Welcome to our (dhcptest ML)
To: <amit_agarr@yahoo.co.in>
Cc: <dhcptest@tahi.org>, <haoda@64translator.com>
Message-Id: <200512200820.jBK8K1GF064065@bahamas.64translator.com>
X-Mail-Count: 00035

Hi, Mr. Amit.

Thanks for your report.
I have read all the test log in your email
carefully.
Here is the explain for the test result, please
refers
to it.

[Item 9&10&13]
It looks the NUT does not relay the packet
received 
from the other relay agent. So the message "NG: 
Can not receive expected Relay Forward Message" 
has been logged.

[Item 18& Item 19]
Please see this line in the test logs,
"
===relayforward_infomationrequest_client1_to_alldh
cp=
ng compare
_UDP_DHCPV6_relayforward_infomationrequest_client1
_to_alldhcp.
LinkAddr received:fe80::200:ff:fe00:a2a2 =
3ffe:501:ffff:101:200:ff:fe00:a5a5
"
the "fe80::200:ff:fe00:a2a2" is received by our
test script.
But the expected Link address should be  
"3ffe:501:ffff:101:200:ff:fe00:a5a5". It is used
to assigned an
So the tests are failed.

Please refer to this text.
RFC3315, page 59, line 3260.

"
   If the relay agent received the message to be
relayed from a client,
   the relay agent places a global or site-scoped
address with a prefix
 
--------------------------------------------------
-------------
   assigned to the link on which the client should
be assigned an
   ----------------------------
   address in the link-address field.
               ----------------------------------

"

Regard yours,
Haoda