C_RFC3315_18_1_4_TransReb.seq - Check the format of Rebind
Client
C_RFC3315_18_1_4_TransReb.seq [-tooloption...]
-pkt C_RFC3315_18_1_4_TransReb.def
-tooloption : v6eval tool option
See Also DHCPv6.def
NUT(Client)
|
|
Link0 --+--------+------------------------ 3ffe:501:ffff:100::/64
|
|
TN(Server)
The client sets the "msg-type" field to REBIND.
The client generates a transaction ID and inserts this value in the
"transaction-id" field.
The client MUST include a Client Identifier option to identify itself
to the server. The client adds any appropriate options, including
one or more IA options. The client MUST include the list of
addresses the client currently has associated with the IAs in the
Rebind message.
- 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/IA_NA option(T1=50, T2=80)
| |
| <---- |Echo Request
| ----> |Echo Reply
| |
| |Wait T2 time expire
| |
| ----> |Rebind (7*)
| |
(7*)PASS: NUT transmits Rebind which conforms to Verification Points.
N/A
Also see RFC3315
18.1.4. Creation and Transmission of Rebind Messages
perldoc V6evalTool