TRACEROUTE6(8)

✨ TRACEROUTE6(8) ✨

ok so bestie, welcome to TRACEROUTE6(8), from the System Manager's Manual β€” yes we're in section 8, the big-kid section, the one where the tools that talk to the actual network live πŸ‘‘. Two little binaries hang out in here and they're literally cousins: rltraceroute6 and tcptraceroute6. Let's get into it, no cap.


πŸŽ€ NAME πŸŽ€

rltraceroute6 β€” the IPv6 traceroute tool πŸ¦‹

tcptraceroute6 β€” the TCP/IPv6 traceroute tool 🌸


πŸ’… SYNOPSIS πŸ’…

like, here's how you actually call them:

traceroute6 [-AdEILlnrSU] [-f min_hop] [-g hop] [ -i iface] [-m max_hop]
[-p port] [-q attempts] [ -s source] [-t tclass] [-w wait] [-z delay_ms]
< hostname/address> [packet length]
tcptraceroute6 [-AdEnrS] [-f min_hop] [-g hop] [ -i iface] [-l
packet_size] [-m max_hop] [-p port] [ -q attempts] [-s source] [-t
tclass] [-w wait] [ -z delay_ms] < hostname/address> [port]

🌷 DESCRIPTON 🌷

okay yes, it's spelled "DESCRIPTON" in the original, we do not gatekeep typos here πŸ’… moving on

rltraceroute6 is an IPv6 traceroute implementation, periodt.

What it does is so main character: it shows you the list of hops along the network route between your local system and whatever destination you specified, by sending packets and incrementing their hop limit each time, until the final destination is finally reached 🎯. It's giving "walking the yellow brick road but with TTL".

By default, rltraceroute6 sends UDP probe packets toward the destination (that's the historical default, the OG vibe). BUT. It can also send TCP packets, much like Michael C. Toren's tcptraceroute does on IPv4 networks 🫢; and tcptraceroute6 sends TCP packets by default (and mimics tcptraceroute command line syntax, cute). And finally, it can also send ICMPv6 Echo Request packets, like some other traceroute implementations (such as the one in Microsoft Windows) do; tracert6 does this by default. So many options, so little time 😭.

You must specify the name or address of the host toward which the network route should be determined. An optional additional parameter specifies either the probe packets length (for UDP and ICMP packets), or the destination port number/service name (for TCP packets).

Note that TCP destination port zero really is TCP port numbered 0 (which cannot be used via the standard higer-level TCP/IP programming interface). Like, zero means zero, bestie, not "pick one for me" πŸ’€

⭐ OPTIONS ⭐

  • -A β€” Send TCP/ACK probe packets. That's very efficient against stateless firewalls (e.g. the official Linux kernel versions up to and including 2.4.31 and 2.6.14), and utterly helpless against stateful ones. Note that TCP/ACK probing cannot determine whether the destination TCP port is open or not. πŸ™ˆ
  • -d β€” Enable socket debugging option (SO_DEBUG). Unless you are debugging the kernel, this is probably not going to have any actual effect. It's giving "I turned it on and nothing happened" πŸ’€
  • -E β€” Send ECN-setup TCP/SYN probe packets (as per RFC 3168) rather than non-ECN-setup TCP/SYN probe packets. This has no effect unless command line optin -S is specified as well.
  • -F β€” This option is ignored for backward compatibility. IPv6 packets are never fragmented en route. Iconic behaviour honestly, it just shows up and does nothing πŸŽ€
  • -f β€” Override the initial IPv6 packets hop limit (default: 1).
  • -g β€” Add an IPv6 route segment within an IPv6 Routing Header. This enables loose source routing. Currently, only "Type 0" routing header is supported.
  • -h β€” Display some help and exit. 🫢
  • -I (rltraceroute6 only) β€” Send ICMPv6 Echo requests (like ping6) as probe packets. That's the default for tracert6. πŸ”₯
  • -i β€” Only send packets through the specified interface. See also BUGS.
  • -I (rltraceroute6 only) β€” Send UDP-Lite (protocol 136) packets (with full checksum coverage) as probe packets instead of normal UDP (protocol 17).
  • -l (rltraceroute6 only) β€” Print the hop limit of received packets. This is mostly used to detect asymmetric routing.
  • -l (tcptraceroute6 only) β€” Specify the size (bytes) of sent packets.
  • -m β€” Override the maximum hop limit (maximum number of hops). The default is 30 hops which should be sufficient on the IPv6 Internet for some time. (some time πŸ‘€)
  • -N β€” Try to resolve each hop's IPv6 address to a host name. This is the default. This option is meant for backward compatibility with tcptraceroute(8).
  • -n β€” Do not try to resolve each hop's IPv6 address to a host name. That may speed up the traceroute significantly. ⚑
  • -p β€” For rltraceroute6, specify the base destination port number (default: 33434). rltraceroute6 assumes that packets toward this port up to this port plus the maximum hop limit are not in use by any program on the final destination and that they are not blocked by some firewall. The fact that this very assumption was not always correct, eventually lead to the development of the original IPv4 tcptraceroute by Michael Toren.

For tcptraceroute6, specify the source port number (default: auto). Note that source port number zero really means number zero, rather than some port number that would be automatically assigned, as is the case with usual softwares. πŸ’…

  • -q β€” Override the number of probes sent to each hop (default: 3).
  • -r β€” Do not route packets, i.e. do not send packets through a gateway that would be specified by the routing table. See also BUGS.
  • -S β€” Use TCP/SYN probe packets. That's the default for tcptraceroute6.
  • -s β€” Specify the source address to use for probe packets explicitly.
  • -S β€” Use UDP probe packets. That's the default for rltraceroute6.
  • -t β€” Specify the traffic class (DSCP) for probe packets. See also BUGS.
  • -U (rltraceroute6 only) β€” Send UDP probe packets. That's the default.
  • -V β€” Display program version and license and exit. ✨
  • -w β€” Override the delay (in seconds) to wait for response once a given probe packet was sent (default: 5 seconds).
  • -x β€” This option is ignored for seamless migration from IPv4 traceroute. The IPv6 header has no checksum field. (no checksum bestie, we don't do that here πŸŽ€)
  • -z β€” Specify a milliseconds delay to wait between each probe with identical hop limit. This can be useful to work-around ICMPv6 rate limitation on some hosts. 🐒

πŸ” DIAGNOSTICS πŸ”

If a response is received, the round-trip time is printed. In addition, specific symbols denote certain errors:

  • * β€” No response
    • No valid response received before the timeout delay (see -w option).
  • !N β€” No route to destination
    • There is no entry for the destination network in the routing table.
  • !A β€” Communication with destination administratively prohibited
    • A firewall explicitly rejected the traffic. 🚫
  • !S β€” Beyond scope of source address
    • The address scope of the source address is too small to reach the destination address. At the time of writing, this can only happen when using a link-local source address to reach a global scope destination. (Note: some IPv4 traceroute implementations use !S for source route error which is completely different)
  • !H β€” Address unreachable
    • The host address is not reachable for some other reasons, particularly a link-layer failure (e.g. Neighbor discovery failure).
  • !P β€” Unrecognized Next Header type encountered
    • The destination does not implement the layer-4 protocol used. You should retry with ICMPv6 Echo Requests (-I command line option) which MUST be supported by any IPv6 node. πŸ‘‘

πŸ” SECURITY πŸ”

rltraceroute6 should be setuid root to allow use by non privileged users. It will drop its root privileges before any attempt is made to send or receive data from the network so as to reduce the possible impact of a security vulnerability. Responsible queen behaviour honestly πŸ’…


πŸ’€ BUGS πŸ’€

However useful they might be, -i and -r options are ignored by the official Linux kernel at the time of writing this manpage, and hence do not work as documented. 😭

Support for option -t was broken until Linux kernel version 2.6.18.

Usage of Routing Header, with option -g, triggers an OOPS on Linux kernel versions below 2.6.17.12. πŸ’€

Receiving TCP/SYN-ACK packets does not work on FreeBSD at all. This severely limits the usefulness of tcptraceroute6 on FreeBSD.

Packet length takes the IPv6 header and, if present, extension headers into account. rltraceroute6 versions before 0.7.4 used it as IPv6 payload length instead, i.e. did not include the layer-3 headers in the computation. Linux iputils traceroute6 does not even include the UDP header. On the whole, the packet length semantic is very inconsistent among IPv6 traceroute implementations. 🫠


πŸ¦‹ SEE ALSO πŸ¦‹

ipv6(7), traceroute(8), tcptraceroute(8), traceroute6(8)


πŸ‘‘ AUTHOR πŸ‘‘

RΓ©mi Denis-Courmont <remi at remlab dot net>

http://www.remlab.net/ndisc6/


and that's the whole page bestie!! πŸ’– this one's from the traceroute6 manual source, dated $Date$, and it lives at TRACEROUTE6(8) β€” so go forth, trace those hops, and remember: zero means zero 🌈✨🫢