I think the following test must be looking for the wrong option?
========== TEST 47 ==========
./S_RFC3315_15.10_ClientIDOPMatch.seq -pkt
./S_RFC3315_15.10_ClientIDOPMatch.def
-log 47.html -ti "Reply message(w/o Client ID option)"
==== NUT Initialization ====
vRemote("dhcp6s.rmt",
"start","link0=eth0","preference=10","startaddr=3ffe:ffff:
100::10","endaddr=3ffe:ffff:100::11")
dhcp6s> Set parameters of DHCPv6 Server manually as following:
dhcp6s> The interfaces used for DHCPv6 Server test is eth0.
dhcp6s> The start address:3ffe:ffff:100::10.
dhcp6s> The end address:3ffe:ffff:100::11.
dhcp6s> The Server Preference value is 10.
dhcp6s>
dhcp6s> Please start the DHCPv6 Server!
dhcp6s> Then press the Enter.
Start Capturing Packets (Link0)
Clear Captured Packets (Link0)
Can not found DUID in this message
Send DHCPv6 Infomation Request Message: CLIENT1 --> all DHCPv6
Servers
InformationRequest Message
DHCPv6 OptionValues
IdentifierIdentifier = 102
Opt_DHCPv6_PreferencePreference = 10
Receive NS NUT --> Any
Send NA: CLIENT1 --> NUT
Receive DHCPv6 Reply Message: NUT --> Any
got DHCPv6 Reply Message
Reply Message
DHCPv6 OptionValues
Opt_DHCPv6_ServerUnicastAddress= 2001:420:3800:4801:203:baff:fe6c:9fb8
Opt_DHCPv6_SIDDUID-LLT HardwareType = 1
DUID-LLT MAC = 00:03:ba:6c:9f:b9
DUID-LLT TIME = 1135784677
IdentifierIdentifier = 102
Opt_DHCPv6_PreferencePreference = 10
NUT return Reply message
Begin check option
NG: The Reply Message includes Client ID option <----- There is no
Client ID option!
DHCPv6 Server stop
dhcp6s> Please stop the DHCPv6 Server!
dhcp6s> Then press the Enter.
Stop Capturing Packets (Link0)
Stop Link0
-> FAIL
Per RFC 3315, an Information-Request message does NOT require a Client
Identifier option. Since none was sent to the server, the server doesn't
return one.
- Bernie