NAT networking randomly won't give out IPs
Posted: 4. Jan 2021, 09:08
I have a VM running as a NAT network, with a few port forwards. This allows me to connect directly to the host IP but access the VM for the ports I've forwarded.
The VM was originally running CentOS 6.10 and I recently created a new VM and installed Debian 10 and migrated everything over. I setup the forwards on the new VM. (they never both run at same time) Normally, this works. However, I'd say about 1 out of 5 reboots, it will not work. There is no network. I need to restart the VM again, and this time it might work, but it's hit and miss. Basically I need to keep restarting it until it works.
Is there a way to make this more consistent so it works every time?
EDIT: I ended up just setting a static IP on the VM so I will see if that solves the issue, still early to tell, will need to test reboot a bunch of times to see. What is the default DHCP range for vbox? Just want to make sure I don't fall within it. I set the IP to 10.0.2.100. I don't plan to have many VMs on this machine so probably not a big deal either way.
The VM was originally running CentOS 6.10 and I recently created a new VM and installed Debian 10 and migrated everything over. I setup the forwards on the new VM. (they never both run at same time) Normally, this works. However, I'd say about 1 out of 5 reboots, it will not work. There is no network. I need to restart the VM again, and this time it might work, but it's hit and miss. Basically I need to keep restarting it until it works.
Is there a way to make this more consistent so it works every time?
EDIT: I ended up just setting a static IP on the VM so I will see if that solves the issue, still early to tell, will need to test reboot a bunch of times to see. What is the default DHCP range for vbox? Just want to make sure I don't fall within it. I set the IP to 10.0.2.100. I don't plan to have many VMs on this machine so probably not a big deal either way.