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.
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.
NET=$(ip -6 route|egrep "^"|cut -d':' -f1-4)
EUI=$(ip -6 route|egrep "^default.*metric 1 "|cut -d':' -f3-6|cut -d' ' -f1)
ping6 $NET:$EUI -B -c 1 > /dev/null 2>&1
if [ $? -eq 0 ]; then
Users browsing this forum: Google [Bot] and 27 guests