NAME
C_RFC3315_CnfReply.seq - Test case of Confirm-Reply Exchange
TARGET
Client
SYNOPSIS
C_RFC3315_CnfReply.seq [-tooloption...]
-pkt C_RFC3315_CnfReply.def
-tooloption : v6eval tool option
See Also DHCPv6.def
INITIALIZATION
NUT(Client)
|
|
Link0 --+--------+------------------------ 3ffe:501:ffff:100::/64
|
|
TN(Server)
Whenever a client may have moved to a new link, the prefixes from the
addresses assigned to the interfaces on that link may no longer be
appropriate for the link to which the client is attached. Examples
of times when a client may have moved to a new link include:
o The client reboots.
o The client is physically connected to a wired connection.
o The client returns from sleep mode.
o The client using a wireless technology changes access points.
In any situation when a client may have moved to a new link, the
client MUST initiate a Confirm/Reply message exchange.
- 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 |
TEST PROCEDURE
NUT TN
| |
| |Initialize NUT(as a DHCPv6 client)
| |
| ----> |Solicit
| <---- |Advertise
| ----> |Request
| <---- |Reply
| |
| |interface down/up NUT
| |
| ----> |Confirm (5*)
| <---- |Reply
| |
| <---- |Echo Request
| ----> |Echo Reply (8*)
| |
JUDGEMENT
(5*)PASS: TN receives Confirm from NUT.
(8*)PASS: NUT sends Echo Reply to TN.
TERMINATION
N/A
REFERENCE
Also see RFC3315
SEE ALSO
perldoc V6evalTool