VirtualBox

Changes between Version 4 and Version 5 of Ticket #8698, comment 9


Ignore:
Timestamp:
Apr 11, 2017 10:03:03 PM (7 years ago)
Author:
dele

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #8698, comment 9

    v4 v5  
    22
    33The workaround suggestsed above 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, in other words, the line like
    4 
     4{{{
    55224.0.0.0        240.0.0.0         On-link      192.168.56.1    656
    6 
     6}}}
    77in the route table (see above the message of shuckc) must not exist at all.
    88

© 2023 Oracle
ContactPrivacy policyTerms of Use