After running dhclient -6 we expect the DHCPv6
assigned address to be
immediately usable. That's true with the Fedora dhclient-script (and the
upstream ISC DHCP one), however it's not true with the Debian
dhclient-script. The Debian script can complete with the address still
in "tentative" state, and the address won't be usable until Duplicate
Address Detection (DAD) completes. That's arguably a bug in Debian (see
link below), but for the time being we need to work around it anyway.
We usually get away with this, because by the time we do anything where the
address matters, DAD has completed. However, it's not robust, so we should
explicitly wait for DAD to complete when we get an DHCPv6 address.
Link:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1085231
Signed-off-by: David Gibson <david(a)gibson.dropbear.id.au>
---
test/passt/dhcp | 2 ++
test/pasta/dhcp | 2 ++
test/two_guests/basic | 3 +++
What about the equivalent cases in passt_in_ns/dhcp and perf/passt_tcp?
--
Stefano