Description of problem:
IPV6 addresses are not assigned to the requested interface by anaconda in the
Version-Release number of selected component (if applicable):
Fedora 9-Alpha anaconda 18.104.22.168
Steps to Reproduce:
1. Install F 9-Alpha from CD in a IPV6 only network in text mode
2. On the interface screen for the ethernet device deselect IPv4 support and
check IPv6 support
3. Select manual address configuration.
Default gw: 2001:838:3ab:1::1
After reboot the file /etc/sysconfig/network-scripts/ifcfg-eth0 contains the
line: IPV6ADDR = none. The file /etc/sysconfig/network contains the line
The ifconfig eth0 command does not show the proper IPv6 address.
The file /etc/sysconfig/network-scripts/ifcfg-eth0 should contain the line
The file /etc/sysconfig/network should contain the lines GATEWAY= and
The command ifconfig eth0 should show the proper IPv6 address.
If I do a network installation intending to use a http installation I deselect
IPv4 and select IPv6 manual configuration. I use the addressing scheme:
Default gw: 2001:838:3ab:1::1
The installation process stops with a: loader received SIGSEGV.
Apparently the IPv6 addressing scheme is badly addled by anaconda.
Created attachment 295166 [details]
Screen after installation use IPv6 only addressing scheme
(In reply to comment #0)
This problem is still present in FC9Beta.
> Additional info:
> If I do a network installation intending to use a http installation I deselect
> IPv4 and select IPv6 manual configuration. I use the addressing scheme:
> Address: 2001:838:3ab:1::22/64
> Default gw: 2001:838:3ab:1::1
> DNS: 2001:838:3ab:1::1
> The installation process stops with a: loader received SIGSEGV.
> Apparently the IPv6 addressing scheme is badly addled by anaconda.
I noticed that Bugzilla Bug 230949: Manual IPv6 configuration for network
install is broken at the end off the discussion addresses the same issue.
*** This bug has been marked as a duplicate of 230949 ***
There are two different issues here: the failure of the network install (same as
in Bug 230949), and the network misconfiguration after a successful install,
which is a different issue. I recall seeing config problems like this with a
v6-only system in F7-test1 (which I forgot to report). Please reopen.
This is fixed in rawhide.
Created attachment 303131 [details]
Screenview from IPv6/IPv4 manual installation
This screen does not make it possible to enter both IPv4 and IPv6 default
gateways and DNS server addresses. Neither is it obvious if you should fill in
IPv4 or IPv6 adressing schemes.
I tested this in rawhide anaconda version 22.214.171.124 dated 2008-04-20. I have
verified, that in a mixed IPv4 and IPv6 installation, using IPv4 DHCP and IPv6
automatic neighbour discovery, the correct network settings are taken to the
settings in /etc/sysconfig/network and
But as soon as I start to use fixed IPv6 addressing scheme in the installation,
although in most of the scenarios anaconda SIGFAULTS (but this is Bug 230949 I
believe), I noticed I can not give anaconda the proper IPv6 default gateway and
nameserver, as I have described in Comment #7. This makes it impossible for
anaconda to configure the above mentioned files properly.
So I don't think this bug is solved completely and should be reopend.
The bug you are encountering, as posted in your screenshot in comment #7, is bug 230949. There are
several issues related to the IPv6 configuration issues in anaconda. Unfortunately, I won't be able to
address all of them in F-9 because it's far to late to make user interface changes. What I can do, is
make what we have now work as best as possible and then fix things up in F-10.
In this bug, what was originally reported is the output to the /etc/sysconfig files was incorrect if you
were doing IPv6-only networking. I verified this and was able to see that, yes, anaconda was not
writing the /etc/sysconfig files correctly when doing IPv6-only. The values for those files are set
during the network postinstall configuration screen, which is after the screen shot you have posted.
During a graphical installer or text install, you will be asked later during installation what you want
your network configuration settings to be. This is done because some people may want different
settings on the final system than what they used for installation.
On that screen, if you edit an individual interface and turn off IPv4 and switch IPv6 to manual and give it
an address an prefix, the values written to /etc/sysconfig will be correct for the static IPv6 address.
Also, the gateway field on the main screen will accept an IPv6 address (even though it's not obvious). If
you give it an IPv6 address, it will write that to /etc/sysconfig/network as IPV6_DEFAULTGW rather than
So, based on the opening comments on this bug, the problem is solved. Unfortunately, bug 230949
(which I'm working on today) prevents you from doing an IPv6-only installation from the very
beginning. But, if you do an install using any other method or IPv4 networking, once you get to the
network postinstall configuration screen, you can change things to IPv6 and have correct values written
What I cannot do now is add another field to prompt for a separate IPv6 gateway. I will be doing that
once F-9 goes out. It's too late to add user interface elements or string changes.
I am working on 230949, but this bug is done based on the original comment. The fix for this bug will
appear in anaconda-126.96.36.199-1.