183
edits
Names and look-ups: Difference between revisions
Traceroute tab
(Traceroute tab) |
|||
| Line 141: | Line 141: | ||
The DNS resolving can also be configured to run periodically after an interval passed and try to resolve IPs of certain given subnets. To prevent high load on the DNS server, only 5 queries may be active in parallel. | The DNS resolving can also be configured to run periodically after an interval passed and try to resolve IPs of certain given subnets. To prevent high load on the DNS server, only 5 queries may be active in parallel. | ||
= Traceroute = | |||
(Starting from v3.7) | |||
The Allegro Network Multimeter can perform a traceroute to IP addresses using the management interface. | |||
Discovering the network hops to reach the target can take a considerable amount of time. | |||
To trade between a swift and complete result, the following settings can be adjusted to meet the requirements: | |||
* '''Ping count on each network hop''': higher values can compensate occasional packet losses and make the displayed packet loss ratio more representative, but increase the traceroute duration | |||
* '''Maximum TTL value''': upper limit of discoverable network hops; lower values reduce traceroute duration but may cut off some network hops closer to the target IP | |||
* '''Timeout per network hop''': duration of milliseconds to wait for a hop response before it fails as timed out; higher values may discover more network hops at the expense of an increased traceroute duration | |||
The currently displayed settings will be applied after clicking the '''Save settings''' button. | |||
To show the currently used settings, the '''Reload settings''' button needs to be clicked. | |||
The default values can be shown by clicking the '''Load default settings''' button, they are not automatically applied. | |||