C_RFC3315_18_1_8_ReqReplyAllIAStatusNoAddrAvail.seq - Check Reply with all IAs with status code of NoAddrsAvail
Client
C_RFC3315_18_1_8_ReqReplyAllIAStatusNoAddrAvail.seq [-tooloption...]
-pkt C_RFC3315_18_1_8_ReqReplyAllIAStatusNoAddrAvail.def
-tooloption : v6eval tool option
See Also DHCPv6.def
NUT(Client)
|
|
Link0 --+--------+------------------------ 3ffe:501:ffff:100::/64
|
|
TN(Server)
If the client receives no addresses in any of the IAs, it may
either try another server (perhaps restarting the DHCP server
discovery process) or use the Information-request message to
obtain other configuration information only.
- 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/Status code/NoAddrsAvail
| |
| ----> |Solicit or Information-reqeust (5*)
| |
(5*)PASS: NUT transmits Solicit or Information-request.
N/A
Also see RFC3315
18.1.8. Receipt of Reply Messages
perldoc V6evalTool