Bug 711879 - IPv6 not working as advertised
IPv6 not working as advertised
Status: CLOSED NOTABUG
Product: Fedora
Classification: Fedora
Component: libvirt (Show other bugs)
15
Unspecified Unspecified
unspecified Severity high
: ---
: ---
Assigned To: Daniel Veillard
Fedora Extras Quality Assurance
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2011-06-08 16:47 EDT by Trever Adams
Modified: 2011-06-08 17:06 EDT (History)
9 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2011-06-08 17:06:33 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Trever Adams 2011-06-08 16:47:43 EDT
Description of problem:

I have marked this urgent as this should be working and today is world IPv6 day.

My network is defined as follows:

<network>
  <name>TheCommons</name>
  <uuid>....</uuid>
  <forward mode='route'/>
  <bridge name='virbr0' stp='off' delay='0' />
  <ip address='10.0.1.1' netmask='255.255.255.0'>
  </ip>
  <ip family='ipv6' address='fd00:xxxx:xxxx:1::1' prefix='64'>
  </ip>
  <ip family='ipv6' address='2001:xxxx:xxxx:0::1' prefix='64'>
  </ip>
</network>

That didn't automatically add any of the ipv6 addresses. As I said, no
radvd. If I read the bug reports correctly, it is supposed to be automagic.

Looking at the systclts mentioned here:  https://bugzilla.redhat.com/show_bug.cgi?id=501934, the sysctls are set exactly as said they would be in that bug.

I see others on the mailing lists saying their configurations work, but they are all bridges to physical devices. So, the problem may be specifically to virtual bridge setups.


Version-Release number of selected component (if applicable):
libvirt-0.8.8-4.fc15.x86_64

Mentioned originally here: https://bugzilla.redhat.com/show_bug.cgi?id=514749
Comment 1 Trever Adams 2011-06-08 17:06:33 EDT
Sorry, on this reboot it started working.

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