mirror of
https://passt.top/passt
synced 2025-05-19 07:55:34 +02:00
test: Wait for DAD on DHCPv6 addresses
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@gibson.dropbear.id.au> Signed-off-by: Stefano Brivio <sbrivio@redhat.com>
This commit is contained in:
parent
75b9c0feb0
commit
53176ca91d
5 changed files with 11 additions and 0 deletions
test/perf
|
@ -116,6 +116,8 @@ iperf3k ns
|
|||
# Reducing MTU below 1280 deconfigures IPv6, get our address back
|
||||
guest dhclient -6 -x
|
||||
guest dhclient -6 __IFNAME__
|
||||
# Wait for DAD to complete
|
||||
guest while ip -j -6 addr show tentative | jq -e '.[].addr_info'; do sleep 0.1; done
|
||||
|
||||
tl TCP RR latency over IPv4: guest to host
|
||||
lat -
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue