Changes between Version 1 and Version 2 of Ticket #13656, comment 2
- Timestamp:
- Dec 8, 2014 3:24:22 PM (10 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Ticket #13656, comment 2
v1 v2 2 2 If I'm wrong and NetworkManager may control vboxnet then something needs to be set. 3 3 4 Summary of what was happening: 4 5 As per the host boot.log, my referenced workaround above in rc.local is invoked at 11:42. 5 6 At 11:42 vboxmanage is called and eth0 becomes 192.168.56.1 and it seems by NetworkManager. … … 29 30 I figure its okay NM to control other interfaces but not vboxnet. 30 31 32 Solution: 31 33 The best approach I've read is to leave NM manage all devices as above, and add NM_CONTROLLED=no to the ifcfg-vboxnet as exception t the controlled interfaces: 32 34 {{{ … … 51 53 Plus, not having vboxnet0 managed by NM this interface got the IP 192.168.56.1 after called vboxmanage and not only after a VM starts (a situation found before solution). 52 54 53 In summary , after I call vboxmanage, NM finds a new device called vboxnet and detached current eth0 ip with the one belonging to vboxnet0, breaking remote access to eth0 and leaving vboxnet without an IP. Kind of strange what it did.55 In summary what was happening IMHO, after I call vboxmanage, NM finds a new device called vboxnet and detached current eth0 ip with the one belonging to vboxnet0, breaking remote access to eth0 and leaving vboxnet without an IP. Kind of strange what it did. 54 56 55 57 I would appreciate a comment from development, because, I want to leave NM working and not allowing it to manage vboxnet. Letting me know if other approaches keeping NM working is known.
