Index: [Article Count Order] [Thread]

Date: Tue, 20 Dec 2005 19:00:12 +0900
From: "haoda" <haoda@64translator.com>
Subject: [dhcptest:00038] Re: Welcome to our (dhcptest ML)
To: <amit_agarr@yahoo.co.in>
Cc: <dhcptest@tahi.org>, <haoda@64translator.com>
Message-Id: <200512201000.jBKA0HSX065122@bahamas.64translator.com>
In-Reply-To: <20051220082126.10684.qmail@web8508.mail.in.yahoo.com>
X-Mail-Count: 00038

Hi, Mr. Amit.

Sorry, the setting of my mail soft has some mistake.
So the lines changed un_properly in the previous 2 mails.

I send it again, please use these one.
The No.1 is the first mail of today.

No.2
=========

Thanks for your use of our DHCPv6 test tool.

 > And also once the script recieves a reply message with server unicast 
> option for the Request Message, the script sends solicit message via 
> unicast, but the SID in the solicit message sent is unknown
> ( that means, not a known DUID). Please check this also.
It is a bug in my script. The SID option can't appears in the Solicit message.
I have fixed it and send it as the attachment of  this mail. 
Please use it.
 

> S_RFC3315_17.2.2_Creation-TransOfAdvMsgUnicast.seq
> These two statements contradict eachother, please com! ment... 
> The script is based on 17.2.2.
The texts of RFC looks not consistent here, I should think about
it and if I have some idea  I'll contact with you.


Regard yours, 
Haoda



No.1
=========

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_alldhcp=
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

attatchment (application/octet-stream) ignored(encoded)