Red Hat Bugzilla – Bug 1009051
mtr doesn't wait for last packets sent out and exits immediately
Last modified: 2013-10-18 15:56:42 EDT
Description of problem:
When in report mode with configured number of cycles, mtr exits when number of cycles is reached. However some packets are still on the way, now mtr doesn't wait for them thus producing inaccurate statistics.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. mtr -r -c 10 www.stanford.edu
Packet loss reported for the destination host
No packet loss reported for the destination host
This bug was not entirely correctly fixed in mtr-0.81 (we always sent out more packets to each host then configured number of cycles), but then patch for this got removed in v0.82 without mentioning this in NEWS.
Bug was originally reported here:
Reproducer might depend on your geographic location and hopcount to the destination host.
Created github pull request in order to get this back upstream.
Patch has been merged https://github.com/traviscross/mtr/commit/6ce1601b27fdd95b44ed65d7fd83604860276d63
mtr-0.84-3.fc19 has been submitted as an update for Fedora 19.
mtr-0.85-3.fc20 has been submitted as an update for Fedora 20.
* should fix your issue,
* was pushed to the Fedora 20 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing mtr-0.85-3.fc20'
as soon as you are able to.
Please go to the following url:
then log in and leave karma (feedback).
mtr-0.85-3.fc20 has been pushed to the Fedora 20 stable repository. If problems still persist, please make note of it in this bug report.
mtr-0.84-3.fc19 has been pushed to the Fedora 19 stable repository. If problems still persist, please make note of it in this bug report.