Try this out for me...?

[Karl Auer]

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
summarise).

- 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.


-- 
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Karl Auer (kauer at biplane.com.au)
http://www.biplane.com.au/kauer
http://www.biplane.com.au/blog

GPG fingerprint: AE1D 4868 6420 AD9A A698 5251 1699 7B78 4EEE 6017
Old fingerprint: DA41 51B1 1481 16E1 F7E2 B2E9 3007 14ED 5736 F687