C_RFC3315_21.4.4.2_RecvAdv.seq - Receiving Advertise Messages
Client
C_RFC3315_21.4.4.2_RecvAdv.seq [-tooloption...]
-pkt C_RFC3315_21.4.4.2_RecvAdv.def
-tooloption : v6eval tool option
See Also DHCPv6.def
NUT(Client)
|
|
Link0 --+--------+------------------------ 3ffe:501:ffff:100::/64
|
|
TN(Server)
The client validates any Advertise messages containing an
Authentication option specifying the delayed authentication protocol
using the validation test.
The client authenticated the Advertise message through which the
client selected the server, the client MUST generate authentication
information for subsequent Request messages sent to the server.
When the client sends a subsequent message, it MUST use the same key
used by the server to generate the authentication information.
- 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 (3*)
| |
(3*)PASS: TN receives Request w/ Authentication Option from NUT.
N/A
see also RFC3315
21.4.2. Message Validation
21.4.4. Client Considerations for Delayed Authentication protocol
21.4.4.2. Receiving Advertise Messages
21.4.4.3. Sending Request, Confirm, Renew, Rebind, Decline or Release
Messages
22.11 Authentication Option
perldoc V6evalTool