C_RFC2462_Stateful_less.seq - Stateful and Stateless Address-configuration
Client
C_RFC2462_Stateful_less.seq [-tooloption...]
-pkt C_RFC2462_Stateful_less.def
-tooloption : v6eval tool option
See Also DHCPv6.def
NUT(Client)
|
|
Link0 --+--------+------------------------ 3ffe:501:ffff:100::/64
|
|
TN(Server)
Router Advertisements also contain zero or more Prefix Information
options that contain information used by stateless address
autoconfiguration to generate site-local and global addresses. It
should be noted that the stateless and stateful address
autoconfiguration fields in Router Advertisements are processed
independently of one another, and a host may use both stateful and
stateless address autoconfiguration simultaneously.
- 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
| |
| <---- |RA with M=1 with prefix1(A=0), prefix2(A=1)
| |
| |Initialize NUT(as a DHCPv6 client)
| |
| ----> |Solicit
| <---- |Advertise
| ----> |Request
| <---- |Reply w/IA_NA option(T1=50, T2=80)
| |
| <---- |Echo Request to prefix1's address
| ----> |Echo Reply (7*)
| <---- |Echo Request to prefix2's address
| ----> |Echo Reply (9*)
| ----> |Solicit
| |
(7*) (9*)PASS: TN receives Echo Reply message from NUT.
N/A
Also see RFC2462 Section 4
Also see RFC3315
perldoc V6evalTool