C_RFC3315_18_1_TransUCast.seq - Check the case that Client Unicast DHCPv6 message
Client
C_RFC3315_18_1_TransUCast.seq [-tooloption...]
-pkt C_RFC3315_18_1_TransUCast.def
-tooloption : v6eval tool option
See Also DHCPv6.def
NUT(Client)
|
|
Link0 --+--------+------------------------ 3ffe:501:ffff:100::/64
|
|
TN(Server)
If the client has a source address of sufficient scope that can be
used by the server as a return address, and the client has received a
Server Unicast option from the server, the client SHOULD unicast Renew
to the server.
- Configurations
| Device Name |
Device Type |
Interface |
Assigned Prefix |
Link Local Addr |
MAC Addr |
| Client |
NUT |
Link0 |
3ffe:501:ffff:100::/64 |
NUT's Linklocal address |
NUT's MAC address |
| Server |
TN |
Link0 |
3ffe:501:ffff:100::/64 |
fe80::200:ff:fe00:a1a1 |
00:00:00:00:a1:a1 |
NUT TN
| |
| |Initialize NUT (as a DHCPv6 Client)
| |
| ----> |Solicit
| |
| <---- |Advertise
| |
| ----> |Request
| |
| <---- |Reply w/Server unicast option(T1=50,T2=80)
| |
| |Before T1 time expires
| |
| ----> |Renew (5*)
| |
(5*)PASS: Renew message is a unicast packet.
N/A
Also see RFC3315
18.1. Client Behavior
22.12. Server Unicast Option
perldoc V6evalTool