-
Notifications
You must be signed in to change notification settings - Fork 498
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Can I set the DHCP lease time via vagrant-libvirt? #1792
Labels
Comments
its currently not implemented. I think it would be pretty straight forward to implement, the closest thing is to look at the old "bootp" related commits for what has to be changed: both the network generation code and the template must be adopted:
commit 80f8c6b comes pretty close to this. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Is your feature request related to a problem? Please describe.
TL;DR: Can I influence the DHCP leasetime for the network created by vagrant-libvirt?
When using vagrant-libvirt on e.g. a laptop, the VM's IP addresses might change if you put the laptop to sleep/suspend and wake it up again. Apparently, the DHCP lease time is only 1 hour, so after that the IPs might change.
In my case it is not possible to set static IPs, so I would like to increase the DHCP lease time to e.g. 24h or even 1 week.
Describe the solution you'd like
Apparently one can set lots of things on private networks, but not for the public network.
https://vagrant-libvirt.github.io/vagrant-libvirt/configuration.html#private-network-options
https://vagrant-libvirt.github.io/vagrant-libvirt/configuration.html#public-network-options
Although there are some DHCP-related options for private networks, there is nothing regarding the leasetime.
A sample Vagrantfile without the network options might look like this:
This results in a new network
vagrant-libvirt
being created whose xml looks like this:All it would need is one line inside the
<range>
according to the libvirt documentation.The text was updated successfully, but these errors were encountered: