Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
For bugs related to Red Hat Enterprise Linux 5 product line. The current stable release is 5.10. For Red Hat Enterprise Linux 6 and above, please visit Red Hat JIRA https://issues.redhat.com/secure/CreateIssue!default.jspa?pid=12332745 to report new issues.

Bug 534087

Summary: ping6 fails if a scope-id is specified for a link scope address
Product: Red Hat Enterprise Linux 5 Reporter: john.haxby <john.haxby>
Component: iputilsAssignee: Jan Synacek <jsynacek>
Status: CLOSED WONTFIX QA Contact: qe-baseos-daemons
Severity: medium Docs Contact:
Priority: low    
Version: 5.4CC: rvokal
Target Milestone: rc   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-03-13 12:13:37 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
Don't circumvent the getaddrinfo() RFC 4007 scope-id address recognition none

Description john.haxby@oracle.com 2009-11-10 14:40:02 UTC
Created attachment 368404 [details]
Don't circumvent the getaddrinfo() RFC 4007 scope-id address recognition

Description of problem:

As a quick check to make sure ipv6 is sort-of working it's useful to be able to ping a remote node.  This is especially useful if the configuration is incomplete and you just want to ping some specific node using its link scope address.  Unfortunately, this doesn't work because ping6 doesn't handle the "address%scope-id" syntax properly (even though the code looks as though it tries).

Version-Release number of selected component (if applicable):
           iputils-20020927-46.el5


How reproducible: Always


Steps to Reproduce:
1. ping6 fe80::206:5bff:fe6b:c8a7%eth0
  
Actual results:
  connect: Invalid argument

Expected results:
  some sort of unreachable destination message unless you happen to have
  a NIC with that MAC address.
  

Additional info:

It is possible to use "-I eth0" but you should be able to use the scope-id like most things that support IPv6 manage: iputils-20071127-8.fc11 gets this right.

The attached patch corrects the over-enthusiastic calling of inet_pton().  This is both unnecessary (getaddrinfo() calls inet_pton() internally) and wrong because the use of inet_pton() means that the RFC 4007 %scope-id is ignored.

Comment 1 john.haxby@oracle.com 2009-11-10 14:46:46 UTC
See also bug 505044.

Comment 5 RHEL Program Management 2010-08-09 18:24:24 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 unfortunately unable to address this
request at this time. Red Hat invites you to ask your support
representative to propose this request, if appropriate and relevant,
in the next release of Red Hat Enterprise Linux.

Comment 6 RHEL Program Management 2011-01-11 20:33:37 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 unfortunately unable to address this
request at this time. Red Hat invites you to ask your support
representative to propose this request, if appropriate and relevant,
in the next release of Red Hat Enterprise Linux.

Comment 7 RHEL Program Management 2011-01-11 22:39:25 UTC
This request was erroneously denied for the current release of
Red Hat Enterprise Linux.  The error has been fixed and this
request has been re-proposed for the current release.

Comment 8 RHEL Program Management 2011-05-31 13:26:16 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 unfortunately unable to address this
request at this time. Red Hat invites you to ask your support
representative to propose this request, if appropriate and relevant,
in the next release of Red Hat Enterprise Linux.

Comment 9 Jan Synacek 2013-03-13 12:13:37 UTC
Red Hat Enterprise Linux 5 has entered Production 2 phase. For more details see https://access.redhat.com/support/policy/updates/errata/. As this bug is not qualified as critical, it is closed as WONTFIX.