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): kernel-2.6.19-1.2895.fc6.x86_64 How reproducible: Always. Steps to Reproduce: 1. Install kernel-2.6.19-1.2895.fc6.x86_64 2. Boot 3. Actual results: No public IPv6 address found on eth0. The link-local one is present (fe80::...) Expected results: A public IPv6 address should be active on eth0 Additional info: 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 2.6.19.2 (which I assumed has been merged into RH:s kernel) broke this. The fix has been posted to netdev: http://www.spinics.net/lists/netdev/msg22663.html 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?