Timeline for VirtualBox internal network with dhcp server
Current License: CC BY-SA 3.0
5 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Aug 31, 2016 at 18:50 | answer | added | Matt Borja | timeline score: 1 | |
| Aug 31, 2016 at 18:34 | comment | added | Matt Borja |
For those of you coming here because of the title and are actually experiencing this problem, you may notice it's caused by the --netname parameter not actually setting up a DHCP server properly, even though you specify it explicitly using the same name from within your VM's network configuration. I was basically unable to get a real DHCP service working with Internal Networking (intnet) using any other name besides intnet.
|
|
| Sep 30, 2015 at 7:36 | vote | accept | rodrunner | ||
| Sep 30, 2015 at 2:01 | answer | added | Isaac Hanson | timeline score: 4 | |
| Sep 29, 2015 at 21:47 | history | asked | rodrunner | CC BY-SA 3.0 |