Bug#792894: Workaround for systemd units for dhcp server (addressing ipv4 and ipv6)

Hello, As mentioned in [0], isc-dhcp-server has failed state in Stretch (via systemd). /etc/init.d/isc-dhcp-server seems to be "buggy" on IPv6 part. With this settings in /etc/default/isc-dhcp-server : -- INTERFACES="MY_INTERFACE_NAME" INTERFACESv4="MY_INTERFACE_NAME" -- isc-dhcp-server

Bug#930367: cloud.debian.org: vagrant images: use systemd-networkd for virtualbox provider

Package: cloud.debian.org Severity: normal Dear Maintainer, I noticed a difference between providers for the same box (debian/stretch64): * with libvirt provider, `systemd-networkd` service is enabled and started after first boot of VM. * with virtualbox provider, `systemd-networkd` service

Bug#930645: Vagrant images debian/stretch64 9.9.1: same client ID for all VM

: ``` config.vm.box = "debian/stretch64" config.vm.box_version = "9.9.0" ``` ### Environment - libvirtd 4.0.0 or libvirtd 3.0.0 - vagrant-libvirt 0.0.45 - vagrant 2.2.4 - debian/stretch64 9.9.1 -- Nicolas Quiniou-Briand n...@inverse.ca :: +1.514.447.4918 *140 :: https://in

Bug#930367: cloud.debian.org: vagrant images: use systemd-networkd for virtualbox provider

Emmanuel, Just for a better understanding, if your patch is accepted in Buster, can you just tell me what will be the networking behavior for virtualbox boxes ? Thanks. -- Nicolas Quiniou-Briand Jabber/XMPP : n...@azyx.fr

Bug#931572: Vagrant box missing stable buster release

Hello, I got the same on my side. I was able to download libvirt box one or two days ago. -- Nicolas