Red Hat Bugzilla – Bug 223431
IPv6 autoconfigure does not work with kernel-2.6.19-1.2895.fc6.x86_64
Last modified: 2007-11-30 17:11:53 EST
Description of problem:
kernel-2.6.19-1.2895.fc6.x86_64 does not autoconfigure IPv6 at boot.
kernel-2.6.18-1.2869.fc6.x86_64 works ok.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Install kernel-2.6.19-1.2895.fc6.x86_64
No public IPv6 address found on eth0. The link-local one is present (fe80::...)
A public IPv6 address should be active on eth0
Running kernel-2.6.18-1.2869.fc6.x86_64 seems to be the best current workaround.
I've seen this as well - the router discoery message seems to be sent, and radvd
seems to reply with a router advertisment message but it seems tobe ignored and
no address is allocated.
I'm also having this exact same problem.
Apparently a fix in 184.108.40.206 (which I assumed has been merged into RH:s kernel)
broke this. The fix has been posted to netdev:
It would be nice if this could be included into the RPM in the near future.
Can the severity of this be changed to high? It should be at least 'high'
because this completely breaks almost any IPv6 LAN with FC 6 boxes on it.
Same problem hits me on an i686 kernel, not nice...
Fixed in pending update kernel, built yesterday, should go into testing today.
*** Bug 227989 has been marked as a duplicate of this bug. ***
*** Bug 225105 has been marked as a duplicate of this bug. ***
Today kernel-2.6.19-1.2911.fc6.x86_64 appeared on updates-testing. It fixes the
problem on my machine at least.
2911 fixes the problem on two i686 machines.
It works for me on my dual processor 2.6.19-1.2911.fc6 system.
25 days lag between noticing a problem with the IPv6 equivalent of DHCP and
having it fixed seems a little ridiculous to me. Should I simply not bother
with IPv6 on any of my networks since RedHat doesn't really want to support it?