Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
According to RHEL 6.4 beta release notes, the new kernel will provide a way
to use ping (icmp echo/icmp echoreply) without root privileges, see:
https://access.redhat.com/knowledge/docs/en-US/Red_Hat_Enterprise_Linux/6-Beta/html-single/6.4_Release_Notes/index.html#sect-Important-Changes-to-External-Kernel-Parameters
It seems that actually it meant the so-called "icmp dgram sockets" (first appeared in the upstream kernel-3.0). If so, the traceroute already support this way, since the version of 2.0.18 .
But the current RHEL6.3 version is 2.0.14 .
IOW, if you want to "traceroute -I" without root privileges (which seems should be possible since the new RHEL6.4 kernel), you should provide traceroute >=2.0.18 in the RHEL6.4
Just a mention from an upstream author... :)
Removing fast and proposing for a regular rebase. Fixing this bug would also fix bug #616420.
Comment 3RHEL Program Management
2013-10-14 00:02:54 UTC
This request was evaluated by Red Hat Product Management for
inclusion in the current release of Red Hat Enterprise Linux.
Because the affected component is not scheduled to be updated
in the current release, Red Hat is unable to address this
request at this time.
Red Hat invites you to ask your support representative to
propose this request, if appropriate, in the next release of
Red Hat Enterprise Linux.
Since the changed behaviour in kernel 3.13, we need traceroute >= 2.0.21 to work properly with `-F' and `--mtu' options (ie. any path mtu discovery features).
Unfortunately, this kernel changes was backported to the current RHEL6 (at least), and now we have this error here (without any changes in traceroute itself -- it was just the kernel change).
Besides that now I've released traceroute-2.0.22. Please, consider this newest version for RHEL needs.
Sorry, I really tried to get the latest version to RHEL-6.
Red Hat Enterprise Linux version 6 is entering the Production 2 phase of its lifetime and this bug doesn't meet the criteria for it, i.e. only high severity issues will be fixed. Please see https://access.redhat.com/support/policy/updates/errata/ for further information.