Bug 461278 - max TTL value cannot be between 1 and 5 ?
Summary: max TTL value cannot be between 1 and 5 ?
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 5
Classification: Red Hat
Component: traceroute
Version: 5.3
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
: ---
Assignee: Jiri Skala
QA Contact: Milos Malik
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2008-09-05 15:00 UTC by Milos Malik
Modified: 2018-11-14 17:14 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
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.
Clone Of:
Environment:
Last Closed: 2011-04-27 10:05:42 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
Proposed patch for this... (685 bytes, patch)
2008-09-08 13:43 UTC, Dmitry Butskoy
no flags Details | Diff


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2011:0469 0 normal SHIPPED_LIVE traceroute bug fix update 2011-04-27 10:05:36 UTC

Description Milos Malik 2008-09-05 15:00:09 UTC
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:

Comment 1 Milos Malik 2008-09-05 15:04:47 UTC
traceroute-2.0.1-5.el5 on RHEL-5 is also affected

Comment 2 Dmitry Butskoy 2008-09-08 13:30:00 UTC
Oops...

The quick work-around is just to specify `-N 1'.

I'll fix this in upcoming upstream's 2.0.12 ...

Comment 3 Dmitry Butskoy 2008-09-08 13:43:45 UTC
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...

Comment 4 Fedora Update System 2008-09-17 16:19:48 UTC
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

Comment 5 Fedora Update System 2008-09-17 16:21:58 UTC
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

Comment 6 Fedora Update System 2008-10-03 22:28:17 UTC
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.

Comment 7 Fedora Update System 2008-10-03 22:34:21 UTC
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.

Comment 8 Casey Dahlin 2009-03-06 18:28:51 UTC
This is still present in RHEL 5. Could we get the fix applied there?

Comment 9 Dmitry Butskoy 2009-03-06 18:47:12 UTC
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...

Comment 10 RHEL Program Management 2009-03-26 16:56:51 UTC
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 "?".

Comment 11 Dmitry Butskoy 2009-03-26 17:10:48 UTC
Jiri?

Comment 12 Dmitry Butskoy 2009-03-27 13:32:34 UTC
Oh, the patch is already attached. Apply it against the current RHEL version of traceroute.

Comment 13 Casey Dahlin 2009-04-01 15:26:21 UTC
Could someone clarify why 5.4.0 was denied, and what is meant by the 5.5.0 flag at this stage?

Comment 14 Casey Dahlin 2009-04-01 15:32:07 UTC
I've had things clarified, so never mind.

Comment 16 Greg A 2009-11-02 18:29:03 UTC
We need this in RHEL 5.3.  Dmitry, when you say the patch is attached do you mean for Fedora?

Comment 17 Dmitry Butskoy 2009-11-03 12:01:05 UTC
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

Comment 18 Dmitry Butskoy 2009-11-03 12:02:39 UTC
I'm usptream author, but not RHEL man, hence it is task for Jiri...

Comment 19 Greg A 2009-11-03 12:52:21 UTC
Ah, got it.  Sorry I missed the attachment.  Jiri, any update on the inclusion of Dmitry's patch for RHEL 5?

Comment 20 Jiri Skala 2009-11-03 15:00:25 UTC
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

Comment 27 Jaromir Hradilek 2011-04-12 15:11:16 UTC
    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.

Comment 29 errata-xmlrpc 2011-04-27 10:05:42 UTC
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


Note You need to log in before you can comment on or make changes to this bug.