C_RFC3315_5_2_InvalidUdpPort.seq - Invalid UDP port
Client
C_RFC3315_5_2_InvalidUdpPort.seq [-tooloption...]
-pkt C_RFC3315_5_2_InvalidUdpPort.def
-tooloption : v6eval tool option
See Also DHCPv6.def
NUT(Client)
|
|
Link0 --+--------+------------------------ 3ffe:501:ffff:100::/64
|
|
TN(Server)
Clients and servers exchange DHCP messages using UDP. Clients listen
for DHCP messages on UDP port 546. Servers and relay agents listen
for DHCP messages on UDP port 547.
To check if the client(NUT) listening UDP port is 546, the server sends
Advertise to NUT. NUT will send Request to TN.
- 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 (1*)
| <---- |Advertise UDP destination port 33536
| ----> |ICMP error message (3*)
| |
(1*)PASS: TN receives Solicit from NUT.
(3*)PASS: TN receives ICMP error message(Destination Unreachable).
N/A
See also RFC3315
6 Client/Server Message Formats
perldoc V6evalTool