Sasquatch wrote:As you say, it doesn't specify Windows Host for this. But, if the wireless interface doesn't work well with bridged, and VB uses it's fallback option, then it makes sense that IPv6 doesn't work. Since IPv6 uses auto-discover and auto-configure based on part of the interface MAC address, this can prevent proper configuration on the Guest when in bridged fallback method. This method means that VB will identify the Guest using the Host's MAC address to get network access, instead of using the Guest's own MAC address. Since the Host has an IPv6 address based on it's MAC, the Guest won't configure itself with that same IP to avoid conflicts.
I don't think that this is actually a problem. The guest will get its MAC from the virtual interface. And that interface specific guest MAC address will be used for autoconfiguration. The correct auto configured address is getting set in the guest OS and the packet makes it into the air with the correct IPv6 address. The problem is that the MAC address in the ethernet header get rewritten to the host wireless interface MAC address, and the neighbor announcement gets sent back not to the guest interface specific MAC address but to the host's wireless MAC address. VB picks up the packet and then should rewrite the correct guest iface MAC into the packet based upon the IPv6 address of the destination. VB doesn't do this yet, because the code hasn't yet been written to do this.
Have you tried assigning a static IPv6 address? I've never heard of requiring to configure the neighbour discovery on any OS other than the one providing the subnet and responds to auto-configure requests. And even there it's only configured to broadcast the subnet and routing information. Not much else to configure. IPv6 configures itself.
Indeed it does, and this works just fine. The problem is that VB does switching based upon IP address for wireless rather than the more normal switching based upon MAC address. The code for doing the switching for IPv6 has yet to be written.
I'm more than willing to help write it, but I don't have experience developing VirtualBox and don't currently have a way to build and test VB on my laptop.