Date: Fri, 27 Jul 2007 22:24:41 +0900
From: <Hideshi.Enokihara@jp.yokogawa.com>
Subject: [dhcptest:00194] Re: Specifiy invalid address range at Reception of Solicit message tests
To: <dhcptest@tahi.org>
Message-Id: <0260031F55435342859BFB2CCA6773D825DA3F06@EXCHANGE03.jp.ykgw.net>
References: <20070727214454.1c34805e.mitch@linux.vnet.ibm.com>
X-Mail-Count: 00194

Hello Chinen-san,
 
Thank you for your report.
 
we will fix these bugs as soon as possible.
#hopefully, begining of Aug.
 
Best regards,
 

________________________________

From: Mitsuru Chinen [mailto:mitch@linux.vnet.ibm.com]
Sent: 2007/07/27 (金) 21:44
To: dhcptest@tahi.org
Subject: [dhcptest:00193] Specifiy invalid address range at Reception of Solicit message tests



Dear TAHI Project folks,

At server test in DHCPv6 Testsuite v1.0.3, I found invalid address
range is specified in the following tests.

  #39 Reception of Solicit message with DUID-LLT
  #40 Reception of Solicit message with DUID-EN
  #41 Reception of Solicit message with DUID-LL

The prefix of start address is 3ffe:501:ffff:100::/64
However the prefix of end address is 3ffe:ffff:100::/64.
`:501:' is lacked at the end address.

I attached a proposal patch for this.
Could you take a look at it?

Best Regards,
----
Mitsuru Chinen <mitch@linux.vnet.ibm.com>


diff -upr DHCPv6_Self_Test_P2_1_0_3.orig/rfc3315/S_RFC3315_SolicitMsgwEN.seq DHCPv6_Self_Test_P2_1_0_3/rfc3315/S_RFC3315_SolicitMsgwEN.seq
--- DHCPv6_Self_Test_P2_1_0_3.orig/rfc3315/S_RFC3315_SolicitMsgwEN.seq  2007-03-11 20:05:54.000000000 +0900
+++ DHCPv6_Self_Test_P2_1_0_3/rfc3315/S_RFC3315_SolicitMsgwEN.seq       2007-07-27 21:06:50.000000000 +0900
@@ -65,7 +65,7 @@ my $IF0 = "Link0";
 #initial NUT config parameters,
 my %NUT_Server_Config = (
 'if_nut0'=> "$V6evalTool::NutDef{Link0_device}",
-'init_opcode' => "vRemote(\"dhcp6s.rmt\", \"start\", \"link0=$V6evalTool::NutDef{Link0_device}\",\"startaddr=3ffe:501:ffff:100::10\",\"endaddr=3ffe:ffff:100::11\")"
+'init_opcode' => "vRemote(\"dhcp6s.rmt\", \"start\", \"link0=$V6evalTool::NutDef{Link0_device}\",\"startaddr=3ffe:501:ffff:100::10\",\"endaddr=3ffe:501:ffff:100::11\")"
 );
 dhcpSvrInit(\%NUT_Server_Config);
 vClear($IF0);
diff -upr DHCPv6_Self_Test_P2_1_0_3.orig/rfc3315/S_RFC3315_SolicitMsgwLL.seq DHCPv6_Self_Test_P2_1_0_3/rfc3315/S_RFC3315_SolicitMsgwLL.seq
--- DHCPv6_Self_Test_P2_1_0_3.orig/rfc3315/S_RFC3315_SolicitMsgwLL.seq  2007-03-11 20:05:54.000000000 +0900
+++ DHCPv6_Self_Test_P2_1_0_3/rfc3315/S_RFC3315_SolicitMsgwLL.seq       2007-07-27 21:07:20.000000000 +0900
@@ -65,7 +65,7 @@ my $IF0 = "Link0";
 #initial NUT config parameters,
 my %NUT_Server_Config = (
 'if_nut0'=> "$V6evalTool::NutDef{Link0_device}",
-'init_opcode' => "vRemote(\"dhcp6s.rmt\", \"start\", \"link0=$V6evalTool::NutDef{Link0_device}\",\"startaddr=3ffe:501:ffff:100::10\",\"endaddr=3ffe:ffff:100::11\")"
+'init_opcode' => "vRemote(\"dhcp6s.rmt\", \"start\", \"link0=$V6evalTool::NutDef{Link0_device}\",\"startaddr=3ffe:501:ffff:100::10\",\"endaddr=3ffe:501:ffff:100::11\")"
 );
 dhcpSvrInit(\%NUT_Server_Config);
 vClear($IF0);
diff -upr DHCPv6_Self_Test_P2_1_0_3.orig/rfc3315/S_RFC3315_SolicitMsgwLLT.seq DHCPv6_Self_Test_P2_1_0_3/rfc3315/S_RFC3315_SolicitMsgwLLT.seq
--- DHCPv6_Self_Test_P2_1_0_3.orig/rfc3315/S_RFC3315_SolicitMsgwLLT.seq 2007-03-11 20:05:54.000000000 +0900
+++ DHCPv6_Self_Test_P2_1_0_3/rfc3315/S_RFC3315_SolicitMsgwLLT.seq      2007-07-27 21:04:47.000000000 +0900
@@ -65,7 +65,7 @@ my $IF0 = "Link0";
 #initial NUT config parameters,
 my %NUT_Server_Config = (
 'if_nut0'=> "$V6evalTool::NutDef{Link0_device}",
-'init_opcode' => "vRemote(\"dhcp6s.rmt\", \"start\", \"link0=$V6evalTool::NutDef{Link0_device}\",\"startaddr=3ffe:501:ffff:100::10\",\"endaddr=3ffe:ffff:100::11\")"
+'init_opcode' => "vRemote(\"dhcp6s.rmt\", \"start\", \"link0=$V6evalTool::NutDef{Link0_device}\",\"startaddr=3ffe:501:ffff:100::10\",\"endaddr=3ffe:501:ffff:100::11\")"
 );
 dhcpSvrInit(\%NUT_Server_Config);
 vClear($IF0);