Description of problem:
The installer asks for IPv6 addresses, but does not ask for an IPv6 default
gateway. It also forgets IPV6INIT=yes in the
/etc/sysconfig/network-scripts/ifcfg-* files, although it does put in the
Version-Release number of selected component (if applicable):
Install a system and provide IPv6 addresses
Steps to Reproduce:
2.Continue to networking settings
3.Enter IPv6 addresses
4.Notice missing default gateway information
6.Check /etc/sysconfig/network: no IPV6_DEFAULTGW
7.Check /etc/sysconfig/network-scripts/ifcfg-eth0, no IPV6INIT
We can add IPV6INIT easily, but prompting for the default gateway for manual
installs isn't doable for 5.2. We have to implement that in Fedora first.
Adding devel-ack, but for IPV6INIT only.
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
Backported from rawhide code with no test.
/etc/sysconfig/network-scripts/ifcfg-eth* sure contains IPV6INIT=yes line.
Nonetheless, the IPv6 address I had set for eth0 during installation has vanished.
In anaconda, I have selected manual IPv6 configuration for eth0 interface and
put a custom value in. After the reboot, IPv6 was active on eth0, but eth0
was using it's site-local address (instead of the one I had specified in
anaconda -- most likely caused by IPV6ADDR=none line in the ifcfg-eth0 file).
I'm not sure whether this is related or not -- anyway, I'll be happy to open
a new bugzilla for this if needed.
Created attachment 294104 [details]
Created attachment 294105 [details]
I'm verifying presence of IPV6INIT=yes line in ifcfg-eth* file
I'm not sure whether the problem with IPV6ADDR=none I mentioned in comment #7
is a bug or a feature, but I filed a new bz for it: bug #432035.
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 the 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.