Changes between Initial Version and Version 1 of Ticket #13656, comment 2
- Timestamp:
- Dec 8, 2014 3:17:26 PM (10 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Ticket #13656, comment 2
initial v1 47 47 }}} 48 48 49 After the above change and rebooting the host, the interface eth0 was not changed. 50 No need for the rc.local workaround. 49 After the above change and rebooting the host, the interface eth0 was not changed when vboxmanage is called. No need for the rc.local workaround. 51 50 52 Plus, not having vboxnet0 managed by NM I got an IP 192.168.56.1 after called vboxmanage and not only after a VM starts (a situation before).51 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). 53 52 54 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. 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 54 56 55 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.

