| 1 |
| Name Resolver Thread |
| Translates the IP-numbers
like 129.12.15.45 or 69.5.111.2 into nice looking names like
119.at-6-1-0.TR1.NYC9.ALTER.NET or pos1-0-155M.cr1.sca1.us.iasiaworks.net
(technically: converts numeric names into symbolic names) |
|
Priority: |
see "Ping Thread" |
|
DNS-Server: |
Name of the server, that provides the resolving informations.
By default, your standard DNS-server will be used. Select some
well known servers from the list.
|
|
try to auto-detect
DNS: |
tries to extract the DNS data from Windows registry.
Might fail due to some Microsoft chaos. |
|
| 2 |
| New Traceroute Pipeline |
|
Do next trace after ... sec.: |
A new trace is started ... seconds after .... [see next topic] |
|
Allow parallel traces: |
If unchecked, a new trace will start after
the current trace is finished delayed with this values.
If checked, a new trace will be started every time after this
value.
If this option is checked and a trace needs more
time than the new-thread-value, you will get more and more parallel
running traces. There is a hardcoded limit to 10 parallel traces. |
|
Start trace with ... TTL: |
Normaly traces start with a TTL of 1, that is from your computer.
This might not be optimal, if the next host is a router that
does ignore ICMP messages. This will result in a slower trace,
because 3d Traceroute has to wait the full timeout period. So
this setting can be used to start with the trace further on and
ignore the non-responding hosts.
|
|
| 3 |
| Visualization Engine |
|
3d maximum rows:
and
2d maximum rows: |
Number of rows in diagram.
Multiply this value with "do next Trace after", to
get the total time monitored in seconds. If the diagram has reached
its capacity, 10% of the data will be removed.
|
|
Add new data in front: |
The data are added so that new data is added
behind the old data (hey, this is the way we engineers think....).
With this switch, new data will be added in front of the old. |
|
Render queue minimum: |
This value determines how often the render engine is started,
if ping results are in the output queue.
Due to the fact that graphics and redrawing images need a lot
of compilation time, this can reduce load. But you will see not
so smooth images. 3 to 5 could be a good value on slow systems.
Zero forces a redraw everytime data is available. "1"
forces a redraw, if one value is in the queue and
the next value arrives. |
|
Add 0. hop: |
adds the local computer into the trace |
|
show axis description: |
adds the axis names and dimensions |
|
| 4 |
| New Ping Pipeline |
| Do next ping after ... millisec.: |
A new ping to a waypoint is send ... milliseconds after the last
one returned. |
|
| 5 |
| Geo Locations |
|
ignore class D+E IPs: |
those IPs should not occure public in todays Internet technologie.
Save to ignore them. |
|
ignore bogus IPs: |
3d Traceroute has a list of bogus, invalid,
stolen, whatever IPs. Data about this IPs might be invalid. |
|
log HTTP request: |
for debugging only: the Geo Data requests are logged into a file. |
|
my location: |
defines the location of your computer. All private
IPs (10.x, 172.x, 192.168.x) will be assigned to this location.
You need to click the "update locations" button. |
|
edit permanent locations: |
Sometimes it is needed to add extra locations that are not in
the database or to fix the database values. Use this button to access
the location database and enter the location data. |
|
| 6 |
This switches enables/disables the data pipeline to that modul. Or in
non tech talk: turning this off disables the module. |
| 7 |
| Ping Thread |
|
Blocksize: |
This amount of data is send to a host every ping.
Set too high it will congest your internet connection and results
will be stupid. |
|
Timeout: |
This is the time a ping must be answered
within from a host. If not, host is unreachable. |
|
Quick samples: |
After the reply from a waypoint, the ping is repeated this
"times minus one" very fast (without delay).
"1" means only one ping is sent after that, "2"
means after the initial ping two ping are send after that. Measured
result will be the average of all this pings.
Raising the value smoothens the graph, but raises load. |
|
Priority: |
This setting determins the thread priority
of the hostname resolving process and the pinger thread. If it
is set to high, it could interfere each other and block the main
process.
Hostnames and latitude/longitude/altitude are cached, so the
name resover thread is only active at the beginning of a trace. |
|
Ping-Type: |
Choose between ICMP, UDP and TCP
pings.  |
|
socket symbol: |
For UDP and TCP ping types it opens the "socket usage control"
dialog and allows to set the port numbers used by 3d Traceroute
on local and remote side. |
|
TOS/DSCP: |
The IP protocol defines a 'type of service' for data packets.
Basic idea is: Voice-over-IP or similar services need to travel
faster than WEB pages. So if you want to have a deeper look into
the quality of service, you need the option to modifiy the TOS-flag
(Type Of Service). 
Refer to RFC 1349 and RFC 1195 for more details. |
|