Dmitry Butskoy

Shunsuke Matsumoto wrote: OPTIONS -4, -6 Explicitly force IPv4 or IPv6 tracerouting. By default, the program will try to resolve the name given, and choose the appropriate protocol automatically. If resolving a host name returns both IPv4 and IPv6 addresses, traceroute will use IPv4. Yes, surely it must be changed. Thanks for the report.

Astrid Yu wrote: Since I'm using it non-interactively, retrieving that information is a bit more of a hassle. Well, maybe just use wrappers? Wrapper is a more correct way here, especially given the non-interactive nature of use. In addition, this is a more universal way, because allows you to add the necessary output functionality without the need for any change in the utilities involved. Sometimes the writing of the wrappers looks difficult or bulky at first glance, but this is a really correct...

Astrid Yu wrote: I know there is a way to explicitly provide a source IP and interface. However, if you don't do that, unless I'm mistaken, I don't believe there is a way to tell what source IP, starting port, and interface is being used. I've looked through the |--help| and I don't think I've found any flags for that, either. ... ||Ideally, I'd like the header to look something like this instead: |traceroute to google.com (64.233.177.113), 30 hops max, 60 byte packets, source IP 192.168.192.168:33434,...

Well, there is already such a patch that has been made for a long time by ALTLinux Distro. That distribution for some reason professes more pedantic warning options, and just like you, uses -W (or -Wextra) by default. Most of the warnings that you reported are taking place due to the fact that the -Wsign-compare option is activated (which is part of the -Wextra set). For the moment, -Wsign-compare is not considered by leading distributions as a mandatory compilation option. For example, neither Fedora...

Sebastian Moeller wrote: FreeBSD's traceroute for IPv4 (a different bninary from traceroute6) has a very interesting diagnostiuc/debug mode that allows to record and then analyse modification to the IP header along a path: Unfortunately we don't have access to the raw IP headers anyway due to implementation limitations. All information is obtained only by the recvmsg(2) system call with the MSG_ERRQUEUE flag set. This way allows unprivileged users to use "udp" and/or "icmp/echo" traces without having...

RFC-3484: Traceroute should defaults to IPv6 instead of IPv4 if possible

Fixed in 2.1.6 .

Enable large file support (LFS)