socratis wrote:Actually the issue of expired leases never came up.
That isn't how I read it.
sparko wrote:I think it's hardcoded 20 minutes in virtualbox DHCP, but after a much longer time after VM with some particular IP was deleted, it is still not assigned to the new VM so you end up stuck with no IP.
Note ">20 minutes after VM using IP was deleted", i.e. after lease expiry.
michaln wrote:Please check the public bug tracker and if there's no existing ticket open for this problem, create one. The forum is a very poor issue tracking tool.
As soon as it's settled that there is a bug to report, then that would indeed be the next step. But, AFAIK one purpose of the forums is to filter what ends up on BugTracker?
Then the action you are calling for has already been suggested.
mpack wrote:Yes it sounds like a bug, so I suggest raising a BugTracker ticket for the problem. The bug sounds trivial to me, if so it should be an easy fix to reuse IPs once the address space is exhausted, and/or increase the lease time.
Since you're at it, another thing to consider would be:
socratis wrote:VirtulBox DHCP server(s) to have a limited, settable, DHCP lease time. Instead of the hardcoded 20 min
Do NOT send me Personal Messages (PMs) for troubleshooting, they are simply deleted.
Do NOT reply with the "QUOTE" button, please use the "POST REPLY", at the bottom of the form.
If you obfuscate any information requested, I will obfuscate my response. These are virtual UUIDs, not real ones.