Pkt_Too_Big - Verify that the NUT sends Packet Too Big Message
Router
Pkt_Too_Big.seq [-tooloption ...] -p Pkt_Too_Big.def
This test is OFFLINK Network Configuration test.
In this test, TN play a Roll of the Router.
Physical Network configuration
Link0
--------+---------------+--------------
| |
NUT TN
| |
--------+---------------+--------------
Link1
Logical Network Configuration
Host A (TN-Link0)
| Link0
--------+-------+-----------------
|
NUT (globaladdress:B)
|
--------+-------+-----------------
| Link1
Router(TN-Link1)
|
----------------+-------+---------
|
HOST B (OFFLINK_LINK1_GLOBAL_ADDRESS)
In this configuration, Packets are send and received.
for example,
In Logical
HOST B -- Echo Reply --> NUT
Actually, in physical
TN (as Router) -- Echo Reply --> NUT
TN attempt to execute remote command 'vRemote(route.rmt)'.
'route add -inet6 OFFLINK_LINK1_GLOBAL_ADDRESS TN-LINK1-address'
And status of Neighbor Cache Entry for TN's addresses are reachable.
This test verifies that the node sends a Packet Too Big Message
in response to a packet that it can not forward because the packet
is larger than the MTU of the outgoing link.
TN NUT
---------------------------
1.
After NUT is initialized (set static route) , NUT sets
the Link MTU of LINK1 Interface to 1300 .
2.
TN send Echo Request to Host B.
=== echo request ===>
3.
NUT send Packet Too Big Message
<=== Packet Too Big Message ===
<< PASS >>
NUT send a Packet Too Big Message.
<< FAIL >>
NUT do not send a Packet Too Big Message.
=head1 SEE ALSO
perldoc V6evalTool
perldoc V6evalRemote