•
Max TCP Length - Maximum size of a TCP packet (default: 1480 bytes).
However, the MTU value of the individual NetDefendOS interfaces determines how the packet
size is split. For example, the maximum UDP length could be set to 60,000 but the interface MTU
size might be 1500 so packets would be split into 41 fragments (60,000/1500).
Keeping these maximum settings to the lowest possible value is beneficial since unreasonably
large packets can be used as a form of attack and they are immediately rejected by NetDefendOS
when they exceed the set maximum.
TCP Length
With TCP, all normally configured TCP stacks will limit the size of TCP packets to the negotiated
Maximum Segment Size
(MSS) value. This MSS value will normally be the MTU value minus the IP
header size of 20 bytes. With an MTU value of 1500 bytes, the MSS will be 1480 bytes and this will
normally never need to be fragmented.
2.6.9. The selftest Command
It may be the case that operational problems are caused by a problem with the hardware
platform and not NetDefendOS. For this reason, the CLI command
selftest
is provided to perform
tests on various aspects of hardware functioning.
Warning: Do NOT conduct tests with live traffic!
It is important to remember that the
selftest
command should not be used on a system
that is carrying live traffic. The command can cause connections and associated data to
be lost and the test results themselves will be unreliable.
Preparing Hardware
To ensure the complete reliability of any selftest, it is recommended to take a complete backup
of the current configuration and reset the hardware unit to the base configuration as well as
having the unit disconnected from any networks.
This is also true for units in an HA cluster. The cluster should be broken up into two separated
hardware units and they should each be reset to the base configuration.
Resetting to the base configuration can be done through the CLI or Web Interface. Using the CLI,
the command is:
gw-world:/> reset -configuration
A Simple Example
A simple use of
selftest
is to test the system memory:
gw-world:/> selftest -memory
This writes a one megabyte block of data to memory and reads it back. The number of
megabytes written can be varied using the
-num=
option. By default, the memory test is
repeated once but could, for example, be repeated 10 times with the command:
gw-world:/> selftest -memory -num=10
Chapter 2: Management and Maintenance
133
Summary of Contents for NetDefendOS
Page 30: ...Figure 1 3 Packet Flow Schematic Part III Chapter 1 NetDefendOS Overview 30 ...
Page 32: ...Chapter 1 NetDefendOS Overview 32 ...
Page 144: ...Chapter 2 Management and Maintenance 144 ...
Page 284: ...Chapter 3 Fundamentals 284 ...
Page 392: ...Chapter 4 Routing 392 ...
Page 419: ... Host 2001 DB8 1 MAC 00 90 12 13 14 15 5 Click OK Chapter 5 DHCP Services 419 ...
Page 420: ...Chapter 5 DHCP Services 420 ...
Page 573: ...Chapter 6 Security Mechanisms 573 ...
Page 607: ...Chapter 7 Address Translation 607 ...
Page 666: ...Chapter 8 User Authentication 666 ...
Page 775: ...Chapter 9 VPN 775 ...
Page 819: ...Chapter 10 Traffic Management 819 ...
Page 842: ...Chapter 11 High Availability 842 ...
Page 866: ...Default Enabled Chapter 13 Advanced Settings 866 ...
Page 879: ...Chapter 13 Advanced Settings 879 ...