Now I do not have machine for testing... But of course it is possible to test in VM too and it should be easy. Just create tun/tap interface for connection between VM and host. On host side start dnsmasq (which has support for RA & DHCPv6) and configure some non /64 prefix (e.g fd00::/100) [1]. And then check if NetworkManager in VM set correct /100 route (ip -6 route) and not some /64. Thats all.
[1] - example dnsmasq configuration (do not know if work, I just write what I remember): $ dnsmasq --enable-ra --dhcp-range=fd00::2,fd00::10,100,12h --interface=tun0 --except-interface=lo --listen-address=fd00::1 --bind-interfaces (host must have tun0 interface with ipv6 address fd00::1) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1254028 Title: [precise] network manager set incorrect /64 prefix from dhcpv6 client Status in NetworkManager: Fix Released Status in “network-manager” package in Ubuntu: Fix Released Status in “network-manager” source package in Precise: Fix Committed Status in “network-manager” source package in Quantal: Fix Released Status in “network-manager” source package in Raring: Fix Released Status in “network-manager” source package in Saucy: Fix Released Status in “network-manager” source package in Trusty: Fix Released Status in “network-manager” package in Debian: Confirmed Bug description: [Impact] * dhcpv6 sets an incorrect netmask on ipv6 networks, leading to probable communication failures in certain networks [Test Case] * You need an ipv6 network using dhcpv6 statefull configuration with prefix which is not equal to /64 [Regression Potential] * None, this patch has been accepted upstream and is available since quantal network-manager in ubuntu precise use incorrect /64 prefix from dhcpv6 client which cause that internet connection not working on some ipv6 networks. this problem was fixed in upstream network-manager version 0.9.6 which is already available in ubuntu quantal and newer - but not in ubuntu precise. because this is critical problem (non working network/internet) new version of network manager (e.g 0.9.6) or at least patch which fixing this problem should be included in ubuntu precise which is LTS. upstream commit which fixing this problem: http://cgit.freedesktop.org/NetworkManager/NetworkManager/commit/?id=eb460b70dad82d366d35fa5703c0e79a1389e4d1 more info about it: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=661885 http://bugzilla.gnome.org/show_bug.cgi?id=656610 To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager/+bug/1254028/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : [email protected] Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
