On 06/08/2011 09:52 AM, Daniel P. Berrange wrote: > On Wed, Jun 08, 2011 at 09:42:22AM -0600, Trever L. Adams wrote: >> >> Would you care to share some documentation of some kind? >> >> <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. > Yes, when you add that <ip family='ipv6'> line and then > restart the network (virsh net-destroy TheCommons && virsh net-create TheCommons) > it should have started radvd automatically. The guest should then have automatically > got an address from radvd. This all works fine in my testing. Ok, I had rebooted the system to do this before. It did NOT work. Now, I just did the virsh and it worked. I also had my wlan0 come up without proper IPv6 when I rebooted even with IPV6INIT=yes in the file for it. So, even though I restart wlan0 from rc.local, I get this: Jun 8 14:56:00 HC kernel: [ 14.219624] ADDRCONF(NETDEV_UP): wlan0: link is not ready So, no IPv6 address. And radvd claims it isn't started and isn't running. After restarting from rc.local wlan0 has fe80, but not 2001 address assigned. However, virbr0 got it right this time. Thank you, Trever -- "One Woman can make you fly like an eagle Another can give you the strength of a lion But only One in the cycle of life can fill your heart with wonder And the wisdom that you have known a singular joy." -- Unknown
Attachment:
signature.asc
Description: OpenPGP digital signature
-- devel mailing list devel@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/devel
