Package: traceroute Version: 1:2.1.0-3 Severity: wishlist Tags: upstream ipv6
Hi, The traceroute binary can currently be used with both address families, IPv4 and IPv6, which is great! However, contrary to how i.e ping behaves traceroute does not chose to use ipv6 when a AAAA dns record exists for the destination of the trace and one needs to explicitely specify -6 to get a trace over ipv6. In the grand mission of pushing internet users more and more towards IPv6, it would make more sense to default to ipv6 whenever it's possible and fallback to IPv4 otherwise. Note: I've only tested the above-mentioned behavior on debian bullseye (so with libc6 2.31) since I don't currently have a debian sid system that's connected to IPv6. -- System Information: Debian Release: bookworm/sid APT prefers unstable APT policy: (500, 'unstable') merged-usr: no Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.18.0-4-amd64 (SMP w/4 CPU threads; PREEMPT) Kernel taint flags: TAINT_WARN Locale: LANG=en_CA.utf8, LC_CTYPE=en_CA.utf8 (charmap=UTF-8) (ignored: LC_ALL set to en_CA.utf8), LANGUAGE not set Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages traceroute depends on: ii libc6 2.34-4 traceroute recommends no packages. traceroute suggests no packages. -- no debconf information
