Bug 684909 - Interface can not acquire an IPv6 address via DHCPv6 if no IPv4 address is configured
Summary: Interface can not acquire an IPv6 address via DHCPv6 if no IPv4 address is co...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 5
Classification: Red Hat
Component: initscripts
Version: 5.4
Hardware: All
OS: Linux
unspecified
high
Target Milestone: rc
: ---
Assignee: initscripts Maintenance Team
QA Contact: qe-baseos-daemons
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-03-14 18:51 UTC by Jonathan Barber
Modified: 2011-07-21 12:40 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Previously, if no IPv4 address was configured, then DHCP for an IPv6 address was not carried out. Subsequently, the eth0 interface had the default IPv6 link-local address assigned to it, instead the address that would be allocated to it via IPv6 dhcpd utility. This bug has been fixed in the /etc/sysconfig/network-scripts/ifup-eth script and now, the dhcp6c daemon is started and an IPv6 address is acquired for the address as well as additional information such as DNS servers etc.
Clone Of:
Environment:
Last Closed: 2011-07-21 08:34:00 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2011:1081 0 normal SHIPPED_LIVE initscripts bug fix and enhancement update 2011-07-21 08:33:52 UTC

Description Jonathan Barber 2011-03-14 18:51:57 UTC
Description of problem:
If no IPv4 address is configured, then DHCP for an IPv6 address is not carried out.

Version-Release number of selected component (if applicable):
initscripts-8.45.30-2.el5

How reproducible:
Always

Steps to Reproduce:
1. Configure IPv6 in /etc/sysconfig/network:
NETWORKING=yes
NETWORKING_IPV6=yes
HOSTNAME=foo
2. Configure the network interface in /etc/sysconfig/network-scripts/ifcfg-eth0:
DEVICE=eth0
BOOTPROTO=none
ONBOOT=yes
HWADDR=00:50:56:99:01:38
DHCPV6C=yes

3. Restart networking:
# service network restart

Actual results:
Interface eth0 has the default IPv6 link-local address assigned to it, but not the address that would be allocated to it via IPv6 DHCPD.

Expected results:
The dhcp6c daemon is started and an IPv6 address is acquired for the address as well as additional information such as DNS servers etc. 

Additional info:
This appears to be a bug in the /etc/sysconfig/network-scripts/ifup-eth script at line 234 where it exec's the ifup-post script (because  IPADDR is not specified and   - and therefore never gets to line 305 for configuration of the interface by DHCP.

Comment 2 RHEL Program Management 2011-03-14 19:19:44 UTC
This request was evaluated by Red Hat Product Management for inclusion in a Red
Hat Enterprise Linux maintenance release.  Product Management has requested
further review of this request by Red Hat Engineering, for potential
inclusion in a Red Hat Enterprise Linux Update release for currently deployed
products.  This request is not yet committed for inclusion in an Update
release.

Comment 6 Tomas Capek 2011-07-13 12:28:55 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:
Previously, if no IPv4 address was configured, then DHCP for an IPv6 address was not carried out. Subsequently, the eth0 interface had the default IPv6 link-local address assigned to it, instead the address that would be allocated to it via IPv6 dhcpd utility. This bug has been fixed in the /etc/sysconfig/network-scripts/ifup-eth script and now, the dhcp6c daemon is started and an IPv6 address is acquired for the address as well as additional information such as DNS servers etc.

Comment 7 errata-xmlrpc 2011-07-21 08:34:00 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-1081.html

Comment 8 errata-xmlrpc 2011-07-21 12:40:40 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-1081.html


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