C_RFC3315_21.4.4.4_SendInfoReq.seq - Sending Information-Request message
Client
C_RFC3315_21.4.4.4_SendInfoReq.seq [-tooloption...]
-pkt C_RFC3315_21.4.4.4_SendInfoReq.def
-tooloption : v6eval tool option
See Also DHCPv6.def
NUT(Client)
|
|
Link0 --+--------+------------------------ 3ffe:501:ffff:100::/64
|
|
TN(Server)
If the server has selected a key for the client in a previous message
exchange, the client MUST use the same key to generate the authentication
information throughout the session.
- 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/ Authentication Option
| |
| ----> |Information-Request w/ Authentication Option (1*)
| <---- |Reply w/ Authentication Option
| |
| --X-> |No Information-Request (2*)
| |
(1*)PASS: TN receives Information-Request w/ Authentication Option from NUT.
(1*)PASS: TN doesn't receive Information-Request w/ Authentication Option from NUT.
N/A
see also RFC3315
21.4.4 Client Considerations for Delayed Authentication protocol
21.4.4.4. Sending Information-request Messages
22.11 Authentication Option
perldoc V6evalTool