Description of problem: When I run traceroute with TTL lower than 6 I get "sim hops out of range" message. I thought that max TTL is between 0 and 255. traceroute from traceroute-1.4a12-25.EL4.1 package has no problem with max TTL value between 1 and 5. Version-Release number of selected component (if applicable): traceroute-2.0.10-1.fc8 How reproducible: Always Steps to Reproduce: $ traceroute -m 5 redhat.com sim hops out of range $ echo $? 2 $ Actual results: traceroute rejects max TTL value between 1 and 5 Expected results: traceroute accepts max TTL value between 1 and 255 Additional info:
traceroute-2.0.1-5.el5 on RHEL-5 is also affected
Oops... The quick work-around is just to specify `-N 1'. I'll fix this in upcoming upstream's 2.0.12 ...
Created attachment 316080 [details] Proposed patch for this... It just removes the initial check for `sim_probes' value, as such a check is actually unneeded...
traceroute-2.0.12-1.fc9 has been submitted as an update for Fedora 9. http://admin.fedoraproject.org/updates/traceroute-2.0.12-1.fc9
traceroute-2.0.12-1.fc8 has been submitted as an update for Fedora 8. http://admin.fedoraproject.org/updates/traceroute-2.0.12-1.fc8
traceroute-2.0.12-1.fc9 has been pushed to the Fedora 9 stable repository. If problems still persist, please make note of it in this bug report.
traceroute-2.0.12-1.fc8 has been pushed to the Fedora 8 stable repository. If problems still persist, please make note of it in this bug report.
This is still present in RHEL 5. Could we get the fix applied there?
Just update RHEL to the latest upstream (2.0.12). As the upstream author, I have no any bug report since 2.0.12 from any distros...
This request was evaluated by Red Hat Product Management for inclusion, but this component is not scheduled to be updated in the current Red Hat Enterprise Linux release. If you would like this request to be reviewed for the next minor release, ask your support representative to set the next rhel-x.y flag to "?".
Jiri?
Oh, the patch is already attached. Apply it against the current RHEL version of traceroute.
Could someone clarify why 5.4.0 was denied, and what is meant by the 5.5.0 flag at this stage?
I've had things clarified, so never mind.
We need this in RHEL 5.3. Dmitry, when you say the patch is attached do you mean for Fedora?
The attached patch (see comment #3) was for the current RHEL version... Anyway, it is much better to upgrade to the one-year-stable upstream's 2.0.12
I'm usptream author, but not RHEL man, hence it is task for Jiri...
Ah, got it. Sorry I missed the attachment. Jiri, any update on the inclusion of Dmitry's patch for RHEL 5?
This component was not scheduled to be updated in release 5.5. Please, contact redhat.com/support if you would like to review this decision. Jiri
Technical note added. If any revisions are required, please edit the "Technical Notes" field accordingly. All revisions will be proofread by the Engineering Content Services team. New Contents: Prior to this update, using the "-m" command line option to specify the maximum time-to-live (TTL) value in the range 1 to 5 caused the traceroute utility to fail with the following error: sim hops out of range This update applies an upstream patch to ensure that all TTL values in the range from 1 to 255 are supported as expected.
An advisory has been issued which should help the problem described in this bug report. This report is therefore being closed with a resolution of ERRATA. For more information on therefore solution and/or where to find the updated files, please follow the link below. You may reopen this bug report if the solution does not work for you. http://rhn.redhat.com/errata/RHBA-2011-0469.html