Changes between Version 8 and Version 9 of Ticket #8698, comment 9

Ticket #8698, comment 9

v8	v9
1	1	I use VirtualBox 5.1.18 on Win7x64, and the problem persists there.
2	2
3		The workaround suggested above by shuckc, in fact, works. But I think 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, in other words, the line like
	3	The workaround suggested above by shuckc, in fact, works. But I think 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, in other words, the line like
4	4	{{{
5	5	224.0.0.0 240.0.0.0 On-link 192.168.56.1 656