C_RFC3633_12_1_ReqWMultiIAPDOpt.seq - Check the format of Requst with multiple IA_PD options
Client
C_RFC3633_12_1_ReqWMultiIAPDOpt.seq [-tooloption...]
-pkt C_RFC3633_12_1_ReqWMultiIAPDOpt.def
-tooloption : v6eval tool option
See Also DHCPv6.def
NUT(Requesting router)
|
|
Link0 --+--------+------------------------ 3ffe:501:ffff:100::/64
|
|
TN(Delegating router)
The requesting router uses a Request message to populate IA_PDs with
prefixes. The requesting router includes one or more IA_PD options
in the Request 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 Requesting router)
| |
| ----> |Solicit w/two IA_PD options
| <---- |Advertise w/two IA_PD options
| ----> |Request w/two IA_PD options (3*)
| |
(3*)PASS: NUT transmits Request with two IA_PD options.
N/A
Also see RFC3633
12.1. Requesting router behavior
perldoc V6evalTool