Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 230949 - Manual IPv6 configuration for network install is broken
Summary: Manual IPv6 configuration for network install is broken
Alias: None
Product: Fedora
Classification: Fedora
Component: libdhcp
Version: rawhide
Hardware: i386
OS: Linux
Target Milestone: ---
Assignee: David Cantrell
QA Contact:
Depends On:
Blocks: IPv6Blocker F9Blocker
TreeView+ depends on / blocked
Reported: 2007-03-04 23:58 UTC by Mark McClelland
Modified: 2008-04-22 03:11 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2008-04-22 03:11:02 UTC

Attachments (Terms of Use)

Description Mark McClelland 2007-03-04 23:58:37 UTC
Description of problem:
If I configure an Ethernet interface manually when setting up for an IPv6 HTTP
install, the settings I entered are not used according to ifconfig. Instead, it
looks like the interface is set up with stateless autoconfig. Also, the address
of the gateway is assigned to the interface. This network has an radvd server,
and no DHCP/DHCPv6 or available IPv4 addresses.

Version-Release number of selected component (if applicable):
Fedora 7 test 2 (i386 or x86_64)

How reproducible:
Every time

Steps to Reproduce:
1. Start anaconda from CD (boot.iso)
2. Choose HTTP install source
3. Choose network interface
4. At "Configure TCP/IP" dialog, uncheck "Enable IPv4 support"
5. Select "Enable IPv6 support" and choose "Manual configuration"
6. On "Manual TCP/IP Configuration" dialog, I entered this info:
  IPv6 address: 2001:470:1f01:2931::42 / 64
  Gateway:      2001:470:1f01:2931::0
  Name Server:  2001:470:1f01:2931::0
7. Enter HTTP server info and wait for X to start

Actual results:
ifconfig output:
eth1    Link encap:Ethernet  HWaddr 00:0F:B5:FB:3B:28
        inet6 addr: 2001:470:1f01:2931::/0 Scope:Global
        inet6 addr: fec0::1:20f:b5ff:fefb:3b28/64 Scope:Site
        inet6 addr: 2001:470:1f01:2931:20f:b5ff:fefb:3b28/64 Scope:Global
        inet6 addr: fe80::20f:b5ff:fefb:3b28/64 Scope:Link
        UP BROADCAST RUNNING MTU:1500 Metric:1

Expected results:
eth1    Link encap:Ethernet  HWaddr 00:0F:B5:FB:3B:28
        inet6 addr: fec0::1:20f:b5ff:fefb:3b28/64 Scope:Site
        inet6 addr: 2001:470:1f01:2931::42/64 Scope:Global
        inet6 addr: fe80::20f:b5ff:fefb:3b28/64 Scope:Link

Additional info:
Here's the routing table (global unicast addresses only). The first entry looks
wrong (but consistent with the ifconfig output).

#route -n -A inet6
Kernel IPv6 routing table
Destination                Next Hop                 Flags Metric Ref Use Iface
2001:470:1f01:2931::/128   2001:470:1f01:2931::     UAC   0      6     0 eth1
2001:470:1f01:2931::/64    ::                       UA    256    35    0 eth1
::/0                       2001:470:1f01:2931::     UG    1024   0     0 eth1
2001:470:1f01:2931:20f:b5ff:fefb:3b28/128    ::     U     0      56270 1 lo

Comment 1 David Cantrell 2007-03-05 15:42:52 UTC
Excellent debugging info, thanks (we don't usually get detailed reports like
this)!  DHCP (for IPv4 and IPv6) in anaconda's loader is handled by libdhcp, so
I've reassigned the component.

Comment 2 David Cantrell 2007-03-08 20:00:46 UTC
OK, so it wasn't in libdhcp.  It was in anaconda's use of libdhcp.  Fixed in
rawhide.  Thanks.

Comment 3 Mark McClelland 2007-03-17 03:01:29 UTC
I'm still seeing this in the Mar. 14 rawhide. I tried using three unique
addresses for the IPv6 address, gateway, and nameserver, and I can confirm that
the gateway text field is where the bogus 2001:470:1f01:2931::/0 address is
coming from.

Comment 4 Matthew Miller 2007-04-06 20:23:08 UTC
This isn't obvious anywhere, but Fedora 7 test bugs should be filed against the
"devel" version.

Comment 5 David Cantrell 2007-05-22 20:31:27 UTC
I think I have this fixed up.  It was staring at me for a while and I kept
overlooking it.

I wasn't disabling the auto neighbor discovery for IPv6 when you select manual
IPv6 configuration in anaconda.  So anaconda would take the information for you,
set it, and then drive over it with the auto discovery garbage.

When you select manual IPv6 configuration, I disable both DHCPv6 *and* auto
neighbor discovery.  Code is checked in to anaconda CVS, will show up in rawhide
the next time we rebuild anaconda.  Going ahead and marking this as closed rawhide.


Comment 6 Mark McClelland 2007-05-26 05:36:03 UTC
Thanks for trying to get a fix in under the wire, but it appears that your fix
needs fixing. I get the error below after entering my IPv6 addresses and hitting
OK. I couldn't get it to happen with IPv4 (manual or otherwise) or IPv6
autoconf, so I suspect it's related to your fix. If not, I can open a new bug.

loader received SIGSEGV! Backtrace:
install exited abnormally [1/1]

Comment 7 David Cantrell 2007-05-29 15:11:42 UTC
Damn.  Yeah, totally related.  I'll get on this, but the window for getting
fixes in for Fedora 7 is closed.  I can get this fixed up and provide you with a
custom initrd.img for F-7 that has the fix.  I hate to leave you hanging where
you can't get it installed in your environment.

First things first, let me reproduce this and get it fixed, then we test, then I
can make you custom initrds (or show you how).

Comment 8 Mark McClelland 2007-05-30 03:12:29 UTC
Don't worry, I'm only trying to install this way for better testing coverage. I
normally use IPv6 autoconfig instead, and I suspect that most IPv6 users do the
same (or use DHCPv6). I'd be glad to test a custom initrd though, since I'm sure
someone else will want it eventually.

Comment 9 David Cantrell 2008-02-09 03:04:23 UTC
Is this happening for you with the current development releases?

Comment 10 Mark McClelland 2008-02-09 06:50:30 UTC
Just tested with F9 alpha i386 DVD askmethod and got this:

loader received SIGSEGV! Backtrace:
install exited abnormally [1/1]

Comment 11 David Cantrell 2008-02-09 08:41:27 UTC
Right, so that was a problem that creeped in to the alpha release of F-9.  If
you could try from the nightly rawhide builds, that would be good.  I have fixed
the problem you see above.

Comment 12 Mark McClelland 2008-02-09 09:57:06 UTC
With the boot.iso dated 08-Feb-2008 15:20:

loader received SIGSEGV! Backtrace:
install exited abnormally [1/1]

I don't know if the fix was supposed to be in that boot.iso already. I'll try
again tomorrow.

Comment 13 Mark McClelland 2008-02-18 01:18:28 UTC
I get basically the same backtrace with boot.iso dated 17-Feb-2008 12:43:

loader received SIGSEGV! Backtrace:
install exited abnormally [1/1]

Comment 14 A.J. Werkman 2008-03-26 21:00:13 UTC

Comment 15 Mark McClelland 2008-04-02 05:42:17 UTC
This bug is still present in F9 beta. The backtrace is virtually the same.

Comment 16 Charles R. Anderson 2008-04-04 03:32:03 UTC
Same crash from Comment #13 in F9 rawhide as of 2008-04-03.

Comment 17 Jon Stanley 2008-04-16 17:16:59 UTC
*** Bug 433290 has been marked as a duplicate of this bug. ***

Comment 18 David Cantrell 2008-04-22 03:11:02 UTC
Fought this bug today and won.  It is actually a libdhcp bug, so changing the components there.  Basically, 
in pumpSetupInterface(), it was not allowing a set of configuration data that only contained a single 
networking stack.  It assumed that every caller would be doing both IPv4 and IPv6.  I released a new 
version of libdhcp with the fix, libdhcp-1.99.8, so you can now do just IPv6 and completely disable IPv4.

There are also some cleanup patches I did for anaconda that are related to this bug, so there should be a 
rebuild there too.

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