[Bug 1354704] [NEW] traceroute --mtu doesn't work on recent kernels

[Launchpad Bug Tracker]

You have been subscribed to a public bug by Graham Inggs (ginggs):

Running traceroute with the --mtu option gives strange output on recent
kernels:

$ traceroute --mtu 8.8.8.8
traceroute to 8.8.8.8 (8.8.8.8), 30 hops max, 65000 byte packets
1 * 0.015 ms * 0.007 ms * 0.006 ms
2 * 0.006 ms * 0.007 ms * 0.006 ms
3 * 0.006 ms * 0.006 ms * 0.006 ms
4 * 0.006 ms * 0.008 ms * 0.007 ms
5 * 0.007 ms * 0.006 ms * 0.006 ms

I see similar numbers up to hop 30 and they appear almost instantly.
In Sid, Ubuntu Utopic and Ubuntu Trusty, traceroute 2.0.20 produces
output as above but 2.0.19 and 2.0.18 all segfault (as in #750759)
with the --mtu option.

In Ubuntu Precise (kernel 3.2), traceroute 2.0.18, 2.0.19 and 2.0.20
all work correctly with the --mtu option.

** Affects: traceroute (Ubuntu)
     Importance: Undecided
         Status: New

** Affects: traceroute (Ubuntu Trusty)
     Importance: Undecided
         Status: New

** Affects: traceroute (Debian)
     Importance: Unknown
         Status: New

-- 
 traceroute --mtu doesn't work on recent kernels
https://bugs.launchpad.net/bugs/1354704
You received this bug notification because you are a member of Ubuntu Sponsors Team, which is subscribed to the bug report.