** Description changed:

+ [SRU] The debdiff attached to comment #4 backports traceroute 1:2.0.20-2 from 
Utopic to Trusty and fixes the following bugs present in 1:2.0.19-3 in Trusty:
+  - Fix segfault with --mtu (LP: #1330558)
+  - Fix --mtu on recent kernels (LP: #1354704)
+ 
+ [IMPACT]
+ Users of traceroute in Trusty are unable to make use of the --mtu option to 
discover the MTU along the path being traced.  This works fine in Precise.
+ 
+ [Test Case]
+ Run traceroute with the --mtu option, e.g.:
+ traceroute --mtu 8.8.8.8
+ 
+ Expected behaviour: a regular traceroute of the path to the host is
+ printed, including F=<NUM> at the hops where the MTU is reached.
+ 
+ Actual behaviour (in Trusty): segmentation fault.
+ 
+ [Regression Potential]
+ Minimal: traceroute is recommended by netperfmeter, subnetcalc and xorp, and 
depended on by libnet-traceroute-perl and zentyal-network.
+ 
+ -----------------------------------------------------------------------------
+ 
  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.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1354704

Title:
   traceroute --mtu doesn't work on recent kernels

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/traceroute/+bug/1354704/+subscriptions

-- 
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to