Try this out for me...?
Joep L. Blom
jlblom at neuroweave.nl
Sun Aug 26 14:56:00 UTC 2012
On 26-08-12 12:18, Karl Auer wrote:
> Hi all.
> I have found that IPv6 does not seem function correctly for a VirtualBox
> VM bridged to a wireless interface, even when the wireless interface is
> working flawlessly for the host.
> Are you in an IPv6 network? Do you have VirtualBox installed? Do you
> normally communicate via wifi? If so, I'd greatly appreciate it if you
> could try this and let me know how you go (off list is fine, I'll
> - install a VM, OS is irrelevant as long as it supports IPv6
> - configure the VM network interface to be bridged to the host adapter
> (wlan0 or similar)
> - see whether you have fully functional IPv6 on the VM
> My experience is that I get weird partial functionality. I see
> autoconfigured addresses and so on, but no useful connectivity is
> possible - no pings, nothing. Neighbor discovery does not complete. And
> yes, I have checked that no firewalls or packet filters are in the way.
> The current suspects are my access point (an ancient Netgear, but the
> host works fine over wifi), the wifi driver in Linux (but the host works
> fine over wifi), and the VirtualBox network drivers (though they work
> fine when the VM is bridged to an ethernet adapter)...
> I've now seen this on 10.10 and 12.04, with two different wifi drivers
> and across two versions of VirtualBox.
> Regards, K.
I don't know if it will help you but you can try VMware and see if they
are a little more advanced as IPv6 actually should be the standard since
at least > 10 years. I must confess I also still work with IPv4 but
that's I am lazy and follow the majority.
More information about the ubuntu-users