S_RFC3315_17.2.2_Creation-TransmissionOfAdvertiseMsgwithStatusCodeOP.seq - Respond to the Solicit Message(w/ Status Code options)
Server
S_RFC3315_17.2.2_Creation-TransmissionOfAdvertiseMsgwithStatusCodeOP.seq [-tooloption ...]
-pkt S_RFC3315_17.2.2_Creation-TransmissionOfAdvertiseMsgwithStatusCodeOP.def
-tooloption: v6eval tool option
See Also DHCPv6.def
TN(Client1) TN(Client2)
| |
Link0 -------+----------+--+----------- 3ffe:501:ffff:100::/64
|
NUT(Server1)
Advertise Message for the Client2
msg-type
ADVERTISE(2)
transaction-id
Same as the Solicit Message
Server Identifier option
Any
Client Identifier option
Same as the Solicit Message
Status Code option
NoAddrsAvail(2)
Configuration
- Server setup
Server can only assign 1 address.
| Device Name |
Device Type |
I/F |
Assigned Prefix |
Link Local Addr |
MAC Addr |
| Server1 |
NUT |
Link0 |
3ffe:501:ffff:100::/64 |
NUT's Linklocal address |
NUT's MAC address |
| Client1 |
TN |
Link0 |
3ffe:501:ffff:100::/64 |
fe80::200:ff:fe00:a2a2 |
00:00:00:00:a2:a2 |
| Client2 |
TN |
Link0 |
3ffe:501:ffff:100::/64 |
fe80::200:ff:fe00:a3a3 |
00:00:00:00:a3:a3 |
NUT TN
| |
| | initialize NUT (as a DHCPv6 Server)
| | Client1
| <---- | Solicit
| ----> | Advertise
| <---- | Request
| ----> | Reply
| |
| | Client2
| <---- | Solicit
| ----> | Advertise (w/ Status Code option w/o IA_NA option)(*1)
| |
Messages must be exchanged correctly.
And the Client1 can be assigned a address from the server.
The Client2 receive the Advertise message with Status Code option.
(*1) PASS:Advertise message with only one Status Code option with
code NoAddrsAvail and a status message for the user.
a Server Id option with the server's DUID, and a
Client ID option with the client's DUID.
N/A
see also RFC3315
17.2.2. Creation and Transmission of Advertise Messages
perldoc V6evalTool