S_RFC3736_InvalidUDPPorts.seq - Implementation of DHCP constants: Invalid UDP port
Server
S_RFC3736_InvalidUDPPorts.seq [-tooloption ...]
-pkt S_RFC3736_InvalidUDPPorts.def
-tooloption: v6eval tool option
See Also DHCPv6.def
TN(Client1)
|
Link0 -------+-----------+--------------- 3ffe:501:ffff:100::/64
|
NUT(Server1)
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.
- Configuration
| 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 |
NUT TN
| |
| | initialize NUT (as a stateless DHCPv6 Server)
| |
| <---- | Information-request(w/ Option Request option) UDP destination port 33536
| --->X |No DHCPv6 Message (1*)
| |
| |
(1*)PASS: NUT should not send any DHCPv6 messages.
N/A
see also RFC3315
5.2. UDP Ports see also RFC3736
5.1, 5.2 and 5.3
perldoc V6evalTool