1Smokeping_probes_TraceroutePing(3) SmokePingSmokeping_probes_TraceroutePing(3)
2
3
4

NAME

6       Smokeping::probes::TraceroutePing - use traceroute to obtain RTT for a
7       router
8

SYNOPSIS

10        *** Probes ***
11
12        +TraceroutePing
13
14        binary = /usr/bin/traceroute # mandatory
15        binaryv6 = /usr/bin/traceroute6
16        forks = 5
17        offset = 50%
18        step = 300
19        timeout = 15
20
21        # The following variables can be overridden in each target section
22        desthost = www.example.com # mandatory
23        host = www-net-router.example.com # mandatory
24        maxttl = 15
25        minttl = 11
26        pings = 5
27        wait = 3
28
29        # [...]
30
31        *** Targets ***
32
33        probe = TraceroutePing # if this should be the default probe
34
35        # [...]
36
37        + mytarget
38        # probe = TraceroutePing # if the default probe is something else
39        host = my.host
40        desthost = www.example.com # mandatory
41        host = www-net-router.example.com # mandatory
42        maxttl = 15
43        minttl = 11
44        pings = 5
45        wait = 3
46

DESCRIPTION

48       Integrates standard traceroute as a probe into smokeping.  The use case
49       for this probe is gateways that do not respond to TCP/UDP/ICMP packets
50       addressed to them, but do return ICMP TTL_EXCEEDED packets for
51       traceroute packets to a host they route to.  It is best used in
52       situations where routing for the path is static or nearly so;
53       attempting to use this on networks with changing routing will yield
54       poor results.  The best place to use this probe is on first- and last-
55       mile links, which are more likely to have static routing and also more
56       likely to have firewalls that ignore ICMP ECHO_REQUEST.
57
58       The mandatory probe variable binary must have an executable path for
59       traceroute.
60
61       The optional probe variable binaryv6 sets an executable path for your
62       IPv6 traceroute.  If this is set to the same value as binary,
63       TraceroutePing will use the -6 flag when running traceroute for IPv6
64       addresses.  If this variable is not set, TraceroutePing will try to
65       find an functioning IPv6 traceroute.  It will first try appending "6"
66       to the path in binary, then try including the "-6" flag in a test
67       command.  Note that Linux appears to have a wide variety of IPv6
68       traceroute implementations.  My Ubuntu 14.04 machine has
69       /usr/sbin/traceroute6 from iputils, but /usr/bin/traceroute (from
70       Dmitry Butskoy) accepts the -6 flag and is actually a better
71       implementation.  You may need to let TraceroutePing autodetect this, or
72       experiment to find the best traceroute.
73
74       The mandatory target variable desthost must name a destination host for
75       the probe.  The destination host itself is not of interest and no data
76       is gathered on it, its only purpose is to route traffic past your
77       actual target.  Selection of a destination just past your target, with
78       static or strongly preferred routing through your target, will get
79       better data.
80
81       The mandatory target variable host must name the target host for the
82       probe.  This is the router that you want to collect RTT data for.  This
83       variable must either be the valid reverse-lookup name of the router, or
84       its IP address.  Using the IP address is preferable since it allows us
85       to tell traceroute to avoid DNS lookups.
86
87       The target variables minttl and maxttl can be used to describe the
88       range of expected hop counts to host.  On longer paths or paths through
89       unresponsive gateways or ending in unresponsive hosts, this reduces the
90       amount of time this probe takes to execute.  These default to 1 and 30.
91
92       The target variables wait sets the traceroute probe timeout in seconds.
93       This defaults to 1, instead of the traditionally higher value used by
94       LBL traceroute.  Traceroute programs often enforce a lower bound on
95       this value.
96

VARIABLES

98       Supported probe-specific variables:
99
100       binary
101           The location of your traceroute binary.
102
103           Example value: /usr/bin/traceroute
104
105           This setting is mandatory.
106
107       binaryv6
108           The location of your IPv6 traceroute binary.
109
110           Example value: /usr/bin/traceroute6
111
112       forks
113           Run this many concurrent processes at maximum
114
115           Example value: 5
116
117           Default value: 5
118
119       offset
120           If you run many probes concurrently you may want to prevent them
121           from hitting your network all at the same time. Using the probe-
122           specific offset parameter you can change the point in time when
123           each probe will be run. Offset is specified in % of total interval,
124           or alternatively as 'random', and the offset from the 'General'
125           section is used if nothing is specified here. Note that this does
126           NOT influence the rrds itself, it is just a matter of when data
127           acqusition is initiated.  (This variable is only applicable if the
128           variable 'concurrentprobes' is set in the 'General' section.)
129
130           Example value: 50%
131
132       step
133           Duration of the base interval that this probe should use, if
134           different from the one specified in the 'Database' section. Note
135           that the step in the RRD files is fixed when they are originally
136           generated, and if you change the step parameter afterwards, you'll
137           have to delete the old RRD files or somehow convert them. (This
138           variable is only applicable if the variable 'concurrentprobes' is
139           set in the 'General' section.)
140
141           Example value: 300
142
143       timeout
144           How long a single 'ping' takes at maximum
145
146           Example value: 15
147
148           Default value: 5
149
150       Supported target-specific variables:
151
152       desthost
153           Final destination host for traceroute packets.  Does not have to be
154           reachable unless it is also your host.
155
156           Example value: www.example.com
157
158           This setting is mandatory.
159
160       host
161           Host of interest to monitor.  Must be either the host's reverse-
162           lookup name, or an IP address.
163
164           Example value: www-net-router.example.com
165
166           This setting is mandatory.
167
168       maxttl
169           Maximum TTL.  Set to the maximum expected number of hops to host.
170
171           Example value: 15
172
173       minttl
174           Minimum TTL.  Set to the minimum expected number of hops to host.
175
176           Example value: 11
177
178       pings
179           How many pings should be sent to each target, if different from the
180           global value specified in the Database section. Note that the
181           number of pings in the RRD files is fixed when they are originally
182           generated, and if you change this parameter afterwards, you'll have
183           to delete the old RRD files or somehow convert them.
184
185           Example value: 5
186
187       wait
188           Waittime.  The timeout value for traceroute's probes, in seconds.
189
190           Example value: 3
191

AUTHORS

193       John Hood <cgull@glup.org>,
194

SEE ALSO

196       smokeping_extend
197
198
199
2002.7.2                             2019-07-26Smokeping_probes_TraceroutePing(3)
Impressum