Bug 466306
| Summary: | dhcp6c is not executed if IPv4 is not configured | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Stas <stas_k_spam> |
| Component: | initscripts | Assignee: | Bill Nottingham <notting> |
| Status: | CLOSED DUPLICATE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | 10 | CC: | bill.nickless, michel.zehnder, notting, rvokal |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2009-02-20 14:44:43 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: | |||
BOOTPROTO isn't supposed to be a IPv4 configuration - it's generic. According to ifup-eth script, setting BOOTPROTO enables running dhclient, so having BOOTPROTO off is the only way to avoid IPv4 configured on host, if DHCP server is configured on network. Also sysconfig.txt says that there's separate option to enable DHCP6:
IPv6-only option to enable DHCPv6 client:
DHCPV6C=yes|no
This will enable the DHCPv6 client, dhcp6c, to be run for the interface. See man dhcp6c(8) and dhcp6c.conf(5).
To clarify: it is not clear what settings you think should be set for a system which is configured via DHCPv6 with IPv4 disabled -- could you please give an example? Your point is correct, but BOOTPROTO was *supposed* to be generic, alas, the IPv6 configuration parameters weren't well thought out. This bug appears to have been reported against 'rawhide' during the Fedora 10 development cycle. Changing version to '10'. More information and reason for this action is here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping I've got the same problem.
Having NO IPv4 address, and DHCP6C for IPv6 does not work.
DHCP6C initialization is missing in /etc/sysconfig/network-scripts/ifup-eth after:
-----
Line 225: /etc/sysconfig/network-scripts/ifup-ipv6 ${CONFIG}
-----
Needs DHCP Code added there:
-----
if [[ "${DHCPV6C}" = [Yy1]* ]] && [ -x /sbin/dhcp6c ]; then
/sbin/dhcp6c ${DEVICE};
dhcp6_pid=(`/bin/ps -eo 'pid,args' | /bin/grep "dhcp6c ${DEVICE}" | egrep -v grep`);
echo ${dhcp6_pid[0]} > /var/run/dhcp6c_${DEVICE}.pid
fi
-----
It then works as expected.
*** This bug has been marked as a duplicate of bug 486507 *** |
Description of problem: dhcp6c is executed in the very end of ifup-eth. Control doesn't reach that point if IPv4 is not configured, because of: if [ "${BOOTPROTO}" = "bootp" -o "${BOOTPROTO}" = "dhcp" ]; then DYNCONFIG=true fi ............ if [ -n "${DYNCONFIG}" -a -x /sbin/dhclient ]; then ............. else if [ -z "${IPADDR}" ]; then ............... /etc/sysconfig/network-scripts/ifup-ipv6 ${CONFIG} exec /etc/sysconfig/network-scripts/ifup-post ${CONFIG} ${2} fi Version-Release number of selected component (if applicable): initscripts-8.76.2 How reproducible: always Steps to Reproduce: 1. set the following in /etc/sysconfig/network-scripts/ifcfg-eth0 DHCPV6C=yes IPV6INIT=yes 2. make sure that IPV4 configuration is turned off in ifcfg-eth0 (BOOTPROTO, IPADDR are not set) 3. ifup eth0 4. ps axlww | grep dhc Actual results: dhcp6c is not running Expected results: dhcp6c should be running Additional info: