C_RFC3315_21.4.4.5_RecvReplyInvalid.seq - Receiving Reply Messages and validation test is failed
Client
C_RFC3315_21.4.4.5_RecvReplyInvalid.seq [-tooloption...]
-pkt C_RFC3315_21.4.4.5_RecvReplyInvalid.def
-tooloption : v6eval tool option
See Also DHCPv6.def
NUT(Client)
|
|
Link0 --+--------+------------------------ 3ffe:501:ffff:100::/64
|
|
TN(Server)
If the client authenticated the Advertise it accepted, the client
MUST validate the associated Reply message from the server. The
client MUST discard the Reply if the message fails to pass the
validation test and MAY log the validation failure. If the Reply
fails to pass the validation test, the client MUST restart the DHCP
configuration process by sending a Solicit message.
- Configurations
Enable Delayed Authenticaion Protocol Service
Authenticaion parameter
- DHCP realm: DHCPv6.TEST.EXAMPLE.COM
- Client DUID: ANY
- Key id: 1
- Shared secret key: TAHITEST_VALID12
| Device Name |
Device Type |
Interface |
Address |
Link Local Addr |
MAC Addr |
| Client |
NUT |
Link0 |
|
NUT's Linklocal address |
NUT's MAC address |
| Server |
TN |
Link0 |
3ffe:501:ffff:100:200:ff:fe00:a1a1 |
fe80::200:ff:fe00:a1a1 |
00:00:00:00:a1:a1 |
NUT TN
| |
| |Initialize NUT (as a DHCPv6 client)
| |
| ----> |Solicit w/ Authentication Option
| <---- |Advertise w/ Authentication Option
| ----> |Request w/ Authentication Option
| <---- |Reply w/ invalid Authentication Option (Key id =2)
| |
| ----> |Solicit w/ Authentication Option (5*)
| |
| |
(5*)PASS: TN receives Solicit w/ Authentication Option from NUT.
N/A
see also RFC3315
21.4.4 Client Considerations for Delayed Authentication protocol
21.4.4.5. Receiving Reply Messages
22.11 Authentication Option
perldoc V6evalTool