Hi all,
I found some server tests specifies unsuitable prefix to the address
range onto dhcp6s.rmt, at RFC3315 section in DHCPv6 Self Test
(version 1.0.5)
#33 Reply-Reply message with Reply message (w/o Interface-id Option)
#34 Reply-Reply message with Reply message (w/ Interface-id Option)
These pass the range whose prefix is 3ffe:501:ffff:100 to dhcp6s.rmt.
The prefix is same as the prefix of the link where server exists.
#37 Part C : Relay-Reply message transmission through the layered Relay agents
These pass the range whose prefix is 3ffe:501:ffff:101. However,
the prefix of the link where client exists is 3ffe:501:ffff:102.
I attached patch for this isssue. Could you look at this?
Best Regards,
----
Mitsuru Chinen <mitch@linux.vnet.ibm.com>
diff -upr DHCPv6_Self_Test_P2_1_0_5.orig/rfc3315/S_RFC3315_17.2.3_Creation-TransmissionOfReplyMsgIfRelayReply.seq DHCPv6_Self_Test_P2_1_0_5/rfc3315/S_RFC3315_17.2.3_Creation-TransmissionOfReplyMsgIfRelayReply.seq
--- DHCPv6_Self_Test_P2_1_0_5.orig/rfc3315/S_RFC3315_17.2.3_Creation-TransmissionOfReplyMsgIfRelayReply.seq 2007-02-15 17:03:42.000000000 +0900
+++ DHCPv6_Self_Test_P2_1_0_5/rfc3315/S_RFC3315_17.2.3_Creation-TransmissionOfReplyMsgIfRelayReply.seq 2007-08-29 19:25:19.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:501:ffff:100::11\")"
+ 'init_opcode' => "vRemote(\"dhcp6s.rmt\", \"start\",\"link0=$V6evalTool::NutDef{Link0_device}\",\"startaddr=3ffe:501:ffff:101::10\",\"endaddr=3ffe:501:ffff:101::11\")"
);
dhcpSvrInit(\%NUT_Server_Config);
diff -upr DHCPv6_Self_Test_P2_1_0_5.orig/rfc3315/S_RFC3315_17.2.3_Creation-TransmissionOfReplyMsgIfRelayReply_wo_IFID.seq DHCPv6_Self_Test_P2_1_0_5/rfc3315/S_RFC3315_17.2.3_Creation-TransmissionOfReplyMsgIfRelayReply_wo_IFID.seq
--- DHCPv6_Self_Test_P2_1_0_5.orig/rfc3315/S_RFC3315_17.2.3_Creation-TransmissionOfReplyMsgIfRelayReply_wo_IFID.seq 2007-02-15 14:24:21.000000000 +0900
+++ DHCPv6_Self_Test_P2_1_0_5/rfc3315/S_RFC3315_17.2.3_Creation-TransmissionOfReplyMsgIfRelayReply_wo_IFID.seq 2007-08-29 19:25:19.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:501:ffff:100::11\")"
+ 'init_opcode' => "vRemote(\"dhcp6s.rmt\", \"start\",\"link0=$V6evalTool::NutDef{Link0_device}\",\"startaddr=3ffe:501:ffff:101::10\",\"endaddr=3ffe:501:ffff:101::11\")"
);
dhcpSvrInit(\%NUT_Server_Config);
diff -upr DHCPv6_Self_Test_P2_1_0_5.orig/rfc3315/S_RFC3315_20.3_Relay-replyConstruction.seq DHCPv6_Self_Test_P2_1_0_5/rfc3315/S_RFC3315_20.3_Relay-replyConstruction.seq
--- DHCPv6_Self_Test_P2_1_0_5.orig/rfc3315/S_RFC3315_20.3_Relay-replyConstruction.seq 2007-02-21 11:01:43.000000000 +0900
+++ DHCPv6_Self_Test_P2_1_0_5/rfc3315/S_RFC3315_20.3_Relay-replyConstruction.seq 2007-08-29 18:38:52.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:101::10\",\"endaddr=3ffe:501:ffff:101::11\",\"valduid=$DUID_CLIENT\")"
+ 'init_opcode' => "vRemote(\"dhcp6s.rmt\", \"start\",\"link0=$V6evalTool::NutDef{Link0_device}\",\"startaddr=3ffe:501:ffff:102::10\",\"endaddr=3ffe:501:ffff:102::11\",\"valduid=$DUID_CLIENT\")"
);
dhcpSvrInit(\%NUT_Server_Config);