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.
Bug 682382 - hardcodes eth0
Summary: hardcodes eth0
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: ppp
Version: 6.1
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Jaroslav Škarvada
QA Contact: BaseOS QE Security Team
URL:
Whiteboard:
Depends On:
Blocks: 682269 1160262 1499211
TreeView+ depends on / blocked
 
Reported: 2011-03-05 02:01 UTC by Bill Nottingham
Modified: 2017-10-06 11:36 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 682381
: 1160262 (view as bug list)
Environment:
Last Closed: 2017-10-04 14:31:38 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)
Patch included in Fedora (27.97 KB, patch)
2014-05-02 15:02 UTC, Michal Sekletar 		no flags Details | Diff
Patch included in Fedora (12.18 KB, patch)
2014-05-02 15:06 UTC, Michal Sekletar 		no flags Details | Diff
Show Obsolete (1) View All

Description Bill Nottingham 2011-03-05 02:01:16 UTC 
+++ This bug was initially created as a clone of Bug #682381 +++

Description of problem:

Network devices can have arbitrary names, and due to
http://fedoraproject.org/wiki/Features/ConsistentNetworkDeviceNaming, will have
different names in Fedora 15. Also, it's possible due to hardware changes, etc. that a box only has eth1, eth2, etc.

ppp-2.4.5/pppd/sys-linux.c:

...
char *
get_first_ethernet()
{
        return "eth0";
}
...
int
ether_to_eui64(eui64_t *p_eui64)
{
...
    strcpy(ifr.ifr_name, "eth0");
    if(ioctl(skfd, SIOCGIFHWADDR, &ifr) < 0)
    {
        close(skfd);
        warn("could not obtain hardware address for eth0");
...

Now, given that it does have fallback code for both of these functions if it fails, I'm not sure it drastically affects functionality at runtime. Filing for completeness.

Version-Release number of selected component (if applicable):

ppp-2.4.5

How reproducible:

By visual inspection.
Comment 2 RHEL Program Management 2011-03-05 02:19:01 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. If you would like it considered as an
exception in the current release, please ask your support
representative.
Comment 5 Suzanne Logcher 2012-02-14 23:07:32 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. If you would like it considered as an
exception in the current release, please ask your support
representative.
Comment 6 RHEL Program Management 2012-09-07 05:09:11 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.
Comment 8 Michal Sekletar 2014-05-02 15:00:48 UTC 
I've recently reworked patch for this bug which was already included in Fedora. We query udev database to get information about network interfaces and then we pick first which looks like ethernet interface.
Comment 9 Michal Sekletar 2014-05-02 15:02:47 UTC 
Created attachment 891913 [details]
Patch included in Fedora
Comment 10 Michal Sekletar 2014-05-02 15:06:28 UTC 
Created attachment 891914 [details]
Patch included in Fedora
Comment 13 Tomáš Hozza 2017-10-04 14:31:38 UTC 
Red Hat Enterprise Linux 6 is in the Production 3 Phase. During the Production 3 Phase, Critical impact Security Advisories (RHSAs) and selected Urgent Priority Bug Fix Advisories (RHBAs) may be released as they become available.

The official life cycle policy can be reviewed here:

http://redhat.com/rhel/lifecycle

This issue does not meet the inclusion criteria for the Production 3 Phase and will be marked as CLOSED/WONTFIX. If this remains a critical requirement, please contact Red Hat Customer Support to request a re-evaluation of the issue, citing a clear business justification. Note that a strong business justification will be required for re-evaluation. Red Hat Customer Support can be contacted via the Red Hat Customer Portal at the following URL:

https://access.redhat.com/
Note You need to log in before you can comment on or make changes to this bug.