Home ▼ Bookkeeping
Online ▼ Security
Audits ▼
Managed
DNS ▼
About
Order
FAQ
Acceptable Use Policy
Dynamic DNS Clients
Configure Domains Dyanmic DNS Update Password Network
Monitor ▼
Enterprise Package
Advanced Package
Standard Package
Free Trial
FAQ
Price/Feature Summary
Order/Renew
Examples
Configure/Status Alert Profiles | |||
Test ID: | 1.3.6.1.4.1.25623.1.0.104010 |
Category: | Nmap NSE net |
Title: | Nmap NSE net: path-mtu |
Summary: | Performs simple Path MTU Discovery to target hosts.;;TCP or UDP packets are sent to the host with the DF (don't fragment) bit set and with varying;amounts of data. If an ICMP Fragmentation Needed is received, or no reply is received after;retransmissions, the amount of data is lowered and another packet is sent. This continues until;(assuming no errors occur) a reply from the final host is received, indicating the packet reached;the host without being fragmented.;;Not all MTUs are attempted so as to not expend too much time or network resources. Currently the;relatively short list of MTUs to try contains the plateau values from Table 7-1 in RFC 1191, 'Path;MTU Discovery'. Using these values significantly cuts down the MTU search space. On top of that,;this list is rarely traversed in whole because: * the MTU of the outgoing interface is used as a;starting point, and * we can jump down the list when an intermediate router sending a;'can't fragment' message includes its next hop MTU (as described in RFC 1191 and required by;RFC 1812) |
Description: | Summary: Performs simple Path MTU Discovery to target hosts. TCP or UDP packets are sent to the host with the DF (don't fragment) bit set and with varying amounts of data. If an ICMP Fragmentation Needed is received, or no reply is received after retransmissions, the amount of data is lowered and another packet is sent. This continues until (assuming no errors occur) a reply from the final host is received, indicating the packet reached the host without being fragmented. Not all MTUs are attempted so as to not expend too much time or network resources. Currently the relatively short list of MTUs to try contains the plateau values from Table 7-1 in RFC 1191, 'Path MTU Discovery'. Using these values significantly cuts down the MTU search space. On top of that, this list is rarely traversed in whole because: * the MTU of the outgoing interface is used as a starting point, and * we can jump down the list when an intermediate router sending a 'can't fragment' message includes its next hop MTU (as described in RFC 1191 and required by RFC 1812) CVSS Score: 0.0 CVSS Vector: AV:N/AC:L/Au:N/C:N/I:N/A:N |
Copyright | Copyright (C) 2011 NSE-Script: The Nmap Security Scanner; NASL-Wrapper: Greenbone Networks GmbH |
This is only one of 99761 vulnerability tests in our test suite. Find out more about running a complete security audit. To run a free test of this vulnerability against your system, register below. |