| 3 | | The workaround suggestsed by shuckc, in fact, works. But I suspect that, technically, it's a wrong way to solve this issue (to manipulate with the metric of the interface). In my case (which seems to be the most common) the VirtualBox network does not have a gateway (the "Default gateway" property of the interface is empty). Therefore, this network interface must not influence routing of packets that do not directly belong to this private network. It doesn't matter whether metric of the interface is large of not. So, it seems to me, that this is a bug in Windows (in TCP/IP-driver and routing). And this must be fixed by Microsoft. (?) |
| | 3 | The workaround suggestsed by shuckc, in fact, works. But I suspect that, technically, it's a wrong way to solve this issue (to manipulate with the metric of the interface). In my case (which seems to be the most common) the VirtualBox network does not have a gateway (the "Default gateway" property of the interface is empty). Therefore, this network interface must not influence routing of packets that do not directly belong to this private network. It doesn't matter whether metric of the interface is large or not. So, it seems to me, this is a bug in Windows (in TCP/IP-driver and routing). And this must be fixed by Microsoft. (?) |
